Database Users

How to root LG D802 with 220H firmware ?

Hi,
Is there any reasonably safe way to root LG D802 (international ANEUBK version) with latest 220H update installed ? The phone was never rooted before. I know how to use ADB, etc.
Thanks !

Cst79 said:
Hi,
Is there any reasonably safe way to root LG D802 (international ANEUBK version) with latest 220H update installed ? The phone was never rooted before. I know how to use ADB, etc.
Thanks !
Click to expand...
Click to collapse
Towelroot

azher98 said:
Towelroot
Click to expand...
Click to collapse
Doesn't work, it sais "phone is not supported". I understand that towelroot exploits a Linux kernel loophole that was patched around June 3.

Ioroot by side loading in stock recovery, or stump root, the only two ways for rooting 20h, powered by codefire team members (those who made Bump! )
http://forum.xda-developers.com/showthread.php?t=2448887
http://forum.xda-developers.com/showthread.php?t=2850906

6ril1 said:
Ioroot by side loading in stock recovery, or stump root, the only two ways for rooting 20h, powered by codefire team members (those who made Bump! )
http://forum.xda-developers.com/showthread.php?t=2448887
http://forum.xda-developers.com/showthread.php?t=2850906
Click to expand...
Click to collapse
Sorry, but I just gave up on it. Everything is such a mess regarding tools, versions, download locations...I will probably just wait for the official Lollipop update (the reason why I wanted to root was to install CM12 eventually).

Cst79 said:
Sorry, but I just gave up on it. Everything is such a mess regarding tools, versions, download locations...I will probably just wait for the official Lollipop update (the reason why I wanted to root was to install CM12 eventually).
Click to expand...
Click to collapse
It's very simple:
1) download ioroot:
http://downloads.codefi.re/autoprime/LG/ioroot/ioroot.zip
2) extract datroot.zip from the archive just downloaded (from bts folder)
3) on the G2 enable dev option (Settings - About Phone. Then go to the bottom and you should see Build Number. This needs to be pressed a total of seven times. You should get a message at the fourth press. On the seventh, you'll get another message saying that Developer Options are unlocked.)
4) enable usb debug on the phone (Development Settings Enable USB Debugging)
5) plug the phone in usb with the pc and accept yhe RSA Fingerprint message.
6) reboot your phone in recovery with adb cmd (tape cmd: adb reboot recovery)
7) choose 'apply update from adb' in the phone recovery menu (navigate with vol down and valid with power)
8) in the pc tape cmd: adb sideload c:\datroot.zip
9) reboot et enjoy
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

6ril1 said:
It's very simple:
Click to expand...
Click to collapse
Thank you, I figured these steps but:
- On one ioroot post (old post - first in thread I think) , they say that I cannot easily install custom recovery without some modified kernel ?? Are you sure I can install TWRP after rooting in order to ensure a way to flash images ?
- Also, can I revert to 100% stock after this (including baseband, bootloader, etc.), if I want to ? If so, with what tools and steps ? This information is very valuable to me.
- Right now I cannot enter recovery mode pressing the Vol Down + power then waiting for LG logo then pressing them again or power button 3 times, no matter what. I can only do this with "adb reboot recovery". Why is this ?
Thanks !

Cst79 said:
Thank you, I figured these steps but:
- On one ioroot post (old post - first in thread I think) , they say that I cannot easily install custom recovery without some modified kernel ?? Are you sure I can install TWRP after rooting in order to ensure a way to flash images ?
- Also, can I revert to 100% stock after this (including baseband, bootloader, etc.), if I want to ? If so, with what tools and steps ? This information is very valuable to me.
- Right now I cannot enter recovery mode pressing the Vol Down + power then waiting for LG logo then pressing them again or power button 3 times, no matter what. I can only do this with "adb reboot recovery". Why is this ?
Thanks !
Click to expand...
Click to collapse
The bootloader is locked. Untill recently, there was only one way to work around it, loki patch.
Only JB bootloader was lokiable, LG patched the KK one and loki doesn't work on it.
So, with loki, you had to downgrade bootloader for being able to apply loki. KK kernel must be patched too for being able to boot behind the downgraded bootloader. All the method for installing a custom recovery with this system was automated by the app autorec.
Recently, Bump was made. it permits to stay with kk booloader. It inject in the kernel (custom recovery and custom kernel) LG authentic Key.
You can easily revert to stock by flashing kdz, or even flashing zip that contains original partition.
I don't understand you last question.

6ril1 said:
The bootloader is locked. Untill recently, there was only one way to work around it, loki patch.
Only JB bootloader was lokiable, LG patched the KK one and loki doesn't work on it.
So, with loki, you had to downgrade bootloader for being able to apply loki. KK kernel must be patched too for being able to boot behind the downgraded bootloader. All the method for installing a custom recovery with this system was automated by the app autorec.
Recently, Bump was made. it permits to stay with kk booloader. It inject in the kernel (custom recovery and custom kernel) LG authentic Key.
You can easily revert to stock by flashing kdz, or even flashing zip that contains original partition.
I don't understand you last question.
Click to expand...
Click to collapse
Sorry, but you lost me here. I can't map your answers to my simple questions. My simple questions are:
- Can I revert to 100% factory stock, if I mess with rooting and install CyanogenMod 12 ? If yes, how ?
- After rooting with ioroot (what's the difference between ioroot and ioroot25 ??) what is the simplest way to install CyanogenMod 12 ? I don't really care about TWRP and such if I don't need to.
I'm really not a noobie, but not living in this world of phone hacking I can't figure out the names, versions, etc.
Thanks !

Cst79 said:
Sorry, but you lost me here. I can't map your answers to my simple questions. My simple questions are:
- Can I revert to 100% factory stock, if I mess with rooting and install CyanogenMod 12 ? If yes, how ?
- After rooting with ioroot (what's the difference between ioroot and ioroot25 ??) what is the simplest way to install CyanogenMod 12 ? I don't really care about TWRP and such if I don't need to.
I'm really not a noobie, but not living in this world of phone hacking I can't figure out the names, versions, etc.
Thanks !
Click to expand...
Click to collapse
No offense, but I tried to answer you on technical aspects, but I perceive me that your questions are more general order.
it takes time to explain what is custom recovery, and there are already tons of readings that relate to this topic.
I answered to your principal question, how to root 80220H.
As i said in my previous edited answer, you can go back to stock if you need.
I also realize that this thread should instead be placed in question/answer section, not in a dev section.

6ril1 said:
No offense, but I tried to answer you on technical aspects, but I perceive me that your questions are more general order.
it takes time to explain what is custom recovery, and there are already tons of readings that relate to this topic.
I answered to your principal question, how to root 80220H.
As i said in my previous edited answer, you can go back to stock if you need.
I also realize that this thread should instead be placed in question/answer section, not in a dev section.
Click to expand...
Click to collapse
Hello,
No, my questions are not generic, I want to find out:
- How do I install CyanogenMod 12 after I root the phone.
- What are the steps to revert to 100% stock after I root the phone and install CM12; Can I just use the LG flash tool and flash the kdz with no complains from the LG software if I have CM12 installed ?
Thanks.

Do you loss data with this metod?
Thanks

D6503 [6.0.1] 23.5.a.0.570 prerooted+recovery+xposed [unlocked/locked bootloader]

XPERIA Z2 D6503 23.5.A.0.570 UNLOCKED/LOCKED BOOTLOADER
FLASHABLE ZIP
YOU WANT THE NEW ANDROID 6.0.1 MARSHMALLOW UPDATE ON YOUR XPERIA Z2 BUT YOU WANT TO KEEP ROOT, RECOVERY & XPOSED?
THEN KEEP READING THIS THREAD! ​
features::angel:
prerooted (BETA-SuperSU-v2.68)
recovery (twrp)
byeselinux
RICDefeat
bootloop fix
signed zip file
optional:
xposed framework v82
Sound 3 in 1 Bass Loud Stereo MM
DMR Function Restore V3 [Team HSxEXR]
and more!#
ftf:
D6503_23.5.A.0.570_1281-9715_R4D [AUSTRALIA]
https://youtu.be/Zx02x357Mo0​
Checklist:
lollipop (stock or stock based)
root
busybox
recovery
USB Debugging + Unknown Sources
ADB Drivers
non-xposed stock (USE xposed-UNINSTALLER)
Introduction:
Download the "Marshmallow_D6503.zip"
extract the zip file
boot into recovery
X. OPTIONAL flash "xposed-uninstaller-20150831-arm.zip" to remove LP xposed
FACTORY RESET
flash "flashableMM.zip"
flash "byeselinux_flashable.zip"
flash "RICDefeat.zip"
flash "Z2-6.0.1_570_bootloop_fix.zip"
wipe cache & dalvik
now it`s time to flash your favourite zip files like:
X. OPTIONAL XPOSED flash "xposed-v82-sdk23-arm.zip"
X. OPTIONAL UB flash "[Team HSxEXR] DRM function restore V3.zip"
X. OPTIONAL UB SOUND flash "Sound 3 in 1 Bass Loud Stereo MM.zip"
wipe cache & dalvik
reboot
install "BusyBox.apk" and install newest available version
X. OPTIONAL install "XposedInstaller_3.0_alpha4" for Xposed
Enable USB Debugging + Unknown Sources
Run "install.bat from /Z2_MM_TWRP_Recovery_V2_By_Serajr/ to install the Recovery
connect the Z2 to PC, phone will reboot into twrp
DONE:victory:
GOT TROUBLE WITH YOUR RECOVERY? RECOVERY FIX in 2 MINUTES:
open any root explorer app like ES FILE MANAGER
Delete /system/etc/mm_twrp_recovery folder
Go to /system/bin/ folder
Look for the "chargemon.stock" file - If it's present, delete this one: chargemon - and now, rename the chargemon.stock to chargemon
Look for the "taimport.stock" file - If it's present, delete this one: taimport - and now, rename the taimport.stock to taimport
Reboot
download "recovery fix.zip" from mega.nz
extract the file and run "adbrecoveryfix.exe" the .exe file will install some needed files (normally into C:\Minimal ADB and Fastboot\ )
copy the files from the folder "RECOVERY FILES" into the "Minimal ADB and Fastboot" Folder
connect your xperia with the pc
open the "m a a d" folder and then SHIFT+RIGHT CLICK to open a command window
now type:
adb shell
su root
mount -o remount,rw /system
exit
exit
install.bat
Click to expand...
Click to collapse
don´t forget to press enter after "adb shell", "su root" and so on!
now your recovery will install again without any errors!
MEGA.nz] DOWNLOAD:
OPTIONAL UB... optional step for unlocked bootloader
OPTIONAL... optional step for locked and unlockedd bootloader
DO NOT FORGET THAT IF YOU HAVE A LOCKED BOOTLOADER YOU ARE NOT ALLOWED TO FLASH ZIPS FOR UB LIKE THE DMR FUNCTION V3 ZIP FILE!
LIST OF WORKING FLASHABLE ZIPS:
xposed framework v82 sdk 23 arm [XPOSED
Sound 3 in 1 Bass Loud Stereo MM [SOUND MOD]
DRM function restore V3 [UB MOD]

thank you!
:good:
seems to work fine on my z2
can I also flash other zips like this one:
http://forum.xda-developers.com/xperia-z2/general/6-0-1-d6503-23-5-0-570-prerooted-t3364817
?

elitephantompro said:
:good:
seems to work fine on my z2
can I also flash other zips like this one:
http://forum.xda-developers.com/xperia-z2/general/6-0-1-d6503-23-5-0-570-prerooted-t3364817
?
Click to expand...
Click to collapse
if the zip file is comptible with marshmallow and the z2 of course you can i recommand to flash the zip files directly after "the bootloop fix file wipe"!

Recovery fix
UPDATE:
I FINALLY FOUND A SOLUTION FOR THE AFTER A WHILE DISAPPERAING TWRP RECOVERY!
SOMETIMES IT`s GOOD TO SEARCH IN OLDER THREADS

Problem! :/
I have some problems about speaker and headset with microphone.
Anyone can't hear me when I speak with speaker
And I can't talk to anyone with headphone. I hear toppy sound.
I think problems source is boomsound, how can I uninstall other extra mods?

Help me please!
I followed all the instructions but at the end my phone ended up in bootloop. How can I recover my phone now?
Please help, Thanks!

SoloTheWolf said:
I followed all the instructions but at the end my phone ended up in bootloop. How can I recover my phone now?
Please help, Thanks!
Click to expand...
Click to collapse
Well if you don't have recovery you have to flash a ftf with flashtool.
If u have recovery you can wipe amd start the process again.
Have you tried the MMbootloop
fix.zip?

nice tutorial
works 100%

SoloTheWolf said:
I followed all the instructions but at the end my phone ended up in bootloop. How can I recover my phone now?
Please help, Thanks!
Click to expand...
Click to collapse
did you flash the bootloop fix.zip? did you try to flash a recovery like the NUT`s Dualrecovery after flashing the needed files? because there is no working recovery except the one in my tutorial! try to only flash the needed files, and skip every optional step! you can try all the zips you want to install after installing the twrp recovery. this tutotial works 100%

Abdülcelil said:
I have some problems about speaker and headset with microphone.
Anyone can't hear me when I speak with speaker
And I can't talk to anyone with headphone. I hear toppy sound.
I think problems source is boomsound, how can I uninstall other extra mods?
Click to expand...
Click to collapse
hey! you installed a soundmod? then i am sorry, you have to reinstall a lollipop ftf, root it (i do it with kingsroot) and install a recovery (i prefer NUT`s dualrecovery)
then do the whole procedure again but skip all the oiptional steps with xposed and so on! dont forget to install the recovery, and use the fix if it disappears after using it for one time. after doing that, check your sound, if its not working, its 100% a hardware bug. if its working, make a full backup using the recovery, and then flash one zip file, check if sound is working, then flash another one (mabye it`s becasue of an incompatible zip!) thats why you should backup the system.

freaky2xd said:
hey! you installed a soundmod? then i am sorry, you have to reinstall a lollipop ftf, root it (i do it with kingsroot) and install a recovery (i prefer NUT`s dualrecovery)
then do the whole procedure again but skip all the oiptional steps with xposed and so on! dont forget to install the recovery, and use the fix if it disappears after using it for one time. after doing that, check your sound, if its not working, its 100% a hardware bug. if its working, make a full backup using the recovery, and then flash one zip file, check if sound is working, then flash another one (mabye it`s becasue of an incompatible zip!) thats why you should backup the system.
Click to expand...
Click to collapse
I actually don't know these things. I just like some advantages of root and wanted to see android mm. I actually don't know what should I do. If there is a video, instruction, photo etc. I follow them and do it. Could you tell me what should I do at first? If I just turn back to 5.1.1 pre rooted and do that process again, will it be fixed?

not worked
it says md5 skipping (sucessful in 1 sec). pls help sony z2

use my own tft file with your tutorial
Hello, I am still waiting for release of CE1 .570 version by Sony. After that I want to create my own pre-rooted file. Should it work with your tutorial? Any special steps needed when creating own tft file to make it work with your tutorial?

miroslav.novotny said:
Hello, I am still waiting for release of CE1 .570 version by Sony. After that I want to create my own pre-rooted file. Should it work with your tutorial? Any special steps needed when creating own tft file to make it work with your tutorial?
Click to expand...
Click to collapse
of course you can use another .570 ftf for the z2! it works the same way, all the zip files (most important the bootloopfix) do work.
but you have to use the same supersu zip file like in my flashablemm file! download it and extract the supersu zip out of the flashablemm zip using winrar you can also try the newest beta from supersu but the one i used is more likely to be safe. (NOT 2.46!!!) just use the prf creator, select your ftf, for root select the supersu zip i used, CHECK all the features (in the right upper box) like fotakernel and so on and ckeck "sign" the zip file to avoid trouble while flashing it. you are invited to press the thanks button!

SidhuZ said:
it says md5 skipping (sucessful in 1 sec). pls help sony z2
Click to expand...
Click to collapse
model= D6503 or D6502?
did you wipe cache and dalvik and made a factory reset via recovery before trying to flash the flashablemm?
of course you need to exctract all the files from "Marshmallow_D6503.zip" and then flash "FlashableMM.zip" and then the other files like me...
maybe you " checked" something like "zip file signature verification" before "swipe to confirm flash"?
try it with and without enabling the zip file signature verification.
if it still doesnt work`, redownload the file! maybe the file got broken while downloading it

miroslav.novotny said:
Any special steps needed when creating own tft file to make it work with your tutorial?
Click to expand...
Click to collapse
I just tried make my own prerooted flashable zip from US ftf and it works for me. See pic. of my settings.
Now i have [LB] D6503 .570 fw SuperSu 2.71 and twrp 3.0.2.0 after rebooting to twrp again I flashed busybox 1.24
Good luck
btw. Do you have any specific reason to wait for CE ftf. You always can disable /uninstall all bloatware with TB.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

petrmelis said:
I just tried make my own prerooted flashable zip from US ftf and it works for me. See pic. of my settings.
Now i have [LB] D6503 .570 fw SuperSu 2.71 and twrp 3.0.2.0 after rebooting to twrp again I flashed busybox 1.24
Good luck
btw. Do you have any specific reason to wait for CE ftf. You always can disable /uninstall all bloatware with TB.
Click to expand...
Click to collapse
I see you used higher version of (beta) SuperSU, any reason? Or you just wanted to try and it worked?
I have no special reason waiting for CE1 .570 apart from wanting to have ROM for my region (despite the fact most of the ROM code is probably the same)
freaky2xd said:
of course you can use another .570 ftf for the z2! it works the same way, all the zip files (most important the bootloopfix) do work.
but you have to use the same supersu zip file like in my flashablemm file! download it and extract the supersu zip out of the flashablemm zip using winrar you can also try the newest beta from supersu but the one i used is more likely to be safe. (NOT 2.46!!!) just use the prf creator, select your ftf, for root select the supersu zip i used, CHECK all the features (in the right upper box) like fotakernel and so on and ckeck "sign" the zip file to avoid trouble while flashing it. you are invited to press the thanks button!
Click to expand...
Click to collapse
Thanks freaky2xd, maybe will give it a try even before the CE1 .570 release!

miroslav.novotny said:
I see you used higher version of (beta) SuperSU, any reason? Or you just wanted to try and it worked?
I have no special reason waiting for CE1 .570 apart from wanting to have ROM for my region (despite the fact most of the ROM code is probably the same)
Thanks freaky2xd, maybe will give it a try even before the CE1 .570 release!
Click to expand...
Click to collapse
I used the supersu beta because the newest "stable" version 2.46 doesn`t with Xperia´s marshmallow! but don`t panic, the beta zips are nearly as stable as the 2.46 but not finally completed for marshmallow. when the final supersu zip for marshmallow is available you can download and simply flash it on your marshmallow system if you want. I used this supersu version because I knew 100% that it will work. everything higher than the version I used will work too

petrmelis said:
....btw. Do you have any specific reason to wait for CE ftf. You always can disable /uninstall all bloatware with TB.
Click to expand...
Click to collapse
Just wanted to make sure it will be the same as I have currently.
BTW where did you get the Z2_RecRootV3_combined.zip? I can find only RecrootV4 for Z3 in some other thread....

BTW where did you get the Z2_RecRootV3_combined.zip? I can find only RecrootV4 for Z3 in some other thread....
Click to expand...
Click to collapse
I took it from here: http://forum.xda-developers.com/showpost.php?p=66534297&postcount=535
I dont know what is a different between V3 and V4 except V3 has Z2 in its name.

TWRP for Z3 compact ; Unlocked Bootloader - GUIDE

Hey guys! Here is how to get recovery for your Z3 Compact without losing any files or flashing any kernels, as this could usually be a pain in the butt if you need a kernel for a custom rom...
I do not take credit for any of the resources in this guide and neither do i take any responsibility for bricked phones,dead SD cards or death
Click to expand...
Click to collapse
Prerequisites
1. Unlocked Bootloader (Its fairly easy to do, a simple google would suffice)
2. TWRP image- Get it Here
3. Flashtool installed with all required drivers
4. ADB and Fastboot (Here)
5. Patience
How to Install
1. Make sure you have an unlocked bootloader or this will, and shall not work.
2. Make sure you are running the latest firmware (.291). If not, use flashtool to update to the latest firmware.
3. Copy the downloaded TWRP image to your adb/fastboot folder and rename it recovery.img for ease.
4. Click shift+right click in any empty space in your adb/fastboot folder and click open command window here.
5. switch off your z3c. press the vol up button and insert USB cable to boot into fastboot mode
6. Make sure everything is working by typing
Code:
fastboot devices
in the cmd window. If all is well, then it should show your device's serial along with fastboot written beside it.
7. Time to flash the recovery:
Type in this command
Code:
fastboot flash recovery recovery.img
Congrats! You now have a recovery
8. To enter recovery mode, power off your phone, and press and hold Vol-down and Power button together until you see the sony logo.
You can now flash any rom or zips you want with this recovery, for root, flash the latest SuperSu Zip from chainfire.
I would also recommend flashing DRM fix zip.
If you want a better version of the stock rom, i will recommend installing SliMM Rom by Wajk
Note: This TWRP can get uninstalled in some cases, for example flashing a rom with twrp built in. But repeat the same process to get TWRP back without losing any data!
Thanks!

Hi, I'm from Brazil and I just bought a used D5833.
As usual, as soon as I bought the device, I did the procedure to unlock Bootloader without knowing that it was not necessary to get root and neither of the side effects of the unlock (about the quality of the camera and etc).
However the whole procedure worked well to install RECOVERY but I still could not get root.
I am using a MM 6.0.1 and TWRP 3.0.2-1 and the problem is always the same at the time of doing the FLASH in Supersu:
Boot image patcher
Finding boot image
--- boot image: / dev / block / mmcblk0p14
extracting ramdisk
Failure, aborting
I tried with the following versions of SUPERSU:
UPDATE-SuperSU-v2.65-20151226141550.zip
BETA-SuperSU-v2.68-20160228150503.zip
UPDATE-SuperSU-v2.76-20160630161323.zip
SR4-SuperSU-v2.78-SR4-20161115184928.zip
Older versions cause a bootloop
I keep looking but I can not do ROOT
I would even like to install the SliMM ROM but you need root first.
Could you help me ??

dansan691 said:
Hi, I'm from Brazil and I just bought a used D5833.
As usual, as soon as I bought the device, I did the procedure to unlock Bootloader without knowing that it was not necessary to get root and neither of the side effects of the unlock (about the quality of the camera and etc).
However the whole procedure worked well to install RECOVERY but I still could not get root.
I am using a MM 6.0.1 and TWRP 3.0.2-1 and the problem is always the same at the time of doing the FLASH in Supersu:
Boot image patcher
Finding boot image
--- boot image: / dev / block / mmcblk0p14
extracting ramdisk
Failure, aborting
I tried with the following versions of SUPERSU:
UPDATE-SuperSU-v2.65-20151226141550.zip
BETA-SuperSU-v2.68-20160228150503.zip
UPDATE-SuperSU-v2.76-20160630161323.zip
SR4-SuperSU-v2.78-SR4-20161115184928.zip
Older versions cause a bootloop
I keep looking but I can not do ROOT
I would even like to install the SliMM ROM but you need root first.
Could you help me ??
Click to expand...
Click to collapse
No, you can install SliMM directly. To get root, you should be using armv23 version... Try this. Also, you should use a DRM restore zip to get back camera quality

Clarification
Should I have to flash DRM Fix every time I flash TWRP?

andry360 said:
Should I have to flash DRM Fix every time I flash TWRP?
Click to expand...
Click to collapse
No need. But if you change reflash ROM, you might need to

i was able to flash to recovery but ive tried tons of version of supersu but still cant get root access, can you give a step by step instructions on how to? thank you so much.

epiii_nephrine said:
i was able to flash to recovery but ive tried tons of version of supersu but still cant get root access, can you give a step by step instructions on how to? thank you so much.
Click to expand...
Click to collapse
Can you please give me the error you get?

panzerox123 said:
Can you please give me the error you get?
Click to expand...
Click to collapse
Boot image patcher
Finding boot image
--- boot image: / dev / block / mmcblk0p14
extracting ramdisk
Failure, aborting
ive tried almost all versions of supersu.
im running the latest stockfirware.
i hope you could help, i really need to get root access on my d5833. thanks

epiii_nephrine said:
Boot image patcher
Finding boot image
--- boot image: / dev / block / mmcblk0p14
extracting ramdisk
Failure, aborting
ive tried almost all versions of supersu.
im running the latest stockfirware.
i hope you could help, i really need to get root access on my d5833. thanks
Click to expand...
Click to collapse
Alright... I know what's up. If you can wait till 9PM IST today, I will create another guide. Thanks!

To Get Root
As I can see, many people are having trouble getting root on their devices. You cannot directly get root on .291 as far as I know.
But since I do not use the stock firmware, there is no way for me to test. I will be using you people as testers now. I know of two methods. First , the shorter one. I got the supersu from Xperience ROM.
Please try this and let me know. Otherwise, the other method is pretty hard and requires flashing kernels.
Download the file from the attachment down.
 @epiii_nephrine

panzerox123 said:
As I can see, many people are having trouble getting root on their devices. You cannot directly get root on .291 as far as I know.
But since I do not use the stock firmware, there is no way for me to test. I will be using you people as testers now. I know of two methods. First , the shorter one. I got the supersu from Xperience ROM.
Please try this and let me know. Otherwise, the other method is pretty hard and requires flashing kernels.
Download the file from the attachment down.
@epiii_nephrine
Click to expand...
Click to collapse
Thank you so much sir! will be testing this version.. i'll let you know :good:

epiii_nephrine said:
Thank you so much sir! will be testing this version.. i'll let you know :good:
Click to expand...
Click to collapse
Sure! If this does not work, I have another method.

After installing the recovery. Every time i reboot my mobile. It goes to TWRP directly.

smahio said:
After installing the recovery. Every time i reboot my mobile. It goes to TWRP directly.
Click to expand...
Click to collapse
Doesn't make any sense... It would so that only if you flashed to boot partition. Download EliteKernel V3 , extract the zip, keep the boot.img in your minimal adb folder and do
Fastboot flash boot boot.img
Then try again

I am having issue with TWRP 3.0.2-1 on my D5833. 3.0.2-0 and other previous versions ran without problem on my Z3C but the display problem occurred in TWRP 3.0.2-1 and the situation is similar with the photo below. (It was running an AOSP 7.1 ROM for Z3C D5803, the bottom of the screen could not display correctly, and the entire screen was flashing)
According to my observations, when my D5833 was running TWRP 3.0.2-1, the color temperature of the interface was colder than that of 3.0.2-0, I guess that's due to a change in the graphics mode or something similar, and once I set the color temperature to warmer (i.e. change the display mode), it will display everything correctly. However, I just can't figure out how to do that, maybe editing some codes? Can anyone please help me?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

ewjy said:
I am having issue with TWRP 3.0.2-1 on my D5833. 3.0.2-0 and other previous versions ran without problem on my Z3C but the display problem occurred in TWRP 3.0.2-1 and the situation is similar with the photo below. (It was running an AOSP 7.1 ROM for Z3C D5803, the bottom of the screen could not display correctly, and the entire screen was flashing)
According to my observations, when my D5833 was running TWRP 3.0.2-1, the color temperature of the interface was colder than that of 3.0.2-0, I guess that's due to a change in the graphics mode or something similar, and once I set the color temperature to warmer (i.e. change the display mode), it will display everything correctly. However, I just can't figure out how to do that, maybe editing some codes? Can anyone please help me?
Click to expand...
Click to collapse
Sh*t this is bad. I dont think it has anything to do with twrp. Try reinstalling stock android marshmallow.
If that doesnt work, than it is a definite problem with hardware.

panzerox123 said:
Sh*t this is bad. I dont think it has anything to do with twrp. Try reinstalling stock android marshmallow.
If that doesnt work, than it is a definite problem with hardware.
Click to expand...
Click to collapse
Thanks for the reply. I have tried to reinstall the stock ROM and many other methods but no one would fix the display problem of TWRP 3.0.2-1 and most third-party ROMs. There are only three types of ROMs can run without display problems on my D5833: stock Sony Xperia ROM, official CyanogenMod 12.1 builds and any third-party ROMs mainly based on stock Xperia ROM and / or CM. CM builds higher than 12.1 will occur the display problems too.
I remember there is another characteristic: the boot screen can indicate the situation - when the boot screen shows "SONY" logo at the center with "XPERIA" logo at the bottom, there is NO display problem. When the boot screen only shows "SONY" logo and the bottom is empty, there WILL BE display problem. It's quite weird.

ewjy said:
Thanks for the reply. I have tried to reinstall the stock ROM and many other methods but no one would fix the display problem of TWRP 3.0.2-1 and most third-party ROMs. There are only three types of ROMs can run without display problems on my D5833: stock Sony Xperia ROM, official CyanogenMod 12.1 builds and any third-party ROMs mainly based on stock Xperia ROM and / or CM. CM builds higher than 12.1 will occur the display problems too.
I remember there is another characteristic: the boot screen can indicate the situation - when the boot screen shows "SONY" logo at the center with "XPERIA" logo at the bottom, there is NO display problem. When the boot screen only shows "SONY" logo and the bottom is empty, there WILL BE display problem. It's quite weird.
Click to expand...
Click to collapse
oh OK. If this problem did not exist on older version of TWRP, then using the same method, roll back to twrp 3.0.2-0. you just need to download that file. All the best!

panzerox123 said:
oh OK. If this problem did not exist on older version of TWRP, then using the same method, roll back to twrp 3.0.2-0. you just need to download that file. All the best!
Click to expand...
Click to collapse
Indeed there will be no problem for older versions. However, I am still unable to install and run many third-party ROMs smoothly, that means the number of ROMs I can try out is limited. Anyway, that is alright, thanks for your reply.

ewjy said:
Indeed there will be no problem for older versions. However, I am still unable to install and run many third-party ROMs smoothly, that means the number of ROMs I can try out is limited. Anyway, that is alright, thanks for your reply.
Click to expand...
Click to collapse
Funny... It works very well for me... In fact it's much more stable than previous versions

[Guide] Nougat with DRM fix, root and TWRP* (SGP771)

Do not work with Nougat 7.1.1 / 32.4.A.0.160 (Bootloop)
New TWRP (You dont need otg and mouse anymore!):
https://www.androidfilehost.com/?fid=745425885120733410 (thanks to andralex8!)
GUIDE UPDATED, TESTED AND SIMPLIFIED 15.2.2017 (thanks to munjeni)
Tested with Saudi Arabia, Germany and Nordic (.378) firmwares
I managed to get my Xperia Z4 Tablet (SGP771) LTE model to have root, TWRP-recovery*, munjenis DRM fix and Adaway working with Nougat firmware (Saudi Arabia). I will share steps that I have done with my own tablet. If this guide brick your device or something goes wrong, I am not responsible for loss of your device. Use this guide only with your own RISK!
This tutorial is not for beginners. You need to have working adb installed yout pc, unlocked tablet, sonys special driver for fastboot. and TA backup (example TA-21062016.img). Use only this tutorial with Sony USB-cable.
*To get TWRP working, you need: OTG-cable and a mouse with wire or wireless mouse with a dongle.
0. Download Nougat 32.3.A.0.376 (Saudi Arabia) firmware with Xperiafirm 32.3.A.0376. to your PC
1. Flash Nougat 32.3.A.0.376 (Saudi Arabia) with Flashtool 0.9.23.2.
2. Boot your device and enable Developer settings from setting
3. Enable USB debugging setting from Developer settings
4. Download Supersu and Magisk to your device:
https://s3-us-west-2.amazonaws.com/supersu/download/zip/SuperSU-v2.79-201612051815.zip
http://tiny.cc/latestmagisk
5. Shutdown your device
6. Download munjenis DRM fix and serajr script package v2 to your pc:
http://munjeni.myiphost.com/ta_poc.rar
https://forum.xda-developers.com/showpost.php?p=70959962&postcount=65
7. Decompress files from munjeni and serajir to same folder.
8. Extract kernel.sin from your nougat firmware ftf (You can use 7zip to do this). Copy it to same folder with DRM fix. Rename kernel.sin to kernelX.sin
9. Copy your TA backup to same folder with DRM fix and rename it TA.img
10. Open Cmd with admistrator persimmions and use DOUBLECLICKME_NOUGAT.bat (search cmd rght mouseclick use admistrator).
11. Follow munjenis tool tutorial: You can choose if you want Sony Ric off. I left it on but turned dm verity off.
12. Download TWRP: https://drive.google.com/drive/folders/0B0j3VJ1Xp5N8cnhQamtxRWVtRmc
13. Press vol up and connect your device to pc to use fastboot. Use command: fastboot flash boot new_boot.img
14. After that use command: fastboot flash recovery TWRP-3.0.2-0-20160604.img
15. Disconnect your device and put otg-cable to tablets usb and connect mouse to otg-cable.
16. Press vol down + power to boot to TWRP. Touchscreen is not workin but you can use your mouse to navigate in TWRP!
17. Allow TWRP to make changes to your device and flash Supersu 2.79 and Magisk 11.1.
18 Boot your device and install magisk manager from the play store.
19. Enable from magisk manager settings: busybox, magisk hide and systemless hosts and Install Adaway (Will not work without Magisk, strange).
I have not managed to get my CTS profile approved but that is not major issue if not playing with Pokemon go (You can use magisk to detect this).
Note1 : Change LTE to 1 priority from mobile setting. Default for SA firmware is GSM
Note2: If you have already tried rootkernel to get drm working; do a full wipe and reflash firmware with flashtool. Rootkernel messes something. Tablet do not boot if you have used rootkernel and after that try to use munjenis DRM fix.
Note3: Magisk 11.1 wont work with Xperia Z4 Tablet without Supersu. So flash Supersu first and Magisk 11.1 after that
Note4: You cannot boot to TWRP by using root and reboot to recovery apps. You need to boot to the recovery with keycommand voldown+power
I hope this guide helps some fellow flashers
Special thanks for
munjeni
serajr
Chainfire
Androplus
topjohnwu
Teamwin
Androxyde
mrRobinson
If I forgot someone I am truly sorry!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Just tried unable to boot to recovery

sahilg009 said:
Just tried unable to boot to recovery
Click to expand...
Click to collapse
Did you do a full wipe? Try to fastboot flash boot new_boot.img after flashing recovery!

Tried wiping now flashing kernel gives me a no sim card error

sahilg009 said:
Tried wiping now flashing kernel gives me a no sim card error
Click to expand...
Click to collapse
Check this out:
https://forum.xda-developers.com/showpost.php?p=70972513&postcount=115

halfvast said:
Check this out:
https://forum.xda-developers.com/showpost.php?p=70972513&postcount=115
Click to expand...
Click to collapse
Even tried that still giving me signal problem

sahilg009 said:
Even tried that still giving me signal problem
Click to expand...
Click to collapse
Strange, I Did not encourter this problem because I could boot to TWRP and do adb trick there. Do you use orginal Sony usb to flash in fastboot? I had once a problem with Samsung Phone (S7) to flash recovery because the usb was not the one that came with my Phone.

Yeah

Try redownload TWRP image and flash it. If not working do a clean flash and try again or wait for Androplus kernel

Tried it all nothing worked still no sim error

sahilg009 said:
Tried it all nothing worked still no sim error
Click to expand...
Click to collapse
I found out munjeni is fixing his tool:
https://forum.xda-developers.com/showpost.php?p=70993277&postcount=173
I used previous version, which is not availble right now.
He says further in his thread he is going to release tomorrow a new version.
I used this version:
http://www.filedropper.com/tapoc

halfvast said:
I found out munjeni is fixing his tool:
https://forum.xda-developers.com/showpost.php?p=70993277&postcount=173
I used previous version, which is not availble right now.
He says further in his thread he is going to release tomorrow a new version.
I used this version:
http://www.filedropper.com/tapoc
Click to expand...
Click to collapse
Couldnt I just do the root and recovery method you have given on the wifi version as im not too bothered about drm fix for now as it looks abit complicated at the moment for me. It would be much more simple for me to flash recovery then super su. I just wanna know if this is possible?
Thanks

I am not sure. You need atleast a correct TWRP. You can try if You dare with your own RISK
But I doubt that it wont work..

halfvast said:
I am not sure. You need atleast a correct TWRP. You can try if You dare with your own RISK
But I doubt that it wont work..
Click to expand...
Click to collapse
Ok then dont think id like to try incase it doesnt boot so I think I might just wait for andro to do his stuff.

I have updated the guide and tested it today (13.2.2017) and it is working again

Guide updated and simplificed 15.2.2017. Thanks to munjeni!

halfvast said:
Guide updated and simplificed 15.2.2017. Thanks to munjeni!
Click to expand...
Click to collapse
Step 8 says Extract kernel.sin from your nougat firmware copy it to same folder with DRM fix. Rename kernel.sin to kernelX.sin. Do I have to extract that from the ftf or my Nougat firmware im currently using? Also does the ftf have to be that region?

RJASSI21 said:
Step 8 says Extract kernel.sin from your nougat firmware copy it to same folder with DRM fix. Rename kernel.sin to kernelX.sin. Do I have to extract that from the ftf or my Nougat firmware im currently using? Also does the ftf have to be that region?
Click to expand...
Click to collapse
You need to extract it from ftf-image. I used 7zip. My device was Nee with stock. I used DE with Marshmallow and I am currently using Saudi Arabia. So I dont think it will matter, which kernel you use with your device. But I would use same kernel version with rom. So If you are using Saudi Arabia rom use Saudi Arabia kernel. For Russia rom use Russia kernel, and so on
I will add tft-image extract to tutorial!

DRM fix doesn't work. XReality (among other things I assume) are ever disabled.
On Marshmallow DRM fix was working fine (was using XReality engine despite the unlocked bootloader)

For me it is working!

Magisk on Stock Xperia Z2 D6503 SAFETY NET PASSED

Firstly, I do not take any responsability in case anything happens to your device or your files. You decided to follow this guide at your own risk.
THIS WORKED FOR ME FOR MAGISK v14.3
ALSO WORKS ON MAGISK v14.5
I highly not recommend to use this guide for a different device other than the Xperia Z2 D6503.
All that aside, I managed to install magisk on my Stock Xperia Z2 and still keep ctsProfile and basicIntegrity: true.
HIGHLY RECOMMEND TO BACK EVERYTHING UP BEFORE PROCEEDING
You will need:
(OPTIONAL)Marshmallow FTF Firmware Here
(OPTIONAL)Flashtool Here
Magisk Manager Here
Rootkernel_v4.31_Windows_Linux.zip Here
ADB and Fastboot Here
Advanced Stock Kernel Here
TWRP Sirius Here
(OPTIONAL BUT HIGHLY RECOMMENDED) Use flashtool to flash the modified version of the stock ROM from above. It worked on this version but I can't really guarantee it will work on others. Can't really guarantee it will work on this either.(after you select the file there are 2 versions. pick the modified one).
1) Extract the Rootkernel_v4.31_Windows_Linux.zip and extract from the advanced stock kernel the boot.img (Rename it from boot.img to Old_boot.img)
2) Open cmd and use cd to reach the folder in which you extracted rootkernel.
Use the command "rootkernel Old_boot.img New_boot.img"
Say Yes to everything except installing TWRP.
3) Install Magisk Manager on your phone and copy "New_boot.img" to the phone.
4) Go to Magisk Manager settings , scroll to Update Channel and select Beta
5) Select install Magisk and select modify boot image. Select "New_boot.img" from the folder you copied it to
6) Extract adb to a folder
7) After patching the boot image at step 6, copy "patched_boot.img" from internal storage/MagiskManager to the folder in which you extracted adb
8) Copy TWRP to the adb folder and rename it to TWRP.img
9) Open cmd and use cd to navigate to the folder in which you copied adb. Type in the console "fastboot flash boot New_boot.img". Turn off your phone and then hold Volume Up whil plugging it into your pc(booting it into fastboot).
10) While still in fastboot, type "fastboot flash recovery TWRP.img"
11) Disconnect your phone from the pc. Wait a few seconds and then boot into TWRP (hold power button and Volume Down). A notification will pop up and select to "Keep System Readonly" (I think something like that). Reboot into system.
If everything worked as intended, a safetynet check will reveal everything in green, allowing you to both have root access and also run apps like Netflix and Android Pay
NOTE: Magisk Modules should be flashed via TWRP. For some reason, Magisk Manager is unable to install them.
EDIT: I tried to install xposed systemlessly but Safetynet was triggered. Don't think I can figure this out.
DahakePL tried with elite kernel and it didn't work. Writing this just in case anyone tries.
This worked for me but I can't guarantee it will work for you. (Photos at the end)
Did this guide help you? If you need any help, I will do my best to answer your questions.
I am not a developer and I do not really understand why or how everything works. I came across this method that worked for me and I thought I'd share it since I couldn't find a guide for my xperia phone when I needed it.
IN CASE SAFETY NET IS TRIGGERED, the only way to restore to everything in green is to reflash the stock rom (you don't have to format everything).
Did it work out for you? Just leave a reply saying that so I can figure out if everything works.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
.

Thank you man
Great job

Hi there and great job. Many thanks for this.
I've a question, "(OPTIONAL BUT HIGHLY RECOMMENDED) Use flashtool to flash the modified version of the stock ROM from above (after you select the file there are 2 versions. pick the modified one)." - what if another .291 stock firmware is used (eg downloaded from Xperifirm)?

fribriz said:
Hi there and great job. Many thanks for this.
I've a question, "(OPTIONAL BUT HIGHLY RECOMMENDED) Use flashtool to flash the modified version of the stock ROM from above (after you select the file there are 2 versions. pick the modified one)." - what if another .291 stock firmware is used (eg downloaded from Xperifirm)?
Click to expand...
Click to collapse
Well, this worked on this exact version. If you don't use it, i can't guarantee it will work.
Well, can't either way
But it worked on that one. I believe you don't have to reinstall your stuff if you already have the stock rom. You can just flash it over without deleting anything

Works fine thank you

Adriano-A3 said:
Thank you man
Great job
Click to expand...
Click to collapse
Awesome
I'm actually surprised.

Doesn't work on elite kernel, just tested, no root and no safetynet

DahakePL said:
Doesn't work on elite kernel, just tested, no root and no safetynet
Click to expand...
Click to collapse
Have you tried with the advanced kernel I linked?
Also, you have to be running stock
Xperia z2

IceGordol said:
Have you tried with the advanced kernel I linked?
Also, you have to be running stock
Xperia z2
Click to expand...
Click to collapse
I'm using the advanced stock kernel method and it works 100%
But I tried elite kernel and it doesn't work at all, just in case someone else wanted to know or something :highfive:

DahakePL said:
I'm using the advanced stock kernel method and it works 100%
But I tried elite kernel and it doesn't work at all, just in case someone else wanted to know or something :highfive:
Click to expand...
Click to collapse
Modified the post in order to specify this. Also credited you. Thanks for this addition.

Where is modified FTF?
Sent from my D6503 using Tapatalk

Why do I need to flash TWRP? It is already included into advanced stock kernel.

After flash magisk, can't mount otg drive in twrp
Sent from my D6503 using Tapatalk

I am running a phone with KK 4.4.4 rooted and xposed installed. What should I do first to use it?
If I want to keep few apks data?
May I install Cyberian Camera MOd after it?

Thanks you! Working finally!

609125 said:
Thanks you! Working finally!
Click to expand...
Click to collapse
How u make it working? I got no clue about step 2... rootkernel old_boot.img new_boot.img? I really have no idea about the instructions...
---------- Post added at 04:10 PM ---------- Previous post was at 04:03 PM ----------
DahakePL said:
I'm using the advanced stock kernel method and it works 100%
But I tried elite kernel and it doesn't work at all, just in case someone else wanted to know or something :highfive:
Click to expand...
Click to collapse
Guys, I once rooted my Z2 with SuperSU in locked bootloader condition (already unroot it). Im interested with magisk and want to try it. Is it possible for me even my device is bootloader locked? Thank you

IceGordol said:
9) Open cmd and use cd to navigate to the folder in which you copied adb. Type in the console "fastboot flash boot New_boot.img". Turn off your phone and then hold Volume Up whil plugging it into your pc(booting it into fastboot).
Click to expand...
Click to collapse
Perfect for me. Thank you very much!
But your step 9 is wrong. should be "fastboot flash boot patched_boot.img"
My ROM is Marshmallow_Stock_575_ROM_Ultraslim
must remove SuperSU (root) before installing, use UPDATE-unSU-signed.zip

Can't get this to work at all. I'm on Customised UK stock ROM.
No matter what I do, I get bootloops once Magisk is installed. If I use the Magisk Uninstaller from TWRP the phone works fine again.
EDIT: I should have said, I've tried with Magisk 16.0 and 16.7 Beta. No luck with either. I've also tried patching the advanced stock kernel boot.img and I've tried installing via TWRP with Bootloader-SonyELF. No luck again, just the same bootloop!
UPDATE: I managed to fix this by using the latest version of the RootKernel patching tool (v5.23) instead of v4.31 and following the rest of the instructions using the boot.img from advanced stock kernel with Magisk 16.7 installed successfully.

Work fine with Magisk 18

okay after two soft brick, red blinking light and the device wont turn on, i finally succeed installing this. the first issue i'm getting is adb command not found when running the "fastboot flash boot patched_boot.img", so i tried to use TWRP to install the img, which refuse saying it need bootbridge, so i install through the recommend option in magisk manager (installing directly) which cause the first brick
the first brick is restored by using flash tool
the second brick can't be restored by flash tool due to the usb debugging is off causing flash tool to said "device connected but using old drivers", luckily xperia companion software (now called emma) restored it succesfully
and i finally figured what causing the soft brick, since emma said the bootloader is locked and magisk can't be used with locked bootloader and that bricked the device.
anyway finally unlocked the bootloader since emma needed it to unbrick the device. and after unlocking the bootloader and follow again the procedure here i finally succeed installing magisk on my z2
TLDR: YOU NEED UNLOCKED BOOTLOADER TO FOLLOW THIS PROCEDURE. to check easily if your bootloader is locked or not is just by running Emma (xperia updater replacement) or use "fastboot oem device-info".
finally can try magisk, since many apps detect supersu now and refuse to work with it. i didn't unlocked the bootloader the first time since supersu can work with locked bootloader >_>