Xperia TA backup and Custom ROM compatibility questions. - Xperia Z5 Premium Q&A, Help & Troubleshooting

After becoming beyond frustrated with the WiFi disconnect issue and generally laggyness of my up to date but stock Z5p, I decided to once again venture into the Custom ROM space.
I am not new to phone customization, but all my previous devices, Oneplus One, Galaxy Note 2, and Galaxy Note, had markedly less complex procedures to accomplish rooting and installing custom recovery and ROMs.
So here is what I would like to accomplish.
Backup the TA partition.
Install TWRP
Install Custom ROM while keeping DRM functionality.
Root phone while maintaining Android Pay, and other SafetyNet app functionality
I am not sure how to go about this and in what order things need to be done. I have found a lot of conflicting information on XDA and in other web searches.
Here are the questions I have remaining.
How do I backup the TA partition?
When do I restore it?
Should I instead use a custom Kernel with DRM built in?
Do custom ROMs even recognize a restored TA partition?
How do I use Magisk or other method to maintain SafetyNet?
Thanks in advance for your help. Hope I was clear enough.

A. TA partition Backup and Restore
1. Pre-requisite: Go To XperiFirm and Download the latest firmware and firmware version 32.0.A.6.170 (Commercial and Journalists)
2. Download iovyroot https://forum.xda-developers.com/crossdevice-dev/sony/iovyroot-temp-root-tool-t3349597
3. All kinds of backup since from this point on any data inside your phone will be gone.
First use flashtool and flash 32.0.A.6.170 first. Make sure to make checkboxes on all lists under Wipe Sin and Misc TA before flashing. Once flash is finished, boot up your phone and get to the home screen.
From Home screen, go to Settings > About Phone > Tap Build Number 5 times to enable Developer Option. Settings > Developer Option > USB Debugging and connect your phone to the PC. Make sure to authorize USB access once the phone is connected.
Open iovyroot folder and simply run tabackup.bat file. Follow instruction and if successful, there should be a TA.img file created in that folder. This means your TA partition has been backed up.
If you want to restore it, use flashtool to lock the bootloader first. Then flash the same 32.0.A.6.170 right away. Once the flashing and rebooting phone is done, enable USB debugging as instructed above, press shift-right-click (in Windows 7) to open Command Prompt from here. If Win 8 or newer, Hit Windows key + X, open command prompt, get to the directory where the iovyroot (you know how to use DOS right?), and then run:
tarestore TA.img
and then follow instruction to restore the TA. Once this task is done, you can reboot or re-flash newer firmware to use the latest firmware with bootloader locked. Remember that iovyroot only works with the older firmware versions (if you check iovyroot xda thread, you can review what firmware version is compatible) So if you want to backup / restore TA, you MUST go back to older firmware to do it. This is my only proven case to successfully backup and restore TA, but if someone else has other solutions, feel free to respond below.
B. Install TWRP
1. Pre-requisite: Go to this thread: https://forum.xda-developers.com/z5-premium/development/safetynet-stock-kernel-twrp-magisk-t3621404 and download the TWRP there. This one is really straightforward that you could've done this without any problem.
How to boot to recovery partition? Simply hold power and low volume button from power off state (with no cable connected) until phone vibrates briefly once. Let it boot to TWRP.
What about that yellow light that comes on when you normally power on, and then you press the down volume key and the light turns orange and then boots TWRP? Well what happened on that one is the kernel developer modified boot.img such that it also has TWRP within the boot partition, making recovery partition not necessarily useless. I had cases where I can launch two different version of TWRP from a same phone.
If you want to stick with stock ROM or stockROM based custom ROM, you can use Zacharia's kernels, where his boot partition embeds the recovery partition, which would make accessing TWRP much easier.
C. Install Custom ROM while keeping DRM functionality
Zacharia's kernels are built with DRM patch. You can use his kernel on stock based ROMs for that. I believe Moonbreaker ROM comes with the kernel that has DRM patch so that shouldn't be a problem (Mind that moonbreaker is marshmallow).
Personally, what I do is stick with stock kernel and stock ROM with bootloader unlocked. Because I just have yet to found custom ROM that works with what I have set up on the next section:
D. Root phone while maintaining Android Pay, and any other SafetyNet app functionality
So starting from the phone state where bootloader is unlocked, have the latest 7.1.1 stock ROM with stock kernel, flashed TWRP as above...
1. Go to this thread: https://forum.xda-developers.com/z5-premium/development/safetynet-stock-kernel-twrp-magisk-t3621404
2. Follow instructions there. This is really straightforward.
3. Reboot and then basically you have a phone that is rooted as well as the phone passes SafetyNet.
Just to review the questions you have posted, other than backup and restore TA partition...
1. Watch out on selecting custom Kernels. EAS and Zacharia's kernels are based on Stock based ROMs, with specific firmware versions. EAS Version 3 only supports Firmware 2.33 (Nougat 7.0, which I personally have yet to make it booting on my phone...). Zacharia kernels have various versions-- You'll have to search through the list of all his postings and see which kernels are for what firmware versions.
2. When you are trying to use Stock based custom ROMs and/or kernels, make sure you flash the correct stock ROM version before. And let it boot the stock firmware fully before jumping into TWRP and flash the custom ROMs.
3. You "could" try to make custom ROMS to recognize a restored TA partition. There is a thread called "Rootkernel", where it fakes the system to think the bootloader is locked and it has proper TA partition. The program uses kernel and your TA partiton to build a modified kernel to do it. Here's the thread if you want to read it: https://forum.xda-developers.com/xp...oot-automatic-repack-stock-kernel-dm-t3301605 But I will let you study and figure this one out on your own. Personally I don't find this useful if you try it on non-stock based custom ROM (LineageOS for example). But again, if someone else has other ideas, do reply...
4. Magisk is like a systemless Supersu (yes I just defined that in a super lazy man's term). Initially there are no "SuperSU" related files in system partition. Only at a certain time in the system booting the Magisk extracts its files themselves out and start deploying system apps that needs root access. Basically having a virtual partition inside system partition, collection of system files that allows root access. Go to Magisk Manager, open settings, enable Magisk Hide. This is the module that will allow to hide Safetynet detection for some apps. When this module is active, and then you look at Magisk Hide in main menu of Magisk, you can then make checkboxes on what apps you want to hide. Android Pay should be checked already... I think you need to have stock firmware and provided kernel to get Magisk to work. But again, if anyone else says otherwise, I'm at all ears.

Related

[HOW-TO] Simplified Root + Recovery + Custom ROM

This is a simplified guide for those new to rooting & flashing a custom ROM on the Optimus V. No need to type complex commands that are hard to follow and prone to mistakes. Basically there are 3 main steps: Root, Install custom recovery, & flash custom ROM.
Windows Drivers for the Optimus V (Optional but suggested):
http://www.lg-phones.org/wp-content/uploads/LG-Optimus-V.zip
Rooting
Rooting is the process of gaining administrative rights to the phone so one can do customizations that aren't normally allowed. Root by itself doesn't do anything interesting, unless there's an app that needs it. The fancy stuff comes from custom ROMs. Just remember Virgin Mobile Activation only works on Froyo ROMs, so do it before going to Gingerbread. The easiest way to root nowadays is to use GingerBreak. It can be found here:
[26.04.2011][v1.2] GingerBreak APK (root for GingerBread) - xda-developers
Instruction Steps:
1. Turn on USB Debugging (Settings - Applications - Development)
2. Copy the GingerBreak.apk to a /sdcard dir, then using a 'file manager' app (search for one in Android Market) install it like a regular app.
3. It can take up to 10 minutes, and will reboot automatically when complete (rooted), if attempt fails, reboot manually & run it again.
Install custom recovery image
The recovery image is an alternative bootup instead of normal Android Operating System. It allows low-level operations such as backup/restore a ROM, wipe partitions, and flash ROMs.
4. Download and copy the recovery image VM670NH_recovery.img (works with new & old OV screens) onto your /sdcard.
5. Install the Flash Image GUI app (save the .apk to a /sdcard directory, then open it with file manager) Run the app & select 'Recovery Image' option with the file above.
Flash Custom ROM
I.H.O CyanogenMod 7 ROM (Gingerbread)
6. Copy the unextracted ROM .zip that you wish to install to the /sdcard dir. Also if installing a CyanogenMod Gingerbread ROM, the unextracted gapps.zip also needs to be placed in the same dir to flash right after the ROM .zip.
7. Boot into Clockworkmod recovery mode (From powered off state, hold vol-down, home, and power button until the LG logo appears).
8. FIRST, BACKUP ORIGINAL ROM! Don't continue until this is successful. Use vol-up/down, camera, & back keys to navigate in recovery.
9. Wipe Data/Factory Reset, wipe cache partition. Under Advanced submenu, wipe dalvik-cache. Then uner Mounts & Storage submenu, format all partitions EXCEPT /sdcard.
10. Flash the custom ROM.zip from sdcard and gapps.zip too if going to a CyanogenMod ROM
11. Reboot and enjoy the new ROM, the first boot takes longer than usual, also some problems may disappear after rebooting.
NOTES:
- NEVER use Android Settings 'Factory Reset' from now on, only do factory reset & wipes from within recovery mode. Most ROMs should have this option removed from the Android settings.
- Some newer Optimus V screens hardware changed, see link: [FIX]Black screen with custom recovery and custom roms (BobZHome's IHO recovery from the Wiki binary -> recovery page also works with newer screens.)
- If restoring a backed up ROM in CWM recovery gives 'MD5 mismatch' error (likely caused by renaming a ROM backup). Try this fix:
# cd /sdcard/clockworkmod/backup/<name_of_backup>
# rm nandroid.md5
# md5sum *img > nandroid.md5
- If you ever want to restore to original stock ROM (ONLY on OV's with older screen), with original recovery and UNrooted:
http://www.prepaidandroid.org/index...e_your_Optimus_V_to_almost_original_condition
titanium backup?
Excellent guide for the likes of me (noob), you might wanna mention titanium backup too
help
Hey u have a great step by step guide, however when I run gingerbreak to root it gives me an error I kno u said reboot manually and I did twice and I couldn't get it to work, any thoughts of to why it did this twice thanks
Zachary droid said:
Hey u have a great step by step guide, however when I run gingerbreak to root it gives me an error I kno u said reboot manually and I did twice and I couldn't get it to work, any thoughts of to why it did this twice thanks
Click to expand...
Click to collapse
What is the exact error you're getting? I believe you have to keep retrying, maybe up to 10 times.
Thanks a lot.Real helpful
Will this work for LG Optimus S? It's been difficult to find specific information for this phone.
Thanks.
KidGusto said:
Will this work for LG Optimus S? It's been difficult to find specific information for this phone.
Thanks.
Click to expand...
Click to collapse
the windows drivers and gingerbreak will work.
you'll need an optimus S custom recovery and rom, though. If you use optimus V software, your home and menu keys will be backwards, and there may be other little issues with the network.
look on android central forums for optimus S development and you'll find roms and recoveries no problem.
Thank you for this. The Rom manager method is great, i was afraid not to brick my optimus one with the adb shell crap and pc connection. They should make a nici sticky like this in the euro section, not with adb crap.
Can this guide by updated, with more details?
The menu options in ROM manager are not the same anymore, and I am flailing around trying to figure out which options to hit.
I'm stuck at the LG logo boot up screen after doing what I think is flashing the bumblebee ROM step. (step 10 in the guide).
I used these steps and they worked great for rooting, but I'm having a problem with recovery. I flashed CWM 3.2.0.1 from ROM Manager and it appeared to work fine, but when I try to boot into recovery I just get a blank screen.
I have done the following:
Busybox 1.19.2 from Stericson, installed to /system/bin
Superuser from market, updated to 2.3.6.3, su is 2.3.2-efgh
Used ROM Manager 4.4.0.7 to flash CWM recovery 3.2.0.1
I've tried getting to recovery using Home+Vol Dn+Power, or the reboot menu option in rom manager, and just get the blank screen.
Anyone run into this or have suggestions?
cobraextreme said:
I used these steps and they worked great for rooting, but I'm having a problem with recovery. I flashed CWM 3.2.0.1 from ROM Manager and it appeared to work fine, but when I try to boot into recovery I just get a blank screen.
I have done the following:
Busybox 1.19.2 from Stericson, installed to /system/bin
Superuser from market, updated to 2.3.6.3, su is 2.3.2-efgh
Used ROM Manager 4.4.0.7 to flash CWM recovery 3.2.0.1
I've tried getting to recovery using Home+Vol Dn+Power, or the reboot menu option in rom manager, and just get the blank screen.
Anyone run into this or have suggestions?
Click to expand...
Click to collapse
[fix]black screen in custom recovery or custom roms
you probably have the newer screen type, which it appears the older custom kernels need a .config setting changed before building to support.
you'll have to use flash_image in adb or terminal.
probably. full instructions and downloads at that link.
yay, you didn't flash a rom through rom manager at the same time! or it'd be a lot harder.
bigsupersquid said:
[fix]black screen in custom recovery or custom roms
you probably have the newer screen type, which it appears the older custom kernels need a .config setting changed before building to support.
you'll have to use flash_image in adb or terminal.
probably. full instructions and downloads at that link.
yay, you didn't flash a rom through rom manager at the same time! or it'd be a lot harder.
Click to expand...
Click to collapse
That did the trick! Thanks!
It would be great to get a sticky about this in here. It's pretty easy to miss the newer display issue if you're just now looking into this forum and don't check AC first.
cobraextreme said:
That did the trick! Thanks!
It would be great to get a sticky about this in here. It's pretty easy to miss the newer display issue if you're just now looking into this forum and don't check AC first.
Click to expand...
Click to collapse
Updated original post with link for the new OV screens.
lamenramen said:
Can this guide by updated, with more details?
The menu options in ROM manager are not the same anymore, and I am flailing around trying to figure out which options to hit.
I'm stuck at the LG logo boot up screen after doing what I think is flashing the bumblebee ROM step. (step 10 in the guide).
Click to expand...
Click to collapse
ROM Manager is only supposed to be use to flash the Clockworkmod recovery image, then everything else is done by booting into the recovery mode. ROM manager's other features should not be used on the OV.
Whyzor said:
Updated original post with link for the new OV screens.
...
Click to expand...
Click to collapse
the only big problem left is getting the "back to stock" up to par for the newer OV's...
if someone could upload the critical part of a nandroid made from the newer stock system after rooting but before installing a custom rom, a more up-to-date back to stock guide could be put up with the newer files, or at least the older files patched with the newer kernel.
anyone want to upload the boot.img from a first nandroid backup off of a newer ov? the boot.img doesn't have any personal info, and it's got the newer kernel, which is all that's needed to fix up the older back-to-stock nandroid files.
bigsupersquid said:
the only big problem left is getting the "back to stock" up to par for the newer OV's...
if someone could upload the critical part of a nandroid made from the newer stock system after rooting but before installing a custom rom, a more up-to-date back to stock guide could be put up with the newer files, or at least the older files patched with the newer kernel.
anyone want to upload the boot.img from a first nandroid backup off of a newer ov? the boot.img doesn't have any personal info, and it's got the newer kernel, which is all that's needed to fix up the older back-to-stock nandroid files.
Click to expand...
Click to collapse
I think there's about an 85% chance that this contains the kernel that you're looking for; not sure if you have some way to deal with that 15% uncertainty but hopefully it's helpful.
Questions about ROM Manager
Hi, can I get a clear clarification about installing the ROM Manager on my LG Optimus p500, when your about to install the ClockwordMod Recovery you would have to select the phone model. LG p500 is not listed. Is there an alternative to it?
luwizwiz said:
Hi, can I get a clear clarification about installing the ROM Manager on my LG Optimus p500, when your about to install the ClockwordMod Recovery you would have to select the phone model. LG p500 is not listed. Is there an alternative to it?
Click to expand...
Click to collapse
This thread is under the Optimus V development section, you should ask questions about the p500 in this forum section:
http://forum.xda-developers.com/forumdisplay.php?f=839
Thanks, i didn't notice that its for Optimus V, i have a Optimus One. many thanks
Complete noob here, I mean a complete noob...first cell phone.
I was hoping to tether my new OV, but i quickly found out i have software version 2.2.2 which does not allow me to turn on hot spots. So I heard I can root my phone to get around this. I did stes 1-3 without issue, now I am stuck on step 3a. When i try to install busybox (not sure what this does for me?), i get the follow error/message "It looks like you have Busybox installed, but there are multiple copies still installed. /system/bin/ is currently as RW. This means that something may have gone wrong in the installation process. Please verify on your end that everything is correctly installed and working.
What do I verify? There is no Busybox app to run, only to install so it looks like the install failed?
ct200 said:
Complete noob here, I mean a complete noob...first cell phone.
I was hoping to tether my new OV, but i quickly found out i have software version 2.2.2 which does not allow me to turn on hot spots. So I heard I can root my phone to get around this. I did stes 1-3 without issue, now I am stuck on step 3a. When i try to install busybox (not sure what this does for me?), i get the follow error/message "It looks like you have Busybox installed, but there are multiple copies still installed. /system/bin/ is currently as RW. This means that something may have gone wrong in the installation process. Please verify on your end that everything is correctly installed and working.
What do I verify? There is no Busybox app to run, only to install so it looks like the install failed?
Click to expand...
Click to collapse
If you go into 'adb shell' from the PC with phone connected, or open the app 'terminal emulator' to get a unix prompt, and type 'busybox', you should see a list of commands. If you get a no command found, then it's not installed. It's suggested to install so you can run unix commands, but not really needed. Root & custom recovery are the important ones. You're probably safe to continue, just make sure to make a backup in recovery mode before doing anything else.

[Q] Restore to Stock and Root Methods

Hi everyone.
I recently got a used Note 2. I've been doing a bit of reading in this section and just wanted to confirm a couple of things.
First off my phone's description:
Carrier: Sprint
Model Number: SPH-L900
Android Version: 4.3
Baseband Version: L900VPUBMK4
Kernel Version: 3.0.31-2106854 [email protected] #1 Mon Nov 11 20:33:03 KST 2013
Build Number: JSS15J.L900VPUBMK4
SE for Android Status: Enforcing SEPF_SPH-L900_4.3_0010
Hardware Version: L900.09
(1) Even though the phone came wiped of all previous data I would like to do a factory reset. Billard412's guide is mentioned several times. Is this the option to go with for my phone?
(2) The phone is not rooted at the moment. Should I use the CF-Auto Root method by Chainfire first and then proceed to install TWRP and then restore back to stock using Billard412's guide?
Thanks for your help in advance.
To start with you have the 100% KNOX on your phone so Billard412's back to stock will be the option you want to use.
You will need to download
TWRP recovery (recommended because billards zip works best with it)
Billards back to stock mc2 with counter reset
The root file located in billards thread
Prep steps
Backup everything you want from your internal sdcard (this will get wiped)
place billards rom and root files on your external sdcard
1. boot phone into download mode
2. use odin to flash twrp recovery (any version but 2.7) make sure you uncheck the reboot option in odin
3. once finished remove cable and battery
4. hold the recovery boot key sequence (vol up, home, and power keys) then insert battery (while holding keys)
5. once in recovery wipe everything
6. flash billards rom (do not wipe anything else after this step)
7. flash the root file
8. reboot and dont get worry when things get funky this is normal
9. the phone will take a bit to boot
10. now you have stock mc2 with root
11. install your recovery of choice (if flashing touchwiz 4.3 or aosp 4.4 roms use Philz 6.07.9) this can be done with odin or an image flashing app
12. now you can flash whatever rom you want
FYI -- when going from touchwiz 4.1x to 4.3 or aosp 4.4 you should format your internal sdcard. The newer roms use a different location for your internal sdcard and without proper formatting you will end up with issues (mostly random reboots and apps force closing) -- Same goes if you go from 4.3 TW/aosp 4.4 to 4.1x TW/4.3 or lower aosp
jlmancuso, thanks for the reply. Couple of things to clarify from your post:
- Regarding the Prep steps.
- I don't have anything on this phone yet so I don't think I need to back anything up. Even if if did the "Android system recovery <3e>" recovery menu does not have an option to back anything up
- Regarding using Odin to flash TWRP
- The 2.7 version to avoid is for TWRP correct? I went to TWRP's Sprint Note 2 page and I cannot seem to find a different version. Where should I get the version of TWRP that actually works?
- From the XDA page on Odin, which version should I use 3.09 or 1.85?
- All of the boxes must be unchecked including the reboot option? If not which ones need to be checked?
- I click on the "PDA" button to load the TWRP zip file correct?
- Regarding step 8:
- What do you mean "dont get worry when things get funky"? Funky as in the phone takes long to reboot or the screen flashes weird colors/patterns?
- Also, I came across Galaxy Note2 TOOLKIT V5.0.0 SPRINT thread. That one seems pretty easy to follow through. Would that option work for me given that I have the KNOX update?
Thanks again for your help.
Well, I've done a bit more reading into the Galaxy Note2 TOOLKIT V5.0.0 SPRINT thread and it seems that might be the way to go. Mark mentions the KNOX update in his changelog. I don't have the necessary posts to post a question in that thread so hopefully someone sees this that's familiar with that method. Does this method apply to a phone that has already undergone the KNOX update?
From what I can understand, Mark has made a recovery as well as a root tool. I bought this phone second hand so any warranty issues (e.g. flash counts, etc.) don't really apply to me. I'm just looking to get the phone to a clean state where I can start fresh and then add TWRP and Root. As far as the version of TWRP, Billard412 says (in post #604) that "Version of twrp doesn't matter as far as I know."
My second question is, using the Unified Toolkit, will i be able to restore my phone to stock and then root it with the least amount of problems?
roofus1218 said:
Well, I've done a bit more reading into the Galaxy Note2 TOOLKIT V5.0.0 SPRINT thread and it seems that might be the way to go. Mark mentions the KNOX update in his changelog. I don't have the necessary posts to post a question in that thread so hopefully someone sees this that's familiar with that method. Does this method apply to a phone that has already undergone the KNOX update?
From what I can understand, Mark has made a recovery as well as a root tool. I bought this phone second hand so any warranty issues (e.g. flash counts, etc.) don't really apply to me. I'm just looking to get the phone to a clean state where I can start fresh and then add TWRP and Root. As far as the version of TWRP, Billard412 says (in post #604) that "Version of twrp doesn't matter as far as I know."
My second question is, using the Unified Toolkit, will i be able to restore my phone to stock and then root it with the least amount of problems?
Click to expand...
Click to collapse
I belive your best option is billard412s thread. You are correct with your Odin steps. Flash TWRP and follow thread you should be golden
Awesome thanks a bunch!

[Q] z1 comact stuck

i try to root me z1 compact (i have unlocked the bootloader) but i forget to save th superuser zip into sd card....i wwant in fastboot mode and i didn t innstall the zip.........and now i am stuck on fastboot mode...and i haven t do backup..what can i do ?plz help
Could you use an external SD card reader and plug to your PC to copy the file you need? then reinsert into your phone.
how?
mkhairym said:
Could you use an external SD card reader and plug to your PC to copy the file you need? then reinsert into your phone.[/QUOTE
man i copy the supersu in the sd card but when i choose zip i press update superSU and it writes ......done
and when i prees reboot system now it gets me into recovery mode again
Click to expand...
Click to collapse
thanos kary said:
mkhairym said:
Could you use an external SD card reader and plug to your PC to copy the file you need? then reinsert into your phone.[/QUOTE
man i copy the supersu in the sd card but when i choose zip i press update superSU and it writes ......done
and when i prees reboot system now it gets me into recovery mode again
Click to expand...
Click to collapse
well a bit more info would help, like on what rom you were on, and what steps you followed? At least you're able to boot into recovery, which lets you flash other roms since you've unlocked the BL
Click to expand...
Click to collapse
listen
darkmystel said:
thanos kary said:
well a bit more info would help, like on what rom you were on, and what steps you followed? At least you're able to boot into recovery, which lets you flash other roms since you've unlocked the BL
Click to expand...
Click to collapse
listen ...i haven t done buckup and i haven t flash my rom......my phone can get in to the recovery mode ONLY....can i get out from the recovery mode ?:crying:
Click to expand...
Click to collapse
Well if you have access to your recovery you should be able to mount your SD card there and then connect it to your PC. From there you can transfer a zip file to your phone and flash it.
I don't see anything mentioned about which custom recovery he flashed.
Could this be a stock recovery that he is in? (that may not allow mounting etc.)
.....
LaZiODROID said:
I don't see anything mentioned about which custom recovery he flashed.
Could this be a stock recovery that he is in? (that may not allow mounting etc.)[/QUOTE
i have done this....... and then what? i have 4.4.4 android
This is a CWM-Based Recovery 6.0.4.6 Touch Recovery for Xperia Z1 Compact!
Credits and special thanks to Koush and everyone else involved in Cyanogenmod project!
[ info ]
This Recovery is built from CWM 6.0.4.6 sources!
I dont have this device with me and I dont intend to buy one... my friend wanted root on his phone so I created this to help him out...
all the testing was done remotely on users devices...
[ PROOF ]
[ credits / special thanks ]
Koush - for the brilliant work & coding on CWM recovery
CyanogenMod and FreeXperia Team (especially jerpelea) for too many things *
special thanks to @swedan for helping out with testing and risking his devices for the sake of development!!! and NO, his phone was NOT damaged during testing
ME for creating this for u guys!
[ Requirements ]
Bootloader unlocked
working fastboot
STOCK ROM FW:
4.4.2
14.3.A.0.757 - v04
14.3.A.0.681 - v03
4.3
14.2.A.1.142 - v02
14.2.A.1.114 - v01
or ROMS BASED ON THAT FIRMWARE
[ features ]
standard CWM recovery 6.0.4.6 - TOUCH RECOVERY!
kernel is insecure (ro.secure=0)
adb debugging is enabled by default in OS
TIP: if u are experiencing very slow backup in CWM do this
[ WARNING ]
for flashing this kernel you WILL NEED TO UNLOCK BOOTLOADER! Check this thread for more info (same steps as Xperia Z1 are used for Xperia Z1 Compact)
UNLOCKING BOOTLOADER WITHOUT TA BACKUP WILL LEAD TO IRREVERSIBLE LOSS OF DRM KEYS!!!
AND YES CAMERA STILL WORKS AFTER UNLOCKING BOOTLOADER!!!
[ known issues ]
adb is not working in recovery (can be fixed later)
[ how to flash this kernel ] (via fastboot)
download the kernel image
save the boot.img to the folder containing fastboot binary
flash the boot.img using fastboot:
Code:
fastboot flash boot boot.img
reboot from fastboot
Code:
fastboot reboot
the device should now start booting
enjoy!
Click to expand...
Click to collapse
....
darkmystel said:
thanos kary said:
well a bit more info would help, like on what rom you were on, and what steps you followed? At least you're able to boot into recovery, which lets you flash other roms since you've unlocked the BL
Click to expand...
Click to collapse
yes i get into recovery and then what i must do?
Click to expand...
Click to collapse
thanos kary said:
darkmystel said:
yes i get into recovery and then what i must do?
Click to expand...
Click to collapse
I think a little more studying should have been done before flashing things. Now that we know you can get into CWM Recovery, you can flash a custom ROM. Note that doing so will involve wiping your data/cache/system - so whatever apps you were using on your phone will be gone (along with the data for each app, like your preferences etc.)
And since your bootloader is unlocked, you can flash pretty much any ROM you like because the unlocked bootloader allows custom kernels to be flashed.
As an example, you can flash SlimKat. It is a custom ROM with a custom kernel. The page is here: http://forum.xda-developers.com/showthread.php?t=2700456. You can find the download links in post #3. There will be a ZIP file for the ROM, and then optionally, another ZIP for the Google Apps (aka GAPPS), which would allow you to sign in to your Google account, use Play Store, etc. SlimKat offers 3 gapps (which I will link here because the GAPPS link on that thread seems to take me to a login page): They have mini, normal, and full. Take your pick..
http://www.slimroms.net/index.php/downloads/dlsearch/viewcategory/1150-addons4-4
Once you've downloaded them, copy the Slimkat ZIP to your external SD card. Also copy the GAPPS zip that you chose (if you wanted that).
Put the external card back into the phone and power it up, and get back into recovery like you did earlier. In recovery, before flashing the zips, you should do your wipes (this is where it wipes your apps/data/system). But as a precaution, maybe go into "install zip from sdcard", navigate through your external card to make sure the ZIP files are available to you.
I think that most ROM install zips take care of these wipes for you, but it's a good habit to get into when flashing custom ROMs.
You're going to:
1) Wipe data/factory reset (this will wipe the data and cache)
2) Go into Advanced and wipe Dalvik cache
3) Go into Mounts and Storage and format /system
Once that's done, you're going to go to "install zip from sdcard", choose your external card, and choose the SlimKat ZIP. That will flash the ROM and kernel. Once that's done, you're going to do one more flash - which is the GAPPS zip (if you decided that you wanted it).
Once that flash is done, you should be able to just reboot and the phone will start to boot into the new ROM. Note that on first boot, it will take some time - so you may be staring at the boot animation for a few minutes.
Click to expand...
Click to collapse
root?
LaZiODROID said:
thanos kary said:
I think a little more studying should have been done before flashing things. Now that we know you can get into CWM Recovery, you can flash a custom ROM. Note that doing so will involve wiping your data/cache/system - so whatever apps you were using on your phone will be gone (along with the data for each app, like your preferences etc.)
And since your bootloader is unlocked, you can flash pretty much any ROM you like because the unlocked bootloader allows custom kernels to be flashed.
As an example, you can flash SlimKat. It is a custom ROM with a custom kernel. The page is here: http://forum.xda-developers.com/showthread.php?t=2700456. You can find the download links in post #3. There will be a ZIP file for the ROM, and then optionally, another ZIP for the Google Apps (aka GAPPS), which would allow you to sign in to your Google account, use Play Store, etc. SlimKat offers 3 gapps (which I will link here because the GAPPS link on that thread seems to take me to a login page): They have mini, normal, and full. Take your pick..
http://www.slimroms.net/index.php/downloads/dlsearch/viewcategory/1150-addons4-4
Once you've downloaded them, copy the Slimkat ZIP to your external SD card. Also copy the GAPPS zip that you chose (if you wanted that).
Put the external card back into the phone and power it up, and get back into recovery like you did earlier. In recovery, before flashing the zips, you should do your wipes (this is where it wipes your apps/data/system). But as a precaution, maybe go into "install zip from sdcard", navigate through your external card to make sure the ZIP files are available to you.
I think that most ROM install zips take care of these wipes for you, but it's a good habit to get into when flashing custom ROMs.
You're going to:
1) Wipe data/factory reset (this will wipe the data and cache)
2) Go into Advanced and wipe Dalvik cache
3) Go into Mounts and Storage and format /system
Once that's done, you're going to go to "install zip from sdcard", choose your external card, and choose the SlimKat ZIP. That will flash the ROM and kernel. Once that's done, you're going to do one more flash - which is the GAPPS zip (if you decided that you wanted it).
Once that flash is done, you should be able to just reboot and the phone will start to boot into the new ROM. Note that on first boot, it will take some time - so you may be staring at the boot animation for a few minutes.
Click to expand...
Click to collapse
man i haven t done root yet.....i have 4.4.4 android can you give instructios? and slimkat it is not support my z1 compact
Click to expand...
Click to collapse
thanos kary said:
man i haven t done root yet.....i have 4.4.4 android can you give instructios? and slimkat it is not support my z1 compact
Click to expand...
Click to collapse
When you say you want to root, it means that you want to root the current system that you are on. But from what you have described in this thread, you are currently having a problem with your phone, where it does not boot normally into the system/ROM. You boot straight into Clockworkmod Recovery, every time. Correct? If this is correct, then rooting your current ROM probably won't help your situation (because you are not able to boot normally into the system).
Slimkat is a ROM that has root access included. I believe that pretty much any custom rom has root included. I'm not sure what you mean when you say that slimkat does not support your Z1 compact. You should be able to flash Slimkat to your Z1 Compact. The link from my previous post points to the Slimkat thread, which is in the Z1 Compact Original Android Development forum, so it is made for Z1 Compact.
That said, you don't need to choose Slimkat - I provided that just as an example of a custom rom that has a custom kernel included. Look through the Xperia Z1 Compact Original Android Development forum for custom roms that use custom kernels. Most of those roms have the custom kernel included in their ZIP. Whichever custom rom you choose, make sure to READ the original post (and other posts if necessary) to get the information you need on how to install it, or to find out what files you will need for that ROM (as some roms have add-ons and stuff you may find interesting).
There are also ROMs that are stock-based. Those can be found in the Xperia Z1 Compact Android Development forum. These roms also have root included, and are built to run on the standard stock Sony kernel. Some of them may be based on a specific stock Sony kernel version, so pay attention to that.
If you want to start over, and flash a pure stock Sony ROM to your phone (also known as an FTF), you can do that at any time by downloading an appropriate FTF for your phone, and flashing it by loading the FTF with FlashTool. It will then ask you to put your phone into FlashMode (which is done by making sure the phone is OFF, then holding the VolDown button, and connecting the USB cable while still holding the VolDown button. Once the flash begins, you can let go of the VolDown button) But !! Please note that if you haven't used FlashTool before, you will need to install some drivers. They are included with FlashTool, in a folder called Drivers. You would choose the driver specific to your phone, plus the FlashMode driver, plus the Fastboot driver. If you are using Windows8, you will have to do some extra work to get those drivers to install correctly. It involves booting Win8 into a mode where Driver Signature Enforcement is disabled, then installing the drivers found in the drivers folder of FlashTool. You can easily find out how to do that by searching online.
Hope this helps... don't make any risky flashing moves if you aren't certain about them - just keep reading and searching and you will eventually find the answers you need.
zoom out
LaZiODROID said:
When you say you want to root, it means that you want to root the current system that you are on. But from what you have described in this thread, you are currently having a problem with your phone, where it does not boot normally into the system/ROM. You boot straight into Clockworkmod Recovery, every time. Correct? If this is correct, then rooting your current ROM probably won't help your situation (because you are not able to boot normally into the system).
Slimkat is a ROM that has root access included. I believe that pretty much any custom rom has root included. I'm not sure what you mean when you say that slimkat does not support your Z1 compact. You should be able to flash Slimkat to your Z1 Compact. The link from my previous post points to the Slimkat thread, which is in the Z1 Compact Original Android Development forum, so it is made for Z1 Compact.
That said, you don't need to choose Slimkat - I provided that just as an example of a custom rom that has a custom kernel included. Look through the Xperia Z1 Compact Original Android Development forum for custom roms that use custom kernels. Most of those roms have the custom kernel included in their ZIP. Whichever custom rom you choose, make sure to READ the original post (and other posts if necessary) to get the information you need on how to install it, or to find out what files you will need for that ROM (as some roms have add-ons and stuff you may find interesting).
There are also ROMs that are stock-based. Those can be found in the Xperia Z1 Compact Android Development forum. These roms also have root included, and are built to run on the standard stock Sony kernel. Some of them may be based on a specific stock Sony kernel version, so pay attention to that.
If you want to start over, and flash a pure stock Sony ROM to your phone (also known as an FTF), you can do that at any time by downloading an appropriate FTF for your phone, and flashing it by loading the FTF with FlashTool. It will then ask you to put your phone into FlashMode (which is done by making sure the phone is OFF, then holding the VolDown button, and connecting the USB cable while still holding the VolDown button. Once the flash begins, you can let go of the VolDown button) But !! Please note that if you haven't used FlashTool before, you will need to install some drivers. They are included with FlashTool, in a folder called Drivers. You would choose the driver specific to your phone, plus the FlashMode driver, plus the Fastboot driver. If you are using Windows8, you will have to do some extra work to get those drivers to install correctly. It involves booting Win8 into a mode where Driver Signature Enforcement is disabled, then installing the drivers found in the drivers folder of FlashTool. You can easily find out how to do that by searching online.
Hope this helps... don't make any risky flashing moves if you aren't certain about them - just keep reading and searching and you will eventually find the answers you need.
Click to expand...
Click to collapse
ooooohhh man i love you ,....it works with slimkat....thank you ...thank you...but i don t like this rom ..tell me if you know......how to get back to the officil from sony?
and if you can give a guide to root 4.4 android z1c
thanos kary said:
ooooohhh man i love you ,....it works with slimkat....thank you ...thank you...but i don t like this rom ..tell me if you know......how to get back to the officil from sony?
and if you can give a guide to root 4.4 android z1c
Click to expand...
Click to collapse
You could try to flash Kitslim (http://forum.xda-developers.com/showthread.php?t=2743177)
It is a slightly optimized rom based on the original Sony stock rom.
I use it and ist awesome. You have the stock feeling with this.
.....
Schlengge said:
You could try to flash Kitslim (http://forum.xda-developers.com/showthread.php?t=2743177)
It is a slightly optimized rom based on the original Sony stock rom.
I use it and ist awesome. You have the stock feeling with this.
Click to expand...
Click to collapse
i will flash this rom...but first i want to go in official rom and then i will root the rom
how to root?
thanos kary said:
i will flash this rom...but first i want to go in official rom and then i will root the rom
Click to expand...
Click to collapse
can anyone tell me how to root....i can not root with easy towel root

[Q] Newbie Help Needed! Z1C - Internal Data Recovery

Hi,
Up until this time yesterday I thought I was relatively tech savy... Unfortunately the last 24 hours have proved otherwise!
I received the notification from Sony PC Companion to update to Lollipop, and without thinking about backing up 4 months worth of pictures / videos of my baby son, went ahead...
Unfortunately the update failed, and I was left with a phone in bootloop mode... and the only solution I found was to use Sony PC Companion to 'repair' it (which installed Lollipop), unaware that this would wipe the internal memory including all of said baby photos / videos. I haven't dared tell my wife yet, and have been up all night trying to find a way to recover the data....
Totally unfamiliar with the concept of bootloaders, rooting, etc... I investigated some recovery software options, assuming they would work in the same way as normal hard drives. It would appear that is the case, but in order to access the internal memory I've opened up (ie. confused) my brain with the more technical side of the Android OS. I've tried and failed to root the phone, as that seems to be the fundamental requirement of the various data recovery programs.
Enough of the summary, here are a few basic questions...
1. Can I root the Z1C in its current state? It's running Lollipop, bootloader unlocked (as far as I'm aware), USB debugging mode enabled, etc... If so, and I understand this is a basic question for this forum, but can someone please explain how? I've tried numerous tutorials and am totally lost...
2. If I can't root the phone as is, am I right to assume I need to downgrade the OS to KitKat or similar? Again, can someone please explain, step by step what is required...
3. Is there a simpler way to recover the internal data, or am I at least in the right ball park?
I really appreciate any help you guys can offer...
Thanks,
Tim
You can try this http://forum.xda-developers.com/son...-5-0-242-r3d-customized-ru-1279-3901-t3081309 , others have succeeded, i for some reason didn´t. But yes, go back to .107, root and then install pre-rooted Lollipop.
1. Can I root the Z1C in its current state? It's running Lollipop, bootloader unlocked (as far as I'm aware), USB debugging mode enabled, etc... If so, and I understand this is a basic question for this forum, but can someone please explain how? I've tried numerous tutorials and am totally lost...
Click to expand...
Click to collapse
With unlocked bootloader u can always root any rom. Just install your favourite Stock ROM. I recommend a FTF File that you can flash with flashtool.
Then flash the FTF / ROM and after that, the Kernel with CWM Recovery like this:
http://forum.xda-developers.com/showthread.php?t=2620794
--> Working Kernel for KitKat 4.44 also for Lollipop 5.02:
Advance Stock Kernel with Recovery v04 (FW:14.3.A.0.757}
Click to expand...
Click to collapse
Now download the latest SuperSU ZIP form here: http://forum.xda-developers.com/showthread.php?t=1538053 and copy that to your SD card.
Finally restart your phone, press vol down when LED appears at bootup and flash SuperSu ZIP. --> now you are rooted.
You can also flash the latest dual recovery ZIP, if you want to return to original Stock Kernel:
To get the original Kernel of your Stock ROM back, use flashtool, select again the FTF file and uncheck all "Wipe settings" and also exclude all "flash settings" except the "KERNEL". Flash it and you are done.
3. Is there a simpler way to recover the internal data, or am I at least in the right ball park?
Click to expand...
Click to collapse
Be aware of installing anything on your internal storage.
You can try to recover your files using this:
https://play.google.com/store/apps/details?id=com.defianttech.diskdigger&hl=de
nataS555 said:
You can try this http://forum.xda-developers.com/son...-5-0-242-r3d-customized-ru-1279-3901-t3081309 , others have succeeded, i for some reason didn´t. But yes, go back to .107, root and then install pre-rooted Lollipop.
Click to expand...
Click to collapse
Thanks for the advice and link. To be honest, even the instructions on that thread are beyond me at the moment... I know it's very basic for you guys, but can you please explain these steps in more detail:
- wipe system, data, cache, davik (all)
- flash this zip
What are the different FTF options listed below the main instructions? Firmware, Kernel Only and Without System?
Thanks,
Tim
aikon96 said:
With unlocked bootloader u can always root any rom. Just install your favourite Stock ROM. I recommend a FTF File that you can flash with flashtool.
Then flash the FTF / ROM and after that, the Kernel with CWM Recovery like this:
http://forum.xda-developers.com/showthread.php?t=2620794
--> Working Kernel for KitKat 4.44 also for Lollipop 5.02:
Now download the latest SuperSU ZIP form here: http://forum.xda-developers.com/showthread.php?t=1538053 and copy that to your SD card.
Finally restart your phone, press vol down when LED appears at bootup and flash SuperSu ZIP. --> now you are rooted.
You can also flash the latest dual recovery ZIP, if you want to return to original Stock Kernel:
To get the original Kernel of your Stock ROM back, use flashtool, select again the FTF file and uncheck all "Wipe settings" and also exclude all "flash settings" except the "KERNEL". Flash it and you are done.
Be aware of installing anything on your internal storage.
You can try to recover your files using this:
https://play.google.com/store/apps/details?id=com.defianttech.diskdigger&hl=de
Click to expand...
Click to collapse
Thanks for breaking it down for me! Really appreciate the time and effort. Will give this a whirl after work today.
Tim

Rooting Help for a Complete Beginner

PLEASE DO NOT FOLLOW MY INSTRUCTIONS. I DO NOT KNOW WHAT I AM DOING.
Basically, I am a complete noob wanting to root my device - using Sony Xperia XZ2 Compact Dual (H8324, build 52.0.A.8.107, so that's Android 9)[1]. I'm hoping someone can check if what I'm doing is correct and answer a few questions, as I am much confused. I appreciate your help. Hopefully, this can help other people like me who want to get into rooting.
I've been reading a lot on this website and other websites, and I think I have a basic idea of what I am supposed to do, but I've been reading some info and I do not know what is outdated and am being overwhelmed.
Before all else, I should have adb and fastboot from the 'android-tools' package (installed from pamac-manager on Linux, but there are other ways to get it for other OS's)[2]. Also, connect device to PC.
First, I need to unlock the bootloader, which can be done using two methods[3]:
1. Using adb/fastboot by running these commands:
Code:
adb reboot bootloader
fastboot oem unlock-go
OR
2. Following Sony's guide on https://developer.sony.com/develop/open-devices/get-started/unlock-bootloader/
Then, I need TWRP, which, officially, does not support the XZ2C, so I need a custom one, like MartinX3's (https://forum.xda-developers.com/xp...recovery-twrp-3-2-2-0-touch-recovery-t3821597)[4], for example:
Download 'Sony Xperia XZ2 Compact/android_9/twrp/custom_rom/2019-07-12_12-15-30_twrp_sodp_xz2c.tar.gz'[4] (which is the latest version as of me writing this).
Extract the archive
Open a terminal in the same directory[5]:
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot boot twrp.img
In TWRP menu on the device, open Advanced Menu, "Install recovery ramdisk" using twrp.img
Finally, I need to install a root manager, Magisk, for example (https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445).
Download 'Latest Stable' (*.zip)
Download MagistManager from the GitHub link (*.apk)
Place the files somewhere on the device through the PC (Downloads folder, for example)
Boot into recovery (which will open TWRP(?))
Install the *.zip
Boot normally and install the *.apk
At this point, I should have a rooted Sony Xperia XZ2 Compact Dual?
Process related questions:
[1] Does build number matter when rooting? Or is it just the Android version?
[2] Are there any specific Sony drivers I need to install on my Linux PC, or is 'android-tools' enough?
[3] Does the method of unlocking the bootloader matter? Which is best for a beginner? Also, when doing the adb/fastboot method, should the device be connected in recovery mode before-hand?
[4] So, over here I am downloading the TWRP for the normal Sony Xperia XZ2 Compact, not the Dual SIM one. Does that matter? I do use the two SIM slots.
[5] Again, when doing these commands, should I be in recovery mode before-hand?
Other questions:
I've been reading a lot about the DRM thing and breaking some functionality, including the camera. Is that still a problem on Android 9? I heard it's mostly not. What am I loosing from unlocking the bootloader on Android 9?
I like to keep my device updated for the security patches. I read that I cannot do that through the device with root, but I have to flash it from my PC each time. Does anyone have a guide for Linux users? Do I loose root? Where do I even download the updates from?
Also, should I keep TWRP and Magisk updated for security and stability? How do I do that?
Thank you for reading this relatively long post, and I appreciate your help.
About the rooting, follow my twrp thread after unlocking in the newest PIE firmware.
With PIE you loose sony backup&restore, OTA, maybe Bluetooth ps4 controller, the login into the Sony club (I think) and maybe low light night antinoise algorithms (I think).
You can also switch to one of the custom ROMs. Existenze is stock and gives you at least an OTA notification.
Or omnirom and sonyaosp, based on SODP, a rewrite of the hardware drivers in an aosp compatible way. (Camera is work in progress).
For stock upgrades you need xperifirm, newflasher and removing the userdata.sin (if you don't want a full wipe)
MartinX3 said:
About the rooting, follow my twrp thread after unlocking in the newest PIE firmware.
With PIE you loose sony backup&restore, OTA, maybe Bluetooth ps4 controller, the login into the Sony club (I think) and maybe low light night antinoise algorithms (I think).
You can also switch to one of the custom ROMs. Existenze is stock and gives you at least an OTA notification.
Or omnirom and sonyaosp, based on SODP, a rewrite of the hardware drivers in an aosp compatible way. (Camera is work in progress).
For stock upgrades you need xperifirm, newflasher and removing the userdata.sin (if you don't want a full wipe)
Click to expand...
Click to collapse
Ok. I think I get.
First I unlock bootloader.
Flash latest stock firmware (which I can download from XperiFirm).
Flash TWRP and Magsik.
Finally, use the eXistenZ Pie patch.
Thank you very much.
But before I go ahead and follow through, I have a few more questions:
Does re-flashing the latest stock firmware mean I will lose personal data stored on the device (like call/chat history for example)?
Also, in the eXistenZ Pie patch, it says it is based on 52.0.A.8.83, but latest firmware is 52.0.A.8.107. Does that matter?
Finally, I will only get the OTA notification, but I will need to follow the process again to update (flash latest firmware from XperiFirm, --> flash TWRP and Magisk, --> eXistenZ patch)?
Again, thank you.
Edit: I almost forgot. Installing TWRP for H8314 on H8324 (Dual SIM) is ok, right? I won't lose that functionality?
orapyt said:
Ok. I think I get.
First I unlock bootloader.
Flash latest stock firmware (which I can download from XperiFirm).
Flash TWRP and Magsik.
Finally, use the eXistenZ Pie patch.
Thank you very much.
But before I go ahead and follow through, I have a few more questions:
Does re-flashing the latest stock firmware mean I will lose personal data stored on the device (like call/chat history for example)?
Also, in the eXistenZ Pie patch, it says it is based on 52.0.A.8.83, but latest firmware is 52.0.A.8.107. Does that matter?
Finally, I will only get the OTA notification, but I will need to follow the process again to update (flash latest firmware from XperiFirm, --> flash TWRP and Magisk, --> eXistenZ patch)?
Again, thank you.
Edit: I almost forgot. Installing TWRP for H8314 on H8324 (Dual SIM) is ok, right? I won't lose that functionality?
Click to expand...
Click to collapse
First flash newest firmware and boot it once, then unlock please
And yes, dual/single is the same twrp.
Existence V9 for 107 comes soon. Yes, sou should wait
MartinX3 said:
First flash newest firmware and boot it once, then unlock please
And yes, dual/single is the same twrp.
Existence V9 for 107 comes soon. Yes, sou should wait
Click to expand...
Click to collapse
I think I understand the process completely now. Thank you for your help.
About the OTA notification: I will get the notification for update from Sony but I will have to wait for the eXistenZ Pie patch to update first, right?
orapyt said:
I think I understand the process completely now. Thank you for your help.
About the OTA notification: I will get the notification for update from Sony but I will have to wait for the eXistenZ Pie patch to update first, right?
Click to expand...
Click to collapse
Yes. Just update to 107, wait for v9 and with existence you'll get the august notification
MartinX3 said:
Yes. Just update to 107, wait for v9 and with existence you'll get the august notification
Click to expand...
Click to collapse
Oh, sorry. My question was not clear enough. I feel bad for wasting your time.
I mean like each time I update I have to re-flash latest stock firmware and start from beginning, losing all data? I cannot update from the UI in the device?
Also, while I wait for v9 (I am on 52.0.A.8.107), can I unlock bootloader now, flash TWRP and Magisk in order to make a backup using Titanium Backup?
orapyt said:
Oh, sorry. My question was not clear enough. I feel bad for wasting your time.
I mean like each time I update I have to re-flash latest stock firmware and start from beginning, losing all data? I cannot update from the UI in the device?
Also, while I wait for v9 (I am on 52.0.A.8.107), can I unlock bootloader now, flash TWRP and Magisk in order to make a backup using Titanium Backup?
Click to expand...
Click to collapse
No problemo, I'm a recognized XDA slave hihi
Oh, just remove userdata.sin all the time before using newflasher and no userdata will be lost
As backup tool I can recommend migrate and titanium backup
Titanium backup makes a backup of each app and can restore it
Migrate makes a big flashable twrp zip.
(Make sure removing the app cache to reduce the backups size)
MartinX3 said:
No problemo, I'm a recognized XDA slave hihi
Oh, just remove userdata.sin all the time before using newflasher and no userdata will be lost
As backup tool I can recommend migrate and titanium backup
Titanium backup makes a backup of each app and can restore it
Migrate makes a big flashable twrp zip.
(Make sure removing the app cache to reduce the backups size)
Click to expand...
Click to collapse
lol
'userdata_X-FLASH-CUST-B6B5.sin' from the firmware folder?
orapyt said:
lol
'userdata_X-FLASH-CUST-B6B5.sin' from the firmware folder?
Click to expand...
Click to collapse
Correct
MartinX3 said:
Correct
Click to expand...
Click to collapse
Thank you. :good:
Is there a way for people like me to contribute to this amazing community?
orapyt said:
Thank you. :good:
Is there a way for people like me to contribute to this amazing community?
Click to expand...
Click to collapse
Yeah, provide ROMs for the xperia Rama devices or be a developer/tester.
Andjoin our Sony slack
And follow the big SODP link I put in all my project pages
Just to give closure to this: I did get eXistenZ on my Sony XZ2C Dual on build 52.0.A.8.107, and here is what I did exactly (could act as a guide, but please read completely before doing anything and I'm not responsible for any losses before, during, or after the process).
Prerequisites:
adb/fastboot (through package manager for Linux ('android-tools') or here for Windows)
mono (required only for Linux, through package manager)
Drivers (only required for Windows--install them from device manager when you have device turned on normally, and then again after you reboot into bootloader, as Windows detects it as a different device)
XperiaFirm
Newflasher
Steps:
I. Flashing the latest firmware:
Use XperiaFirm to get latest stock firmware with your customization (run with mono on Linux)
Delete userdata{somethingsomething}.sin from the firmware folder created by XperiaFirm
Place Newflasher into the folder
Shut-off phone
Hold volume-down button and plug in phone to computer to enter recovery mode
Run Newflasher and enter 'n' when prompted
Just wait until everything finishes (no data should be deleted).
II. Unlocking the bootloader:
Before you do, understand that you are voiding your warranty. Also it has some side-effects:
MartinX3 said:
With PIE you loose sony backup&restore, OTA, maybe Bluetooth ps4 controller, the login into the Sony club (I think) and maybe low light night antinoise algorithms (I think).
Click to expand...
Click to collapse
Get the unlock code for your device here.
Enable USB debugging from developer menu
Plug in phone to computer
Connect to fastboot:
Code:
adb reboot bootloader
Enter unlock code:
Code:
fastboot oem unlock 0x<insert your unlock code>
Wait for device to boot again (For me data was deleted. Also, don't mind the "can't check for corruption"; it's a side-effect of unlocking the bootloader)
III. Installing TWRP:
Get TWRP for XZ2
From the "Download," navigate to "Xperia XZ2 Compact/android_9/twrp/stock/" and download latest one
Extract, and open terminal in the extracted folder as a working directory
Plug in phone
Copy twrp{sometingsomething}.img to phone somewhere
Boot into TWRP:
Code:
adb reboot bootloader
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot boot twrp{somethingsomething}.img
Enter pin if prompted
Go to Advanced, Install recovery ramdisk, and pick the copied twrp image (this will install twrp to recovery mode, so you just shutdown phone, hold volume-down button and power, wait for vibration, and let go to enter TWRP)
IV. Flashing other stuff (Magisk, permissive):
Copy Magisk .apk and .zip, and permissive .zip from the twrp .tar.gz downloaded above to your phone somewhere
Enter installed TWRP by going into recovery mode (shutdown phone, hold volume-down button and power, wait for vibration, and let go)
Go to install, pick the Magisk .zip, and slide to install
Reboot into system and install the Magisk .apk to make sure it's working (do not update Magisk as it may be unsupported; only use the version provided in the twrp .tar.gz)
Boot back into TWRP and install permissive the same way Magisk .zip was installed
Reboot into system and launch Magisk manager, go to modules to check if permissive is working
V. Installing eXistenZ:
Download the version for your firmware version
Place the .zip somewhere on your phone
Boot into TWRP (shutdown phone, hold volume-down button and power, wait for vibration, and let go)
Got to wipe, advanced, and selected only Data and Dalvik/ART Cache
Now install eXistenZ .zip like installing the Magisk .zip
Reboot into system
??? (takes a long time)
Profit!! (for me data was deleted, so I had to reinstall Magisk and permissive)
Notes:
You probably want to backup your data.
Personally, I used UK customization firmware because that is what my phone shipped with.
Some guides say remove the *.ta files from the firmware folder, but I did not and it worked fine??
For some reason, all fastboot commands return "FAILED (command write failed (Success))" on Linux (fastboot version 9.0.0_r41) for me, but worked on Windows??
If you get 'error getting bootctrl module,' in TWRP you might need to mount something... forgot what exactly (might be OEM)??
Edit 1: Added drivers for Windows

Categories

Resources