Related
I am sure this is a noob question here so I apologize in advance. I am a bit confused about how to go about disabling / removing encryption on my Nexus 6. When I look into it, it seems to be required to flash a new boot.img. However, you already need to use a modified boot.img to root.
So, once you are rooted, you can change your boot.img without losing root?
Does the modified boot.img from Chainfires post already disable / remove encryption?
Is there a modified boot image that disables encryption and allows root?
When I am in Titanium Backup, I see encryption: DISABLED. Is that telling me that my phone encryption is disabled or that just Titanium Backup Encryption is disabled?
Also, now there is MRA58K/N/R. Chainfires post has the modified boot image from K. Has the boot.img changed at all from K to N to R? If so, how can one still use the modified boot.img from K after flashing to R?
1. you need to flash a modified kernel(boot.img) that allows for decryption.
2. secondly, you have to format your user data and cache, which will delete everything from your phones storage.
3. now when you boot up, you will be decrypted.
simms22 said:
1. you need to flash a modified kernel(boot.img) that allows for decryption.
2. secondly, you have to format your user data and cache, which will delete everything from your phones storage.
3. now when you boot up, you will be decrypted.
Click to expand...
Click to collapse
I understand this. What I am wondering though, if this will remove root being you have to flash a modified boot image to obtain root. This is why I am confused. Does the modified boot image from chainfire for rooting the Nexus 6 remove encryption? I see where it may disable forced encryption, but does that mean that it removes encryption as well? Here is the post:
http://forum.xda-developers.com/apps/supersu/wip-android-6-0-marshmellow-t3219344
Sorry if I sound straight noob. I just don't get it. If I follow the root method which already requires a modified boot.img, how can I turn around and then flash yet another modified boot.img to remove encryption? Or does the modified boot.img for root also remove encryption?
Rektifying said:
I understand this. What I am wondering though, if this will remove root being you have to flash a modified boot image to obtain root. This is why I am confused. Does the modified boot image from chainfire for rooting the Nexus 6 remove encryption? I see where it may disable forced encryption, but does that mean that it removes encryption as well? Here is the post:
http://forum.xda-developers.com/apps/supersu/wip-android-6-0-marshmellow-t3219344
Sorry if I sound straight noob. I just don't get it. If I follow the root method which already requires a modified boot.img, how can I turn around and then flash yet another modified boot.img to remove encryption? Or does the modified boot.img for root also remove encryption?
Click to expand...
Click to collapse
you can flash different kernels all day long, and youll never lose root. only if you flash a rom will you lode root. about chainfires kernel i am clueless.
simms22 said:
you can flash different kernels all day long, and youll never lose root. only if you flash a rom will you lode root. about chainfires kernel i am clueless.
Click to expand...
Click to collapse
Do you have a Nexus 6? The current root method required a modified boot.img. So are you saying that after you flash the modified boot.img and obtain root, you then can change the boot.img and still have root?
Anyone else care to answer this for me? I am newer to Android period so I apologize again for sounding noob. I just don't fully quite understand how this root method works. So if a modified boot.img is required for root, how can I turn around and flash a different boot.img and still have root?
I am literally sitting here waiting to flash my Nexus 6 to MRA58R until I figure this out. I am well aware how to flash stock images, custom recovery, sideload superSU. I just want to clean flash my Nexus 6, have root, and have encryption disabled.
Rektifying said:
Do you have a Nexus 6? The current root method required a modified boot.img. So are you saying that after you flash the modified boot.img and obtain root, you then can change the boot.img and still have root?
Click to expand...
Click to collapse
i use despair kernel. technically, any custom kernel is a modified kernel. and it alows for decryption, even though i did not decrypt. i flashed marshmallow, flashed despair, then flashed supersu. now im on marshmallow with root.
what im saying is that i have never used chainfires kernel, so dont know anything about it.
I have been googling my a$$ off and still can not find an answer. All I wan't to know, is that after I obtain root on my Nexus 6, which requires a modified boot.img, can I turn around a flash a different boot.img, and still have root. I want my Nexus 6 to be rooted and not use encryption. That is all I wan't. I can not believe I am having this hard of a time figuring this out.
Everything I find even closely related to this is about 5.0 / 5.1. I am new to Android, my Nexus 6 is my first Android device and all I know is 6.0 Marshmallow. I believe the root methods for 6.0 are different than 5.0/5.1 but I could be wrong. I prefer direct answers. No where can I find a definite answer.
Rektifying said:
I have been googling my a$$ off and still can not find an answer. All I wan't to know, is that after I obtain root on my Nexus 6, which requires a modified boot.img, can I turn around a flash a different boot.img, and still have root. I want my Nexus 6 to be rooted and not use encryption. That is all I wan't. I can not believe I am having this hard of a time figuring this out.
Everything I find even closely related to this is about 5.0 / 5.1. I am new to Android, my Nexus 6 is my first Android device and all I know is 6.0 Marshmallow. I believe the root methods for 6.0 are different than 5.0/5.1 but I could be wrong. I prefer direct answers. No where can I find a definite answer.
Click to expand...
Click to collapse
first off, to make things easier, a boot.img is a kernel. you can flash any custom kernel when rooting on marshmallow, not just chainfires. if it doesnt allow unencryption, then you cam flash any other custom m kernel. you dont lose any information/data when flaahing kernels, so you never have to reroot. theres nothing hard here to understand, you can download and flash any kernel that you want, that will work on m. which one you chose is your choice. the vast amount of custom kernels allow for decryption.
simms22 said:
first off, to make things easier, a boot.img is a kernel. you can flash any custom kernel when rooting on marshmallow, not just chainfires. if it doesnt allow unencryption, then you cam flash any other custom m kernel. you dont lose any information/data when flaahing kernels, so you never have to reroot. theres nothing hard here to understand, you can download and flash any kernel that you want, that will work on m. which one you chose is your choice. the vast amount of custom kernels allow for decryption.
Click to expand...
Click to collapse
Ok lets leave encryption out of it a second. So lets say I have stock 6.0. I flash the modified boot image, sideload SuperSU, and I am now rooted. Then I turn around and flash the stock boot.img. SO I will still have root then?
Rektifying said:
Ok lets leave encryption out of it a second. So lets say I have stock 6.0. I flash the modified boot image, sideload SuperSU, and I am now rooted. Then I turn around and flash the stock boot.img. SO I will still have root then?
Click to expand...
Click to collapse
yes(but im not sure with marshmallow). with all other android builds, yes.
simms22 said:
yes(but im not sure with marshmallow). with all other android builds, yes.
Click to expand...
Click to collapse
Ok I think I am starting to get it now. So the modified boot image that is needed to obtain root, is only initially needed to initially obtain root. Once root is obtain, you can flash different boot.img's all day long and you will not lose root? I understand boot.img is the kernal?
Rektifying said:
Ok I think I am starting to get it now. So the modified boot image that is needed to obtain root, is only initially needed to initially obtain root. Once root is obtain, you can flash different boot.img's all day long and you will not lose root? I understand boot.img is the kernal?
Click to expand...
Click to collapse
yes.
but the thing i dont know about is that the stock marshmallow kernel might prevent root, even though the files are still there. but you can flash any marshmallow custom kernel(for n6).
I figured it out. Here is what I ended up doing. I hope it was the best way to do so. I probably went overboard with some stuff but I wanted to start fresh from stock.
Booted into TWRP Recovery and did a full wipe 3 times over
Rebooted to bootloader
Flashed bone stock MRA58R
Rebooted to bootloader
Flashed modified boot.img, reboot bootloader
Flashed TWRP Recovery, reboot into recovery
Format Data, disabling encryption
Installed SuperSU, Wiped Dalvik Cache / Cache
Reboot System
I am now running Android 6.0 MRA58R / Rooted / No Encryption
I did not realize that encryption could be disabled right in TWRP. So that is why I was so confused because I thought I had to flash a modified boot.img to obtain root (which you do), then a different modified boot.img for encryption removal. If that was the case, I was worried that flashing the modified boot.img for encryption removal would remove root. Oh well. I have it figured out now.
Thank you for your help @simms22. You have given me a better understanding of root access and kernals.
Rektifying said:
I figured it out. Here is what I ended up doing. I hope it was the best way to do so. I probably went overboard with some stuff but I wanted to start fresh from stock.
Booted into TWRP Recovery and did a full wipe 3 times over
Rebooted to bootloader
Flashed bone stock MRA58R
Rebooted to bootloader
Flashed modified boot.img, reboot bootloader
Flashed TWRP Recovery, reboot into recovery
Format Data, disabling encryption
Installed SuperSU, Wiped Dalvik Cache / Cache
Reboot System
I am now running Android 6.0 MRA58R / Rooted / No Encryption
I did not realize that encryption could be disabled right in TWRP. So that is why I was so confused because I thought I had to flash a modified boot.img to obtain root (which you do), then a different modified boot.img for encryption removal. If that was the case, I was worried that flashing the modified boot.img for encryption removal would remove root. Oh well. I have it figured out now.
Thank you for your help @simms22. You have given me a better understanding of root access and kernals.
Click to expand...
Click to collapse
awesome
Rektifying said:
I figured it out. Here is what I ended up doing. I hope it was the best way to do so. I probably went overboard with some stuff but I wanted to start fresh from stock.
Booted into TWRP Recovery and did a full wipe 3 times over
Rebooted to bootloader
Flashed bone stock MRA58R
Rebooted to bootloader
Flashed modified boot.img, reboot bootloader
Flashed TWRP Recovery, reboot into recovery
Format Data, disabling encryption
Installed SuperSU, Wiped Dalvik Cache / Cache
Reboot System
I am now running Android 6.0 MRA58R / Rooted / No Encryption
I did not realize that encryption could be disabled right in TWRP. So that is why I was so confused because I thought I had to flash a modified boot.img to obtain root (which you do), then a different modified boot.img for encryption removal. If that was the case, I was worried that flashing the modified boot.img for encryption removal would remove root. Oh well. I have it figured out now.
Thank you for your help @simms22. You have given me a better understanding of root access and kernals.
Click to expand...
Click to collapse
I was trying to figure out the same thing. What modified boot.img did u use for root access and which modified boot.img did u use to remove encryption. Thanks.
Basically any kernel that does not check encryption and force it to be applied... In other words almost any 3rd party kernel... But double check the kernels feature list and make sure it says no forced encryption.
The device will probably give you a "system is corrupt" error with a stock kernel and root installed. I would flash a custom kernel for sure because it usually doesn't force encryption and does support root! I am using elementalx right now and it's a very good kernel for this. Many other custom kernels work just as well! I HAVE used chainfire's kernel, and it does not force encryption, it also supports root, I can confirm this. If you use chainfire's kernel, make sure you format your data to unencrypt. You can use the "format data" option in TWRP or use the fastboot command "fastboot format userdata". Hope I helped!
EDIT: You have to format your data to decrypt regardless of WHICH kernel you choose, sorry if that sounded confusing.
I am looking for an easy way to be able to receive OTA updates after rooting with the 'systemless' root method, the steps I mention below assume that the system partition remains untouched after rooting. I have searched and not found a clear answer on this.
Would I be correct in assuming that this procedure should work to receive an OTA update and keep stock recovery after rooting?
Start with completely stock Android 6.0
fastboot boot twrp-recovery.img (boot TWRP, NOT flash, to maintain stock recovery after rooting)
Flash systemless root with TWRP
OTA arrives (Android 6.0.1 for example)
fastboot flash boot boot.img (with stock 6.0 kernel, root lost)
Accept & install OTA update
Success?
So unless I am missing something, this method would leave the system in a stock, unrooted state after the OTA is installed, and could be repeated for future updates. Anybody have any experience with this yet?
Sounds like it will work, but why mess with the ota? More work and risk honestly.
Since you're already using fastboot just flash the newest boot and system.img. Then flash/boot twrp and flash su like you'd need to do anyway. Done. You don't lose anything flashing system.
yosmokinman said:
Sounds like it will work, but why mess with the ota? More work and risk honestly.
Since you're already using fastboot just flash the newest boot and system.img. Then flash/boot twrp and flash su like you'd need to do anyway. Done. You don't lose anything flashing system.
Click to expand...
Click to collapse
That is true, kind of just wondering/gathering information. It just seemed like with the new root method, OTA would be possible and less risky than before.
Sent from my MotoG3 using Tapatalk
@quakeaz there is one step missing on your guide. After boot.img you also have to flash stock recovery.img. From Lollipop, Google is also checking installed recovery, and for successful OTA, it has to be stock as well.
Otherwise, your guide should work, I've done same thing with my Nexus 5 and 7 for like last 3 months.
Srandista said:
@quakeaz there is one step missing on your guide. After boot.img you also have to flash stock recovery.img. From Lollipop, Google is also checking installed recovery, and for successful OTA, it has to be stock as well.
Otherwise, your guide should work, I've done same thing with my Nexus 5 and 7 for like last 3 months.
Click to expand...
Click to collapse
Thanks for your reply, but I intentionally left that step out, due to step 2 in my list. By only booting TWRP, instead of flashing, I assume stock recovery will remain after rooting.
Sent from my MotoG3 using Tapatalk
quakeaz said:
Thanks for your reply, but I intentionally left that step out, due to step 2 in my list. By only booting TWRP, instead of flashing, I assume stock recovery will remain after rooting.
Sent from my MotoG3 using Tapatalk
Click to expand...
Click to collapse
Ah, sorry, I overlooked that.
Since I have flashed TWRP instead of stock recovery, I'm going by same process as you write, just reflash stock recovery. And can confirm, that the process is indeed working (no need to install system.img, as with previous system-based SuperSU).
Sounds good!
Sent from my MotoG3 using Tapatalk
quakeaz said:
I am looking for an easy way to be able to receive OTA updates after rooting with the 'systemless' root method, the steps I mention below assume that the system partition remains untouched after rooting. I have searched and not found a clear answer on this.
Would I be correct in assuming that this procedure should work to receive an OTA update and keep stock recovery after rooting?
Start with completely stock Android 6.0
fastboot boot twrp-recovery.img (boot TWRP, NOT flash, to maintain stock recovery after rooting)
Flash systemless root with TWRP
OTA arrives (Android 6.0.1 for example)
fastboot flash boot boot.img (with stock 6.0 kernel, root lost)
Accept & install OTA update
Success?
So unless I am missing something, this method would leave the system in a stock, unrooted state after the OTA is installed, and could be repeated for future updates. Anybody have any experience with this yet?
Click to expand...
Click to collapse
Instead of fastboot flashing boot.img, you can use "Settings --> Full Unroot" in SuperSU. During SuperSU systemless flash, your old boot image is backed up. Among other things, the full unroot option will restore the backup, assuming it hasn't been lost due to a factory reset and whatnot.
On many firmwares, this procedure also restores stock recovery. This requires that both the firmware supports recreating the recovery from the boot image plus a patch file (most do), and that TWRP did not remove said patch file (which some versions do).
That being said, if you're using fastboot anyway, flashing boot, recovery, system and vendor manually is always the safest thing before an OTA.
Thanks for the info. So I take it while using systemless root, installing ota without unrooting is a big nono? The January ota just downloaded and is asking me to install, should I do it manually?
Chainfire said:
Instead of fastboot flashing boot.img, you can use "Settings --> Full Unroot" in SuperSU. During SuperSU systemless flash, your old boot image is backed up. Among other things, the full unroot option will restore the backup, assuming it hasn't been lost due to a factory reset and whatnot.
On many firmwares, this procedure also restores stock recovery. This requires that both the firmware supports recreating the recovery from the boot image plus a patch file (most do), and that TWRP did not remove said patch file (which some versions do).
That being said, if you're using fastboot anyway, flashing boot, recovery, system and vendor manually is always the safest thing before an OTA.
Click to expand...
Click to collapse
Thank you for this thread and the procedure. I tried myself to avoid as much as possible to use a computer for super easy OTA update. But there is always one obligatory step: to root the phone.
Phone systemless rooted (2.66) - TWRP installed - OTA arrives.
In SuperSu app : Fully unroot
Install OTA - success
Fastboot boot (or install) TWRP
Flash superSu 2.66.zip
And that's it!
My question is the following: Does it exist a possibility to load on step 3. something that could flash superSu.zip from within the phone, no computer required?
Maybe FlashFire? I guess not, for it needs root and the point is to flash a rooting zip... You see the loop there...
Would it be theoreticaly possible at all?
Judim said:
Maybe FlashFire? I guess not, for it needs root and the point is to flash a rooting zip... You see the loop there...
Would it be theoreticaly possible at all?
Click to expand...
Click to collapse
Yes, this is one of the use-cases of FlashFire. I just haven't finished updating it to 6.0 yet.
Oh nice!
I didn't know it cause I never had the chance to try out FlashFire.
Thanks so much for everything you do for the Android community!
Cheers!
Srandista said:
Ah, sorry, I overlooked that.
Since I have flashed TWRP instead of stock recovery, I'm going by same process as you write, just reflash stock recovery. And can confirm, that the process is indeed working (no need to install system.img, as with previous system-based SuperSU).
Click to expand...
Click to collapse
mine fail here. i previously got systemless root 2.62, blu spark kernel and twrp. fastboot flash stock boot and recovery. reboot to update and it fail. any idea why?
ShanxRoux said:
mine fail here. i previously got systemless root 2.62, blu spark kernel and twrp. fastboot flash stock boot and recovery. reboot to update and it fail. any idea why?
Click to expand...
Click to collapse
Did you modify system?
Try flashing system, boot, and recovery.
Then try again.
Hi, I have a Oneplus One and today has been released an OTA, so I tried the method. I have COS13 JK (latest full rom) firmware, with systemless 2.84beta supersu and twrp.
The only apps that have root access are AdAway and Greenify (without mods to system apps). No Busybox installed.
I reverted via fastboot to original JK boot.img and recovery.img, and restored, via Adaway, the original hosts file, then I applied the OTA via stock Cyano Recovery, but update failed ("system partition has unexpected contents" error).
Why?
Thanks.
you have to unroot first from the app.Revert to original boot. and then flash
Sent from my ASUS_Z00LD using Tapatalk
caldent said:
you have to unroot first from the app.Revert to original boot. and then flash
Sent from my ASUS_Z00LD using Tapatalk
Click to expand...
Click to collapse
I tried: no way to install OTA, I had to wait for the full rom, and dirty flashed it via TWRP without a problem.
Then I rerooted.
Bye!
ok i seem to be getting the run around on where i need to be to ask my question(s)
i am very interested in systemless root....
that being said i am clueless and all info i am findingis just super confusing me.
if someone could humor a noob to systemless rooting that would be greatly appreciated!!
i recently bought 2 new phone for my household, both are the lg tribute hd (also called lg x style)
one click root and pc method of kingoroot etc dont work... i cant locate a twrp or a cwm for this model easily by searching so i am assuming there isnt one (maybe someone could located or help to build one?)- or maybe im not tech smart enough and i can use any?(i dont think so)
model is lg ls675,android 6.0.1, kernel version 3.10.49, build # MXB48T, software is ls676zv3
main reason at the moment for trying to get root is to remove bloatware and to be able to wifi tether without limitations buy the provider, on ther phone that i have obtained root on i used an app called WIFI Tether Router which works beautifully but requires root...
please help as this is how we use our computer with internet and its beneficial all the way around especially to get rid of bloatware and keep device running smoothly...
thanks again for any help. greatly appreciated.
if im not in the right thread please kindly direct me to the correct one. thanks
Wow no need for custom recovery...
http://www.androidpolice.com/2017/0...hout-root-installing-without-custom-recovery/
@ultramag69 Maybe he doesn't follow Magisk closely? I know I don't. Magisk is only on used my stepmom's OP3T H2OS (which I update but don't look at the change log since it's only there in case I need it in the future), the other 2 phones I support don't use Magisk they use LOS su add-on. Not everyone who uses root cares about all the bloated/"nifty" features that come out, some just want plain old root.
I only use for root too but every so often I open magisk manager as it updates both the manager app and magisk itself....
It's done that for ages... The only one I found that didn't was 13.1, that one needed TWRP.
I'm letting people know that with 14 they can keep stock recovery and take OTAs
ultramag69 said:
I only use for root too but every so often I open magisk manager as it updates both the manager app and magisk itself....
It's done that for ages... The only one I found that didn't was 13.1, that one needed TWRP.
Click to expand...
Click to collapse
Before you flame someone you should read the link. FOR THE FIRST TIME YOU CAN KEEP STOCK RECOVERY SO YOU CAN TAKE OTAS
lollyjay said:
Before you flame someone you should read the link. FOR THE FIRST TIME YOU CAN KEEP STOCK RECOVERY SO YOU CAN TAKE OTAS
Click to expand...
Click to collapse
I have had stock recovery on more than one without having to reflash recovery with custom one .
If you use fastboot to flash the recovery, Instead of replacing with TWRP, you can use the command "fastboot boot TWRP.img" (TWRP.img being the name of the TWRP image you have such as twrp-3.1.1-0-oneplus5.img) , this will just boot you into TWRP where you can flash SuperSU or Magisk as you please but will revert back to stock recovery once you boot again while retaining root.
ultramag69 said:
I have had stock recovery on more than one without having to reflash recovery with custom one .
If you use fastboot to flash the recovery, Instead of replacing with TWRP, you can use the command "fastboot boot TWRP.img" (TWRP.img being the name of the TWRP image you have such as twrp-3.1.1-0-oneplus5.img) , this will just boot you into TWRP where you can flash SuperSU or Magisk as you please but will revert back to stock recovery once you boot again while retaining root.
Click to expand...
Click to collapse
No need to do that now
Honestly, who roots a phone without flashing a custom recovery the very second after? Unless they are forced to use Flashfire without BL unlock, I guess.
lollyjay said:
No need to do that now
Click to expand...
Click to collapse
Yeah, but using magisk to root my Axon 7 with unlocked bootloader didn't work...
There's still problems with some phones...
ultramag69 said:
Yeah, but using magisk to root my Axon 7 with unlocked bootloader didn't work...
There's still problems with some phones...
Click to expand...
Click to collapse
No problems at all with my OP5
Magisk 14.0 breaks XPosed so had to go back to Magisk 13.3
Now where can we obtain a copy of the stock boot.img?
almostthere said:
Now where can we obtain a copy of the stock boot.img?
Click to expand...
Click to collapse
What you're supposed to do is make a backup of your boot partition any time you update your rom. So if you didn't do that then you can dirty flash your current Rom and that would give you the stock boot.img and again, go into recovery and make a backup of your boot partition. then if you want to flash a custom kernel you can.
Help the noobs
Would any of you more experienced guys please post a step-by-step of how to do it?
From what Eric214 wrote I still don't understand where (or how) to get a copy of the stock_boot.img.
If you get the copy of the stock boot image, is it possible to do it without unlocking the bootloader?
I already installed everything before reading how to root - stupid me, and don't want to reinstall everything.
s_ofer said:
Would any of you more experienced guys please post a step-by-step of how to do it?
From what Eric214 wrote I still don't understand where (or how) to get a copy of the stock_boot.img.
If you get the copy of the stock boot image, is it possible to do it without unlocking the bootloader?
I already installed everything before reading how to root - stupid me, and don't want to reinstall everything.
Click to expand...
Click to collapse
I have the stock 4.5.10 boot.img for download here:
https://drive.google.com/file/d/0B3gcDbDvV4Mkbm5EMEZ4dnpSbk0/view?usp=drivesdk
Sent from my OnePlus5 using XDA Labs
Thanks.
Do any of you think it is possible to FLASH anything without unlocking the bootloader?
There is a thread somewhere for OP3T that shows somehow that is possible to load TWRP on the phone without unlocking the bootloader or wiping data.
I only use for root too but every so often I open magisk manager as it updates also both the manager app and magisk itself. But using magisk to root my Axon 7 with unlocked bootloader.
I have a Samsung Galaxy S7 edge, international version, Android 6, unlocked bootloader, rooted with CF-auto-root, now has SuperSU installed, pure stock rom.
And I am wondering whether it will be possible to install Magisk (even if I have to uninstall SuperSU) without TWRP or any other custom recovery?
Will it also be possible to have full disk encryption (to be honest I don’t know whether my device is currently encrypted - is there a way to check this)?
orifori said:
I have a Samsung Galaxy S7 edge, international version, Android 6, unlocked bootloader, rooted with CF-auto-root, now has SuperSU installed, pure stock rom.
And I am wondering whether it will be possible to install Magisk (even if I have to uninstall SuperSU) without TWRP or any other custom recovery?
Will it also be possible to have full disk encryption (to be honest I don’t know whether my device is currently encrypted - is there a way to check this)?
Click to expand...
Click to collapse
Yes it is possible... Check the magisk release thread for the method applicable for you... About encryption, it works just fine...
Edit: here https://forum.xda-developers.com/showthread.php?t=3473445
Sent from my MI 5 using Tapatalk
Thank you! I need some help regarding the Installation Instructions.
The stock rom I have (which is to be patched by Magisk Manager) is a ZIP file with 5 .tar.md5 files in it...
1 - Where should I copy it - internal phone memory?
2 - Should I copy the ZIP file or the 5 files in it?
3 - Magisk Manager asks for .RAR or .IMG file while I have a .ZIP - should I simply rename the .ZIP to .RAR or...?
4 - Installing CSC_... would do a wipe while HOME_CSC_... would not - and I definitely do not want a wipe - so how to proceed?
5 - If I want full device encryption I just tick Preserve force encryption option (I don't know whether the phone is now encrypted)?
orifori said:
Thank you! I need some help regarding the Installation Instructions.
The stock rom I have (which is to be patched by Magisk Manager) is a ZIP file with 5 .tar.md5 files in it...
1 - Where should I copy it - internal phone memory?
2 - Should I copy the ZIP file or the 5 files in it?
3 - Magisk Manager asks for .RAR or .IMG file while I have a .ZIP - should I simply rename the .ZIP to .RAR or...?
4 - Installing CSC_... would do a wipe while HOME_CSC_... would not - and I definitely do not want a wipe - so how to proceed?
5 - If I want full device encryption I just tick Preserve force encryption option (I don't know whether the phone is now encrypted)?
Click to expand...
Click to collapse
You need to patch and flash the boot image only. That'll be inside the ROM zip. Don't forget to change the output format in the Manager settings to .img.tar.
It usually says under Android settings -> Security if your device is encrypted or not. But I've no idea if Samsung do that. I don't do Samsung.
This has been discussed a few times in the Magisk forums already, so if you search you'll be able to find more info on it. Always do your homework before flashing...
Examples of threads to search and/or read trough:
https://forum.xda-developers.com/apps/magisk/mod-magisk-v1-universal-systemless-t3432382
https://forum.xda-developers.com/apps/magisk/magisk-discussion-thread-t3467229
https://forum.xda-developers.com/apps/magisk/flashing-patched-boot-img-odin-t3670503
Worked like a charm, thank you! Extracted AP_... file from the zip archive, them extracted boot.img file from AP_... file and copied it onto the SD card of the phone, then Magisk modified it, I copied it to my laptop and flashed it in Odin (AP field).
Everything works fine, except OTA updates - I try to download updates manually (About device -> Download updates manually) but I get a message "The operating system on your device has been modified in an unauthorized way."
So are OTA updates possible 1. without TWRP and 2. with preserved encryption - like in my case - and how is that possible? Maybe Magisk settings?
orifori said:
Everything works fine, except OTA updates - I try to download updates manually (About device -> Download updates manually) but I get a message "The operating system on your device has been modified in an unauthorized way."
So are OTA updates possible 1. without TWRP and 2. with preserved encryption - like in my case - and how is that possible? Maybe Magisk settings?
Click to expand...
Click to collapse
In order to be able to take an ota, you need stock recovery, with unmodified system, and probably stock boot... (Magisk only touched the boot.img, so you just need to restore that)...
Sent from my MI 5 using Tapatalk
orifori said:
Everything works fine, except OTA updates - I try to download updates manually (About device -> Download updates manually) but I get a message "The operating system on your device has been modified in an unauthorized way."
So are OTA updates possible 1. without TWRP and 2. with preserved encryption - like in my case - and how is that possible? Maybe Magisk settings?
Click to expand...
Click to collapse
You can't update with OTA if you've modified /system or the boot image (Magisk). A custom recovery would also cause it to fail, but that's not an issue for you...
Since you've got a Samsung there are probably more checks as well (unlocked bootloader and such).
You might have to flash updates manually... Best place for answers would be your device's forum.
Didgeridoohan said:
You can't update with OTA if you've modified /system or the boot image (Magisk)
Click to expand...
Click to collapse
So there is absolutely no chance for OTA updates in case of installed Magisk? I have a pure stock rom and the only thing modified is the boot.img file (modified by Magisk in order to gain root).
orifori said:
So there is absolutely no chance for OTA updates in case of installed Magisk? I have a pure stock rom and the only thing modified is the boot.img file (modified by Magisk in order to gain root).
Click to expand...
Click to collapse
You could restore the stock boot image to get the OTA and then re-root.
Don't know if Samsung updates care about KNOX (which will be triggered). I don't think they do, but I don't do Samsung so I can't say for sure...
I am trying to root my phone using magisk. I do not have any custom recovery. I was told that I can still root it by patching my stock boot image. But I couldn't find it anywhere. I do have my phone's stock firmware, and if I'm not wrong it Should be inside it, but the problem is that, the firmware file is in .nb0 format. I do not know how to open it and get access to the boot.img, can someone please help me.
My phone is Infocus m535
This is the firmware ?
mediafire.com/file/y2zru5gda08jder/Infocus_M535_G40-026P-0-00WW-A02.zip
???? Please help
Loku_kika said:
I am trying to root my phone using magisk. I do not have any custom recovery. I was told that I can still root it by patching my stock boot image. But I couldn't find it anywhere. I do have my phone's stock firmware, and if I'm not wrong it Should be inside it, but the problem is that, the firmware file is in .nb0 format. I do not know how to open it and get access to the boot.img, can someone please help me.
My phone is Infocus m535
This is the firmware [emoji116]
mediafire.com/file/y2zru5gda08jder/Infocus_M535_G40-026P-0-00WW-A02.zip
[emoji120][emoji120][emoji120][emoji120] Please help
Click to expand...
Click to collapse
Try 7zip...
You have to have an unlocked bootloader and a working fastboot in order to root without custom recovery...
Sent from my MI 5 using Tapatalk
Loku_kika said:
I am trying to root my phone using magisk. I do not have any custom recovery. I was told that I can still root it by patching my stock boot image. But I couldn't find it anywhere. I do have my phone's stock firmware, and if I'm not wrong it Should be inside it, but the problem is that, the firmware file is in .nb0 format. I do not know how to open it and get access to the boot.img, can someone please help me.
My phone is Infocus m535
This is the firmware
mediafire.com/file/y2zru5gda08jder/Infocus_M535_G40-026P-0-00WW-A02.zip
Please help
Click to expand...
Click to collapse
For future references: Samsungs firmware files can be compressed with their LZ4 format and thus needs to be uncompressed again in the case of a boot.img.lz4 file so that you have boot.img file which magisk then can properly use. Otherwise you might get an error sating something like: unable repack boot image, when trying to patch the boot image with Magisk.
guys i have flash magisk patched image without custom recovery and via fastboot but now I am always boot to recovery.. Phone doesnt start at all.
In focus m535 magisk
OK bro I try it
Sorry
Hi, I try do to same thing on my S7 but with a Oreo 8.0 Android version.
Perhaps it's change something.
And each time I reboot after flash a boot.img patched or even patch TWRP, my phone don't boot and ask me to reset it (in French it write reinistialisation in an tactile screen).
If I reload with Odin a BL, AP ect... my phone restart and I didn't lose any data. But it is no root.
Could you help me please ?
I want to root stock PIE rom releases(s) on my own, just for learning sake. I am having trouble figuring out how to extract the system.img.lz4, direct from the AP.md5. I ultimately want to be able to extract the system.img, so I can have it on hand to flash in TWRP, to keep the device from bootlooping on stock roms. Thanks
Amd4life said:
I want to root stock PIE rom releases(s) on my own, just for learning sake. I am having trouble figuring out how to extract the system.img.lz4, direct from the AP.md5. I ultimately want to be able to extract the system.img, so I can have it on hand to flash in TWRP, to keep the device from bootlooping on stock roms. Thanks
Click to expand...
Click to collapse
use the search feature.
...lz4 needs to be unpacked.
not sure what is to be learned but even rom devs make a script to flash root( magisk) after flashing/extracting the rom to the device. they just use the stock magisk.zip and flash that. nothing is integrated or baked in the rom.
anwyas you just need to find the lz4 unpacker
and bootloops are because stock kernel cant boot a device rhat have custom recovery. you have to flash magisk to patch the kernel. you can also use a custom kernel and flash that and be able to boot.