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!
Related
When I saw that I could upgrade to Lollipop I was interested. Then I realized there probably was no root for this yet. So I went about figuring out a way to root it before going to it. Technically this isn't a root once you have already gone to Lollipop.
THIS WILL ONLY WORK IF YOU ARE STILL ON KITKAT, ROOTED, WITH RECOVERY (TWRP is what I use via NUT's Dual Recovery for the Z1).
Requirements:
PRFCreator - Creates pre-rooted firmware - Click Here to Download
Flashtool - Allows you to flash the FTF - Click Here to Download
The FTF for the upgrade - C6916_14.5.B.0.236_T-mobile_US.ftf - Click Here
The latest SuperSU zip from ChainFire - Click here to Download
I'm assuming you have adb, drivers installed and a general understanding of how to navigate the tools above, if not read up on how they work.
Create a pre-rooted flashable firmware with PRFCreator. Install/Download PRFCreator and put the FTF and the latest SuperSU binary zip in the spot labeled SuperSU Zip. Make sure to check the box next to kernel in the include box on the top right side. See screenshot below.
{
"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"
}
Congrats you have just created a flashable zip with SuperSU loaded into it. You might ask why you're not gonna add NUT's XZDualRecovery into there. Reading on the forms at the time of this post and it apppears that PRFCreator and/or Nut's recovery doesn't play well with Lollipop and causes bootloops. So run NUT's Z1xzdualrecorvery installer via bat or sh after the fact and not during via PRFCreator until they can work it out.
Make sure you have the original C6916_14.5.B.0.236_T-mobile_US.ftf in the firmwares folder either C:\Flashtool\Firmwares or C:\User\[username]\.flashtool\firmwares
Now take the flashable zip you created via PRFCreator and put it on your phones internal storage, sdcard etc.
Now that you have the flashable zip with SU preinstalled and ready to fire, reboot your phone into recovery. adb reboot recovery etc.
Once your phone has rebooted into recovery you will need to flash the flashable zip you created with PRFCreator.
After flashing the zip I'd suggest wiping the cache/dalvik. And then you will want to go to the reboot screen and power off the device.
Once the device is powered off open Flashtool.
After it loads and syncs the devices (takes a second) you'll want to double click C9XX from the list (Z1).
Next click the BOLT icon in the top left navigation that has a tooltip that says "Flash"
When the flash screen comes up select the right firmware based on the FTF location, check SYSTEM and BASEBAND under the exclude section and uncheck DATA under the wipe section, I unchecked APPSLOG but you don't have to uncheck it (to be honest I think it slowed my initial bootup by upgrading my apps) via this screenshot:
Now click the "Flash" button with your device disconnected and powered off. Follow the directions. For your Z1s you'll want to hold the "DOWN VOLUME" button and then plug the USB connector into it.
Next you will see Flashtool flashing away. Once it's complete you can unplug your phone and then power it up.
Your device is now rooted and running Lollipop. In terms of installing a custom recovery, again all of that is untested and you'll need to play around with the latest XZdualrecovery from NUT to see how it works.
REMINDER: This doesn't solve killing ric etc. Which is important to note for being able to mount the system etc. You can kill ric via tasker and an .sh script like I do or via a flashable kill ric (seen a few floating around) if you get recovery installed after the fact etc.
Thanks to:
Chainfire for his SUPERSU
zxz0O0 for his PRFCreator tool
Androxyde for keeping flashtool going
greatremix for posting up the FTF
I'll be uploading the flashable zip that I made from PRFCreator. It's over a gb obviously so it might be just as easy for you all to create it yourself.
Reserved
To solve most issues with not being able to write to the system which most root apps need. Install NUT's latest xzdualrecovery which can be found at this address under xzdualrecovery. I installed 2.8.15 via the installer (not the flashable)
http://nut.xperia-files.com/
I update rom using sony companion and rooted by king root, i tried to unlockbootloader with flashtool a minutes ago and its say :
can i flash some rom ?
Lavievn said:
I update rom using sony companion and rooted by king root, i tried to unlockbootloader with flashtool a minutes ago and its say :
can i flash some rom ?
Click to expand...
Click to collapse
Whoah whoah whoa... Let me make sure I got this straight... You... have a Z1S (Not a Z1, but Z1S) and you actually managed to root it on lollipop AND unlock the bootloader?!!!?!... Please tell me you are not joking. Or am I just not understanding correctly...
THE BOOTLOADER UNLOCKED?!!!?! If you did that... that is amazing. Do you know how long people have been trying to unlock the bootloader for this dam thing? But.. before I jump to conclusions. I'll wait for your reply.
Yazuken1 said:
Whoah whoah whoa... Let me make sure I got this straight... You... have a Z1S (Not a Z1, but Z1S) and you actually managed to root it on lollipop AND unlock the bootloader?!!!?!... Please tell me you are not joking. Or am I just not understanding correctly...
THE BOOTLOADER UNLOCKED?!!!?! If you did that... that is amazing. Do you know how long people have been trying to unlock the bootloader for this dam thing? But.. before I jump to conclusions. I'll wait for your reply.
Click to expand...
Click to collapse
i've unlocked that bootloader, install RockZ1L kernel, so i tried to install DstrikerZ1kaiRom
when it's ask me what's my model of my phone i choose 6902...it's flashed and boot to system too slowly at first time, after that it's had to shutdown...it take very long time and has been loop boot, i trying to take it's back to .236 stock rom now
p/s sorry for bad english, it's have successfull to flash custom kernel with good double tab to wake ...and something...but can't run with other rom
Lavievn said:
i've unlocked that bootloader, install RockZ1L kernel, so i tried to install DstrikerZ1kaiRom
when it's ask me what's my model of my phone i choose 6902...it's flashed and boot to system too slowly at first time, after that it's had to shutdown...it take very long time and has been loop boot, i trying to take it's back to .236 stock rom now
p/s sorry for bad english, it's have successfull to flash custom kernel with good double tab to wake ...and something...but can't run with other rom
Click to expand...
Click to collapse
That is the reason why the bootloader is locked. It might say you have unlocked the bootloader but you really haven't. It's still locked hence the inability to flash a custom ROM. I would suggest against anyone trying flashtool to unlock the bootloader, it will not work.
Best to get root, recovery and xposed if it works.
joedeveloper said:
That is the reason why the bootloader is locked. It might say you have unlocked the bootloader but you really haven't. It's still locked hence the inability to flash a custom ROM. I would suggest against anyone trying flashtool to unlock the bootloader, it will not work.
Best to get root, recovery and xposed if it works.
Click to expand...
Click to collapse
i'm stuck now, do you have a C6902 stock kernel, or any way to change phone infomation by flashtool ?
it's show that my phone is C6902 in flash tool now, so i can't flash any rom or back to stock now
@joedeveloper I'm currently on 4.4.4, rooted with baseband .59, but noticed by your directions with "prfcreator" that you do not have us "check" modem when building the flashable zip. Would it hurt to include the modem so as to get the updated baseband to .69?
Also being deodexed, will that cause issues?
Thanks for the help
Not to distract from joedevelopers hard work, but I think its important for me to inform you guys that if you have already upgraded to lollipop through sony pc companion, or ota, King root does in fact work just fine. It will give a screen saying that it could not find that xperia z1s is rootable, but it will also give an option to try to root anyway. After pressing it, it will tell you the device was sucessfully rooted. And if you check with root verifier it will let you know root was successful. So you're still good if you upgraded to lollipop.
@joedeveloper Settings>About Phone reports baseband .69 after update, so that answers that.
I went back to tft .37 and did a fresh install so I have no information if one with a deodexed phone will be effected.
Many thanks to this update method.
SOLVED
Anyone get xposed to work after this update?
Can you clarify the ric thing?
So far so good, got recovery installed, now im going to try to install the audio mod, cause i desperately need that lol
SO I finally got it to where i got a flash able zip and it worked phone says its rooted , but it won"t let me install adblocker , edit file with root explore and busybox they all say failed , please help
throonis said:
SO I finally got it to where i got a flash able zip and it worked phone says its rooted , but it won"t let me install adblocker , edit file with root explore and busybox they all say failed , please help
Click to expand...
Click to collapse
This is what I'm referring to as the issue with sony ric being enabled. It's sony's way of preventing you from writing to the system, and most root apps need this. If you were to run:
adb shell
then
su
then
mount -o remount,rw /system
What does it tell you? "Denied"?
In order to prevent sony ric from blocking it, try installing NUT's xzdualrecovery version 2.8.15. Z1-lockeddualrecovery2.8.15-RELEASE.installer.zip
http://nut.xperia-files.com/
It has a built in ric killer and will solve your issues.
So all I have to do is flash the zip on my z1s to have.recovery correct I have root supersu
Got root, thanks.
Okay, got root. Thank you. The trick is to keep doing the ADB root until it works. It doesn't work the first couple of times. I gave it 20 minutes each time before trying to install again.
Jellybean
I tried your steps from Jellybean but got no root on lollipop but I can't get root from 4.4.4. Is there a 4.4.2 firmware floating around and could that be the problem? I did the steps twice and followed it exactly. The only difference is 4.3.
Lavievn said:
i've unlocked that bootloader, install RockZ1L kernel, so i tried to install DstrikerZ1kaiRom
when it's ask me what's my model of my phone i choose 6902...it's flashed and boot to system too slowly at first time, after that it's had to shutdown...it take very long time and has been loop boot, i trying to take it's back to .236 stock rom now
p/s sorry for bad english, it's have successfull to flash custom kernel with good double tab to wake ...and something...but can't run with other rom
Click to expand...
Click to collapse
HOW TO INSTALL CWM AND ROCKZ1L KERNEL ??? STEP BY STEP ! MY Z1S IS ON STOCK 5.0.2, BOOT LOADER UNLOCKED : YES.
SORRY , MY ENGLISH IS VERY BAD ! THANKS SO MUCH .
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.
So many LEECHERS exist, It's not hard to press a button..
{
"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"
}
Hi xda users,
I am very pleased to present LATEST NOUGAT FTFs Google Drive Mirror, Patched Kernels and TWRP .
I spend lots of time and bandwidth for you, so please hit Thanks :fingers-crossed: button and comment below..
Bootloader LOCKED Devices
-Just follow 1 to 14 steps
Bootloader UN-LOCKED Devices
-Just follow 1 to 30 steps
Google Drive Mirror File List
-7.1.1 (32.4.A.1.54) FTFs (E6603, E6633, E6653, E6683)
-Patched Kernels
-TWRP 3.1.1.0 thanks to @kv123
-ROOT Methods (SuperSU, phh and Magisk)
-Flashtool, Flashtool-drivers (0.9.23.2)
Click this for List view
Patched Kernel Specifications
sony-ric
dm-verity
drm-fix
busybox-1.26.2
fully /system read&write access
If r/w didn't work for you, please do that. It will be fixed.
1.Install Termux on Play Store.
2.Write "su" command and give root access.
3.Then write this
Code:
echo 0 > /sys/kernel/security/sony_ric/enable
4.Lastly write this
Code:
busybox mount -o rw,remount,rw /system
Done
Step by Step Installation
Summary
Install Flashtool & Drivers
Flash FTF
Flash Patched Kernel & TWRP
Flash ROOT
Detailed
1-) Install flashtool-0.9.23.1-windows.exe
2-) Copy x10flasher.jar file into "C:\Flashtool", open Flashtool wait until process done then quit program.
3-) Disable "Driver Signature Verification"
Windows 7 : Tap F8 while booting and select required option
Windows 8, 8.1, 10 : Read This Instructions
4-) Install Flashtool-drivers.exe (flashmode, fastboot, z5)
5-) Copy FTF file into "C:\Users\YOUR PC NAME\.flashTool\firmwares"
6-) Backup your Photos & Videos & Musics etc. on Internal Memory to SDCard or PC
7-) Shutdown your phone
Open Flashtool (x32 suggested)
9-) Click Flash button (top left) then Ok button, select FTF on left side
10-) Select ALL wipe options, no NEED Misc TA for every flash (SKIP this, if you want to just UPDATE and keep data)
11-) Click Flash button, wait 1 minute (you will see an info)
12-) Push VOLUME DOWN button, then connect phone to pc (green led)
13-) When flashing done, disconnect and boot-up your phone, complete setup wizard (required)
14-) If you want to use Patched Kernel or ROOT your phone then continue otherwise flashing FTF process done
You have to BL Unlocked device to continue..
15-) Shutdown your phone
16-) Push VOLUME UP button, then connect phone to pc (blue led)
17-) Copy 32.4.A.1.54_E66XX.img and twrp_recovery.img file into "C:\Flashtool\x10flasher_lib"
1 Open "C:\Flashtool\x10flasher_lib" folder
19-) Then press LEFT SHIFT and click mouse right button into this folder
20-) Then press Open command window here option
21-) Then type this code into cmd (xx your model)
Code:
fastboot.exe flash [COLOR="red"]boot[/COLOR] 32.4.A.1.54_E66[COLOR="red"]xx[/COLOR].img
fastboot.exe flash [COLOR="red"]recovery[/COLOR] twrp_recovery.img
22-) Disconnect your phone and boot-up (required)
23-) If you want to ROOT your phone then continue otherwise flashing Patched Kernel process done
24-) Put ROOT files into Internal Memory
SuperSU - Most common root solution
phh's Superuser - I think best root solution
Magisk - Module solution & It has built-in phh root solution
25-) Boot-up your phone into TWRP
-TWRP : Volume DOWN + Power
26-) If you want to use SuperSU, just flash zip and reboot
27-) If you want to use phh, just flash zip and reboot You have to install "me.phh.superuser.apk"
Latest Magisk
Latest Magisk Uninstaller
2 If you want to use SuperSU & Magisk, flash SuperSU first then Magisk then Install Magisk Manager
29-) If you want to use Magisk, flash latest Magisk then Install Magisk Manager
30-) Have fun :fingers-crossed:
You can delete ALL System Apps with System App Remover ROOT APP
HELP ME!
HI :3
a request, could use the same kernel of the Latin American version of the model 6603? since I use that version, and this device and has the fingerprint sensor, please, I currently use the kernel of the US version and I do not have the fingerprint sensor enabled, or is there any way to reactivate this sensor with the American kernel?
SKGT said:
HI :3
a request, could use the same kernel of the Latin American version of the model 6603? since I use that version, and this device and has the fingerprint sensor, please, I currently use the kernel of the US version and I do not have the fingerprint sensor enabled, or is there any way to reactivate this sensor with the American kernel?
Click to expand...
Click to collapse
No, usa kernel was broken. I use TR and Germany kernels.
Thank You so much!
4th comment!
Sent from my E6653 using XDA-Developers Legacy app
Can I flash this ROM using TWRP?
Sent from my E6653 using XDA-Developers Legacy app
GeramanX said:
Can I flash this ROM using TWRP?
Sent from my E6653 using XDA-Developers Legacy app
Click to expand...
Click to collapse
No. Follow the instructions of the OP.
Sent from my E6653 using Tapatalk
@sceryavuz is it possible to add kcal support on .54 kernel.
s.hossein said:
@sceryavuz is it possible to add kcal support on .54 kernel.
Click to expand...
Click to collapse
+1
s.hossein said:
@sceryavuz is it possible to add kcal support on .54 kernel.
Click to expand...
Click to collapse
devilmaycry2020 said:
+1
Click to expand...
Click to collapse
Flash 7.1.x_kcal_support.zip via TWRP. :fingers-crossed:
I have flashed it. It works so nice. Battery last longer. Phone doesn't heat up, only warm up a bit. But why does the phone heat up while charging only? Is there any way to fix this?
Thank You
s.hossein said:
@sceryavuz is it possible to add kcal support on .54 kernel.
Click to expand...
Click to collapse
sceryavuz said:
Flash 7.1.x_kcal_support.zip via TWRP. :fingers-crossed:
Click to expand...
Click to collapse
Thank you. Working well on .54 kernel
sceryavuz said:
No, usa kernel was broken. I use TR and Germany kernels.
Click to expand...
Click to collapse
Sorry for my english, google translator
So, I have to flash the ftf of germany? Does this kernel have the fingerprint sensor? I want to recover the fingerprint sensor, but I do not want to lose the drm keys I also do not want to lose root, any help? I use an e6603, with the ftf of latin america, but with the kernel of usa, is there any way to enable the fingerprint sensor?
thanks: 3
thank you sir for your work..but twrp still looping after flashing it>>>what shall i do(the phone stocked on twrp )
i did wipe cache and again mounted the system and flashed supersu>>>>>>but unfortunately.....didnot worked ...any suggestions???
thanks in advance
amer78 said:
thank you sir for your work..but twrp still looping after flashing it>>>what shall i do(the phone stocked on twrp )
i did wipe cache and again mounted the system and flashed supersu>>>>>>but unfortunately.....didnot worked ...any suggestions???
thanks in advance
Click to expand...
Click to collapse
Where did you flash it? And what model do you use?
Sent from my E6653 using Tapatalk
saiz136 said:
Where did you flash it? And what model do you use?
Sent from my E6653 using Tapatalk
Click to expand...
Click to collapse
i flashed rooted kernel via flash tool (fastboot)
then flashed twrp (same method)
then flashed supersu as always
my model is E6633 (dual sim z5)
amer78 said:
i flashed rooted kernel via flash tool (fastboot)
then flashed twrp (same method)
then flashed supersu as always
my model is E6633 (dual sim z5)
Click to expand...
Click to collapse
Are you sure you flashed the right firmware? With ".TA" removed? Try to flash the firmware and make sure it's the right model and build number using flashtool. Also check the img file if it's the right model too.
Sent from my E6653 using Tapatalk
saiz136 said:
Are you sure you flashed the right firmware? With ".TA" removed? Try to flash the firmware and make sure it's the right model and build number using flashtool. Also check the img file if it's the right model too.
Sent from my E6653 using Tapatalk
Click to expand...
Click to collapse
i did it all as mentioned but .....no hope...still stocked at twrp..and hone refuse to boot normaly..
i did wipe cahe ..fixing permissions...everything...n chance
amer78 said:
i did it all as mentioned but .....no hope...still stocked at twrp..and hone refuse to boot normaly..
i did wipe cahe ..fixing permissions...everything...n chance
Click to expand...
Click to collapse
Try to flash ftf (firmware without the boot.img and twrp.img) also I might recommend to download the ftf via Xperifirm and not the one provided by the OP. Use the customised version.
Sent from my E6653 using Tapatalk
saiz136 said:
Try to flash ftf (firmware without the boot.img and twrp.img) also I might recommend to download the ftf via Xperifirm and not the one provided by the OP. Use the customised version.
Sent from my E6653 using Tapatalk
Click to expand...
Click to collapse
i think the problem comes from twrp.....
its not compatible with my device
is there any other method to root?
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 >_>
Unofficial release -TWRP recovery for the Galaxy SM-M105F/DS, Exynos7870
About Samsung Galaxy M10
Here are some of the key features and specifications of the newly launched Samsung Galaxy M10 smartphone.
- Firstly, it has a 6.22 inches display with a resolution of 720 by 1520 pixels. A total of 270 pixels per inch.
- And Samsung Galaxy M10 also comes with Android 8.1 OREO.
- And under the hood, the phone has an Exynos 7870 chipset.
- The Phone also comes with 3GB/2GB Ram and 32GB/16GB Storage.
- Furthermore, the camera sensor is – 13MP + 5MP dual rear camera and 5MP front shooter.
- Finally, the battery on the phone is a non-removable 3400 mAh.
tested on SM-M105F with android 8.1.0 (must work in other models but not tested).
-mtp not work in linux
if adb not work disable MTP from mount menu in recovery
use odin or heimdall for flash recovery image.
use Magisk 18.1 for rooting.
before flash recovery file you need to unlock bootloader with OEM unlock from developer options.
Heimdall file ----> download
Odin file ----> download
use latest kernel source from opensource.samsung.com and A3 2017 official device three for building.
hi there can you provide step by step installation guide please.. appreciated!
Hello thank you for your work, i have a SM-M105F from India in Germany.
I have unlocked the OEM Bootloader and Reset the Phone.
Twrp installed with Odin and Boot into Twrp work.
The System not Booting. It is in Bootloop, but Twrp work.
I have now install the Official Firmware back with Odin.
I need to make TWRP an System work parallel with Root.
I need Help.
gtabuni said:
Hello thank you for your work, i have a SM-M105F from India in Germany.
I have unlocked the OEM Bootloader and Reset the Phone.
Twrp installed with Odin and Boot into Twrp work.
The System not Booting. It is in Bootloop, but Twrp work.
I have now install the Official Firmware back with Odin.
I need to make TWRP an System work parallel with Root.
I need Help.
Click to expand...
Click to collapse
Maybe try flashing 'no-verity-opt-encrypt' and 'RMM Bypass' zip files?
EDIT: Flash Magisk zip too (it removes dm-verity), and format the data partition
Thank you for your good tips, i need to test it.
gtabuni said:
Hello thank you for your work, i have a SM-M105F from India in Germany.
I have unlocked the OEM Bootloader and Reset the Phone.
Twrp installed with Odin and Boot into Twrp work.
The System not Booting. It is in Bootloop, but Twrp work.
I have now install the Official Firmware back with Odin.
I need to make TWRP an System work parallel with Root.
I need Help.
Click to expand...
Click to collapse
by default dm-verity is active for system , vendor and odm partitions. you can use magisk to disable it
surbiks said:
by default dm-verity is active for system , vendor and odm partitions. you can use magisk to disable it
Click to expand...
Click to collapse
so just flash magisk to remove dm-verity and get root ?
madi3d8 said:
so just flash magisk to remove dm-verity and get root ?
Click to expand...
Click to collapse
yes. use magisk
please make a more detailed tutorial because I have already burned my phone a faith and I want to be sure of what I am doing this faith. thank you
This work for m105g?
No, its not
BlacklightMG said:
Maybe try flashing 'no-verity-opt-encrypt' and 'RMM Bypass' zip files?
EDIT: Flash Magisk zip too (it removes dm-verity), and format the data partition
Click to expand...
Click to collapse
where is 'no-verity-opt-encrypt' and 'RMM Bypass' zip files?
madi3d8 said:
where is 'no-verity-opt-encrypt' and 'RMM Bypass' zip files?
Click to expand...
Click to collapse
RMM Bypass: https://forum.xda-developers.com/attachment.php?attachmentid=4481843&d=1524258795
no-verity-opt-encrypt: https://build.nethunter.com/android-tools/no-verity-opt-encrypt/no-verity-opt-encrypt-6.0.zip
ojol Cipinang said:
This work for m105g?
Click to expand...
Click to collapse
i dont know, you must test, but its must be work
surbiks said:
i dont know, you must test, but its must be work
Click to expand...
Click to collapse
I have tested at m105g twrp It was successfully installed and the root was successful but after rebooting I was stuck on a screen that read "storage of damaged devices" please reset your device. Always like that ... help me
Please TWRP for SM-A105G/DS
Can we flash gsi image with this recovery??
I got an error
I do everything infact after install twrp i also install the no verity opt and rmm bypass but i still got this **** error everytime i boot my phone..
Data is corrupt reset your mobile i do it many times but same again bootup and gives this msg...
{
"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"
}
I have on my SM-M105FD the Firmware 8.1.0 and Working Root. With twrp System not work.
Download the Firmware 8.1.0 on the PC and the AP File put on the Phone.
Download and install magisk apk on your Device and patch the AP in Magisk file.
flash the Firmware full with Odin but put on the AP Option the Patched AP file flash and work.
I have with Magisk install the Xposed Framework and install nice plugins.
gtabuni said:
I have on my SM-M105FD the Firmware 8.1.0 and Working Root. With twrp System not work.
Download the Firmware 8.1.0 on the PC and the AP File put on the Phone.
Download and install magisk apk on your Device and patch the AP in Magisk file.
flash the Firmware full with Odin but put on the AP Option the Patched AP file flash and work.
I have with Magisk install the Xposed Framework and install nice plugins.
Click to expand...
Click to collapse
How to unlock the bootloader M10? is It enough by enabled OEM unlock option?