Related
Installing the new Sony Bootloader and Recovery
THIS IS FOR ALREADY UNLOCKED DEVICES!
DO NOT TRY THIS ON A GPE!Since a lot of people seem to have problems keeping their recovery when flashing Lollipop-ROMs i decided to put up this little guide...
You can also Skip this whole guide, by just flashing the newest stock-FW at least once!
First off, as already said, this is for already unlocked devices. You can use this Guide until "Install Custom ROM", except the rooting part, for rooting use this, if you haven't already!
Don't do it if you don't atleast somewhat know what you are doing.
I am not responsible for bricked devices, or whatever you might end up with.
So, lets get started.
1. Download Sonys FlashTool "EMMA" and install it: http://developer.sonymobile.com/downloads/tool/flash-tool-for-xperia-devices/
In the .zip file from the FlashTool you'll find a File "customization.ini"
Copy this file to the installation directory of EMMA, usually "C:\Program Files (x86)\Sony Mobile\Emma"
If you don't copy that file, Emma will ask you for a login, don't create an account there, you will NEVER get any activation-email!
2. Open EMMA and boot your Phone into FlashMode (Power off your device -> Press and hold volume DOWN -> while pressing volume DOWN insert USB-Cable)
3. Emma should now recognize your device, but you have to select it manually tough. Select your EXACT model number. Again, I am not responsible for any bricked devices or whatever you end up with!
Now select the "(Open Devices) TA update" and click "Apply Service"
It should take a few seconds and should then display SUCCESS.
You can now close Emma
4. If you haven't already download FastBoot and Drivers: http://forum.xda-developers.com/showthread.php?p=48915118#post48915118
(Run as Administrator!)
5. Download the newest version of twrp and put it somewhere:
New Inoffcial twrp-3.0.0 build by me: http://forum.xda-developers.com/xperia-z-ultra/development/togari-twrp-recovery-3-0-0-t3314440
Old official versions: https://twrp.me/devices/sonyxperiazultra.html
6. Finally boot up you Phone in FastBoot-mode (Power off -> press and hold volume UP -> while pressing wolume UP insert USB-Cable
Your LED should now light up blue
Shift+Rightklick in the Folder where you have put TWRP recovery, and select "Open Commandprompt here"
Now write "fastboot flash recovery FILENAME_OF_TWRP_FILE"
You can now unplug your USB-Cable and boot into recovery and continue from there.
Your recovery will be permanent, meaning you won't loose it or replace with any other recovery that might come with your ROM.
I hope this was somewhat helpfull
Any one can flash this to C6806?
jacklau2000 said:
Any one can flash this to C6806?
Click to expand...
Click to collapse
You can try, just select your modelnumber in emma
If the "Open Devices (TA Update)" show up, you're fine. If not just don't do anything.
But do not try this on a GPE!
alia5 said:
You can try, just select your modelnumber in emma
If the "Open Devices (TA Update)" show up, you're fine. If not just don't do anything.
But do not try this on a GPE!
Click to expand...
Click to collapse
tried, but no luck. thanks.
It's really weird, I used emma, and installed their latest ta update. Now I can get into fastboot mode, all commands execute successfully, but the recovery never takes. The vol down + Power doesn't work, nor does 'adb reboot recovery'. Am I missing a step somewhere? This isn't my first android device, but from where I sit, it seems like something is up with my xzu.
If I try and install the 14.4* update through emma, it goes through the whole process, completes "successfully", then boots into 14.5. Something is clearly not working here.
The TA update only unlocks the ability to boot to recovery, it doesn't install one. And no, flashing official TWRP to recovery partition doesn't work, it must be compiled again to work on normal recovery partition and not in FOTAKernel, where it must be flashed to work.
Regards
teddy74eva said:
The TA update only unlocks the ability to boot to recovery, it doesn't install one. And no, flashing official TWRP to recovery partition doesn't work, it must be compiled again to work on normal recovery partition and not in FOTAKernel, where it must be flashed to work.
Regards
Click to expand...
Click to collapse
I´m on CM 11 M12 (looking forward to 12) + the new sony bootloader without any custom Kernel stuff.
Sadly, you are right. It´s not done with downloading twrp-2.8.5.0-togari.img and fastboot flash recovery yourfile.img.
The last offical TWRP release for Xperia Z Ultra is from february 2015, any chance they release an updated version for the new Sony bootloader?
Hermann1222 said:
I´m on CM 11 M12 (looking forward to 12) + the new sony bootloader without any custom Kernel stuff.
Sadly, you are right. It´s not done with downloading twrp-2.8.5.0-togari.img and fastboot flash recovery yourfile.img.
The last offical TWRP release for Xperia Z Ultra is from february 2015, any chance they release an updated version for the new Sony bootloader?
Click to expand...
Click to collapse
I will try to compile one because, you know, summer holidays and no school however I don't know if I will make it.
Regards
Is there any (wish for TWRP) recovery for togari, which use the new bootoader?
FYI:
My device is a brazilian c6843.
Emma recognizes the device automatically and indicates with an exclamation point that there is no services available to the unit.
In the case someone doesn't know, it's basically the c6833 with DTV 1seg. It's totally compatible with c6833 firmware, losing TV, of course.
You sir are the real hero! Thank you!
I have a xzu running cm12.1, and I have 2 quick questions for those with more knowledge than me
Is it possible to flash the new bootloder using the open source FlashTool?
If I have to use emma, is it possible to just apply the open device ta update *without* installing stock firmware first?
pbgapski said:
If I have to use emma, is it possible to just apply the open device ta update *without* installing stock firmware first?
Click to expand...
Click to collapse
You can totally do that, BUT, the newest stock firmware also has some firmware updates regarding nfc, also having the newest stock rom flashed at least once will be kind of a requirement to get everything properly working on marshmallow roms.
So I would say flash the newest stock rom at least once!
missing clues on new recovery partition
alia5 said:
You can totally do that, BUT, the newest stock firmware also has some firmware updates regarding nfc, also having the newest stock rom flashed at least once will be kind of a requirement to get everything properly working on marshmallow roms.
So I would say flash the newest stock rom at least once!
Click to expand...
Click to collapse
I followed your advice, but it seems I am missing a few clues.
My sirius was on cm12.1. I backedup and flashed D6543_23.4.A.1.232_1281-5466_R6C.ftf with flashtool on linux. I tried to use emma (several times) afterwards to check for any TA updates, but all I got was "no services matched this device" or something like that. Google tells me I am not the only one with this issue with emma
Then I used fastboot to install twrp 3 from twrp.me to recovery partition, but I could not access twrp.
I fastbooted recovery again with twrp 2.8.7, and this time I could enter twrp and reflashed CM.
Now I can access twrp using the button combinations while booting, but rebooting to recovery from CM leads to a bootloop. Has anyone experienced this as well?
So it seems I am still missing a few clues to using the recovery partition. Is any build of twrp supposed to work on both FOTAkernel and recovery partitions?
Is there a TWRP 3 build that works from 'coldboot to recovery' and 'cm reboot to recovery' with the new bootloader? Any pointers?
pbgapski said:
Now I can access twrp using the button combinations while booting, but rebooting to recovery from CM leads to a bootloop. Has anyone experienced this as well?
So it seems I am still missing a few clues to using the recovery partition. Is any build of twrp supposed to work on both FOTAkernel and recovery partitions?
Is there a TWRP 3 build that works from 'coldboot to recovery' and 'cm reboot to recovery' with the new bootloader? Any pointers?
Click to expand...
Click to collapse
Well, booting to recovery on separate partition from os, requires the rom to have a patch... the "new" mm-roms (when they finally hit aka. are ready to be shared in public) will have that, so no worry, just wait.
why it said my phone have no available service, i am on c6833
alia5 said:
Well, booting to recovery on separate partition from os, requires the rom to have a patch... the "new" mm-roms (when they finally hit aka. are ready to be shared in public) will have that, so no worry, just wait.
Click to expand...
Click to collapse
I have the same problem but not bootloop just stuck at starting apps screen,BTW did you have a TWRP scripts for flashing TWRP 3.0 into FOTAkernel
hi .. after this update can i relock my phone and restore drm functions?! or phone go to unlocked forever?!
pls help i need answer
erfanzz said:
pls help i need answer
Click to expand...
Click to collapse
Search the forums on how to backup TA partitions. I have mine but never tried to restore them
Hi someone can give MI guide to root my xperia z5c android 5.1.1 E5823 firmware 32.0.a.6.200 please? Tank to the helpers
N22121991 said:
Hi someone can give MI guide to root my xperia z5c android 5.1.1 E5823 firmware 32.0.a.6.200 please? Tank to the helpers
Click to expand...
Click to collapse
Enable developer options first in your phone, followed to enable OEM unlock and enable USB debugging.
Search on google there is a Sony official site to let you input your IMEI and get the unlock key. You'll need to use fastboot(search on google if you don't know what is it) to unlock via command prompt in Windows, a factory reset will perform after unlocked.
Kernel: http://forum.xda-developers.com/z5-compact/orig-development/kernel-zombie-t3224735
Recovery: http://forum.xda-developers.com/z5-compact/orig-development/twrp-z5-compact-t3235161 (you only need the recovery.img from it)
And then, you just need to "fastboot flash boot boot.img" and "fastboot flash recovery recovery.img" in command prompt to flash custom kernel and custom recovery.
https://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip
At last, "fastboot boot recovery.img" to flash the flashablesu.zip in recovery and install any of busybox utility via Playstore. Upgrade to camera 2.0 via "What's new" if you will install xposed bcoz stock cam 1.0 will FC.
Pretty much that's all of it.
hello
Thanks
Does it work with encrypted device ?
Bear in mind that if you unlock bootloader, your camera will worsen, you will lose image enhancements like x reality and your warranty will be void. Etc. Etc. So you might want to hold off on root. Just letting you know, that is
Sadman Khan said:
Bear in mind that if you unlock bootloader, your camera will worsen, you will lose image enhancements like x reality and your warranty will be void. Etc. Etc. So you might want to hold off on root. Just letting you know, that is
Click to expand...
Click to collapse
i don't totally agree because what i did,well,unlock device's bootloader & everything blah blah blah..but camera seems to be just fine.but of course,you'd definitely can see the difference..now since drm restore for our devices is already available however,it indeed restored the functions and the bravia engine & all(except the drm key itself),i noticed that my rooting status has changed from "unlock bootloader allowed: yes" to unlock bootloader allowed: no"!also,even if says so,my phone still has twrp installed,rooted & a custom kernel..all seems to be working as i so far observed..just that rooting status thing changed..kinda wierd,though!
Arturiuz! said:
i don't totally agree because what i did,well,unlock device's bootloader & everything blah blah blah..but camera seems to be just fine.but of course,you'd definitely can see the difference..now since drm restore for our devices is already available however,it indeed restored the functions and the bravia engine & all(except the drm key itself),i noticed that my rooting status has changed from "unlock bootloader allowed: yes" to unlock bootloader allowed: no"!also,even if says so,my phone still has twrp installed,rooted & a custom kernel..all seems to be working as i so far observed..just that rooting status thing changed..kinda wierd,though!
Click to expand...
Click to collapse
Mine says the same "unlock bootloader allowed: no" but root and everything works fine, and the camera definitely improved although its still crap in my opinion. Have a couple of before and after shots if someone is interested.
Radeon1337 said:
Mine says the same "unlock bootloader allowed: no" but root and everything works fine, and the camera definitely improved although its still crap in my opinion. Have a couple of before and after shots if someone is interested.
Click to expand...
Click to collapse
wait!let me correct myself a little(this is really weird!)..my drm keys are restored,to wc as far as i am knowledgable of,that shouldnt be the case after unlocking the BL..
*apologies here!im still trying to figure out how to insert a screenshot as a proof!i'm just using my phone atm..peace!
Arturiuz! said:
wait!let me correct myself a little(this is really weird!)..my drm keys are restored,to wc as far as i am knowledgable of,that shouldnt be the case after unlocking the BL..
*apologies here!im still trying to figure out how to insert a screenshot as a proof!i'm just using my phone atm..peace!
Click to expand...
Click to collapse
got it!here's for the screenshot before i unlocked my device..then drm keys lost..then when flashed the drmrestore.zip,consecutively..
MystereT said:
hello
Thanks
Does it work with encrypted device ?
Click to expand...
Click to collapse
Did you ever take the plunge with encryption? TWRP supposedly supports encryption, but want to make sure I have a way to a working phone if encryption doesn't work.
Don't remember if I can undo encryption via twrp, or at that point is it just prudent to flashtool it back to a clean image if not? My understanding is really just need to get a kernel on there that will boot, and provide the rest of the system with or without encryption.
Ready to pull the trigger on this to root and try with my encryption, but think I'll pull down a clean version of .200 firmware for the z5c first...
Yesterday there is a way to get Z5/Z5C/Z5P Rec & Root
and revive DRM & BE2 & Camera noise reduction by one-click (need unlocked BL),
I'm afraid to try...
Works like a charm
I can confirm drm-restore patch works like a charm and everything (camera noise reduction etc.)
iMaeGoo said:
Yesterday there is a way to get Z5/Z5C/Z5P Rec & Root
and revive DRM & BE2 & Camera noise reduction by one-click (need unlocked BL),
I'm afraid to try...
Click to expand...
Click to collapse
TheEndHK said:
Enable developer options first in your phone, followed to enable OEM unlock and enable USB debugging.
Search on google there is a Sony official site to let you input your IMEI and get the unlock key. You'll need to use fastboot(search on google if you don't know what is it) to unlock via command prompt in Windows, a factory reset will perform after unlocked.
Kernel: http://forum.xda-developers.com/z5-compact/orig-development/kernel-zombie-t3224735
Recovery: http://forum.xda-developers.com/z5-compact/orig-development/twrp-z5-compact-t3235161 (you only need the recovery.img from it)
And then, you just need to "fastboot flash boot boot.img" and "fastboot flash recovery recovery.img" in command prompt to flash custom kernel and custom recovery.
https://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip
At last, "fastboot boot recovery.img" to flash the flashablesu.zip in recovery and install any of busybox utility via Playstore. Upgrade to camera 2.0 via "What's new" if you will install xposed bcoz stock cam 1.0 will FC.
Pretty much that's all of it.
Click to expand...
Click to collapse
hi Bro! is there any trouble if i flash (obviously via fastboot) only the recovery over the stock kernel firmware .200?? or is mandatory flash kernel and recovery?
thanks!
acabreram said:
hi Bro! is there any trouble if i flash (obviously via fastboot) only the recovery over the stock kernel firmware .200?? or is mandatory flash kernel and recovery?
thanks!
Click to expand...
Click to collapse
Stock kernel will get a bootloop if you rooted. The current build of Z5c kernel got dm-verity, when it detect your /system has changed like flashed flashablesu.zip to attempt to root probably it will not boot. You need a custom insecure kernel to root.
TheEndHK said:
Stock kernel will get a bootloop if you rooted. The current build of Z5c kernel got dm-verity, when it detect your /system has changed like flashed flashablesu.zip to attempt to root probably it will not boot. You need a custom insecure kernel to root.
Click to expand...
Click to collapse
ok Bro thanks!! there is not custom kernel of firmware .200 yet right?
acabreram said:
ok Bro thanks!! there is not custom kernel of firmware .200 yet right?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=64849573&postcount=2
plz read it clearly
can someone share stock E5823 fw .200 kernel, I need it to test this method
Help
TheEndHK said:
Enable developer options first in your phone, followed to enable OEM unlock and enable USB debugging.
Search on google there is a Sony official site to let you input your IMEI and get the unlock key. You'll need to use fastboot(search on google if you don't know what is it) to unlock via command prompt in Windows, a factory reset will perform after unlocked.
Kernel: http://forum.xda-developers.com/z5-compact/orig-development/kernel-zombie-t3224735
Recovery: http://forum.xda-developers.com/z5-compact/orig-development/twrp-z5-compact-t3235161 (you only need the recovery.img from it)
And then, you just need to "fastboot flash boot boot.img" and "fastboot flash recovery recovery.img" in command prompt to flash custom kernel and custom recovery.
https://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip
At last, "fastboot boot recovery.img" to flash the flashablesu.zip in recovery and install any of busybox utility via Playstore. Upgrade to camera 2.0 via "What's new" if you will install xposed bcoz stock cam 1.0 will FC.
Pretty much that's all of it.
Click to expand...
Click to collapse
Hello, tks by the step by step u did... Sorry by my poor english, i am braziliam and need little help here.
1 - My z5c already is unlocked;
2 - I download the zombie kernel like u said (ok, get the boot.img file);
3 - I try to download the recovery, but when open the 7zip on windows cannot unzip the recovery.img file;
4 - Try to download this one (TWRP for Z5C) and ok, i get the recovery.img file from this (this is the same recovery file ???).
So the questoin is:
I can flash this files above (boot and recovery) on my z5c - E5823 - 32.0.A.6.200 ????
And why not flash the boot.img from the recovery zip file ??? Whats the diference ???
Regards and tks again !!!
puiatmp said:
Hello, tks by the step by step u did... Sorry by my poor english, i am braziliam and need little help here.
1 - My z5c already is unlocked;
2 - I download the zombie kernel like u said (ok, get the boot.img file);
3 - I try to download the recovery, but when open the 7zip on windows cannot unzip the recovery.img file;
4 - Try to download this one (TWRP for Z5C) and ok, i get the recovery.img file from this (this is the same recovery file ???).
So the questoin is:
I can flash this files above (boot and recovery) on my z5c - E5823 - 32.0.A.6.200 ????
And why not flash the boot.img from the recovery zip file ??? Whats the diference ???
Regards and tks again !!!
Click to expand...
Click to collapse
because it's only meant to be flashed in/by fastboot mode through command prompt or cmd.flashing it using recovery won't install those img's..not unless those were re/packed that could also be flashed through recovery..i've tried it but gave me error. & it's better that way installing it through command prompt/fastboot mode.
Arturiuz! said:
because it's only meant to be flashed in/by fastboot mode through command prompt or cmd.flashing it using recovery won't install those img's..not unless those were re/packed that could also be flashed through recovery..i've tried it but gave me error. & it's better that way installing it through command prompt/fastboot mode.
Click to expand...
Click to collapse
hey friend, tks for response.
I know we need to use fastboot to flash this files and i know how to do this.
I only wanna know if the files are compatible with my model and version device.
puiatmp said:
hey friend, tks for response.
I know we need to use fastboot to flash this files and i know how to do this.
I only wanna know if the files are compatible with my model and version device.
Click to expand...
Click to collapse
yes! it's(actually)for E5823 devices to be specific & as per OP(even as i have checked the links)..it even worked on mine wc is E5803! might want try it out first & see for yourself!
So the OFFICIAL 6.0.1 is already out and this is not the BETA version. It's for consumer release.
So how do you get to this eh?
NOTES: Flashtool can be used for both LB/UB. You won't lose DRM keys or unlock bootloader if you flash via flashtool.
1. Install Flashtool (get it here: http://www.flashtool.net/downloads.php).
2. There is a XperiFirm option there which would allow you to download official FTF files.
3. Navigate your way to Z3 Compact and grab the D5803 version US Variant (since this is configured for GLOBAL-LTE but i might still need to test bands). Or just grab anything you want there as long as it's version: 23.5.A.0.570
3. Flash using flashmode (hit the lightning icon there).
Now there's this "WIPE" Box, you have 2 options!
- Check User data and App logs and hit flash -- this will factory reset phone so you better have a backup!
- Leave them UNCHECKED if you want to retain your apps from your previous STOCK ROM. (might automatically uninstall incompatible apps in the process).
Once it asks for your device to be connected. Do as it says (power down, then hold the vol. down button as you plug the phone in).
-- this should start flashing.
4. After the process you may now boot the phone and there you have it!
-- Things below require unlocked BL --
If you want root, you can use fastboot and TWRP 3.X (I've tested the TWRP version 3.0.2 on the 6.0.1 beta before)
send this command on fastboot:
Code:
fastboot flash recovery <your twrp img here>
and hit enter. It must return 'OKAY'.
Unplug phone then boot into recovery and flash your SuperSU.zip
https://download.chainfire.eu/924/SuperSU/BETA-SuperSU-v2.68-20160228150503.zip
MINE!
Give a link to proper TWRP image please
tRippinthehead said:
Give a link to proper TWRP image please
Click to expand...
Click to collapse
If you have a locked BL, then root and install DualRecovery. There is an excellent thread here on XDA and you'll be on TWRP in no time. It also makes sure you'll have the drivers and flash tool and everything that you'll need for this already configured and ready to go.
If you have an unlocked BL, just go find TWRP and flash through fastboot.
Thanks OP!
P.S. I'm guessing for those with locked BLs, we can use PRFCreator and that FTF from Xperifirm to create a flashable, pre-rooted MM ROM...anyone tried? My Z3c is currently bricked (hopefully fixable) so I can't test at the moment.
Another DEV published a root method, both for the LB and UB:
http://forum.xda-developers.com/z3/general/wip-sony-android-6-0-mm-t3337357/page1
Keep in mind that that method was used for the BETA version of the rom, but yeah it's more likely that it would work with the consumer release. I'll update the OP once I relock my BL and successfully gain root with it.
The UB method there has the same effect as mine
I could not get root with the method, i would get boot img failure on flashing superSU in twrp with unlocked BL but to solve the issue i just flashed the advanced kernel for 6.0.1 and superSU flashed fine..not sure if anyone else is having this problem but this method did not work for me.
Do I keep root with locked bootloader with this method ?
Title of this topic is confusing, it seems that you need BL unlocked to get root.
hayatesan said:
Do I keep root with locked bootloader with this method ?
Title of this topic is confusing, it seems that you need BL unlocked to get root.
Click to expand...
Click to collapse
No you will lose root if you flash ftf on locked BL, you will need to root again using whichever method you used previously. If you flash an ftf file on ANY bootloader locked or unlocked it resets your phone to the contents of the ftf file.
Fictional Reality said:
No you will lose root if you flash ftf on locked BL, you will need to root again using whichever method you used previously. If you flash an ftf file on ANY bootloader locked or unlocked it resets your phone to the contents of the ftf file.
Click to expand...
Click to collapse
And which is the method to root this version with BL??
hv6478 said:
P.S. I'm guessing for those with locked BLs, we can use PRFCreator and that FTF from Xperifirm to create a flashable, pre-rooted MM ROM...anyone tried? My Z3c is currently bricked (hopefully fixable) so I can't test at the moment.
Click to expand...
Click to collapse
I'm giving it a try so I'll let you know.
EDIT: Admittedly I haven't got a clue how to use prfcreator but I tried and whilst it flashed there was no root or recovery.
2nd EDIT: XDR doesn't work on MM yet. I'll give TWRP a try.
TWRP 3.0.2 for Z3C https://dl.twrp.me/z3c/twrp-3.0.2-0-z3c.img.html
Buleste said:
I'm giving it a try so I'll let you know.
EDIT: Admittedly I haven't got a clue how to use prfcreator but I tried and whilst it flashed there was no root or recovery.
2nd EDIT: XDR doesn't work on MM yet. I'll give TWRP a try.
TWRP 3.0.2 for Z3C https://dl.twrp.me/z3c/twrp-3.0.2-0-z3c.img.html
Click to expand...
Click to collapse
Nice that sounds promising, at least it worked with the .zip that you created!
Which version of SuperSU are you using?
Thanks,
hv
hv6478 said:
Nice that sounds promising, at least it worked with the .zip that you created!
Which version of SuperSU are you using?
Thanks,
hv
Click to expand...
Click to collapse
I'm using BETA-SuperSU-v2.71-20160331103524.zip
However I was looking at the PRFCreator thread and it looks like if you add Recroot v2 as the SuperSU it should work. Not sure if it will give a recovery though.
EDIT: Okay. Didn't install the SuperSU binary properly but Kingroot could install the root though. Tried to remove it and replace with SuperSU and got a bootloop. However I have a cunning plan.
Xperia Z3 Compact - UB
I could not get TWRP recovery with the fastboot method.
I tried to install several "recoverys" but none are installed.
Help me please.
Buleste said:
I'm using BETA-SuperSU-v2.71-20160331103524.zip
However I was looking at the PRFCreator thread and it looks like if you add Recroot v2 as the SuperSU it should work. Not sure if it will give a recovery though.
EDIT: Okay. Didn't install the SuperSU binary properly but Kingroot could install the root though. Tried to remove it and replace with SuperSU and got a bootloop. However I have a cunning plan.
Click to expand...
Click to collapse
I love the sound of progress!
rvnlvrz said:
So the OFFICIAL 6.0.1 is already out and this is not the BETA version. It's for consumer release.
So how do you get to this eh?
NOTES: Flashtool can be used for both LB/UB. You won't lose DRM keys or unlock bootloader if you flash via flashtool.
1. Install Flashtool (get it here: http://www.flashtool.net/downloads.php).
2. There is a XperiFirm option there which would allow you to download official FTF files.
3. Navigate your way to Z3 Compact and grab the D5803 version US Variant (since this is configured for GLOBAL-LTE but i might still need to test bands). Or just grab anything you want there as long as it's version: 23.5.A.0.570
3. Flash using flashmode (hit the lightning icon there).
Now there's this "WIPE" Box, you have 2 options!
- Check User data and App logs and hit flash -- this will factory reset phone so you better have a backup!
- Leave them UNCHECKED if you want to retain your apps from your previous STOCK ROM. (might automatically uninstall incompatible apps in the process).
Once it asks for your device to be connected. Do as it says (power down, then hold the vol. down button as you plug the phone in).
-- this should start flashing.
4. After the process you may now boot the phone and there you have it!
-- Things below require unlocked BL --
If you want root, you can use fastboot and TWRP 3.X (I've tested the TWRP version 3.0.2 on the 6.0.1 beta before)
send this command on fastboot:
Code:
fastboot flash recovery <your twrp img here>
and hit enter. It must return 'OKAY'.
Unplug phone then boot into recovery and flash your SuperSU.zip
https://download.chainfire.eu/924/SuperSU/BETA-SuperSU-v2.68-20160228150503.zip
Click to expand...
Click to collapse
It doesn't work, I have trying out for a while, but fastboot doesn't flash anything
hv6478 said:
I love the sound of progress!
Click to expand...
Click to collapse
We have progress of sorts.
With prf creator add superSU and create the prerooted ROM.
In TWRP Wipe everything but SDcard and OTG
Install pre rooted ROM
Then Install RICDefieat.zip, byeselinux_flashable.zip, and BusyBox-v1.24.1-Stericson.zip
Power off the phone.
Open Flashtool
Load ftf of .570 and check the Exclude System box and flash the phone
Install TWRP using Z3C_MM_TWRP_Recovery_V2_By_Serajr
And that should be it.
Managed to get everything working bar the TWRP but I think that was my fault.
A download file of everything you need bar the ROM.
Buleste said:
We have progress of sorts.
With prf creator add superSU and create the prerooted ROM.
In TWRP Wipe everything but SDcard and OTG
Install pre rooted ROM
Then Install RICDefieat.zip, byeselinux_flashable.zip, and BusyBox-v1.24.1-Stericson.zip
Power off the phone.
Open Flashtool
Load ftf of .570 and check the Exclude System box and flash the phone
Install TWRP using Z3C_MM_TWRP_Recovery_V2_By_Serajr
And that should be it.
Managed to get everything working bar the TWRP but I think that was my fault.
A download file of everything you need bar the ROM.
Click to expand...
Click to collapse
Worked?
marlontravagli said:
Worked?
Click to expand...
Click to collapse
It seems to be working for me at the moment. Even TWRP.
Edit: TWRP is unstable and sometimes becomes unavailable . If that happens just find SGP621-RICDefeat.zip to enable R/W again and reinstall.
Buleste said:
We have progress of sorts.
With prf creator add superSU and create the prerooted ROM.
In TWRP Wipe everything but SDcard and OTG
Install pre rooted ROM
Then Install RICDefieat.zip, byeselinux_flashable.zip, and BusyBox-v1.24.1-Stericson.zip
Power off the phone.
Open Flashtool
Load ftf of .570 and check the Exclude System box and flash the phone
Install TWRP using Z3C_MM_TWRP_Recovery_V2_By_Serajr
And that should be it.
Managed to get everything working bar the TWRP but I think that was my fault.
A download file of everything you need bar the ROM.
Click to expand...
Click to collapse
ok...this sims to be right, thanks
superpipo said:
ok...this sims to be right, thanks
Click to expand...
Click to collapse
It seems that updating busybox to 1.24.1 stericson stops R/W permissions and the ability to access TWRP however it is easily fixed.
THIS POST IS EXTENSION TO
https://forum.xda-developers.com/xp...t-xperia-x-f5122-android-n-34-2-2-47-t3594502
and
https://forum.xda-developers.com/xperia-x/development/root-xperia-x-f512234-3-0-206-7-1-1-t3635595
Please read carefully and flash kernel for the LATEST UPDATE (Project SUZU )
for F5122_34.3.A.0.238 - 7.1.1 - 2 OCTOBER 2017 update
F5122 IS AT https://mega.nz/#F!7RRWEJjZ!qbotcsuXiKfXs2gwpVoBAw
F5121 .. https://mega.nz/#F!qUwV3R5Q!zpi18kKSNuS7vAHH9jOoQA (THANKs @velemas )
both f5121/5122 folders have two kernel images, if you flash the WITH SU image, the device will wakeup rooted. However if you flash the CLEAN kernel, you must flash TWRP3.1.1 (use adb fastboot commands) and from twrp you must flash SUPERSU or Magisk (whichever) -
PLEASE PROVIDE ME WORKING MAGISK (some friends have had been using) i will update my repository.
-if you don't have th 34.3 fsc script , i have included in the folder (closing Partitions takes TIME, so be Patient ! )
-also i have inclused mixer_paths_wcd9335.xml, on 98% VOLUME level, IF you think sound output is LOW,,, just REPLACE it from /system/etc folder!
-
.
Click to expand...
Click to collapse
for F5122_34.3.A.0.224 - 7.1.1 - 8 SEPTEMBER 2017 update
F5122 IS AT https://mega.nz/#F!GFo1EArZ!ngb5WsZJtbmFwXk_ImN-TA
F5121 .. https://mega.nz/#F!2EQniYoZ!0Rhj15GN7nSRmrTFMC8smg (THANKs @Mikolaj612 and @velemas )
-if you don't have th 34.3 fsc script , i have included in the folder (closing Partitions takes TIME, so be Patient ! )
-also i have inclused mixer_paths_wcd9335.xml, on 98% VOLUME level, IF you think sound output is LOW,,, just REPLACE it from /system/etc folder!
-
.
.
Click to expand...
Click to collapse
ROOT DIRECTORY (ON MEGA)
https://mega.nz/#F!aZAljazZ!zNLnLxH6flBxUsaTb167Jw
____________________________________
for F5122_34.3.A.0.217 - 7.1.1 - 8Aug2017 update
F5122 IS AT https://mega.nz/#F!iUB00abB!N7sDP1pv33ZCEC76j3RkYQ
F5121 .. AT https://mega.nz/#F!2FI0BI4B!f-wrWGTOzhgYX-_aLEBhBg ( THANK YOU @Mikolaj612 )
Code:
[SIZE="5"]
-if you don't have th 34.3 fsc script , i have included in the folder
-also i have inclused mixer_paths_wcd9335.xml, on 98% VOLUME level, IF you think sound output is LOW,,, just REPLACE it from /system/etc folder!
- :)
[/SIZE]
base directory
https://mega.nz/#F!aZAljazZ!zNLnLxH6flBxUsaTb167Jw
____________________________________________________
for F5122_34.3.A.0.206 - 7.1.1 - july2017 update
UPDATED KERNELS
F5121 IS AT https://mega.nz/#F!HcZmTIhR!0oCiMfh9uT-AdHp-bdSqZw (THANKS TO @velemas)
F5122 IS AT https://mega.nz/#F!fRBEVS5C!QjT-TgxZc9FYwAbh-F5IgA
during past 3 days; I had to flash my X, 3 times for build 34.3.A.0.238 ,
why?
here are my findings and i want your contribution
1.
after CLEAN FLASHING OF STOCK via FLASHTOOL ... I BOOT MY DEVICE, SETUP THE GOOGLE ACCOUNT(S) sync data etc AND then i switched off the device and FLASHED KERNEL without twrp and without SuperSU, i had to FLASH TWRP3.1.1 via ADB. when I boot my device held power+volumeDOWN key and went in to recovery. I FOUND twrp3.1.1 cannot access internal storage, asked password
SO
2.
after CLEAN FLASHING OF STOCKROM VIA FLASHTOOL, I NEVER BOOT MY DEVICE AND DIRECTLY flashed KERNEL ( version which doesn't have twrp orsupersu) LATER I flashed TWRP3.1.1 via ADB. I went in to recovery and this time twrp was able to access my internel storage. So I flashed KCAL (which later i found doesn't work for this kernel) and I FLASHED SUPERSU 2.82.zip.
I switched off my device and later boot it up, I setup all the accounts in android and sync data.
LATER I FOUND that my internal storage has only 10gb left, I got surprised and I found that my SYSTEM STORAGE is TAKING 50GB out of 64GB. I never found any such folder in the /system having files worth 40gb after android itself (10gb).
3.
again third time, after CLEAN FLASHING OF STOCKROM VIA FLASHTOOL. I FLASHED KERNEL having no TWRP but having SUPERSU. and boot my device and went thru sony setup. I found out that found out that only 15GB out of 64GB is used.
and now i am using device normally
the only explanation i can give is that when i flashed superSU via twrp3.1.1, it made partitions incorrectly, but when supersu is flashed by script, it works just fine.
any comments? who can try all above with his device?
If I flash latest update using xperifirm which option should I exclude to keep TWRP as recovery?
kloroform said:
If I flash latest update using xperifirm which option should I exclude to keep TWRP as recovery?
Click to expand...
Click to collapse
Fotakernel is the option you are looking for
Doesn't your phone distort at that high gain(I.e 92)?? Mine starts to crackle at 86 or 88 on headphones..
With 7.1. Update Sony made our x more quite but clearer, before it was more loud but harsh too..
Nice work :good:
I was going to ask if I can flash your older kernel to newer one, but I guess I don't have too. By the way, do you know what's the difference between .238 and .224 kernels? Didn't sony just released security update? Sorry, I'm new to Xperia Phones. :silly:
you wrote include wrongly(probably typo)
kloroform said:
If I flash latest update using xperifirm which option should I exclude to keep TWRP as recovery?
Click to expand...
Click to collapse
You may skip FotaKernel.
however you can always flash latest recovery twrp3.1.1 is out,
gaurav_15 said:
Doesn't your phone distort at that high gain(I.e 92)?? Mine starts to crackle at 86 or 88 on headphones..
With 7.1. Update Sony made our x more quite but clearer, before it was more loud but harsh too..
Click to expand...
Click to collapse
at 96, it does, I felt 86 (even 88) pretty low , special if the mobile is in bag and i am driving.
but at 92, its just fine.
also when u use the noise cancellation option ON, you get perfect quality sound on sony headphones
btw, i am using samsung earbuds, and works amazingly well!
Dominykas Only One said:
Nice work :good:
I was going to ask if I can flash your older kernel to newer one, but I guess I don't have too. By the way, do you know what's the difference between .238 and .224 kernels? Didn't sony just released security update? Sorry, I'm new to Xperia Phones. :silly:
you wrote include wrongly(probably typo)
Click to expand...
Click to collapse
welcome to Sony's complex world of kernels builds and LOST DRM KEYS
1. KERNEL USUALLY GETS UPDATE AS AND WHEN GOOGLE UPGRADES ANDROID ( for example from marshmellow to nougat )
2. on Nougat (android 7) the Linux kernel is 3.1.x.x , on this kernel sony has been releasing various builds with minor chances in security patch and/or some bug fixes in volume rockers / bluetooth / NFC connectivity etc
so technically, you CAN use android N kernel came with initial build by sony over latest BUILDS by sony.
on the booting level it will not affect your device
however I am not sure what will happen once android is loaded and it may show u older security patches or may crash
hey, thanks a lot for the update!
I am on .228 rooted, I got notification for system update, so after I update + flash your .238 with SU and I am good to go?
Prerooted Magisk Manager compatible kernel
You can flash from TWRP, just select Install then click Image File, select the kernel img file and selectBoot and flash
https://www.mediafire.com/file/40v6g55eluw7k70/patched_boot.img
Intsall Magisk Manager from here
https://github.com/topjohnwu/MagiskManager/releases/download/v5.3.0/MagiskManager-v5.3.0.apk
JukiCro said:
hey, thanks a lot for the update!
I am on .228 rooted, I got notification for system update, so after I update + flash your .238 with SU and I am good to go?
Click to expand...
Click to collapse
on unlocked bootloader, OTA fails. but you can try!
but if anyhow you upgrade to .238 via OTA, you will lose you rooting and twrp. so yes you will have to FLASH the kernel only.
kloroform said:
Prerooted Magisk Manager compatible kernel
You can flash from TWRP, just select Install then click Image File, select the kernel img file and selectBoot and flash
https://www.mediafire.com/file/40v6g55eluw7k70/patched_boot.img
Intsall Magisk Manager from here
https://github.com/topjohnwu/MagiskManager/releases/download/v5.3.0/MagiskManager-v5.3.0.apk
Click to expand...
Click to collapse
thank you! i found magisk interesting option since its system , Open source and let you install modules (including xposed) (if supported)
Does the 238 kernel include drmfix? I am still on Android 6.0.1 and am looking to jump straight to the latest 7.1.1fw note i don't have drm key's they are long gone.
sucker for sony's said:
Does the 238 kernel include drmfix? I am still on Android 6.0.1 and am looking to jump straight to the latest 7.1.1fw note i don't have drm key's they are long gone.
Click to expand...
Click to collapse
you and update directly to 7.1.1
the kernel has drm fix
where can i download the 34.3.a.0238 tft rom ?
nova001 said:
where can i download the 34.3.a.0238 tft rom ?
Click to expand...
Click to collapse
Using xperifirm software or directly from xpericheck.com
hhjadeja007 said:
Using xperifirm software or directly from xpericheck.com
Click to expand...
Click to collapse
yee a saw, but i dont have alfa file account :S
flashtool (xperifirm ): error invalid upda information...
if i flash this kernel do i lose my drm key's? what is better version to use with SU or without? Best Regards.
Doesn't work for me. Root works just half a way. I can use root apps like adaway etc. but i can't uninstall any apps, mount /system as rw and even install busybox. Something is broken out there. 34.3.A.0.238
Hello. So basically my friend has a xperia Z5 Compact phone and he wants to get magisk 19.1 on it. I am new to the phone and do not know how to root it etc. so I need help on getting TWRP and magisk on it. The bootloader is already unlocked because I tried to get TWRP on it but it ended in frozen boot screen. I have since flashed the phone and now need help to actually do something with it.
Hope you have made a backup of the phone's TA partition prior to unlocking its bootloader. Anyway, once it is already unlocked, put it in fastboot mode (hold the volume up button whilst connecting it to the computer, util the led remains lit in blue color), either copy or move the TWRP image file (twrp.img from now on) to the directory where the fastboot tool is present, then enter the command (attention: it's case sensitive):
Code:
fastboot flash FOTAKernel twrp.img
Now, to enter TWRP, disconnect it from the computer and hold both the power and the volume down buttons. When the phone vibrates (as if it was being booted up), release the power button; when the screen lights up, release the volume down button. TWRP should come up.
By the way, in my Z5C phone I use the stable Magisk 19.3 version, along with the MagiskHide Props Config, Busybox for Android NDK, and Systemless Hosts (this one is found in Magisk Manager settings) modules. This way my phone passes both Safetynet tests, and it shows as certified by Play Store.
casouzaj said:
Hope you have made a backup of the phone's TA partition prior to unlocking its bootloader. Anyway, once it is already unlocked, put it in fastboot mode (hold the volume up button whilst connecting it to the computer, util the led remains lit in blue color), either copy or move the TWRP image file (twrp.img from now on) to the directory where the fastboot tool is present, then enter the command (attention: it's case sensitive):
Code:
fastboot flash FOTAKernel twrp.img
Now, to enter TWRP, disconnect it from the computer and hold both the power and the volume down buttons. When the phone vibrates (as if it was being booted up), release the power button; when the screen lights up, release the volume down button. TWRP should come up.
By the way, in my Z5C phone I use the stable Magisk 19.3 version, along with the MagiskHide Props Config, Busybox for Android NDK, and Systemless Hosts (this one is found in Magisk Manager settings) modules. This way my phone passes both Safetynet tests, and it shows as certified by Play Store.
Click to expand...
Click to collapse
Alright Im going to try that in the next few days.
casouzaj said:
Hope you have made a backup of the phone's TA partition prior to unlocking its bootloader. Anyway, once it is already unlocked, put it in fastboot mode (hold the volume up button whilst connecting it to the computer, util the led remains lit in blue color), either copy or move the TWRP image file (twrp.img from now on) to the directory where the fastboot tool is present, then enter the command (attention: it's case sensitive):
Code:
fastboot flash FOTAKernel twrp.img
Now, to enter TWRP, disconnect it from the computer and hold both the power and the volume down buttons. When the phone vibrates (as if it was being booted up), release the power button; when the screen lights up, release the volume down button. TWRP should come up.
By the way, in my Z5C phone I use the stable Magisk 19.3 version, along with the MagiskHide Props Config, Busybox for Android NDK, and Systemless Hosts (this one is found in Magisk Manager settings) modules. This way my phone passes both Safetynet tests, and it shows as certified by Play Store.
Click to expand...
Click to collapse
Can you tell me why you told to flash the twrp to FOTKernel and not to recovery?
At the moment I am on Android 5.1.1 (Kernel 3.10.49 , Build-Number 32.0.A.6.200). I followed this guide here to backup my TA-Partition and my bootloader is unlocked.
But when I came to the step to flash the boot.img and the twrp the E5823 does not start anymore.
Any idea?
Greetings by Idijt
I_did_it_just_tmrrow said:
Hope you have made a backup of the phone's TA partition prior to unlocking its bootloader. Anyway, once it is already unlocked, put it in fastboot mode (hold the volume up button whilst connecting it to the computer, util the led remains lit in blue color), either copy or move the TWRP image file (twrp.img from now on) to the directory where the fastboot tool is present, then enter the command (attention: it's case sensitive):
Can you tell me why you told to flash the twrp to FOTKernel and not to recovery?
At the moment I am on Android 5.1.1 (Kernel 3.10.49 , Build-Number 32.0.A.6.200). I followed this guide here to backup my TA-Partition and my bootloader is unlocked.
But when I came to the step to flash the boot.img and the twrp the E5823 does not start anymore.
Any idea?
Greetings by Idijt
Click to expand...
Click to collapse
Which files, exactly, from which threads, have you flashed, to which respective partitions?
Sent from my Xperia Z5 Compact using XDA Labs
casouzaj said:
Which files, exactly, from which threads, have you flashed, to which respective partitions?
Sent from my Xperia Z5 Compact using XDA Labs
Click to expand...
Click to collapse
THX for reply.
I do the steps:
-How To Backup TA Partiton
So I flashed the "E5823_32.0.A.6.200_R4B_Australia Generic_1298-7260.ftf" from here , from this thread.
-Backing Up TA Partiton
This step was a success . So I was able to run the script from the iovyroot_v0.4.zip , from this thread.
-Unlocking The Bootloader
I do this and I got the unlockcode from sony but when I run:
Code:
fastboot oem device-info
I got an error. He did not know this cmd. But when I do this, I got "Bootloader unlocked -> Yes"
*#*#7378423#*#* to access the service menu.
Tap Service info > Configuration > Rooting Status. If Bootloader unlock allowed says Yes, then you can continue with the next step. If it says No, or if the status is missing, your device cannot be unlocked.
-Rooting The Device
And this step my journey ends. I can flash a twrp, for example this one.
I do this with:
Code:
fastboot flash recovery the-name-of-the-twrp.img
With no errors. The howto from here told that I should flash the boot.img from here before flashng the twrp but when I do this I am not able to boot into anything else then the fastboot (vol+ and plugin the cable) anymore.I try the boot.img from Z5C_AndroPlusKernel_v31.zip and from Z5C_AndroPlusKernel_v43.zip but both giving me the same result as mentioned before.
Perhaps my problem is that I am still on 5.1.1. At the moment I try to find a compatible E5823 ftf-File to latest stock-rom (should be 7.0.1?)
Greetings by Idijt
EDIT:
The result when I just try to boot a twrp recovery:
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot boot C:\Users\idijt\Downloads\twrp-3.0.2-0-E5823-20160417.img
downloading 'boot.img'...
OKAY [ 0.392s]
booting...
FAILED (remote: dtb not found)
finished. total time: 0.459s
I_did_it_just_tmrrow said:
THX for reply.
I do the steps:
-How To Backup TA Partiton
So I flashed the "E5823_32.0.A.6.200_R4B_Australia Generic_1298-7260.ftf" from here , from this thread.
-Backing Up TA Partiton
This step was a success . So I was able to run the script from the iovyroot_v0.4.zip , from this thread.
-Unlocking The Bootloader
I do this and I got the unlockcode from sony but when I run:
I got an error. He did not know this cmd. But when I do this, I got "Bootloader unlocked -> Yes"
*#*#7378423#*#* to access the service menu.
Tap Service info > Configuration > Rooting Status. If Bootloader unlock allowed says Yes, then you can continue with the next step. If it says No, or if the status is missing, your device cannot be unlocked.
-Rooting The Device
And this step my journey ends. I can flash a twrp, for example this one.
I do this with: With no errors. The howto from here told that I should flash the boot.img from here before flashng the twrp but when I do this I am not able to boot into anything else then the fastboot (vol+ and plugin the cable) anymore.I try the boot.img from Z5C_AndroPlusKernel_v31.zip and from Z5C_AndroPlusKernel_v43.zip but both giving me the same result as mentioned before.
Perhaps my problem is that I am still on 5.1.1. At the moment I try to find a compatible E5823 ftf-File to latest stock-rom (should be 7.0.1?)
Greetings by Idijt
EDIT:
The result when I just try to boot a twrp recovery:
Click to expand...
Click to collapse
In your computer, run Flashtool and click on the XF icon (the last one in the line of icons on the top part). XperiFirm will be downloaded and run. On it, under : Smartphone 2015'', click on 'Xpetia Z5 Compact' and on the specific model. Now clock on 'Check All'. Select a ROM bearing 'Customized' in its name and with version 32.4.A.1.54, which is Android 7.1.1). The list of available files appear on the right. Click on the most updated one and on 'Download'. Wait until the ROM is downloaded and unpacked. When the progress bar gets blank and says 'Downloaded successfully', click on 'Close'. Then, click on the X in the XperiFirm window to kill it. Flashtool will resume its work, which will culminate with the creation of the ftf file in the right directory.
To flash the ROM, click on the bolt icon, in Flashtool , select 'Flashmode', click on the little arrow at the left of the model name. The same for the specific model and for the ROM name. Finally, click on the ROM to be flashed. Mark all the boxes in the upper 'Wipe' section and click on 'Flash'. While it is preparing the files, turn the phone off. When an animated window requesting connection comes up, hold the phone's volume down button whilst connecting it to the computer. Release the button when the animated window goes away. Wait for the process to completely finish. Disconnect the phone from the computer
The ftf is located in C:/Users/your_username/.flashTool/firmwares. Copy it to anywhere you wish and change the copy's extension to zip.. Double click on it and extract 'kernel.sin'. In Flashtool, click on Tools > Sin Editor, and click on the tree dots on the right. Navigate to the location of the kernel.sin file, select it and click on 'Extract data'. File kernel.elf has been created.
Do you know rootkernel? (https://forum.xda-developers.com/xp...t-automatic-repack-stock-kernel-dm-t3301605). Copy the kernel.elf and the phone's TA.img to the rootkernel directory. In a terminal window in that directory, enter:
flash_dk TA.img DK.ftf
Copy the DK.ftf file to .flashTool/firmwares directory. Flash it in flashmode, just like you did when you flashed the ROM.
Back to the terminal window, enter:
rootkernel kernel.elf new-boot.img
In the script which runs, answer yes to disable Sony RIC' and to DRM fix. Answer no to things like dm-verity, busybox and TWRP. Copy new-boot.img to the phone.
In the rootkernel thread there's an attachment called DRM-Fix_System_Mode.zip. Download it and copy it to the phone.
The TWRP I use is this one: https://forum.xda-developres.com/z5-compact/general/twrp-twrp-3-3-0-z5-compact-t3929320, which I fastboot'ed to the FOTAKernel partition.
In TWRP (with the phone off, hold both power and vol-, remember?), click on 'Install' and on the flash img button. Select the new-boot.img file and the boot partition. Click on the flash zip button, select the Magisk v19.3 file and install it. Install
DRM-Fix_System_Mode.zip as well.
This is getting too extense. As you progress, I will write other stuff.
Sent from my Xperia Z5 Compact using XDA Labs
casouzaj said:
In your computer, ........
In TWRP (with the phone off, hold both power and vol-, remember?), click on 'Install' and on the flash img button. Select the new-boot.img file and the boot partition. Click on the flash zip button, select the Magisk v19.3 file and install it. Install
DRM-Fix_System_Mode.zip as well.
This is getting too extense. As you progress, I will write other stuff.
Sent from my Xperia Z5 Compact using XDA Labs
Click to expand...
Click to collapse
Wow, thx for this guide!
I came now to the point to start twrp. The only thing I did not was installing Magisk. Then I hit reboot to system. Sadly at the moment it just stuck in the first white Sony-Logo screen.
The only chance to came out of this is to press all buttons in the same time.
My target is to have twrp and Berni's LineageOS build.
Do you have some last tips for me, I fell very close
EDIT:
I flashed Magisk v19.3 and it wokred... Yes, as you told me :/
Can I simply flash Berni LineageOS now and did I need to flash the new-boot.img, the DRM-Fix_System_Mode.zip and Magisk always after flashing a new rom?
I_did_it_just_tmrrow said:
Wow, thx for this guide!
I came now to the point to start twrp. The only thing I did not was installing Magisk. Then I hit reboot to system. Sadly at the moment it just stuck in the first white Sony-Logo screen.
The only chance to came out of this is to press all buttons in the same time.
My target is to have twrp and Berni's LineageOS build.
Do you have some last tips for me, I fell very close
Click to expand...
Click to collapse
At any state the phone is in, in order to turn it off, hold both the power and the volume up buttons, until it vibrates thrice.
Then, enter TWRP by holding both the power and the volume down buttons. When the phone vibrates (as if it was being turned on), release the power button. When the screen lights up, release the volume down button. Then, under TWRP, install the new-boot.img, the Magusk-V19.3.zip and the DRM-Fix.zip.
Sent from my Xperia Z5 Compact using XDA Labs
---------- Post added at 05:39 PM ---------- Previous post was at 04:42 PM ----------
Regarding Berni's LineageOS builds, I'm running his 14.1 firmware. It has some issues. I don't go back to the stock ROM because I would have to wipe my data in the process, and, at the moment, it's not an option for me. The big advantage of the stock ROM is that you can have all your DRM keys active, although the bootloader is unlocked. The big disadvantage is to have outdated security updates. Berni's 15.1 build has more bugs than the 14.1 one,, and with his 16.0 build, the phone doesn't even boot up.
By the way, the new-boot.img file doesn't fit any of the LineageOS builds. It's the kernel which holds the pointers to the DRM keys you flashed (DK.ftf). It is to the be used either with stock firmwares or ROMs based on it only. An indication is that the stock boot image is some 14+MB long, whereas LineageOS' boot images lenght is some 9MB only.
Sent from my Xperia Z5 Compact using XDA Labs
I too am trying to root my Z5 Compact E5823
Could you help me clarify a few things, I followed another Z5 compact guide for MM and wasn't able to get SU installed without the bootloop I have my Z5 compact E5823 working after flashing 32.0.A.6.200_Australia_Generic firmware. I came across this thread and you gave such good instructions I thought I'd try Magisk which seems to be the standard now. I only got the Z5 compact to replace a broken Z3 compact, I needed a compact phone with ANT+ and the Z5 compact is the most advanced of the Sony's that offer it I never was able to get my Z3 rooted, I want to be able to rid the phone of bloatware I'm not sure the ANT+ works with Lineage so I'm stuck with Stock, at least if I get TWRP installed I can maybe experiment too.
As part of the guide I followed ( I can't post link because I joined just to ask for help, but it's titled "Sony Z5 Compact: Root without losing TA partition (DRM features) on Marshmallow") the part for the TA partition was as follows:
"Copy your TA partition backup to the rootkernel folder.
Open up a command prompt to the rootkernel folder and type in the following:
flash_dk TA-####.img restore-drm-keys.ftf
In Flashtool, click on the lightning bolt icon
Select flashmode
Select "DeviceKey" and click Flash
Hold "volume DOWN" and plug in USB cable.
Unplug and restart phone when instructed (read the activity log)"
do I have to repeat your instructions to:
flash_dk TA.img DK.ftf
Copy the DK.ftf file to .flashTool/firmwares directory. Flash it in flashmode, just like you did when you flashed the ROM.
Click to expand...
Click to collapse
should I still answer these this way?
Back to the terminal window, enter:
rootkernel kernel.elf new-boot.img
In the script which runs, answer yes to disable Sony RIC' and to DRM fix. Answer no to things like dm-verity, busybox and TWRP. Copy new-boot.img to the phone.
Click to expand...
Click to collapse
I can't find the DRM-Fix_System_Mode.zip, is it necessary? Where on the phone do I copy it?
In the rootkernel thread there's an attachment called DRM-Fix_System_Mode.zip. Download it and copy it to the phone.
Click to expand...
Click to collapse
You mis-spelled the link but I found the thread. Are you using "20190514-TWRP-3.3.0-suzuran-recovery.img" or the newer one "20190517-TWRP-3.3.1-suzuran-recovery.img"
I do this with the code you have above?
fastboot flash FOTAKernel twrp.img
The TWRP I use is this one: which I fastboot'ed to the FOTAKernel partition.
Click to expand...
Click to collapse
is Magisk v19.3 still the one to use? When in TWRP can I install new-boot.img , and then Magisk v19.3, right after or do I need to reboot.
In TWRP (with the phone off, hold both power and vol-, remember?), click on 'Install' and on the flash img button. Select the new-boot.img file and the boot partition. Click on the flash zip button, select the Magisk v19.3 file and install it. Install
DRM-Fix_System_Mode.zip as wells
Click to expand...
Click to collapse
One last thing as you mentioned above
By the way, in my Z5C phone I use the stable Magisk 19.3 version, along with the MagiskHide Props Config, Busybox for Android NDK, and Systemless Hosts (this one is found in Magisk Manager settings) modules. This way my phone passes both Safetynet tests, and it shows as certified by Play Store.
Click to expand...
Click to collapse
Are these all installed through Magisk Manager settings, or installed separately?
I hope all this isn't asking too much.
Thanks in advance for any help you can offer.
P.S. ( I am also getting the NFC firmware failed error when first booting after flashing firmware, I tried about 4 times different things, LL, MM, and Nougat. I was able to install Boot.img when SU wasn't in the rootkernel folder but the after booting to TWRP the bootloop happened.)
gnostisus said:
Could you help me clarify a few things, I followed another Z5 compact guide for MM and wasn't able to get SU installed without the bootloop I have my Z5 compact E5823 working after flashing 32.0.A.6.200_Australia_Generic firmware. I came across this thread and you gave such good instructions I thought I'd try Magisk which seems to be the standard now. I only got the Z5 compact to replace a broken Z3 compact, I needed a compact phone with ANT+ and the Z5 compact is the most advanced of the Sony's that offer it I never was able to get my Z3 rooted, I want to be able to rid the phone of bloatware I'm not sure the ANT+ works with Lineage so I'm stuck with Stock, at least if I get TWRP installed I can maybe experiment too.
As part of the guide I followed ( I can't post link because I joined just to ask for help, but it's titled "Sony Z5 Compact: Root without losing TA partition (DRM features) on Marshmallow") the part for the TA partition was as follows:
"Copy your TA partition backup to the rootkernel folder.
Open up a command prompt to the rootkernel folder and type in the following:
flash_dk TA-####.img restore-drm-keys.ftf
In Flashtool, click on the lightning bolt icon
Select flashmode
Select "DeviceKey" and click Flash
Hold "volume DOWN" and plug in USB cable.
Unplug and restart phone when instructed (read the activity log)"
do I have to repeat your instructions to:
should I still answer these this way?
I can't find the DRM-Fix_System_Mode.zip, is it necessary? Where on the phone do I copy it?
In the rootkernel thread there's an attachment called DRM-Fix_System_Mode.zip. Download it and copy it to the phone.
You mis-spelled the link but I found the thread. Are you using "20190514-TWRP-3.3.0-suzuran-recovery.img" or the newer one "20190517-TWRP-3.3.1-suzuran-recovery.img"
I do this with the code you have above?
fastboot flash FOTAKernel twrp.img
You mis-spelled the link but I found the thread. Are you using "20190514-TWRP-3.3.0-suzuran-recovery.img" or the newer one "20190517-TWRP-3.3.1-suzuran-recovery.img"
I do this with the code you have above?
fastboot flash FOTAKernel twrp.img
The TWRP I use is this one: which I fastboot'ed to the FOTAKernel partition.
is Magisk v19.3 still the one to use? When in TWRP can I install new-boot.img , and then Magisk v19.3, right after or do I need to reboot.
One last thing as you mentioned above
Are these all installed through Magisk Manager settings, or installed separately?
I hope all this isn't asking too much.
Thanks in advance for any help you can offer.
P.S. ( I am also getting the NFC firmware failed error when first booting after flashing firmware, I tried about 4 times different things, LL, MM, and Nougat. I was able to install Boot.img when SU wasn't in the rootkernel folder but the after booting to TWRP the bootloop happened.)
Click to expand...
Click to collapse
Magisk modules are installed by the Magisk Manager app. Tap on the menu button (the 3 bars at the top left) and select 'Download'. Tap on the search button and type in at least part of the module's name, and tap on 'Install'. The only module that is installed differently is the systemless hosts one. Tap on 'Menu > Settings > Systemless hosts'. After all the modules you wanted get installed, reboot your phone.
By the way, in my Z5C phone I'm currently running the latest stable Magisk v20.4. In its Menu > Settings part, I turn on the 'Magisk Hide' key.
Regarding flashing the Dk.ftf file, I do it whenever I flash a full ftf, because I guess the alternative partition it is flashed to gets overwritten.
Sent from my Sony E5823 using XDA Labs
Berni's LineageOS
I managed to get everything working and set up. Unfortunately I couldn't get the ANT+ working, it is disabled or buggy above LL, I tried the ANT+ Enabler app with no luck, the app claims to work on LineageOS so I want to give that a try but you wrote above
casouzaj said:
]Regarding Berni's LineageOS builds, I'm running his 14.1 firmware.
By the way, the new-boot.img file doesn't fit any of the LineageOS builds. It's the kernel which holds the pointers to the DRM keys you flashed (DK.ftf). It is to the be used either with stock firmwares or ROMs based on it only. An indication is that the stock boot image is some 14+MB long, whereas LineageOS' boot images lenght is some 9MB only.
Click to expand...
Click to collapse
So would I be able to flash from TWRP In a similar manner and what files would I need, or do I have to flash the Berni's LineageOS firmware with flashtool and install a different TWRP build to install Magisk? Otherwise I'm stuck with stock 5.1.1 which I had tried to get rooted with no luck.
Thanks for the reply.
gnostisus said:
I managed to get everything working and set up. Unfortunately I couldn't get the ANT+ working, it is disabled or buggy above LL, I tried the ANT+ Enabler app with no luck, the app claims to work on LineageOS so I want to give that a try but you wrote above
So would I be able to flash from TWRP In a similar manner and what files would I need, or do I have to flash the Berni's LineageOS firmware with flashtool and install a different TWRP build to install Magisk? Otherwise I'm stuck with stock 5.1.1 which I had tried to get rooted with no luck.
Thanks for the reply.
Click to expand...
Click to collapse
I've never used ANT+. I can't help you with that.
Berni's builds (like practicality all custom ROMs) are flashable zips. Install them from TWRP. .If you need the Google stuff, install a Gapps package, also from TWRP (I use to get the most updated mini one from opengappsI.com). Wipe all your data and caches. To get root access, install Magisk (the stable v20.4, I guess).
Good luck!
Sent from my Sony E5823 using XDA Labs
quick question about Berni's build
casouzaj said:
Berni's builds (like practicality all custom ROMs) are flashable zips. Install them from TWRP..
Click to expand...
Click to collapse
All I have to do is put the Berni's build zip file on my phone and In TWRP click on 'Install' and on the flash img button. Select the zip file. There's nothing I need to do to prepare the phone first?
Wipe all your data and caches.
Click to expand...
Click to collapse
How do I do this?
I guess most important do I need to install the DRM-Fix_System_Mode.zip or anything else other than Magisk again?
Thanks again
gnostisus said:
All I have to do is put the Berni's build zip file on my phone and In TWRP click on 'Install' and on the flash img button. Select the zip file. There's nothing I need to do to prepare the phone first?
How do I do this?
I guess most important do I need to install the DRM-Fix_System_Mode.zip or anything else other than Magisk again?
Thanks again
Click to expand...
Click to collapse
You can either copy the zip files to your phone (or SD card), select the storage where the files are located and tap on ' Install', or keep them on your PC and, in TWRP tap on 'Advanced > add sidelioad', slide the bar, connect your phone to your PC, launch a command window, navigate to the folder where the files are located and enter:
add sideload filename.zip
Wait until the sideload process is finished (TWRP returns to the normal adb interface).
To clear your data, tap on the 'Wipe' softbutton and slide the bottom bar to factory reset.
Sent from my Sony E5823 using XDA Labs