So, never had a Sony-Device, the guides and instructions here are a bit unclear to me.
As far as i understood before going custom:
Downgrade to .532 with flashtool -> run BackupTA -> upgrade to latest again (rly neccessary?) -> then unlock Bootloader
Pretty straight forward up until here.
From there on i can use [NUTS]s XZDualRecovery if i want to stay on stock-kernel and flash custom roms frem there without any problem as far as i understood.
Is this correct?
But what if i want to use a custom kernel at some point?
DooMKernel for example is flahsed via Fastboot, but only compatible with Stock-Sony-Roms
PimpedKernel for example on the other hand is CM-based only and only uses a recovery flashable zip
I'm a little bit confused because of that.
Is a Kernel and / or recovery included in every ROM? (Edit: Yep Kernel is..)
Can i just use [NUTS] recovery and then flash any ROM / Kernel trough it? And afterwards a custom Kernel if the one included in ROM (if any?) lacks any features i want?
competent devs who maintain roms for this phone would include a recovery in their package
slimrom does this and i don't have to worry about losing trwp recovery
alia5 said:
So, never had a Sony-Device, the guides and instructions here are a bit unclear to me.
As far as i understood before going custom:
Downgrade to .532 with flashtool -> run BackupTA -> upgrade to latest again (rly neccessary?) -> then unlock Bootloader
Pretty straight forward up until here.
From there on i can use [NUTS]s XZDualRecovery if i want to stay on stock-kernel and flash custom roms frem there without any problem as far as i understood.
Is this correct?
But what if i want to use a custom kernel at some point?
DooMKernel for example is flahsed via Fastboot, but only compatible with Stock-Sony-Roms
PimpedKernel for example on the other hand is CM-based only and only uses a recovery flashable zip
I'm a little bit confused because of that.
Is a Kernel and / or recovery included in every ROM? (Edit: Yep Kernel is..)
Can i just use [NUTS] recovery and then flash any ROM / Kernel trough it? And afterwards a custom Kernel if the one included in ROM (if any?) lacks any features i want?
Click to expand...
Click to collapse
The downgrading is no longer necessary, use the easyroot tool. Or use the dualrecovery installer for locked bootloaders then flash superuser zip from recovery. Once you have it rooted then back up TA and unlock bootloader. You should be able to flash boot.img from flashtool, if you wanted to download a rom and pull it from zip. I mention that because most roms only have one recovery, so if you flash the img from the rom you want to install first with flashtool you could make a backup that could be restored with new recovery. One other thing that I learned the hard way is a backup made before unlocking bootloader will relock it if restored.
No downgrading, just root and back up TA, great
So i need to flash boot.img from the ROM every time i want to install a new ROM? Or just the first time going from stock to custom? Or just if i have twrp n current rom and the rom i wanna flash is only compatible with CWM?
alia5 said:
No downgrading, just root and back up TA, great
So i need to flash boot.img from the ROM every time i want to install a new ROM? Or just the first time going from stock to custom? Or just if i have twrp n current rom and the rom i wanna flash is only compatible with CWM?
Click to expand...
Click to collapse
Here is a brand spanking new guide to check out that is up to date.
http://forum.xda-developers.com/xperia-z-ultra/general/guide-everything-root-4-4-4-t2938098
I will try to put forth an example to try and demonstrate what I trying to convey in regards to flashing boot.img.
Example.... You are on a rom that contains CWM and you are going to flash a rom that contains TWRP and you wish to have a backup of first rom that could be restored you would flash the img. with TWRP then make backup. Another option would be to just go ahead and use CWM to make backup but you would need to flash that img. in order to be able to restore. I think most roms can be flashed from either recovery at the moment, the concern is your backup being compatible with whichever one is in your current rom.
So, in the boot.img is Kernel+Recovery, alright, and i only need to worry about flashing boot.img für backup reasons.
Pretty much answers what i was wondering, thanks guys
[Noob] Need help to confirm/correct basic understanding of root/custom ROM process involving the latest apks/roms etc.
Device (RN4SD) bootloader unlocked, running MIUI 8.5.8 Stable ROM
Root access only, stock ROM:
1. Only Magisk v.14, No TWRP
- Place stock recovery.img (extracted from mido ROM folder) into phone internal storage
- Install Magisk Manager v.5.4.0 apk on Phone
- Q. Whether to install Magisk v14 zip from Magisk Manager or from MiFlash on PC?
- Q. If from MiFlash on PC, whether to unzip Magisk v.14 into a folder?
- Q. How to patch with stock recovery?
- Q. Whether to select dm-verity option in Manager?
- Q. Will lazyflasher still be needed? If yes, when and how to be flashed?
- Q. Will reboot to system boot into stock ROM, now with root access?
2. Root Access and Custom ROM (e.g. xiaomi.eu)
- Flash install TWRP 3.1.1.0.img (from MiFlash through PC)
- Flash install lazyflasher zip (from TWRP on phone)
- Flash install Magisk v.14 zip (from TWRP) on phone
- Q. Now Reboot? Will this boot into existing MIUI ROM?
Or
- Q. Flash/install custom rom (e.g. xiaomi.eu) (from TWRP on phone) and then reboot to system?
- Q. When do we need to select wipe cache option in TWRP?
Thanks much
powerofone said:
[Noob] Need help to confirm/correct basic understanding of root/custom ROM process involving the latest apks/roms etc.
Device (RN4SD) bootloader unlocked, running MIUI 8.5.8 Stable ROM
Root access only, stock ROM:
1. Only Magisk v.14, No TWRP
- Place stock recovery.img (extracted from mido ROM folder) into phone internal storage
- Install Magisk Manager v.5.4.0 apk on Phone
- Q. Whether to install Magisk v14 zip from Magisk Manager or from MiFlash on PC?
- Q. If from MiFlash on PC, whether to unzip Magisk v.14 into a folder?
- Q. How to patch with stock recovery?
- Q. Whether to select dm-verity option in Manager?
- Q. Will lazyflasher still be needed? If yes, when and how to be flashed?
- Q. Will reboot to system boot into stock ROM, now with root access?
2. Root Access and Custom ROM (e.g. xiaomi.eu)
- Flash install TWRP 3.1.1.0.img (from MiFlash through PC)
- Flash install lazyflasher zip (from TWRP on phone)
- Flash install Magisk v.14 zip (from TWRP) on phone
- Q. Now Reboot? Will this boot into existing MIUI ROM?
Or
- Q. Flash/install custom rom (e.g. xiaomi.eu) (from TWRP on phone) and then reboot to system?
- Q. When do we need to select wipe cache option in TWRP?
Thanks much
Click to expand...
Click to collapse
Well, I guess, I've no idea about MIUI, but fact that currently I'm running on Xiaomi.eu ROM. I just flashed latest magisk via TWRP, that's it. There's no need to extract it and install apk, as I already said, just flashing magisk zip via TWRP is enough on eu, not sure about other miui Roms.
Custom ROMs and magisk? Ezz easy bruh, all you've to do is to get the latest Magisk zip from magisk thread and flash it via TWRP. There's no need to extract it and install it separately on custom Roms. That's it.
Edit : nah, I didn't flash lazyflasher.zip on either eu or custom Roms. Just flash magisk and boot into system.
if you using official miui rom and using official twrp, you must flash lazyflasher, otherwise you cannot boot into system.
Sent from my Redmi Note 4 using Tapatalk
Ok so Let me go through the whole story. I wanted to root my Xperia z3 tablet compact SPG611 and I was being a bit of a noob so I opened the bootloader and I was so eager so I get on to rooting as I did it before on my Xperia z3 but on that I dropped it and it broke sooo... but yeah I went to this thread https://forum.xda-developers.com/z3...ment/advanced-stock-kernel-twrp-root-t2959720 and flashed this onto my tablet. But I had 2 problems I was in a boot loop but I was able to go to recovery and the twrp is at v2.7.1.0 so my clever self decided to wipe everything, I mean everything off of the tablet and I didn't back up. This meant that I had no os installed and I can't download a custom rom because there is always a problem, mainly cannot execute updater-binary when I flash paranoid. Also when I flash a newer version of twrp through fast boot it says finished okay but doesn't update on my tablet.
So I'm basically asking has anyone either got a way of updating twrp or a download for another recovery and has anyone got either a stock rom or a custom rom that they dowloaded on a Xperia z3 tablet compact SPG611 that actually worked.
Sorry for the long issue but can someone please help it would be the most appreciated.
Thanks in advance.
I always embed both twrp, SuperSU and Xposed Framework inside the kernel with the Rootkernel script. The only downside is that you have to use this procedure when updating Xposed and SuperSU.
After you created the patched kernel, just flash the kernel with fastboot. After that you have twrp (and SuperSU and Xposed if you included those).
Systemless Root & SafetyNet working [GUIDE][Magisk][StockROM-6.0.1][SkyMelon][TWRP]
Hi XDA friends,
After quite investigation I finally have found the way to have our devices Systemless Rooted.
The main advantage? SafetyNet working on our rooted device. That means Google does not notice our device is rooted ...yes, you can play Nintendo games or use Android Pay as well!
View attachment 4371569 View attachment 4371476
Here is the step by step guide:
You Must Have: Unlocked bootloader, ADB Fastboot drivers and Flashtool installed.
- Flash Stock Android 6.0.1 ROM with Flashtool (Wipes checked). I recommend 26.3.A.1.33 for the E2303 model. You can find Stock ROMs in this post.
- Flash TWRP from ADB: "fastboot flash recovery recovery.img" (I tried with v3.0.2.0 and also the new v3.2.1-0 recently published here!)
- Flash custom kernel (SkyMelon 8.1 or 9 without-root) from TWRP. Download v8.1 from this post or v9 directly here: View attachment 9-20171210-no-root.zip. Wipe Dalvik/Cache after install it.
- Flash the latest version of Magisk with TWRP. Wipe Dalvik/Cache after install it. GitHub repo: https://github.com/topjohnwu/Magisk/releases
- Install the latest version of Magisk Manager.apk. GitHub repo: https://github.com/topjohnwu/MagiskManager/releases
- [Optional] In order to avoid flashing errors with TWRP it is recommended to update directly through Magisk Manager. If you want to install previous versions of Magisk (between v14.6 and v15.2), could be neccesary to check the box "Preserve AVB 2.0/dm-verity" before "Direct Install" it.
Note: Magisk v16.4 and Magisk Manager v5.7.0 was the last version working tested by me. From this version I will discontinue testing new Magisk releases on this device. Feel free to post your experience with the new ones
- This method is compatible with E2303, E2306 (reported by @zputnyq) and E2333 (reported by @Yester_Ko) models.
- Compatibility with Apps2SD reported by @tim_pear
Please if this works for you, thanks are very welcome to my first post! Also ideas or improvements to the post are welcome.
Credits:
- Special thanks to @osmank3 who built SkyMelon v9 without-root and help me with Magisk updates.
thanks for sharing your experience , I have A question what about DRM fix , did restore you TA backup ?
Hi! Thanks for your guide. Can you share your safety net check screen on magisk? I try that kernel and some other kernels with different magisk versions, but I don't understand safety net checking status.
Hi othmane.os,
I cannot provide information about restoring the TA. My warranty expired some time ago and I don´t have a TA backup.
Thanks for comment.
othmane.os said:
thanks for sharing your experience , I have A question what about DRM fix , did restore you TA backup ?
Click to expand...
Click to collapse
Hi osmank3,
I have modified the post with the screenshot request and also with some links to the material used in the guide.
If you have any problem, I will be glad to help you. Thanks for comment.
osmank3 said:
Hi! Thanks for your guide. Can you share your safety net check screen on magisk? I try that kernel and some other kernels with different magisk versions, but I don't understand safety net checking status.
Click to expand...
Click to collapse
I want to use your guide but I'm busy to do current configuration of my phone. I delete some files on my system partition for gaining storage (I copied some new versions of upgraded apps to system partition) This take my time but I haven't got enough.
I use skymelon 9 kernel, with supersu. I guess because of supersu changed system partition and safetynet fails. I dislike supersu app but skymelon 9 comes with it. So I built skymelon 9 myself without supersu, but I didn't flash stock rom before installing skymelon 9 without-root and magisk. Now on my phone Magisk15 and skymelon9(compiled by me) installed. Magisk's hide function hiding itself from google apps and choosen apps but safetynet check fails.
Can you or anybody try this guide with skymelon 9 without-root which built by me?
View attachment 9-20171210-no-root.zip
Thanks
Hi osmank3,
I have tested the kernel that you built and it is working perfect. Thank you! This version has been added to the post and of course is menctioned your contribution.
I'm afraid you'll have to install a stock ROM...
BTW: I cannot get working Magisk v15. If I install it direclty from Magisk Manager the installation fails. If I install it through TWRP (and do wipes), the process is correct but when I check it, Magisk Manager not shows it as installed. So for the moment, it is only working for v14.5.
osmank3 said:
I want to use your guide but I'm busy to do current configuration of my phone. I delete some files on my system partition for gaining storage (I copied some new versions of upgraded apps to system partition) This take my time but I haven't got enough.
I use skymelon 9 kernel, with supersu. I guess because of supersu changed system partition and safetynet fails. I dislike supersu app but skymelon 9 comes with it. So I built skymelon 9 myself without supersu, but I didn't flash stock rom before installing skymelon 9 without-root and magisk. Now on my phone Magisk15 and skymelon9(compiled by me) installed. Magisk's hide function hiding itself from google apps and choosen apps but safetynet check fails.
Can you or anybody try this guide with skymelon 9 without-root which built by me?
View attachment 4371416
Thanks
Click to expand...
Click to collapse
GameBoy1989 said:
BTW: I cannot get working Magisk v15. If I install it direclty from Magisk Manager the installation fails. If I install it through TWRP (and do wipes), the process is correct but when I check it, Magisk Manager not shows it as installed. So for the moment, it is only working for v14.5.
Click to expand...
Click to collapse
I'm using magisk manager to patch boot.img with v15. I flash patched_boot.img with TWRP. It is working.
When I update it from v14.5 /data/magisk link crashing. I delete /data/magisk and upgrade on magisk manager as recommended type and reboot system, it is starting to work.
Ups! I forget to say. Check AVB 2.0/dm-verity
It works
Thank you very much. Post updated!
osmank3 said:
I'm using magisk manager to patch boot.img with v15. I flash patched_boot.img with TWRP. It is working.
When I update it from v14.5 /data/magisk link crashing. I delete /data/magisk and upgrade on magisk manager as recommended type and reboot system, it is starting to work.
Ups! I forget to say. Check AVB 2.0/dm-verity
Click to expand...
Click to collapse
Hey, i downloaded Magisk v14.5 and tried to flash it with twrp but i got error "invalid zip file format" What should i do now or what did i do wrong?
Yay i got this work but little bit different way.
1. Flashed stock rom with flashtool. I downloaded my stock rom from XperiFirm.
2. Flashed TWRP with this guide.
3. Flashed Skymelon 8.1 with TWRP and wiped Dalvik/Cache after install.
4. Flashed Magisk v14.0 with TWRP from this post and wiped Dalvik/Cache after install.
When that was done i rebooted and Magisk and Magick manager was installed. They aren't latest versions so i updated them.
1. Downloaded latest Magisk manager from here and installed it.
2. From Magisk manager i checked "Preserve AVB 2.0/dm-verity" and installed it with choosing the recommended option "Direct Install"
Everything seems to working fine and i did this to my E2303 with 26.3.A.1.33
Great! Thanks for sharing :good:
Which is the difference between methods? I see that it also works for you by flashing Magisk v14.0.
Artsii said:
Yay i got this work but little bit different way.
1. Flashed stock rom with flashtool. I downloaded my stock rom from XperiFirm.
2. Flashed TWRP with this guide.
3. Flashed Skymelon 8.1 with TWRP and wiped Dalvik/Cache after install.
4. Flashed Magisk v14.0 with TWRP from this post and wiped Dalvik/Cache after install.
When that was done i rebooted and Magisk and Magick manager was installed. They aren't latest versions so i updated them.
1. Downloaded latest Magisk manager from here and installed it.
2. From Magisk manager i checked "Preserve AVB 2.0/dm-verity" and installed it with choosing the recommended option "Direct Install"
Everything seems to working fine and i did this to my E2303 with 26.3.A.1.33
Click to expand...
Click to collapse
GameBoy1989 said:
- Flash Magisk v14.5 from TWRP. Wipe Dalvik/Cache after install it. GitHub repo: https://github.com/topjohnwu/Magisk/releases
Click to expand...
Click to collapse
This was only thing i made differently. I didn't find right magisk there what would work when flashing because i had problem with "invalid zip file format" so i downloaded that magisk zip file from another place.
This worked fine for me but I directly tried flashing/installing latest version (15.1) from TWRP and later after booting via adb the .apk of the Manager.
Didn't show the Magisk as installed.
With making a backup in TWRP of the boot (just renaming it to .img it has a different extension in the name) and then modifying it (as Manager tells you when you want to install) I could make it work (flashing the modified boot image with fastboot).
(Other steps like flashing the stock ROM and the recovery worked as usual. Also no problems with installing the kernel in TWRP.)
If you try to flash directly the last Magisk version (v15.1 in this case) I don´t know why yet but it doesn´t work. For that reason it is neccesary to first flash Magisk v14.5 (last version working with TWRP).
The way that you do it is also a very good one! Thanks for sharing @lordmd.
lordmd said:
This worked fine for me but I directly tried flashing/installing latest version (15.1) from TWRP and later after booting via adb the .apk of the Manager.
Didn't show the Magisk as installed.
With making a backup in TWRP of the boot (just renaming it to .img it has a different extension in the name) and then modifying it (as Manager tells you when you want to install) I could make it work (flashing the modified boot image with fastboot).
(Other steps like flashing the stock ROM and the recovery worked as usual. Also no problems with installing the kernel in TWRP.)
Click to expand...
Click to collapse
After magisk 14.6+ there is a problem about dm-verity. Magisk can't patch it, so we must preserve the original dm-verity. When you are applying magisk 14.6+ from twrp, you can't preserve and magisk can't patch it. The true way is using magisk manager and patch with preserve dm-verity.
Magisk 15.2 version notes says that problem solved but I try it, it is not solved yet.
My first applying procedure is:
First, patch skymelon 9 boot.img file with new magisk version also with preserve dm-verity on Magisk Manager,
Flash recovery and open with twrp
Apply skymelon 9 wipe dalvik and cache
Apply new magisk
Flash patched img
Let´s see if the next v15.3 beta finally works. Thanks @osmank3
BTW: Did you finally install the stock ROM or could you unroot your CFW for installing Magisk?
osmank3 said:
After magisk 14.6+ there is a problem about dm-verity. Magisk can't patch it, so we must preserve the original dm-verity. When you are applying magisk 14.6+ from twrp, you can't preserve and magisk can't patch it. The true way is using magisk manager and patch with preserve dm-verity.
Magisk 15.2 version notes says that problem solved but I try it, it is not solved yet.
My first applying procedure is:
First, patch skymelon 9 boot.img file with new magisk version also with preserve dm-verity on Magisk Manager,
Flash recovery and open with twrp
Apply skymelon 9 wipe dalvik and cache
Apply new magisk
Flash patched img
Click to expand...
Click to collapse
GameBoy1989 said:
Let´s see if the next v15.3 beta finally works. Thanks @osmank3
BTW: Did you finally install the stock ROM or could you unroot your CFW for installing Magisk?
Click to expand...
Click to collapse
I must flash system partition from stock Rom, after that safetynet passed.
Ty
Is pexorom better than stock. Is this going to work on pexorom.
Please reply
I´ve tried with Pexo Rom v3 and systemless root works with Magisk but it does not passed Safety Net check.
Sayan Qadri said:
Is pexorom better than stock. Is this going to work on pexorom.
Please reply
Click to expand...
Click to collapse
Hi my oneplus nord 2 pac man edition has the stock Android 12 / DN2103_11_C.12How can I install the twrp to flash the new a13 Roms like derpfest?
Is there a way to do this without a windows pc?
Thx looking forward to try new roms.
yes its possible, first install the latest version of framaroot here https://forum.xda-developers.com/t/root-framaroot-a-one-click-apk-to-root-some-devices.2130276/
then on top select install supersu and at the bottom there will be 3 options of rooting, try all of the until one works, after roting install the twrp app here https://dl.twrp.me/twrpapp/me.twrp.twrpapp-26.apk.html
and then when you have rooted and installed the twrp app, agree to everything in the twrp app and its important to select use wirh root permissions, then you will have three options, select file to flash, flash to recovery, flash to boot, click on select file to flash, then select the twrp for a12, and flash to recovery, then reboot to recovery and boom you have twrp, if flash to recovery doesnt work try flash to boot.