I've been trying to root my device for a few days. I patch the AP file with the magisk application in the software I downloaded from the sammobile site with magisk. I installed it on my phone with odin. but above the samsung text, under the exclamation mark, the red color ''this phone is not running samsungs official software. you may have problems with features or security, and wont be able to install seoftware updates'' remains. The phone turns off after a certain period of time, it seems to turn on, but the same screen appears again and so on. Also, I enter the recovery mode, I do a wipedata/factory reset and it says something like this.
Wiping data...
Formatting /data...
[PDP] lstat /c___/pdp_b___ :0 - no Pdp scenario
formatting /cache...
formating /metadata
data wipe complete
[libfs__mgr]eariError updating for slot select
nothing?
Rooting a device's Android is adding a suitable su cmdlet to Android's filesystem and make it executable, nothing else. This can get achieved by means od ADB.
same issue here - bootloop after patching boot.img with Magic. B
ut new version - 24 is relased today to open beta channel. Maybe?
Succesfully patched boot.img from M526BPUU1AUI5 with latest Magisk Manager, flashed with ODIN and after wipe got rooted M52 (m-m52b/ds). You must patch exactly your firmware version boot. Also, flashing empty vbmeta disables verity protection - needed for custom recovery flashing. My goal now is to make TWRP working, but no success so far.
See here for root
GALAXY M52 5G - UNLOCK AND ROOT
Unlock and Root Galaxy M52 5G I just share my experience. Do it at your own risk Tested on M526BRXXU1AUK2 firmware I. Unlock bootloader 1. Enable developer options by tapping build number 7 times 2. Go to Developer options, turn on OEM...
forum.xda-developers.com
Related
TWRP 3.0.2-1. for the Samsung Galaxy A9 pro SM-A910F - Qualcomm MSM8976
Needs someone to test and report what works what doesn't giving plenty of detail and if possible the recovery log. It may boot, it may not.
Please note I don't own this device.
Stock Recovery is posted below if TWRP doesn't boot.
NOTE:
FLASHING CUSTOM STUFF VOIDS YOUR WARRANTY. THIS WILL TRIP THE KNOX FLAG.
Install:
Boot to download mode.
Flash with Odin using the AP slot.
Uncheck Auto-reboot.
Reboot to recovery immediately after flashing using POWER + HOME + VOL DOWN, as soon as the screen goes blank change to VOL UP whilst still holding the other buttons.
TWRP should now boot.
NOTE: ON SOME ANDROID 5.1.1 and 6.01 DEVICES IT IS NECESSARY TO GO TO:
Settings -> Developer Options -> OEM unlocking
AND ENABLE OEM UNLOCK FIRST OR YOU MAY ENCOUNTER 'BLOCKED BY FRP LOCK' WHEN FLASHING.
Install with ODIN:
twrp_3.0.2-1_sm-a910f_25716
Stock recovery:
A910FXXU1APFC_stock_recovery
IMPORTANT
At the moment TWRP isn't working with encryption, this means the DATA Partition and internal storage cannot be mounted.
To mount the Data partition encryption needs to be removed and the relevant boot image needs to be flashed below
This can be done via the FORMAT DATA button under the WIPE option in TWRP.
Please note this will erase all user data.
The boot image can be flashed with ODIN or extracted and flashed with TWRP.
The boot image MUST be flashed before booting the device to system or the DATA partition will be re-encrypted at boot time.
A910FXXU1APFC_no_encryptable_boot
TO ROOT
Flash the file below in twrp.
https://download.chainfire.eu/964/Su...0519174328.zip
.
Reserved
http://forum.xda-developers.com/showthread.php?t=3424350
Thread closed by ashyx.
Moved to development.
http://forum.xda-developers.com/sam...wrp-3-0-2-1-samsung-galaxy-a9-pro-sm-t3426701
Sent from my SM-T280 using XDA-Developers mobile app
Installing Stock Oreo 8.1.0 on Nexus 6P with Root
This is a quick guide on how to install and root stock Oreo 8.1.0 on a Nexus 6P.
The main problem I came across was trying to find a modified bootloader for Oreo 8.1.0, so instead I replaced the stock kernel with ElementalX-N6P-6.01 kernel. This alleviated the need for a modified bootloader. The reason this is required (or a modified bootloader) is to prevent the stock rom from replacing the custom recovery with the stock recovery on every boot. In addition, there is a need to remove the forced encryption of the data partition that is used in MM, Nougat and Oreo. Installing ElementalX kernel resolved both of these issues plus several other benefits including colour calibration plus plenty more.
This is not a beginner’s guide so I will assume you have the correct drivers and SDK tools installed on your PC (or Mac). Perform the following:
1. Enable USB Debugging (Developer Options)
2. Allow OEM Unlock (Developer Options)
3. Boot into download mode and unlock the bootloader with fastboot oem unlock
Downloads
1. Download the official stock firmware, currently “8.1.0 (OPM5.171019.014, Jan 2018, Softbank)” from here https://developers.google.com/android/images
2. Download “twrp-3.2.0-0-angler-4core.img” from https://androidfilehost.com/?fid=745849072291692306
3. Download “ElementalX-N6P-6.01.zip” from https://elementalx.org/devices/nexus-6p/
4. Download Magisk (Latest version) from https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Method
Have your phone switched on.
1. Within the downloaded stock firmware file there is a “flash-all.bat” file. Run this batch file. The phone will reboot into bootloader mode and flash the stock image.
2. When finished reboot the phone and finish the setup. No need to set up too much at this point as it will all be erased again shortly. Now you’re on stock rom 8.1.0. Again,ensure the following:
Enable USB Debugging (Developer Options)
Allow OEM Unlock (Developer Options)
At the moment the data partition is encrypted (default with Oreo, Nougat and MM) and this is not good for TWRP or rooting, so this needs to be changed.
5. Boot the phone into download mode, connect to your PC and flash TWRP
fastboot flash recovery twrp-3.2.0-0-angler-4core.img
6. Boot your phone into recovery. TWRP will now load but will ask for a password because the data partition is encrypted. Press “Cancel” in TWRP.
7. Slide the bar to allow modification to the system partition when asked by TWRP.
8. To decrypt the data partition, go to Wipe > Format Data and enter “Yes” in the provided field. It should not take more than a few seconds and then reboot into recovery again. This time it will not ask for a password and you should have access to the storage area of the phone from your PC.
9. Remain in TWRP and copy “ElementalX-N6P-6.01.zip” from your PC to the phone and install it.
10. While still in TWRP, install Magisk.
11. Wipe Cache/Dalvik cache and the reboot into the system.
Extras
• Check the colour calibration within ElementalX
• Viper4Android can be installed via Magisk downloads. Use the version for Magisk 15. It works.
dave457 said:
(snipped)
Click to expand...
Click to collapse
Couple thoughts:
1) Please replace every reference of "bootloader" with "boot." Bootloader is entirely different from the boot (kernel). Know the difference if you're going to provide instructions. Using these words interchangeably will cause new users to brick their device because they flashed the bootloader.img when they rarely need to install this. You only flash an image to its similarly named partition on the phone, bootloader does not equal boot.
2) You do not need a custom kernel to get root on Oreo. Your post is misleading. Magisk roots the stock boot image just fine.
3) TWRP will persist between reboots with just the stock boot image rooted with Magisk.
4) TWRP works when you are encrypted. I am unsure why you have a hangup with TWRP and encryption. Are you referring to File Based Encryption which can only be enabled through Developer Options?
5) Why are you making people install a 4 core version of TWRP? If they do not have the BLOD, why force people to use a version of TWRP they do not need?
Sent from my Nexus 5X using Tapatalk
Could you point me in the direction of a beginners guide for this process? I do know it does have a TWRP partition, I do not know which version. My Kernel is 3.10.73- Elemental X4.05 and my baseband in angler 03.78. Any and all help is appreciated.
This is a quick guide on how to install and root stock Oreo 8.1.0 on a Nexus 6P.
The main problem I came across was trying to find a modified bootloader for Oreo 8.1.0, so instead I replaced the stock kernel with ElementalX-N6P-6.01 kernel. This alleviated the need for a modified bootloader. The reason this is required (or a modified bootloader) is to prevent the stock rom from replacing the custom recovery with the stock recovery on every boot. In addition, there is a need to remove the forced encryption of the data partition that is used in MM, Nougat and Oreo. Installing ElementalX kernel resolved both of these issues plus several other benefits including colour calibration plus plenty more.
This is not a beginner’s guide so I will assume you have the correct drivers and SDK tools installed on your PC (or Mac). Perform the following:
1. Enable USB Debugging (Developer Options)
2. Allow OEM Unlock (Developer Options)
3. Boot into download mode and unlock the bootloader with fastboot oem unlock
Downloads
1. Download the official stock firmware, currently “8.1.0 (OPM5.171019.014, Jan 2018, Softbank)” from here https://developers.google.com/android/images
2. Download “twrp-3.2.0-0-angler-4core.img” from https://androidfilehost.com/?fid=745849072291692306
3. Download “ElementalX-N6P-6.01.zip” from https://elementalx.org/devices/nexus-6p/
4. Download Magisk (Latest version) from https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Method
Have your phone switched on.
1. Within the downloaded stock firmware file there is a “flash-all.bat” file. Run this batch file. The phone will reboot into bootloader mode and flash the stock image.
2. When finished reboot the phone and finish the setup. No need to set up too much at this point as it will all be erased again shortly. Now you’re on stock rom 8.1.0. Again,ensure the following:
Enable USB Debugging (Developer Options)
Allow OEM Unlock (Developer Options)
At the moment the data partition is encrypted (default with Oreo, Nougat and MM) and this is not good for TWRP or rooting, so this needs to be changed.
5. Boot the phone into download mode, connect to your PC and flash TWRP
fastboot flash recovery twrp-3.2.0-0-angler-4core.img
6. Boot your phone into recovery. TWRP will now load but will ask for a password because the data partition is encrypted. Press “Cancel” in TWRP.
7. Slide the bar to allow modification to the system partition when asked by TWRP.
8. To decrypt the data partition, go to Wipe > Format Data and enter “Yes” in the provided field. It should not take more than a few seconds and then reboot into recovery again. This time it will not ask for a password and you should have access to the storage area of the phone from your PC.
9. Remain in TWRP and copy “ElementalX-N6P-6.01.zip” from your PC to the phone and install it.
10. While still in TWRP, install Magisk.
11. Wipe Cache/Dalvik cache and the reboot into the system.
Extras
• Check the colour calibration within ElementalX
• Viper4Android can be installed via Magisk downloads. Use the version for Magisk 15. It works.[/QUOTE]
Nice thanks man
---------- Post added at 04:42 PM ---------- Previous post was at 04:38 PM ----------
jam_09 said:
Could you point me in the direction of a beginners guide for this process? I do know it does have a TWRP partition, I do not know which version. My Kernel is 3.10.73- Elemental X4.05 and my baseband in angler 03.78. Any and all help is appreciated.
Hey jam_09
I will help you Install 8.1 oreo
First tell me which career are you using? Is your current rom a career specific or a global one check and tell me .. and I'll instruct on what to do further
Click to expand...
Click to collapse
dave457 said:
Installing Stock Oreo 8.1.0 on Nexus 6P with Root
This is a quick guide on how to install and root stock Oreo 8.1.0 on a Nexus 6P.
The main problem I came across was trying to find a modified bootloader for Oreo 8.1.0, so instead I replaced the stock kernel with ElementalX-N6P-6.01 kernel. This alleviated the need for a modified bootloader. The reason this is required (or a modified bootloader) is to prevent the stock rom from replacing the custom recovery with the stock recovery on every boot. In addition, there is a need to remove the forced encryption of the data partition that is used in MM, Nougat and Oreo. Installing ElementalX kernel resolved both of these issues plus several other benefits including colour calibration plus plenty more.
This is not a beginner’s guide so I will assume you have the correct drivers and SDK tools installed on your PC (or Mac). Perform the following:
1. Enable USB Debugging (Developer Options)
2. Allow OEM Unlock (Developer Options)
3. Boot into download mode and unlock the bootloader with fastboot oem unlock
Downloads
1. Download the official stock firmware, currently “8.1.0 (OPM5.171019.014, Jan 2018, Softbank)” from here https://developers.google.com/android/images
2. Download “twrp-3.2.0-0-angler-4core.img” from https://androidfilehost.com/?fid=745849072291692306
3. Download “ElementalX-N6P-6.01.zip” from https://elementalx.org/devices/nexus-6p/
4. Download Magisk (Latest version) from https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Method
Have your phone switched on.
1. Within the downloaded stock firmware file there is a “flash-all.bat” file. Run this batch file. The phone will reboot into bootloader mode and flash the stock image.
2. When finished reboot the phone and finish the setup. No need to set up too much at this point as it will all be erased again shortly. Now you’re on stock rom 8.1.0. Again,ensure the following:
Enable USB Debugging (Developer Options)
Allow OEM Unlock (Developer Options)
At the moment the data partition is encrypted (default with Oreo, Nougat and MM) and this is not good for TWRP or rooting, so this needs to be changed.
5. Boot the phone into download mode, connect to your PC and flash TWRP
fastboot flash recovery twrp-3.2.0-0-angler-4core.img
6. Boot your phone into recovery. TWRP will now load but will ask for a password because the data partition is encrypted. Press “Cancel” in TWRP.
7. Slide the bar to allow modification to the system partition when asked by TWRP.
8. To decrypt the data partition, go to Wipe > Format Data and enter “Yes” in the provided field. It should not take more than a few seconds and then reboot into recovery again. This time it will not ask for a password and you should have access to the storage area of the phone from your PC.
9. Remain in TWRP and copy “ElementalX-N6P-6.01.zip” from your PC to the phone and install it.
10. While still in TWRP, install Magisk.
11. Wipe Cache/Dalvik cache and the reboot into the system.
Extras
• Check the colour calibration within ElementalX
• Viper4Android can be installed via Magisk downloads. Use the version for Magisk 15. It works.
Click to expand...
Click to collapse
dumb question but wanted to check
My bootloader is already unlocked, but if I do the other steps, any data I have on the phone now will be lost correct?
storo1975 said:
dumb question but wanted to check
My bootloader is already unlocked, but if I do the other steps, any data I have on the phone now will be lost correct?
Click to expand...
Click to collapse
Yes because later in the process you are going to wipe the data partion to get rid of the encryption this will erase everything on your phone it is like doing a factory rest.
---------- Post added at 09:31 PM ---------- Previous post was at 09:23 PM ----------
I don't know alot about the newer versions of Android like 6 7 8 but I know I read that if you don't root the first time you install twrp then the stock recovery will over write twrp when you reboot. And I also read that magisk modifies the system img in order to hid root. so you can still use gpay and Netflix and pass the safety net check. So I think installing the custom kernel is an extra step that is not nessesary but on the other hand you get certian perks with a custom kernel. Again I don't know much about the newer modding community so o don't know how stable elementalx is. Without installing it I won't know. I have tried dozens of kernels some were spectacular like those from faux others not so much. Also keep in mind to ur technically not on stock rooted version of Android if you have a custom kernel. It no longer is stock software.
Thank you so much for this thread. I was actually about to make one asking how to get back to stock. I used to love flashing the phone all the time, but it got to the point where I never did anything with customization and got bored of it, so I'd rather just be on stock these days.
hi sorry but how to flash the ziP? through TWRP?
The below works for Nougat ROMs. I didn't have a chance to try with Oreo yet, sorry.
The ability to encrypt a device doesn’t depend on the presence of the stock recovery nor no-verity-opt-encrypt being flashed or not. It simple needs an unrooted boot.img at the moment the encryption is attempt. You do however need no-verity-opt-encrypt flashed to allow a custom ROM to boot. So the desired state to allow encryption from within a custom ROM is to have the stock boot.img with only no-verity-opt-encrypt applied to it.
The simplest sequence to archive a fully encrypted device with a custom ROM is the following:
- Flash (I recommend Dr. Ketan) ROM as always, but DISABLE ANY ROOTING in the installer
- Encrypt the device from the settings menu
- Flash the ROM one more time, this time WITH MAGISK ROOT. It will display a warning about /data not being mountable as it is now encrypted. That is ok as everything we need is already in place
If you didn’t choose fast encryption (which I recommend for security), download Trimmer (fstrim) from Play Store, tick all partitions and click Trim Now. This will free up all the sectors overwritten by the encryption process on the flash controller and makes your device work super smooth like before encryption.
This obviously only works that simple with ROMs that offer the ability to initially flash without root and if you’ve been on stock or a rootless ROM before. If that’s not the case you have the following options:
- Flash Magisk Uninstaller after initial ROM flash. You may have to reflash no-verity-opt-encrypt in TWRP again, in case it fails to boot now.
- Flash the stock book.img back in Odin and apply no-verity-opt-encrypt in TWRP. Use 7-Zip to create a tar only containing the stock BOOT.IMG and flash it in Odin using the AP slot.
- Flash back a TWRP backup taken of the boot partition before installing a root ROM, but after flashing no-verity-opt-encrypt.
Updating your ROM works no different then usual also. Just dirty flash over if it's the same ROM unless the release notes explicitly mention to factory reset. You don't need /data writable for a ROM update.
Enjoy your fully encrypted and rooted device.
Thank you, I'll try this when I'm at home. Nice recommendation with the trimmer tool, too!
Chainfire root & encryption [N950F]
Many thanks for this guide, plop12345. When it comes to the S7, Chainfire has been bit less optimitic in terms of encryption in conjunction with root, though. Maybe this is related to the weird case that on the S7, encryption seems to be enabled by default whereas it (once again) isn't on the Note 8 which doesn't make any sense to me as it was released after the S7.
Anyway, could you maybe elaborate on whether TWRP and Magisk are necessary or a stock rom with stock recovery and Chainfire's SuperSU only suffices as well?
So far I relinquish the encryption and only rooted by this method.
I would greatly appreciate your advice, thanks.
Encryption in oreo rom
Hi there,
nice guide to a encryped rooted rom :good:
I tried it with the new Dr.Ketan oreo rom o5, but it does not work. Is this guide also for the oreo update?
Everytime i hit the encryped button in settings, the phone only soft reboots. I also tried the stock boot.img from AP, without any luck.
Greez,
hallo
halloweltkk said:
Hi there,
nice guide to a encryped rooted rom :good:
I tried it with the new Dr.Ketan oreo rom o5, but it does not work. Is this guide also for the oreo update?
Everytime i hit the encryped button in settings, the phone only soft reboots. I also tried the stock boot.img from AP, without any luck.
Greez,
hallo
Click to expand...
Click to collapse
I haven't tried it with Oreo yet. But I'll probably give it a spin with Oreo within the next month. Sorry for that, will add a note to the guide.
little-endian said:
Many thanks for this guide, plop12345. When it comes to the S7, Chainfire has been bit less optimitic in terms of encryption in conjunction with root, though. Maybe this is related to the weird case that on the S7, encryption seems to be enabled by default whereas it (once again) isn't on the Note 8 which doesn't make any sense to me as it was released after the S7.
Anyway, could you maybe elaborate on whether TWRP and Magisk are necessary or a stock rom with stock recovery and Chainfire's SuperSU only suffices as well?
So far I relinquish the encryption and only rooted by this method.
I would greatly appreciate your advice, thanks.
Click to expand...
Click to collapse
Sorry for the late reply. I have no S7 to try, but believe using Magisk instead of SuperSu should work. Magisk has means to work with devices with forced encryption. AFAIK with an encrypted device it will put things to the cache partition first and on the next boot move things to the final location. I'm not aware of a similar mechanism in SuperSu.
I would try to unroot with Supersu, flash TWRP and give Magisk a spin. Keeping the stock ROM should be ok, however it will likely fail SafetyNet after plain Magisk Root. In that case try the universal SafetyNet fix also available as module within the Magisk app. If it fails to boot after Magisk root, try flashing the no verify opt encryption patch, but I don't think you need it.
I tried it in O5 as well and cannot get it to work. Just soft reboot as mentioned. No magisk just the ROM with stock kernel and still fails. Any advice?
will this work on s8?
Worked for me on S9 (GF-960F)! Thanks!
Had to use the Magisk Uninstaller first though, as I've alrady rooted.
Has anyone had any luck with this on Oreo? I've been trying to get my N960F simultaneously rooted and encrypted, but haven't had any luck with any method I've tried thus far. I can root it just fine, or encrypt it, but I've not found a way to do both at the same time without it resulting in "Verification failed" and a reset loop.
no-verity-opt-encrypt unable to find boot block location
I am having problems following these indications for rooting/encrypting an S2 tablet (nougat). The problem happens with the installation of no-verity-opt-encrypt from twrp, the script fails with "Unable to find boot block location". I have tried various versions of no-verity-... starting with 6.0 with same results. I wonder whether I have done something wrong in the process or if the S2 tablet behaves differently than the Note 8.
I started unrooting an earlier chainfire installation and reinstalling a stock boot image without problems, then comes the unsuccessful no-verity-opt-encrypt and if I carry on I end with an encrypted system that gets broken when I try to root with magisk.
I have also tried to use the no-verity-opt-encrypt features of magisk (KEEPVERITY=false and KEEPFORCEENCRYPT=false in /data/.magisk) without success.
The other thing that bothers me is that as soon as I have an encryted (but not rooted) system I am unable to mount /data from twrp. I have followed various threads with workarounds on the topic but my twrp (3.2.3) seems to behave differently.
Thanks for any hint that you may have.
sllorent said:
I am having problems following these indications for rooting/encrypting an S2 tablet (nougat). The problem happens with the installation of no-verity-opt-encrypt from twrp, the script fails with "Unable to find boot block location". I have tried various versions of no-verity-... starting with 6.0 with same results. I wonder whether I have done something wrong in the process or if the S2 tablet behaves differently than the Note 8.
I started unrooting an earlier chainfire installation and reinstalling a stock boot image without problems, then comes the unsuccessful no-verity-opt-encrypt and if I carry on I end with an encrypted system that gets broken when I try to root with magisk.
I have also tried to use the no-verity-opt-encrypt features of magisk (KEEPVERITY=false and KEEPFORCEENCRYPT=false in /data/.magisk) without success.
The other thing that bothers me is that as soon as I have an encryted (but not rooted) system I am unable to mount /data from twrp. I have followed various threads with workarounds on the topic but my twrp (3.2.3) seems to behave differently.
Thanks for any hint that you may have.
Click to expand...
Click to collapse
Maybe it's too late to answer to you, but this could be usefull for someone else.
I had same problem, "Unable to find boot block location", with same TWRP 3.2.3.
To solve this problem i downgrade TWRP 3.2.3 to TWRP 3.1.0-1 - Nougat that i found here https://forum.xda-developers.com/tab-s2/development/twrp-3-0-2-1-galaxy-tab-s22016-sm-t713-t3390627.
Than i followed the step to root, but i used Magisk 17.3 instaead SuperSu (Magisk 18.0 gave me some problem). Now i have root permissions with Magisk
Thanks, it is interesting that that particular version of twrp works with the no-verity script. Did you also succeed in keeping the tablet encrypted while rooted with Magisk?
sllorent said:
Thanks, it is interesting that that particular version of twrp works with the no-verity script. Did you also succeed in keeping the tablet encrypted while rooted with Magisk?
Click to expand...
Click to collapse
I don't know, sorry. How can i check that?
Inviato dal mio SM-T819 utilizzando Tapatalk
Android root + encryption possible at all ???
According to TWRP root + encryption is not possible / working.
One could easily disable encryption / extract the password by having access to root and kernel files using TWRP recovery. There are also programs like "Oxygen OS" that can be flashed from the recovery and bypass the password prompt. That would make the whole procedure useless...
Any thoughts on this? And other ideas on Android / third party encryption apps? Encrypting containers with EDS would be an alternative (recommended by Veracrypt) since full disc encryption is still not available for Android (why btw.? nobody seems to care...) - but I am not sure if one could run / move apps into the container (like contacts, sms, e-mail-apps etc.)...
Cheers!
no ideas - nobody ??
no ideas - nobody ??
Finally, rooted with Magisk and encrypted data note8 exynos
Followed these threads
https://forum.xda-developers.com/galaxy-s7/help/to-magisk-data-encryption-s7-t3667007
https://forum.xda-developers.com/note-fe/how-to/exynos-8890-sm-n935f-ds-twrp-root-t3771767
Tested with stock Nougat and TWRP-3.2.1.0-greatlte (with twrp-3.2.3-0 fail)
got these combinations working
Samsung_S7+Oreo+Magisk+Xposed+root+encryption
LG_V30+OreoAOSP+Magisk+Xposed+root+encryption(+BThandsfree)
also according to TWRP and the threads it was impossible. the TWPR might not be able to read files, i don't care as long as i have encrypted system. I can flash from the system.
Wouldn't like 3rd party solution as i want Secure Boot and type password during the boot.
Encryption and root is a must. But it's getting difficult more and more nowadays. ROM threads don't list limitations since KNOX was ever introduced, and that sucks. Instead of "knox will be tripped, warning boot screen will be showm, TWRP won't read filesystem, BT handsfree won't work, encryption won't work" you get "no limitations". Have to read full threads to discover the truth.
Hope Note9 and S10 will be ok.
No encryption working on my N960FD
I tried to install it while updating to DrKetan p09 and it doesnt work.
Is it possible for somebody to help me ?
I ve done a clean install and unrooted the no-verity-encrypt flash (The phone didn't even unlocked with pin )
xdaparanoia said:
According to TWRP root + encryption is not possible / working.
One could easily disable encryption / extract the password by having access to root and kernel files using TWRP recovery. There are also programs like "Oxygen OS" that can be flashed from the recovery and bypass the password prompt. That would make the whole procedure useless...
Cheers!
Click to expand...
Click to collapse
Is this true??
I have a weird issue. Not sure whats going on. Tab S3 is on Android 7.0. I'M running the stock rom but had rooted and installed twrp many months ago. Disabled updates on the device. For some reason yesterday it rebooted and now boots to a screen citing ( Security Error: This device has been flashed with unauthorized software & is locked. Call your mobile operator for additional support. " There is another small message on top , "Custom binary blocked by FRP. (boot.img). I did not change any OEM unlocking toggle. I'm the only one who uses the tablet so no one else did either. Any Ideas ? It does not let me boot to recovery, I cant turn the device off either it just keeps rebooting. The only screen i can get to successfully is download mode.
From some basic ideas I'm thinking maybe flash twrp again in odin and try to flash magisk again or the no-verity-opt-encrypt-6.0 file to see if it will boot up. I want to recover the device without formatting everything but if no one has nay ideas i guess I will try re-flashing the current firmware again to stock. I still have the odin files for the current firmware.
Don't panic, I had this too after upgrading the bootloader. I thougt it was soft-bricked...
- Flash a legit Samsung update with Odin
- The trick of the seven days (read further)
- Flash TWRP with Odin
- IMMEDIATELY reboot in recovery
If you use a custom ROM do as usual
- Delete DATA, wipe everything
- Flash custom ROM AND Magisk
If you want to keep Samsung OS and TWRP without Magisk, I believe you need to
- Flash a dm-verity patch.
Hope you have backup eveything as I did...
The option to disable OEM lock disappear from developper menu, even if it is activated. It seems you have to wait for seven days before the option show up again. During this time you're enable to use a custom ROM or a custom RECOVERY.
- Disable time by network
- Set date 8 days in the past
- Do a manual check update
- Reboot
- Set the actual date
- Check for updates again
Now the OEM option is present, now you can do what you want.
You're right but there's new security zip to flash together with dm-verity patch it is RMM bypass. https://forum.xda-developers.com/galaxy-a8-2018/samsung-galaxy-a8-2018-guides-news--discussion/guide-root-install-twrp-samsung-january-t3760975 .
Note: After flashing both files Data format is necessary not data wipe/factory reset.
I have similar security issues weeks back.
Tips?
samsuffit said:
Don't panic, I had this too after upgrading the bootloader. I thougt it was soft-bricked...
- Flash a legit Samsung update with Odin
- The trick of the seven days (read further)
- Flash TWRP with Odin
- IMMEDIATELY reboot in recovery
If you use a custom ROM do as usual
- Delete DATA, wipe everything
- Flash custom ROM AND Magisk
If you want to keep Samsung OS and TWRP without Magisk, I believe you need to
- Flash a dm-verity patch.
Hope you have backup eveything as I did...
The option to disable OEM lock disappear from developper menu, even if it is activated. It seems you have to wait for seven days before the option show up again. During this time you're enable to use a custom ROM or a custom RECOVERY.
- Disable time by network
- Set date 8 days in the past
- Do a manual check update
- Reboot
- Set the actual date
- Check for updates again
Now the OEM option is present, now you can do what you want.
Click to expand...
Click to collapse
Geoz said:
You're right but there's new security zip to flash together with dm-verity patch it is RMM bypass. https://forum.xda-developers.com/galaxy-a8-2018/samsung-galaxy-a8-2018-guides-news--discussion/guide-root-install-twrp-samsung-january-t3760975 .
Note: After flashing both files Data format is necessary not data wipe/factory reset.
I have similar security issues weeks back.
Click to expand...
Click to collapse
I still had the odin files from when i first rooted this. I flashed the same files ( BL, AP, HOME_CSC ). Device booted back up with all data intact but now the device is no longer rooted. Any way to root without losing data again ( Ex. Factory reset). I had to re-enable OEM Unlock even though i never disabled it don't know what happened there. Also device is still on Android 7.0
naruto.ninjakid said:
I still had the odin files from when i first rooted this. I flashed the same files ( BL, AP, HOME_CSC ). Device booted back up with all data intact but now the device is no longer rooted. Any way to root without losing data again ( Ex. Factory reset). I had to re-enable OEM Unlock even though i never disabled it don't know what happened there. Also device is still on Android 7.0
Click to expand...
Click to collapse
To root you may need to flash magisk with TWRP, I don't know if there's any other way.
If TWRP you have to format data after flashing security files so everything including internal storage will be wiped.
I was a Mi A2 user for a while, now I'm moving to Note 9 Pro and I feel a bit lost because of lacking of guides and tools.
I encounter some unexpected issues with disabling phone encryption. In short, I followed the steps I used for my Mi A2, but it seemed only working partially, and I encountered boot loop when upgrading ROM afterwards.
The details are as follow:
I have Note 9 Pro global (joyeuse), originally it was on stock ROM V11.0.5.0.QJZMIXM
After unlocking bootloader, I booted to TWRP with TWRP-3.4.1B-joyeuse-fix.img (from https://xiaomi.eu/community/threads/custom-twrp-3-4-1b-for-redmi-note-9-pro-joyeuse.56896/ ) and flashed Magisk, then Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip (from https://zackptg5.com/android.php#disverfe )
Everything was fine, I could debloat and disable Xiaomi services, and Google Pay was working (with Magisk Hide and MagiskHide Props Config).
But when entering TWRP again, TWRP requested passcode to decrypt data, that's when I realized the phone was not decrypted. Booting to normal mode, phone Settings showed "Encrypted". But because TWRP was able to decrypt with passcode and could backup as normal, so I ignored it.
When V11.0.7.0.QJZMIXM was released, I backed up /data using TWRP and flashed the new ROM using fastboot without erasing data. Then the phone was in boot loop (it showed redmi logo then vibrated then rebooted)
I flashed back V11.0.5.0.QJZMIXM without erasing data, but it still entered boot loop.
I decided to wipe data (using TWRP and using Wipe menu in XIaomi recovery mode), but boot loop still occurred.
I flashed V11.0.7.0.QJZMIXM again, but this time without keeping data (flash_all.bat), but boot loop still occurred.
I accidentally selected flash all & lock bootloader (in MiFlashTool), then phone could boot up normally. But I lost root, and bootloader was relocked.
Additional info: In a rage, I turned on Developer mode and tapped to bind mi account, and now I have to wait 168hrs to unlock bootloader again.
Questions:
What have I done wrong that the phone entered boot loop even after wiping data?
What's the proper way of using TWRP so that I can backup data and can update ROM in the future without going through this mess again?
HRSE said:
I was a Mi A2 user for a while, now I'm moving to Note 9 Pro and I feel a bit lost because of lacking of guides and tools.
I encounter some unexpected issues with disabling phone encryption. In short, I followed the steps I used for my Mi A2, but it seemed only working partially, and I encountered boot loop when upgrading ROM afterwards.
The details are as follow:
I have Note 9 Pro global (joyeuse), originally it was on stock ROM V11.0.5.0.QJZMIXM
After unlocking bootloader, I booted to TWRP with TWRP-3.4.1B-joyeuse-fix.img (from https://xiaomi.eu/community/threads/custom-twrp-3-4-1b-for-redmi-note-9-pro-joyeuse.56896/ ) and flashed Magisk, then Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip (from https://zackptg5.com/android.php#disverfe )
Everything was fine, I could debloat and disable Xiaomi services, and Google Pay was working (with Magisk Hide and MagiskHide Props Config).
But when entering TWRP again, TWRP requested passcode to decrypt data, that's when I realized the phone was not decrypted. Booting to normal mode, phone Settings showed "Encrypted". But because TWRP was able to decrypt with passcode and could backup as normal, so I ignored it.
When V11.0.7.0.QJZMIXM was released, I backed up /data using TWRP and flashed the new ROM using fastboot without erasing data. Then the phone was in boot loop (it showed redmi logo then vibrated then rebooted)
I flashed back V11.0.5.0.QJZMIXM without erasing data, but it still entered boot loop.
I decided to wipe data (using TWRP and using Wipe menu in XIaomi recovery mode), but boot loop still occurred.
I flashed V11.0.7.0.QJZMIXM again, but this time without keeping data (flash_all.bat), but boot loop still occurred.
I accidentally selected flash all & lock bootloader (in MiFlashTool), then phone could boot up normally. But I lost root, and bootloader was re-locked.
Additional info: In a rage, I turned on Developer mode and tapped to bind mi account, and now I have to wait 168hrs to unlock bootloader again.
Questions:
What have I done wrong that the phone entered boot loop even after wiping data?
What's the proper way of using TWRP so that I can backup data and can update ROM in the future without going through this mess again?
Click to expand...
Click to collapse
first of all you are not the only one that faces same problems. So chears mate. Next is the TWRP and the lack of stable/working version since i have done quite few phones now i can tell that the TWRP encryption ignore is not persistent and it works while you don't touch the recovery and not booting it up. Upon the boot it triggers the encryption and although he filesystem is not encrypted it still thinks it is.
Solution for now? wait for the fixed version while this is new phone and may take some time to re-code he recovery (find the damn cause of the encryption trigger).
Anyways. I am still thinking to do the fastboot rom mod, root it while it is not flashed and hen flash it while i don't actually need. I just need to remove all the miui/xiaomi stuff, block the damn ADS and root the phone and those things can be done on a pc i am just figuring out the correct way to do i.
The idea about skipping the TWRP came right after i downloaded mi-flash tool and found out that it uses same fastboot mode to flash everything and the file structure of the rom is not packet or something. Img files can be exacted and re-packed again so everything in the image can be modified.
What i really hate is the fact that there is tons of tools for other phones but somehow Xiaomi was skipped in the device selection...
Downloaded unlock tool, nice but limited to only requesting ad unlocking the phones bootloader. Next thing is the flash tool, it is limited to only flashing. There is xiaomi tool v2 that can also install the twrp, and cause the encryption crap or download and install stock or xiaomi.eu...
What i was looking for was the tool that can take the stock, decompress it and allow you to choose the apps you want to be per-installed, add some functions to it, mod bootscreens, pre-root it and eventually pack and flash the damn thing. While you are skipping the recovery procedure you are way safer than with its crap.
Agree with me?
daigtas said:
first of all you are not the only one that faces same problems. So chears mate. Next is the TWRP and the lack of stable/working version since i have done quite few phones now i can tell that the TWRP encryption ignore is not persistent and it works while you don't touch the recovery and not booting it up. Upon the boot it triggers the encryption and although he filesystem is not encrypted it still thinks it is.
Solution for now? wait for the fixed version while this is new phone and may take some time to re-code he recovery (find the damn cause of the encryption trigger).
Anyways. I am still thinking to do the fastboot rom mod, root it while it is not flashed and hen flash it while i don't actually need. I just need to remove all the miui/xiaomi stuff, block the damn ADS and root the phone and those things can be done on a pc i am just figuring out the correct way to do i.
The idea about skipping the TWRP came right after i downloaded mi-flash tool and found out that it uses same fastboot mode to flash everything and the file structure of the rom is not packet or something. Img files can be exacted and re-packed again so everything in the image can be modified.
What i really hate is the fact that there is tons of tools for other phones but somehow Xiaomi was skipped in the device selection...
Downloaded unlock tool, nice but limited to only requesting ad unlocking the phones bootloader. Next thing is the flash tool, it is limited to only flashing. There is xiaomi tool v2 that can also install the twrp, and cause the encryption crap or download and install stock or xiaomi.eu...
What i was looking for was the tool that can take the stock, decompress it and allow you to choose the apps you want to be per-installed, add some functions to it, mod bootscreens, pre-root it and eventually pack and flash the damn thing. While you are skipping the recovery procedure you are way safer than with its crap.
Agree with me?
Click to expand...
Click to collapse
More than one month, 280 view, 1 comment, no solution, no answer. Everyone out there are competing with each other to create their own ROMs/recovery/kernel images with whatever catchy names they can think of. Nice. But what's the point if the basics are not yet nailed down?
BTW, Telegram channel is flooded with non-contributing chit chat.
My casual observation is that lrtwrp seems to be a common theme for those who have had major issues on Joyeuse.
sir_bazz said:
My casual observation is that lrtwrp seems to be a common theme for those who have had major issues on Joyeuse.
Click to expand...
Click to collapse
For what it's worth, TWRP does not currently have any official builds for curtana OR joyeuse as far as I can tell. The flashing of early, unofficial, pre-alpha ports of TWRP directly onto partitions causing bricks is not that surprising. Xiaomi locking down EDL access is a ****ty move, but still.