Database Develop

Root Your Z1 Now [4.3[[Unlock Bootloader]

Here is the tip to root your Z1 (4.3) with the easy method. You Z1 must Unlock the Bootloader.
Please Copy All Your Zip Files To SD Card for Flash it with Recovery
Download SuperSU from Here
1.Unlock Bootloader by using Fastboot Command [If You Cannot Do It Then Stop Here]
2.Flash DoomKernel V3 (You can download from Here)
Command :
fastboot flash boot Z1-DooMKernel-v03.img
After flash the DoomKernel V3 please command :
fastboot reboot
It will go to Recovery Mode
Press Volume Up for CWM and Volume Down for TWRP
Flash all your Zip Files including SuperSu-v1.86.zip and then turn offf
3. Flash Your 14.2.A.0.290 Kernel by Using Flashtool (Kernel Only)
Where is Kernel? It's in your Firmware
After finish reboot your phone and enjoy the rooted.
Anything wrong please correct me. And I am welcome for all questions.
Brian Ly Mataba

Yes, seems to easy. You skipped few processes like how instal recovery to install kernel.

eclyptos said:
Yes, seems to easy. You skipped few processes like how instal recovery to install kernel.
Click to expand...
Click to collapse
Just flash the Doomkernel it will come with Recovery ^_^

Brianlymtb said:
Just flash the Doomkernel it will come with Recovery ^_^
Click to expand...
Click to collapse
Via flashtool in flashmode?

no, in flashtool with fastboot mode
or use fastboot and command window
fastboot flash boot "insert kernel name here"

gregbradley said:
no, in flashtool with fastboot mode
or use fastboot and command window
fastboot flash boot "insert kernel name here"
Click to expand...
Click to collapse
Cheers Man, this is confirmed full root without problems on mouting/unmouting?

Brianlymtb said:
Here is the tip to root your Z1 (4.3) with the easy method. You Z1 must Unlock the Bootloader.
Please Copy All Your Zip Files To SD Card for Flash it with Recovery
Download SuperSU from Here
1.Unlock Bootloader by using Fastboot Command [If You Cannot Do It Then Stop Here]
2.Flash DoomKernel V3 (You can download from Here)
Command :
fastboot flash boot Z1-DooMKernel-v03.img
After flash the DoomKernel V3 please command :
fastboot reboot
It will go to Recovery Mode
Press Volume Up for CWM and Volume Down for TWRP
Flash all your Zip Files including SuperSu-v1.86.zip and then turn offf
3. Flash Your 14.2.A.0.290 Kernel by Using Flashtool (Kernel Only)
Where is Kernel? It's in your Firmware
After finish reboot your phone and enjoy the rooted.
Anything wrong please correct me. And I am welcome for all questions.
Brian Ly Mataba
Click to expand...
Click to collapse
did you try relocking your bootloader afterwards? can we do that and keep the root?
i did so on my xperia ZR, only problem is phone usually goes into bootloop after relocking of the bootloader, but i made a nandroid backup before the relocking, and after relocking just flashed some rootable fw installed recovery and flashed the nandroid i made before.

eclyptos said:
Cheers Man, this is confirmed full root without problems on mouting/unmouting?
Click to expand...
Click to collapse
Yes and no...
You'll have read/write in recovery but only read in OS.
So basically, you'll have fully working root but you'll have to flash MODs or system APKs from recovery.
That shouldn't be problem...
This is (at the moment) best way to root your 4.3 OS
Sent from my Z1

If you have unlocked the bootloader and flashed one of the modified stock kernels from here then you have full root, and can write to system. I have done it several times today.

Kernel issue?
Ok, I followed this to the best of my knowledge but when I tried to flash the kernel.sin it kept giving an error that it's not a boot image... so I flashed the kernel from firmware in flashmode (by using the ftf but excluding everything besides kernel). Root apps work fine to my knowledge now, but am I supposed to be missing recovery now? I've tried installing busybox with no luck and can't get into recovery to install the zip. I'm guessing I did something wrong flashing the kernel in flashmode instead of fastboot. Can you give me advice? Thanks.
Edit: Got it with above post, thanks.

I want to try this now but do i need to back-up my TA before doing this?.using unbranded ftf

gaboh24 said:
I want to try this now but do i need to back-up my TA before doing this?.using unbranded ftf
Click to expand...
Click to collapse
You should backup TA and DRM keys but if you are on 4.3 you can't because you need root. You have to downgrade to 4.2.2, root the system, backup everything, update again and follow the steps.

eclyptos said:
You should backup TA and DRM keys but if you are on 4.3 you can't because you need root. You have to downgrade to 4.2.2, root the system, backup everything, update again and follow the steps.
Click to expand...
Click to collapse
thanks mate! is your z1 already rooted now?

gaboh24 said:
thanks mate! is your z1 already rooted now?
Click to expand...
Click to collapse
I got so amazing battery life so I'm scared to flash it again because from my experience when someting working very well you should not messing up with that. I will follow the steps to root this way only if I will had the opportunity to backup my TA and DRM keys, just in case something go wrong, without have to downgrade to 4.2.2. I do not want to downgrade at all so still undecided what do. I probably will wait and enjoy my phone this holidays and see if in few week coming up something new.
Anyway I still don't know well why I should backup my TA and DRM keys if with 4.3 everything working fine.

eclyptos said:
I got so amazing battery life so I'm scared to flash it again because from my experience when someting working very well you should not messing up with that. I will follow the steps to root this way only if I will had the opportunity to backup my TA and DRM keys, just in case something go wrong, without have to downgrade to 4.2.2. I do not want to downgrade at all so still undecided what do. I probably will wait and enjoy my phone this holidays and see if in few week coming up something new.
Anyway I still don't know well why I should backup my TA and DRM keys if with 4.3 everything working fine.
Click to expand...
Click to collapse
hahahahaha! I see! me too still undecided in this..you have a point and maybe I'll just wait more days because I can smell the upcoming stable root for 4.3.. BTW ecplyptos about 20MP and 8MP in iauto, the one that we are talking yesterday, remember?. for me it's not important if our ftf is default in 8MP superior auto..do you have any idea why vodafone ftf superior auto is default in 20MP?.geez!

My phone says no bootloader unlock allowed on service menu.
Question:
Can I still unlock it or no?
Sent from my C6903 using Tapatalk

albertobom said:
My phone says no bootloader unlock allowed on service menu.
Question:
Can I still unlock it or no?
Sent from my C6903 using Tapatalk
Click to expand...
Click to collapse
how did that happen?...

albertobom said:
My phone says no bootloader unlock allowed on service menu.
Question:
Can I still unlock it or no?
Sent from my C6903 using Tapatalk
Click to expand...
Click to collapse
No. There is no way.

I'm on Vodafone ES contract... I belive it's locked by the company by default, no?
Sent from my C6903 using Tapatalk
---------- Post added at 02:13 AM ---------- Previous post was at 02:11 AM ----------
eclyptos said:
No. There is no way.
Click to expand...
Click to collapse
So no custom firmware for me?
But can I root it? Cause on the previous firmware I could.
Sent from my C6903 using Tapatalk

gaboh24 said:
BTW eclyptos about 20MP and 8MP in iauto, the one that we are talking yesterday, remember?. for me it's not important if our ftf is default in 8MP superior auto..do you have any idea why vodafone ftf superior auto is default in 20MP?.geez!
Click to expand...
Click to collapse
20mpx in iAuto seem to be worse than expected, this was said from users with that FTF. I also don't care about that but I don't like restricted devices at all and even if the pictures are not good as they should be I will like anyway to have that option, switch between 20 and 8. We don't know yet why Vodafone has that but to me is just a marketing move to be interested more on they stuff.
---------- Post added at 01:25 AM ---------- Previous post was at 01:17 AM ----------
albertobom said:
I'm on Vodafone ES contract... I belive it's locked by the company by default, no?
So no custom firmware for me?
But can I root it? Cause on the previous firmware I could.
Sent from my C6903 using Tapatalk
Click to expand...
Click to collapse
Nobody know who locked the phones, Vodafone or Sony, and why, can be for FTF compatibility, restrictions or something else.
Anyway with Locked Bootloader you can install custom rooms, you can install stock kernels, you can root your phone if it's on Android 4.2.2 but on 4.3 the rooting for Locked BL still in developing so you have to wait. The only thing which you can't install on your phone with locked BL is custom kernels. That's all.
---------- Post added at 01:28 AM ---------- Previous post was at 01:25 AM ----------
gaboh24 said:
how did that happen?...
Click to expand...
Click to collapse
Is not happen, it's was just lock from factory. Happen rarely after updates but I think is not the case.

[Q] why downgrade when you can flash FW with root? // backup DRM

hey guys,
why do you have to downgrade the fw to 4.4.4 if you could easily flash a new firmware with root included already?
guide I used: http://forum.xda-developers.com/z3-compact/general/how-to-root-backup-drm-keys-t3013343
also, where are the DRM keys in the file system? I use Linux and I can't use the mentioned Windows bat file tool to back them up. And I don't want to rewrite the batch files into a shell script...

The DRM keys are raw data inside seperate partitions as far as I have understood it correctly. Maybe someone can comment on the details but you should be able to dump them using dd if you identify the correct partitions.. On the first question, I would be interested in this too.
Why would you downgrade and root if you can flash a pre-rooted image?
How come you can flash a pre-rooted image with locked BL? Doesn't the phone check CRC before flashing a firmware with locked BL? Doesn't it refuse to flash if tampered with? How does that work?

Regarding TA-backup
someone worked on a linux port, see
https://github.com/DevShaft/Backup-TA/issues/10
However unfortunately the original developer (Devshaft) is afk and doesn't merge it...
https://github.com/DevShaft/Backup-TA/pull/10
and
https://github.com/DevShaft/Backup-TA/issues/6
unlocked Bootloader vs Root
These things doesn't have to do with each other.
Root is "basically" when you have the su binaries in your system partition.
An unlocked bootloader you need only when you want to flash (/boot from) a non-stock / custom kernel, e.g. cyanogen mod.

faxd said:
Regarding TA-backup
someone worked on a linux port, see
https://github.com/DevShaft/Backup-TA/issues/10
However unfortunately the original developer (Devshaft) is afk and doesn't merge it...
https://github.com/DevShaft/Backup-TA/pull/10
and
https://github.com/DevShaft/Backup-TA/issues/6
unlocked Bootloader vs Root
These things doesn't have to do with each other.
Root is "basically" when you have the su binaries in your system partition.
An unlocked bootloader you need only when you want to flash (/boot from) a non-stock / custom kernel, e.g. cyanogen mod.
Click to expand...
Click to collapse
Hiya, thank you for the reply. I am aware of what root is, the point is that the guides to root indicate you need to flash the old version of KitKat and use the expoit to gain root so the bootloader can remain locked. Then you should upgrade to lollipop while keeping root.
My point was that there are also pre-rooted images available, why not just flash a pre-rooted image using Flashtool instead of doing the exploit and stuff? Or does the pre-rooted image not flash on a locked bootloader because it has been modified?

pakjebakmeel said:
Hiya, thank you for the reply. I am aware of what root is, the point is that the guides to root indicate you need to flash the old version of KitKat and use the expoit to gain root so the bootloader can remain locked. Then you should upgrade to lollipop while keeping root.
My point was that there are also pre-rooted images available, why not just flash a pre-rooted image using Flashtool instead of doing the exploit and stuff? Or does the pre-rooted image not flash on a locked bootloader because it has been modified?
Click to expand...
Click to collapse
I have this question too.
Maybe because pre root images can have something installed that could hazardous?

I pulled the TA / DRM keys manually like this:
Code:
cd /sdcard/
dd if=/dev/block/platform/msm_sdcc.1/by-name/TA of=TA.img
md5 /dev/block/platform/msm_sdcc.1/by-name/TA TA.img
exit
exit
adb pull /sdcard/TA.img TA.img
Worked flawlessly. Then I flashed an image I rooted myself with Linux zip tools. Worked, too. TA didn't change, so I suspect you can flash a pre-rooted image without problems in the first place.

pakjebakmeel said:
Hiya, thank you for the reply. I am aware of what root is, the point is that the guides to root indicate you need to flash the old version of KitKat and use the expoit to gain root so the bootloader can remain locked. Then you should upgrade to lollipop while keeping root.
My point was that there are also pre-rooted images available, why not just flash a pre-rooted image using Flashtool instead of doing the exploit and stuff?
Click to expand...
Click to collapse
To quote someone else:
twisteroid said:
Well, because you need a recovery to flash the pre-rooted zip, and to have a recovery you have to root first. The pre-rooted SYSTEM partition cannot be flashed using Flashtool because it would not pass signature check. The only way to flash it is to use root access and a working recovery.
Click to expand...
Click to collapse
And here you are still confusing root with (locked/unlocked/whatever) bootloader:
pakjebakmeel said:
Or does the pre-rooted image not flash on a locked bootloader because it has been modified?
Click to expand...
Click to collapse
Read above this doesn't has to do with the bootloader, but rather if you have access to the system partition.
HTH

faxd said:
To quote someone else:
And here you are still confusing root with (locked/unlocked/whatever) bootloader:
Read above this doesn't has to do with the bootloader, but rather if you have access to the system partition.
HTH
Click to expand...
Click to collapse
No, no, I think I got it now but my wording is a bit off I guess. Here are my understandings:
- Flashtool flashes through Sony firmware flash mode, this mode only flashes official tft files that pass signature check. When you add root to an image it fails signature check because of the mismatching hash and it will refuse to flash.
- To flash a 'tampered' image you need to use a custom recovery as it does not refuse.
- To get a custom recovery you need to get root to be able to flash the recovery partition.
- To get root you need to downgrade and use the exploit to get the su binary on.
Correct right?
Just one more question, how does the signature check work? I would understand it if you could download images from Sony like OTA's, they'd be signed and sealed by Sony. Just like driver signing based on RSA keys and such. If you modify them they fail the signature check obviously.
But I've seen people create FTF files from their own phones and it seems to pass the signature check, how is the file signed then? What is the 'signature' check based upon? Or is the image signature included on the phone and pulled into the FTF file when the image is pulled from the phone?
So basically the question is: "Where does the signature come from if one would create an FTF file from a working phone?"
Sorry, sorry, many questions. I'm just trying to understand all details, can't stand not knowing how stuff works.. :silly: I think I at least understand the root/bootloader/recovery part now. :victory:

phre5k said:
I pulled the TA / DRM keys manually like this:
Code:
cd /sdcard/
dd if=/dev/block/platform/msm_sdcc.1/by-name/TA of=TA.img
md5 /dev/block/platform/msm_sdcc.1/by-name/TA TA.img
exit
exit
adb pull /sdcard/TA.img TA.img
Worked flawlessly. Then I flashed an image I rooted myself with Linux zip tools. Worked, too. TA didn't change, so I suspect you can flash a pre-rooted image without problems in the first place.
Click to expand...
Click to collapse
Restore goes well with this simpler method as well?

PantsDownJedi said:
Restore goes well with this simpler method as well?
Click to expand...
Click to collapse
Windows script does the exact same thing after looking at it, it does some logic for looking at the partitions a bit better is all. Hopefully nothing has changed since newer versions of Andriod.

Customized Stock Kernel {32.2.A.0.305 - 6.0.1} {Version 4}

============================={Update}{Version 4}=================================
***Fixed Bootloop On Z5 Premium
***Better Battery Life
***Advanced Thermal Configuration
***Updated SuperSu
***Updated BusyBox
***Updated DRM Patch
***Fixed Minor Bugs
============================={Update}{Version 3}=================================
***Added Support For Xperia Z5 Premium
***Fixed Screen Flickering Issue On ZP
***Optimized Kernel Size
***Updated CPU Optimizer
***Updated Thermal Driver
============================={Update}{Version 2}=================================
***Fixed all bugs of twrp.
***Fixed all bugs of kernel.
***Improved boot time.
***Kernel is now pure and very fast.
***Added CPU optimizer for better battery life (I guarantee won't affect performance)
========================================================================================
Customized Stock Kernel
This is a modified/customized kernel for the firmware 32.2.A.0.305 - 6.0.1 .
================================================================
****************************************Features****************************************
*** Thermal Manager
*** Disabled Sony RIC
*** CPU Optimizer
*** Disabled DM-VERITY
*** Added Root Support
*** Added DRM Fix
*** Added Busybox Support
*** Added TWRP Recovery
**************************************How To Install?*************************************
** Download The Zip From The Google Drive.
** Extract The Zip File And Run The Kernel Flasher!
Note : Kernel Flasher Has Some Problem So Uploaded The Boot Images Itself.
Install The Images Using :
fastboot flash boot boot.img
Note : ADB And FastBoot Should Be Installed On Your PC!
**************************************Downloads*************************************
Google Drive
MOD EDIT: no links to source
***************************************************************************************************
Please Hit Thanks If Helped
Thank You!
****************************************************************************************************

Do I need to unlock bootloader first? I have stock firmware 32.2.A.0.305. I don't want to back up my DRM, just want to have root access.

Minn14 said:
Do I need to unlock bootloader first? I have stock firmware 32.2.A.0.305. I don't want to back up my DRM, just want to have root access.
Click to expand...
Click to collapse
Well, I think it is not possible to root without unlocking the bootloader. It is recommended to backup ta partition. Unless you backup the ta partition you will not be able to use x reality engine,software updates etc..
I don't know whether a prerooted firmware can be used to root without unlocking the bootloader.

can i install TWRP with this kernel??

pandu.negara said:
can i install TWRP with this kernel??
Click to expand...
Click to collapse
I hope so.

pandu.negara said:
can i install TWRP with this kernel??
Click to expand...
Click to collapse
You can install TWRP with every kernel.
---------- Post added at 03:02 PM ---------- Previous post was at 02:24 PM ----------
heptyle said:
Well, I think it is not possible to root without unlocking the bootloader. It is recommended to backup ta partition. Unless you backup the ta partition you will not be able to use x reality engine,software updates etc..
I don't know whether a prerooted firmware can be used to root without unlocking the bootloader.
Click to expand...
Click to collapse
1. No exploit has been found, you indeed need to unlock BL to gain root access. You will lose usage of x reality engine etc once unlocked.
2. But, you are able to use x reality engine etc. as long as the DRM fix is in place in new kernel.
3. You cannot use anything else than official firmware as long as the bootloader is locked.

pandu.negara said:
can i install TWRP with this kernel??
Click to expand...
Click to collapse
Now you don't have to install twrp manually. I have merged recovery with the kernel.
Download the same from attachements.
Thank You!

HELP
Thanks Dev for all ur hard work. I am coming from a Htc One M8, rooting is very different now. Pls house help me out;
My xperia isE5803 on. 305, locked BL, unrooted. If i want root i just have to unlock BL and instal Kernel right? No need to revert back to lollipop {root} b4 installing. 305 then root again?
Pls can someone be so kind to give me steps. Dont want to loose d Sony features and updates. But need root so i dont feel like an i-sheep.

paq1170 said:
Thanks Dev for all ur hard work. I am coming from a Htc One M8, rooting is very different now. Pls house help me out;
My xperia isE5803 on. 305, locked BL, unrooted. If i want root i just have to unlock BL and instal Kernel right? No need to revert back to lollipop {root} b4 installing. 305 then root again?
Pls can someone be so kind to give me steps. Dont want to loose d Sony features and updates. But need root so i dont feel like an i-sheep.
Click to expand...
Click to collapse
If you have pc and teamviewer installed then i will do the rest.
[email protected]

paq1170 said:
Thanks Dev for all ur hard work. I am coming from a Htc One M8, rooting is very different now. Pls house help me out;
My xperia isE5803 on. 305, locked BL, unrooted. If i want root i just have to unlock BL and instal Kernel right? No need to revert back to lollipop {root} b4 installing. 305 then root again?
Pls can someone be so kind to give me steps. Dont want to loose d Sony features and updates. But need root so i dont feel like an i-sheep.
Click to expand...
Click to collapse
Not sure the backup TA tool works or not in MM, if not working you'll need down to LP first.
Okay, if you can backup your TA in 305, then yes, lock bl via Sony offical unlock site and flash the elf kernel in this thread with flashtool. Remember to flash the supersu in twrp too.

TheEndHK said:
Not sure the backup TA tool works or not in MM, if not working you'll need down to LP first.
Okay, if you can backup your TA in 305, then yes, lock bl via Sony offical unlock site and flash the elf kernel in this thread with flashtool. Remember to flash the supersu in twrp too.
Click to expand...
Click to collapse
I think it is not possible to backup TA on 305 because the ta backup tool only supports LP kernel.
You don't have to flash supersu because the kernel contains the latest supersu build.

heptyle said:
I think it is not possible to backup TA on 305 because the ta backup tool only supports LP kernel.
Click to expand...
Click to collapse
If you don't care void warranty or come with no warranty, you can just unlock the BL now.
http://www.xperiablog.net/2015/03/17/guide-to-installing-xperia-lollipop-using-xperifirm-and-flashtool/
If you need to keep the warranty, you'll need to run XperiFirm to download any 152/200 firmware and follow this guide to create the image to flash.

Did anyone experience any bug in the kernel?

heptyle said:
Did anyone experience any bug in the kernel?
Click to expand...
Click to collapse
installing your kernel now probably need a day or two to tell any problem from your kernel or 305

TheEndHK said:
installing your kernel now probably need a day or two to tell any problem from your kernel or 305
Click to expand...
Click to collapse
Ok,Thank You!

heptyle said:
Ok,Thank You!
Click to expand...
Click to collapse
Early testing showed no problem. DRM patched and twrp working fine but default set at enforcing mode, can you set the kernel to permissive mode?
OMG, opencamera can't recording 4K video(actually FHD seems not work too) on 305 while no problem on 224/253. I've to roll back and stick with XPower V3 now.

It would be so nice if you could give us the complete rom to be flashed via twrp I don't have a pc

ric69 said:
It would be so nice if you could give us the complete rom to be flashed via twrp I don't have a pc
Click to expand...
Click to collapse
is xposed integrated as well ? would be nice to have all the stuff system-less like supersu

sheraro said:
is xposed integrated as well ? would be nice to have all the stuff system-less like supersu
Click to expand...
Click to collapse
Nope! Xposed has not been integrated.

sheraro said:
is xposed integrated as well ? would be nice to have all the stuff system-less like supersu
Click to expand...
Click to collapse
You can just flash the SuperSU+Aroma+2.78-SR1+v3.zip in twrp, it got options to pick system mode or system-less mode.

DRM FIX FOR 32.3.a.0.372?????????? FOR XPERIA Z3+ SINGLE

DRM FIX FOR 32.3.a.0.372?????????? FOR XPERIA Z3+ SINGLE???????

Try
https://forum.xda-developers.com/xp...matic-repack-stock-kernel-dm-t3301605/page171
I am downloading firmware for my e6533. Will try drm fix and root after downloading.

waseemakhtar said:
Try
https://forum.xda-developers.com/xp...matic-repack-stock-kernel-dm-t3301605/page171
I am downloading firmware for my e6533. Will try drm fix and root after downloading.
Click to expand...
Click to collapse
I ain't that good at this stuff, but I was brave enough to flash a DRM-fix for Z5. It actually booted and made me able to root it, so I'm happy! It ain't my work, but I couldn't find the original post, so I hope it's okay to upload the .zip I downloaded!
Edit: Phone reacted pretty slow and camera didn't work, so trying some other things!

Downloaded the firmware and tried fix the kernel. Rootkernel v5.0 stuck at drm fix.

waseemakhtar said:
Downloaded the firmware and tried fix the kernel. Rootkernel v5.0 stuck at drm fix.
Click to expand...
Click to collapse
I have seen that you are one of the first Rooter of this phone and followed your posts.:good:
I'm Rooted running Stock firmware with custom recovery. Can I follow this guide for re-locking bootloader?
So theoritically,
1. flash a lollipop ROM using Flashtool
2. Restore TA Partition (this will relock the bootloader?)
3. Flash Marshmallow ROM and then wait for Android N update?
Do you suggest to wait for DRM fix and use Rooted Nougat?
Thanks.

waseemakhtar said:
Downloaded the firmware and tried fix the kernel. Rootkernel v5.0 stuck at drm fix.
Click to expand...
Click to collapse
Did you fix drm and root it successfully?

I have successfully rooted. Here is the guide and patched kernel if any one want.
https://forum.xda-developers.com/xp...ernel-stock-nougat-kernel-patched-dm-t3540997

GryTEcHoG said:
I have successfully rooted. Here is the guide and patched kernel if any one want.
https://forum.xda-developers.com/xp...ernel-stock-nougat-kernel-patched-dm-t3540997
Click to expand...
Click to collapse
You're the boss!

batmobile_bang said:
I have seen that you are one of the first Rooter of this phone and followed your posts.:good:
I'm Rooted running Stock firmware with custom recovery. Can I follow this guide for re-locking bootloader?
So theoritically,
1. flash a lollipop ROM using Flashtool
2. Restore TA Partition (this will relock the bootloader?)
3. Flash Marshmallow ROM and then wait for Android N update?
Do you suggest to wait for DRM fix and use Rooted Nougat?
Thanks.
Click to expand...
Click to collapse
I'm not a developer, just a common user.

[Root][sm-n9600]Root no TWRP method[Sept 21]

This method really is only a workaround for root while TWRP is getting it's finishing touches
You need oem unlock to complete this root method.
Magisk modules aren't installing, but may be an easy environmental fix. But root is there.
This boot.img has been taken from TGY Hong Kong firmware. There is a big chance this won't work on any other firmware. If you want to risk it, then have a full Odin firmware ready to flash.
If you upload your stock boot.img to me, I will pre patch them also but the method is really quite simple to do yourself.
Magisk has the ability to patch a boot.img that is on your sdcard. So by installing the magisk manager apk, you can then patch the boot.img. Then all you have to do is package it into a .tar and flash it with Odin.
Download folder
https://mega.nz/#F!H19RQLRD!f9lCXblRXyfZ6b090eU73w
--->

Incredible! Thank so you much.
I have the same model and Hong Kong firmware. So am I to just download and odin flash the tar file?
Latest odin will do? Or is the modified version preferred?

How can you tell if you have Hong Kong firmware on your device

Mekael162 said:
How can you tell if you have Hong Kong firmware on your device
Click to expand...
Click to collapse
Look for TGY under software information/software provider SW ver

FYI I have just found modules don't install, but root is present at least.
[emoji450] --->

Root for N9600 running nicely for me here

Thanks for work!!.

Do you have to run that crom app to unlock the bootloader?

elevatorguy said:
Do you have to run that crom app to unlock the bootloader?
Click to expand...
Click to collapse
Nope just need oem unlocked.

TGY firmware patch boot image file failed
SM-N9600ZKDTGY
AP-N9600ZHU1ARH2
- Copying image to cache
- Device platform: arm64-v8a
- Existing zip found
- Extracting files
- Unpacking boot image
MagiskBoot v17.1(17100) (by topjohnwu) - Boot Image Modification Tool
Parsing boot image: [/data/user_de/0/com.topjohnwu.magisk/install/boot.img]
! Sony ELF64 format detected
! Stock kernel cannot be patched, please use a custom kernel
! Installation failed
My English is pretty basic, please don't mind... :silly::silly::silly:

Hello everyone. Can you tell me if this model N9600 can use the stock FM Radio after Rooting? Thanks

chengddjack said:
SM-N9600ZKDTGY
AP-N9600ZHU1ARH2
- Copying image to cache
- Device platform: arm64-v8a
- Existing zip found
- Extracting files
- Unpacking boot image
MagiskBoot v17.1(17100) (by topjohnwu) - Boot Image Modification Tool
Parsing boot image: [/data/user_de/0/com.topjohnwu.magisk/install/boot.img]
! Sony ELF64 format detected
! Stock kernel cannot be patched, please use a custom kernel
! Installation failed
My English is pretty basic, please don't mind... :silly::silly::silly:
Click to expand...
Click to collapse
TGY is the img i rooted already. Just download that.
--->

jotade said:
Hello everyone. Can you tell me if this model N9600 can use the stock FM Radio after Rooting? Thanks
Click to expand...
Click to collapse
I have radio on the TGY firmware
--->

lawtq said:
Incredible! Thank so you much.
I have the same model and Hong Kong firmware. So am I to just download and odin flash the tar file?
Latest odin will do? Or is the modified version preferred?
Click to expand...
Click to collapse
Im pretty sure im using stock odin, and yes to just flash the file.
--->

Mentalmuso said:
I have radio on the TGY firmware
--->
Click to expand...
Click to collapse
Thanks Friend. Im buying this model because i want to root it and also i need FM Radio. Is everything working after root?

jotade said:
Thanks Friend. Im buying this model because i want to root it and also i need FM Radio. Is everything working after root?
Click to expand...
Click to collapse
So far I haven't noticed any issues except for Magisk root itself. Modules can't be installed, but I may figure a workaround for that if TWRP doesn't rectify a few things soon. It's probable TWRP will be fully functional soon though. It's all related to the kernel.
--->

TGY
Mentalmuso said:
TGY is the img i rooted already. Just download that.
--->
Click to expand...
Click to collapse
Thank you for everything you have done for me,
This is a great help, I will do a flash test later and pay back.
If you are free, can you explain the error there?
Very grateful!!!

Questions from a samsung-noob:
1. Will this method also trip knox?
2. Do I still need to factory reset after enabling oem unlock?

chengddjack said:
Thank you for everything you have done for me,
This is a great help, I will do a flash test later and pay back.
If you are free, can you explain the error there?
Very grateful!!!
Click to expand...
Click to collapse
I don't know where you got that kernel from to patch, but seeing that it says Sony in the error. I would imagine it is the seeing boot.img
[emoji450]--->

otaconremo said:
Questions from a samsung-noob:
1. Will this method also trip knox?
2. Do I still need to factory reset after enabling oem unlock?
Click to expand...
Click to collapse
Yes and yes.
Rooting will always trip Knox. Basically anything that mods away from stock will trip Knox. And there is no going back after. You will never be able to use Samsung pay or secure folder again after.
[emoji450]--->