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.
Is it possible to dump the boot.img file without root to patch it and install Magisk? If so, how is that done?
niccotaglia said:
Is it possible to dump the boot.img file without root to patch it and install Magisk? If so, how is that done?
Click to expand...
Click to collapse
Short answer: no
Long answer: The boot.img cannot be touched at all because these Fire tablets have a locked bootloader. Tamper with the boot.img in any way, and the device will be bricked until you sideload the stock firmware. Current ROMs exist by gaining root, and then flashing a system.img that is compatible with the stock boot.img. This is why we are able to gain slimmed down ROMs (my favorite is FireNexus by ggow), but we can't install any kernels or magisk. Also, any root that is labeled as "system-less" works by injecting itself into the boot.img, so it won't work. This means SuperSu in system-less mode, and magisk.
Hope that helps.
So, just got the OTA update to Android Pie for my Mi 8 Global, and want to try flashing TWRP again. Every single version of TWRP I have flashed before has always either fail to boot, or always reboots into recovery and the ROM never loads. Anyone can suggest a real working TWRP file to flash? Do I need to wipe data? Etc. Since TWRP hasn't worked for me at all, I have to root with a roundabout way. Install Magisk Manager, extract and recompile boot.img into patched_boot.img and flash that in fastboot. This gives me roo but no TWRP so I can't flash any custom kernels or ROMs.
Rommco05 said:
Hi, I can't help you with twrp because I still waiting for countdown for unlocked it. From your post I understand u have a stock recovery.img, where u find stock recovery?
Click to expand...
Click to collapse
I just flash the stock boot.img and it reverts everything
Rommco05 said:
Where I can find stock .imgs?
Click to expand...
Click to collapse
Download a stock ROM and grab the boot.img from inside it.
I noticed that a lot of people are having problems updating to the latest Android 10 custom ROMs. The problem is that the stock base has changed to the BTFN version and TWRP can't flash it. The solution is to flash the TWRP version for BTFN with Odin but how to do that isn't very clear. So I extracted the right recovery.img file and made a tar file that you flash from AP with Odin
vbmeta.tar
https://drive.google.com/file/d/1k7-wkeGTfVEedoLkfdtUleZJUU0MQlZg/view?usp=sharing
Before flashing the TWRP tar, you must first flash the vbmeta.tar and let it reboot. It will take you to the stock recovery where you will need to perform a factory reset and let it reboot. Connect to wifi, skip everything and enable developer mode. Then goto download mode to flash TWRP. Turn off auto reboot before flashing. When its finished, hold vol down and power till the screen turns off. Immediately switch from vol down to vol up to boot to TWRP.
So use it to flash the ROM zip of your choice. Hope it helps.
edit: This is for the T510. I don't know if it will work for the T515
Hi, I have a T515 running on stock, BTH4. Before I try your TWRP and possibly have to reinstall the stock ROM again, where can I learn to make my own TWRP compatible with my ROM?
lewmur said:
I noticed that a lot of people are having problems updating to the latest Android 10 custom ROMs. The problem is that the stock base has changed to the BTFN version and TWRP can't flash it. The solution is to flash the TWRP version for BTFN with Odin but how to do that isn't very clear. So I extracted the right recovery.img file and made a tar file that you flash from AP with Odin
https://drive.google.com/file/d/1k7-wkeGTfVEedoLkfdtUleZJUU0MQlZg/view?usp=sharing
So use it to flash the ROM zip of your choice. Hope it helps.
edit: This is for the T510. I don't know if it will work for the T515
Click to expand...
Click to collapse
From where did you get the "right" recovery.img?
AdelCraftPro said:
From where did you get the "right" recovery.img?
Click to expand...
Click to collapse
From the latest Nexus ROM from Aug 7th.
AdelCraftPro said:
From where did you get the "right" recovery.img?
Click to expand...
Click to collapse
If you'll notice, I changed the OP to add the vbmeta.tar. It needs to be flashed first to allow custom binaries.
bedwere said:
Hi, I have a T515 running on stock, BTH4. Before I try your TWRP and possibly have to reinstall the stock ROM again, where can I learn to make my own TWRP compatible with my ROM?
Click to expand...
Click to collapse
I have no idea how to make a custom TWRP. I just extracted the recovery.img and vbmeta.img files from the custom Nexus ROM.
I would like to know if someone has managed to root with magisk from CMD without twrp?
You can root with magisk on any miui 14 without using twrp.Just get the boot image from the rom,install magisk apk and patch the boot.img, reboot to fastboot mode ,open cmd and write "fastboot flash boot_ab boot.img" just replace boot.img with the name of your generated magisk boot. The boot image is located in different location according to the rom you are using .Normal miui recovery rom contain file that called payload.bin.You need to download this tool https://github.com/tobyxdd/android-ota-payload-extractor. Follow the instructions in the link and you will get the boot.img .If you using miui.eu rom ,you just need to extract the zip and you will see the boot.img. Also if you want to use Miui 14 global or EEA, you can use the fastboot rom that I created and the zip file contain the boot.img .You can get download link on this thread link https://forum.xda-developers.com/t/fastboot-version-of-miui-14-eea-global-and-older-miui-13.4381953/ .
or965 said:
You can root with magisk on any miui 14 without using twrp.Just get the boot image from the rom,install magisk apk and patch the boot.img, reboot to fastboot mode ,open cmd and write "fastboot flash boot_ab boot.img" just replace boot.img with the name of your generated magisk boot. The boot image is located in different location according to the rom you are using .Normal miui recovery rom contain file that called payload.bin.You need to download this tool https://github.com/tobyxdd/android-ota-payload-extractor. Follow the instructions in the link and you will get the boot.img .If you using miui.eu rom ,you just need to extract the zip and you will see the boot.img. Also if you want to use Miui 14 global or EEA, you can use the fastboot rom that I created and the zip file contain the boot.img .You can get download link on this thread link https://forum.xda-developers.com/t/fastboot-version-of-miui-14-eea-global-and-older-miui-13.4381953/ .
Click to expand...
Click to collapse
ive use your method but my phone still gone to bootloop. im using eu rom currently.
martin132014 said:
ive use your method but my phone still gone to bootloop. im using eu rom currently.
Click to expand...
Click to collapse
What did you do? I wrote several options.
Hey Guys!!!
4 Android 13 we not use Magisk!!! We use Lygisk its a Version direct 4 Android 13 and works great!!!
you can choose witch File you would Patch Boot.img/Recovery.img!! So you can Boot with boot.img normaly into Rooted System!!! And when you Patch the Recovery.img and Flash this, you must start with the Button-Combo that starts Recovery-Mode, so its start the Rooted System, when you start it normaly not over Recovery-Mode the System is Not Rooted!!! Thats the Difference between the 2 Methods,and a Patched Recovery dont set you in Bootloop!!!
Lygisk APK ZIP
System23 said:
Hey Guys!!!
4 Android 13 we not use Magisk!!! We use Lygisk its a Version direct 4 Android 13 and works great!!!
you can choose witch File you would Patch Boot.img/Recovery.img!! So you can Boot with boot.img normaly into Rooted System!!! And when you Patch the Recovery.img and Flash this, you must start with the Button-Combo that starts Recovery-Mode, so its start the Rooted System, when you start it normaly not over Recovery-Mode the System is Not Rooted!!! Thats the Difference between the 2 Methods,and a Patched Recovery dont set you in Bootloop!!!
Lygisk APK ZIP
Click to expand...
Click to collapse
Hi, sorry, but i bit confused about the method here. You mean to just patch either or both. This method is for fastboot or twrp. Sorry if im asking noob question.
or965 said:
What did you do? I wrote several options.
Click to expand...
Click to collapse
I use the method for eu that you posted. First i install magisk 25.2 and then i patch the rom boot.img. I boot to fastboot and flash the patch boot.img using the command. It flash successful then i reboot. But it still bootloop.
And for context, im using Eu weekly rom, not stable and twrp-3.7.0_12-v7.2_A13-venus-skkk.img for recovery. The recovery im using in eu rom forum method for installation.
martin132014 said:
Hi, sorry, but i bit confused about the method here. You mean to just patch either or both. This method is for fastboot or twrp. Sorry if im asking noob question.
Click to expand...
Click to collapse
All good say what you think!! not booth one of them boot.img or recovery.img!! you can flash zip via TWRP than you dont need other steps!!! you can install the Apk and Patch the Boot.img or recovery.img!!! than you can flash it in fastboot, twrp Image or twrp terminal!! choose your method
martin132014 said:
And for context, im using Eu weekly rom, not stable and twrp-3.7.0_12-v7.2_A13-venus-skkk.img for recovery. The recovery im using in eu rom forum method for installation.
Click to expand...
Click to collapse
and what your experience with that!!! Tell me why you like this!!!
System23 said:
All good say what you think!! not booth one of them boot.img or recovery.img!! you can flash zip via TWRP than you dont need other steps!!! you can install the Apk and Patch the Boot.img or recovery.img!!! than you can flash it in fastboot, twrp Image or twrp terminal!! choose your method
Click to expand...
Click to collapse
I guess i should post how I'm doing with the root situation. I guess i miss the part that you need to format the rom after installing new rom. And then do flash the boot.img steps. Now magisk is installed and no bootloop.
I on the other hand do format and flash rom. And continue the boot.img process. I guess that's why it doesn't work.
I'm in the process on restoring my data.
martin132014 said:
I guess i should post how I'm doing with the root situation. I guess i miss the part that you need to format the rom after installing new rom. And then do flash the boot.img steps. Now magisk is installed and no bootloop.
I on the other hand do format and flash rom. And continue the boot.img process. I guess that's why it doesn't work.
I'm in the process on restoring my data.
Click to expand...
Click to collapse
ok a Tip to you!!! when you only Backup Data Partition you can restore it and all Contacts,SMS,Accounts,Apps are availibile again on new ROM!!!
Why you dont use the Magisk.zip and flash it via TWRP after Flash ROM!!! you can rename Magisk.apk to Magisk.zip and flash it!! than you dont need other steps to Root!!! when it dosnt work use the recovery.img to Patch it and try this Method for Rooting, but dont forgett when ya do so you need to try the Buttons-Combo to start in Recovery to boot the System in Root and you have no Recovery-Mode at this Method!!! Also to use Recovery again you must Flash it again via Fastboot!!
And in TWRP use the WIPE Option to make a Factory Reset or WIPE a Single Partition, after some Flashing CROMS its needed to be WIPE the Data Partition!!!
martin132014 said:
I guess i should post how I'm doing with the root situation. I guess i miss the part that you need to format the rom after installing new rom. And then do flash the boot.img steps. Now magisk is installed and no bootloop.
I on the other hand do format and flash rom. And continue the boot.img process. I guess that's why it doesn't work.
I'm in the process on restoring my data.
Click to expand...
Click to collapse
you can ask me what you would i share my Informations with ya!!! when iam not knowing iam googleing it out to find a solution!! the talk we have start are hope helpfully!! when ya have intresst we can stay in kontakt and make what we can, even its public 4 all or PM!!! PS i must not hide my Knowledge, but PM its OK too!!!