Hello,
My Thor device seems to be bricked after trying to enable encryption in Lineage OS (this happened a couple of months ago).
The device used to have an unlocked bootloader with TWRP 3.1.1-1, Lineage OS 14.1 20170710 and Open GApps installed and was running without any problems (thanks to all the people here who have made this possible btw!) until enabling encryption. The encryption process was running for an eternity (more than one day), so I switched the device off.
Since then, I only get a grey "kindle fire" logo. No booting of Lineage or TWRP anymore . It's possible to start in fastboot mode via pressing the on/off switch and the volume button simultaneously, though.
I don't have any experience with bricked devices. Any suggestions what to do? And are there known issues with encryption on this device?
Many thanks in advance for your help!
RiseT said:
Hello,
My Thor device seems to be bricked after trying to enable encryption in Lineage OS (this happened a couple of months ago).
The device used to have an unlocked bootloader with TWRP 3.1.1-1, Lineage OS 14.1 20170710 and Open GApps installed and was running without any problems (thanks to all the people here who have made this possible btw!) until enabling encryption. The encryption process was running for an eternity (more than one day), so I switched the device off.
Since then, I only get a grey "kindle fire" logo. No booting of Lineage or TWRP anymore . It's possible to start in fastboot mode via pressing the on/off switch and the volume button simultaneously, though.
I don't have any experience with bricked devices. Any suggestions what to do? And are there known issues with encryption on this device?
Many thanks in advance for your help!
Click to expand...
Click to collapse
Have you tried booting a TWRP image from fastboot? If that works recovery will be a lot easier.
fastboot devices
--> if no response to this command you'll need to update host drivers
fastboot boot <twrp-image-name>
--> you can download a suitable TWRP image from here
Davey126 said:
Have you tried booting a TWRP image from fastboot? If that works recovery will be a lot easier.
fastboot devices
--> if no response to this command you'll need to update host drivers
fastboot boot <twrp-image-name>
--> you can download a suitable TWRP image from here
Click to expand...
Click to collapse
Excellent! MANY MANY THANKS! You've made my day! Worked like a charm (i. e. worked like a charm after my usual trial & error for hours to make Windows accept a Kindle Fire driver for fastboot - had to force one it warned me about on it to make it finally work).
A couple more question if I may:
When and why does one need a "Fastboot cable" (always been confused about this)?
Do you happen to know if device encryption normally works with this device?
Does switching debugging off in Lineage prevent unbricking via fastboot like this (wouldn't think so but want to make sure)?
Thanks again!
RiseT said:
Excellent! MANY MANY THANKS! You've made my day! Worked like a charm (i. e. worked like a charm after my usual trial & error for hours to make Windows accept a Kindle Fire driver for fastboot - had to force one it warned me about on it to make it finally work).
A couple more question if I may:
When and why does one need a "Fastboot cable" (always been confused about this)?
Do you happen to know if device encryption normally works with this device?
Does switching debugging off in Lineage prevent unbricking via fastboot like this (wouldn't think so but want to make sure)?
Thanks again!
Click to expand...
Click to collapse
Quick answers as I'm on the move (sorry for brevity) ...
- Moto drivers almost always work with HDX devices; install this package (don't have to launch it) which includes drivers; no warnings either
- Fastboot cables are largely ineffective on Amazon devices and rarely needed (special/unique cases beyond scope of this post)
- Encryption is NOT supported with custom ROMs on this device; dipping your head in boiling oil is a more enjoyable experience
- Prior debug setting in Lineage should have little/no impact on unbricking success
If you are unable to reload a ROM (Lineage in particular) you may have to do some further work on the data partition to remove encryption remnants. Post back if this is the case; I'll try to scare up the related material.
Davey126 said:
If you are unable to reload a ROM (Lineage in particular) you may have to do some further work on the data partition to remove encryption remnants. Post back if this is the case; I'll try to scare up the related material.
Click to expand...
Click to collapse
Thanks for your replies!
Thanks, my Thor is already up & running with the latest LineageOS and Open GApps. No problems so far. Prior to installing, In order to play it safe, I've made sure to wipe/format all partitions (including the data partition) from TWRP. Had a feeling that this would possibly be a good thing to do after that (partially?) failed encryption experience...
RiseT said:
Thanks, my Thor is already up & running with the latest LineageOS and Open GApps. No problems so far. Prior to installing, In order to play it safe, I've made sure to wipe/format all partitions (including the data partition) from TWRP. Had a feeling that this would possibly be a good thing to do after that (partially?) failed encryption experience...
Click to expand...
Click to collapse
Suspect encryption run was incomplete as simply the wiping data partition in TWRP is usually insufficient to remove critical remnants. A format is needed along with something else I don't immediately recall. You would be aware if that was needed as Lineage would hang on boot.
I can second this warning, do NOT USE ENCRYPTION. I tried so unter Lineage OS 14.1. As a result I had to wipe/format the data partition using TWRP, which let me escape from the bootloop.
Davey126 said:
Suspect encryption run was incomplete as simply the wiping data partition in TWRP is usually insufficient to remove critical remnants. A format is needed along with something else I don't immediately recall. You would be aware if that was needed as Lineage would hang on boot.
Click to expand...
Click to collapse
Can you give more details on how to remove these remnants? I did the same thing as OP this morning & now I'm here trying to undo my mistake :crying:
I still have TWRP 3.1.1-1 & I can flash stock 4.5.5 rom, but I can't flash any other custom roms as I'd get into a boot loop with grey kindle fire logo. I did wipe everything except sdcard, and the stock rom is running perfectly fine, except for root & gapps, of course.
Edit: SOLVED, courtesy to this post https://forum.xda-developers.com/showpost.php?p=74710623&postcount=1029
Related
Hello folks!
Apparently the official TWRP recovery 3.0.2 has some sort of problems with android 7.1.1 Nougat, so this unofficial recovery was created to work around those issues in the meantime.
The official hosting of this unofficial recovery is in this thread: http://forum.xda-developers.com/nex...recovery-twrp-2-8-7-0-touch-recovery-t3234976
It is buried almost all the way at the end.
For sake of convenience, I am making it available here for those that wish to get going with it quickly. Note that I am not the developer of this nor am I the maintainer. This is here for easy reference only. You should speak with TWRP Grand Poobah Dees_Troy in the above thread for further details.
twrp-3.0.2-3-angler.zip 14.2 MB
https://mega.nz/#!tdcUAa4a!G-bGMWznEUAkE3Ih3ioaHq2Fx0NdzGnIlhY-nuPg__s
Installation instructions are straightforward:
1. Decompress the zip file so you have the .img file. Do not flash the zip file!
2. Place the recovery image in the same folder as your ADB / fastboot apps.
3. Put your phone in boot loader mode: Power button + volume down button.
4. Pull open a console in this directory and type fastboot devices. Proceed when you a serial number and "fastboot" next to it.
5. Type fastboot flash recovery twrp-3.0.2-3-angler.img. If all goes well you should see a success message of some sort.
6. Reboot and enjoy!
I've been using this for a few ROM installs already and haven't seen any problems.
Best of luck to you!
Guess I'll give this a go and report back later on heh. Will this recovery actually stay after a restart?
Sent from my Nexus 6P using XDA-Developers mobile app
Hmm, seems to be working ok for me on the 7.1.1 DP2 release.
Sent from my Pixel XL using Tapatalk
PearsonDKA said:
Guess I'll give this a go and report back later on heh. Will this recovery actually stay after a restart?
Click to expand...
Click to collapse
Like some others have mentioned, I keep seeing it disappear after restarting the phone once, twice or a few times, so I have to re-flash it almost every time I need it.
Not sure what the hangup is. Size-related?
CaptShaft said:
Like some others have mentioned, I keep seeing it disappear after restarting the phone once, twice or a few times, so I have to re-flash it almost every time I need it.
Not sure what the hangup is. Size-related?
Click to expand...
Click to collapse
You need to flash either Root or a modified boot image for it to stay
jaytv said:
You need to flash either Root or a modified boot image for it to stay
Click to expand...
Click to collapse
Good to know. 2 questions:
1) What modifications to a regular boot image do we need to make to keep it?
2) Are all boot images the same? Can we all use the same modified boot image or does it differ depending on the ROM?
CaptShaft said:
Good to know. 2 questions:
1) What modifications to a regular boot image do we need to make to keep it?
2) Are all boot images the same? Can we all use the same modified boot image or does it differ depending on the ROM?
Click to expand...
Click to collapse
Sounds like time for you to do some reading as to what root and boot images are. Search works great. I suggest the threads on SuperSU (a form of root) and also looking at the many wonderful custom boot images and Roms that are floating around in this forum.
The simple answer is flash Super Su or find a modified boot image for the current release and flash that.
Also, Heisenberg's excellent beginner's thread in Nexus 6p general is a great place to start.
Enjoy!
Just what I was looking for.
I was in TWRP loop forever and couldn't figure it out till this thread. No issues now
I've installed the one from the main thread and it's working for me.
I just wanted to mention what the bugs are:
shadowstep said:
TWRP versions 3.0.2-1 and above work with Android Nougat 7.0's encryption, TWRP 3.0.2-0 and below don't. Also, both versions 3.0.2-1 and 3.0.2-2 are buggy at the moment, but none of those bugs are along the lines of encryption. Read the end of this post for more information.
(Replies snipped)
EFS partition is never needed to be restored under any general circumstance. It is the partition where the phone stores its IMEI information, MAC address, product code, etc. and will never be needed to be modified or changed in any way. Even if you're flashing a stock factory image (be it of 6.0.1 or 7.0, whenever it is out), it would never touch this partition. You should just backup it once, store it away for emergency purposes and never backup or restore it again.
Okay now moving onto important notes and the bugs:
1. TWRP 3.0.2-0: Is stable and has no known bugs. However, it has not been updated to handle Android Nougat 7.0's encryption. Hence, if you're on 7.0 and you're encrypted, it will keep asking for an encryption password even if you don't have one or if you have one and are inputting it correctly, it will refuse to accept it. If you're on 7.0 and you're unencrypted, then this version should be fine.
2. TWRP 3.0.2-1: Is not stable and has a known bug. The bug would affect those who are restoring their EFS partition using this version of TWRP. The EFS partition has two subparts to it, i.e. /efs1 and /efs2. So, when you check EFS at the backup option menu in TWRP, it backups /efs1 to efs1.emmc.win and /efs2 to efs2.emmc.win, which is fine. However, while restoring (and here is when the bug comes in), it restores efs1.emmc.win to /efs1 but restores the same backup of efs1.emmc.win to /efs2 as well (which it shouldn't be doing and instead it should be restoring the corresponding efs2emmc.win to /efs2). This can brick your phone. Hence, the fatal bug.
This version, however, supports Android Nougat 7.0's encryption. Therefore, as long as you don't backup/restore EFS with this version, you should be good using it with either Android Marshmallow 6.0.1 or Android Nougat 7.0, encrypted or unencrypted.
3. TWRP 3.0.2-2: Is not stable and has a known bug (with the EFS bug most likely fixed in this version, but this is unconfirmed since there is no changelog available yet). The bug would affect those who are backing up their data using this version. TWRP creates the backups of your selected partitions as tar files. The bug that is present in this version would give you an error (most likely the one that @stankyou got) as it is unable to write the second tar file after processing approximately 1 GB of data and would cancel the backup. Hence, the bug.
This version, however, also supports Android Nougat 7.0's encryption. Therefore, as long as you don't create backups with this version, you should be good using it with either Android Marshmallow 6.0.1 or Android Nougat 7.0, encrypted or unencrypted.
4. @jcadduono has created unofficial builds (versions 3.0.2-3) for the Nexus 6P (Angler) and Nexus 5X (Bullhead) without the broken patches. They are up-to-date, but have the adb backup patches rebased out until the bugs are solved. These builds are untested, and he recommends sticking with 3.0.2-0 instead for the time being.
Click to expand...
Click to collapse
TL;DR 3.0.2-0 doesn't support Nougat encryption. 3.0.2-1 has bug restoring EFS. 3.0.2-2 has bug creating backups over 1GB.
ADB sideload is not working in TWRP 3.0.2-3 (twrp-3.0.2-3-angler.img - MD5 2fcc19da388ab727aac69b6165ac7888), not sure if this is @jcadduono or not. It's working in previous build IIRC. Is this expected? Thank you.
vibranze said:
ADB sideload is not working in TWRP 3.0.2-3 (twrp-3.0.2-3-angler.img - MD5 2fcc19da388ab727aac69b6165ac7888), not sure if this is @jcadduono or not. It's working in previous build IIRC. Is this expected? Thank you.
Click to expand...
Click to collapse
I had a few failures with it in TWRP, yes.
Until fixed, you'll have to do ADB push instead and then load from TWRP install.
Alternately, you can do fastboot flash commands while in the bootloader.
Grospolina said:
I've installed the one from the main thread and it's working for me.
I just wanted to mention what the bugs are:
TL;DR 3.0.2-0 doesn't support Nougat encryption. 3.0.2-1 has bug restoring EFS. 3.0.2-2 has bug creating backups over 1GB.
Click to expand...
Click to collapse
I noticed that bug yesterday restoring a backup. TWRP appeared to hang whilst restoring, I left it a further five minutes, then hard reset the power button. When the phone loaded up, I found it had restored correctly.
3.0.2-4 twrp ?
Anybody have the capabilities to roll the 3.0.2-3 version in with The Flash's 3.0.2-0_F2FS version lol; and make a version compatible with Nougat encryption as well as F2FS (and without EMS restore problem, nor backup error issue) ?
I know I sure don't, and now that I'm on christmas break I am just sitting around - in fact if anybody could point me to a resource, I have the time and I'm sure I could pick it up quick, I could try and compile it! I've been wanting to give back to this great community since I joined; maybe now that I've done a couple years of engineering school and been searching thru the forums, I can help throw this together.
I'm going to assume that I look up those two builds sources on GitHub, then use Parallels Windows to use a Linux distro (because I'm on a Macbook Pro) to combine the sources and make a build? Honestly, if I could get any advice, I'd love to jump on it.
3.0.3.0 is out. Anyone know the changelog ?
Here's the link: https://dl.twrp.me/angler/twrp-3.0.3-0-angler.img.html
Would be nice to know a changelog
ariefabuzaky said:
3.0.3.0 is out. Anyone know the changelog ?
Click to expand...
Click to collapse
Unfortunately, the answer is here. I did not expect to see a nag screen after making a backup!
bkkzak said:
Here's the link: https://dl.twrp.me/angler/twrp-3.0.3-0-angler.img.html
Would be nice to know a changelog
Click to expand...
Click to collapse
You can always look at their repository
Since 2016-09-01:
- Change version to 3.0.3 to support the app release - 27 hours ago
- Update Ukraine language translation (via jemmini) - 27 hours ago
- Add TWRP app install via TWRP recovery - 29 hours ago
- TWRP Language Update - 7 days ago
- Change handling of /cache due to AB devices not having cache - 7 days ago
- Support backup/restore of FBE policies - 8 days ago
- Support File Based Encryption - 10 days ago
- Add boot slot support - 12 days ago
- Support new AB OTA zips - 12 days ago
- Copy Kernel Logs - 5 months ago
- Improve backup & wipe exclusion handling - 2 weeks ago
- Fix adb shell in 7.0 tree - 6 weeks ago
- Check if mount point is dir during startup - 6 weeks ago
- MD5 verification sanity - 8 weeks ago
- Fix image flashing: attempt 2 - 8 weeks ago
- Fix image flashing - 3 months ago
- Update to android-7.1 - 4 weeks ago
- Fix libcrypto dependency in 6.0 trees - 3 months ago
- Clean up PartitionSettings - 3 months ago
- Fix compressed backups with split archives - 3 months ago
- Fix restore of subpartitions - 4 months ago
Unfortunately for me, I still have issues decrypting an encrypted phone on TWRP 3.0.2-3 and 3.0.3-0. TWRP prompts for a password and won't take my PIN.
Running the latest ResurrectionRemix (CM-based), which enables device encryption. I'm still searching around to see what I need to do about this.
Edit: Update: Huh, weird, got it to mount.
I rebooted back into Android, went in to Security and set a device encryption password with "Change encryption password".
I hadn't set one before. It requests my screen lock PIN then to enter an alphanumeric encryption password.
Attempted to remove it again immediately (it doesn't show any feedback when I tap "Replace encryption password" then enter my screen lock PIN), and rebooted into recovery.
TWRP prompted again for an encryption password but now accepts my device lock PIN and it mounts!
Rebooted again, and now the phone requests a PIN unlock during boot >.<
Went back in to Security and went straight to "Replace encryption password", entered my PIN, and saw no feedback again. Rebooted back into Recovery.
TWRP prompts again but accepts my PIN. Rebooting to Android again, I am prompted again on boot to enter my screen PIN to finish the boot process. Sooo now I guess I have to figure out how to disable the device encryption PIN, or something. Oh well. I'll update if I make progress.
The end goal is to reach a point where TWRP will mount (even if it's manually with an entered PIN), and to not have a phone that requires a PIN unlock during boot. But I guess that's still safer and I can live with it. It's just different from how the ROM originally behaved, is all.
Edit: Update again!
Disabled my PIN/security altogether, rebooted into recovery. TWRP mounts without any prompts. Nice. Reboot int system, it boots fine. Also nice.
Set a new screen lock PIN, do not select to use it on bootup, and set my fingerprints again. Apps work immediately fine after, I did not have to reset them to use that auth method. Woot, nice.
Restart into TWRP, no prompt, good. Restart into System again, no prompt during boot.
So I guess in the end you have to disable and re-enable device screen locking security if you hit this issue in TWRP on a 6P? It could be my ROM as well.
CaptShaft said:
Hello folks!
Apparently the official TWRP recovery 3.0.2 has some sort of problems with android 7.1.1 Nougat, so this unofficial recovery was created to work around those issues in the meantime.
The official hosting of this unofficial recovery is in this thread: http://forum.xda-developers.com/nex...recovery-twrp-2-8-7-0-touch-recovery-t3234976
It is buried almost all the way at the end.
For sake of convenience, I am making it available here for those that wish to get going with it quickly. Note that I am not the developer of this nor am I the maintainer. This is here for easy reference only. You should speak with TWRP Grand Poobah Dees_Troy in the above thread for further details.
twrp-3.0.2-3-angler.zip 14.2 MB
https://mega.nz/#!tdcUAa4a!G-bGMWznEUAkE3Ih3ioaHq2Fx0NdzGnIlhY-nuPg__s
Installation instructions are straightforward:
1. Decompress the zip file so you have the .img file. Do not flash the zip file!
2. Place the recovery image in the same folder as your ADB / fastboot apps.
3. Put your phone in boot loader mode: Power button + volume down button.
4. Pull open a console in this directory and type fastboot devices. Proceed when you a serial number and "fastboot" next to it.
5. Type fastboot flash recovery twrp-3.0.2-3-angler.img. If all goes well you should see a success message of some sort.
6. Reboot and enjoy!
I've been using this for a few ROM installs already and haven't seen any problems.
Best of luck to you!
Click to expand...
Click to collapse
tu 2: is that recovery image the same as under point one? and where is the ADB /fastbootfolder? these not exist
I will try to describe problem as much as I can:
1.Unlocked bootloader(unofficial way).
2.Installed TWRP 3.0.M4-0(success).
3.Installed(in such order as stated by some guide) : CM14.1 Firmware(Kate) - 26.11.2016 >>> CM14.1-20161222 Nightly Kenzo >>> Opengapps arm64 7.1 nano with TWRP(success).
4.Reboot, CM 14.1 launches correctly, although it has saved settings and apps from MIUI, making it real mess. Now the problem starts. I assumed by doing factory reset I'll get clean 14.1 - wrong. After that turning on my phone causes it to launch TWRP instead of system.
(Failed)Attempts to fix:
1.Install CM14.1 again.
2.Wipe + install CM14.1 again.
3.Can't get into EDL mode(as stated here http://en.miui.com/thread-290959-1-1.html)
Additional info:
1.Fastboot mode launches, but 'adb devices' doesn't find anything(it was before). Device manager sees phone as well as MiFlash. Not succesful trying to update drivers(system found them up-to-date).
2.I have Kate edition, started installing after reading this http://forum.xda-developers.com/redmi-note-3/how-to/index-custom-roms-t3396628 , last posts states, that sometimes it's necessary to flash non-hlos.bin file to system(not sure if even necessary in my case, as CM14.1 launched before factory cleaning).
3.Only similar thing I found is : http://forums.androidcentral.com/sa...p-after-factory-reset-cyanogenmod-12-1-a.html , but about different device and CM version.
I'll appreciate any suggestions on how to fix it(either getting into CM14.1 or back to MIUI, preferably the first).
@edit - Solved myself. For anyone encountering such problem, I could install succesfully MIUI back, when I launched my windows in Disable Drivers Signature Mode.
what exactly have you done at the point "factory cleaning" ? do you mean anything in running android or in TWRP?
h0LLe said:
what exactly have you done at the point "factory cleaning" ? do you mean anything in running android or in TWRP?
Click to expand...
Click to collapse
Factory clean from android settings after running CM14.1 succesfully for the first time. No idea why it caused a problem, but as I wrote in edit, it is solved.
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 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.
Already opened an issue on GitHub but looks like the dev got a long backlog. If anyone has a fix I'd really appreciate it.
I experienced the following when updating TWRP to 3.5.0_90:
- long loading time: takes ~20s to finish initialization
- when I deal with anything that supposedly work with the /system partition the device will freeze and shutdown. Tried: wipe system+data; flash magisk; flash gapps. Somehow dirty flashing a rom worked just fine (manipulating /data is fine I guess?)
Tried reversing to 3.4.0 and won't be able to properly mount existing partitions. Guess I should just wait for a fix. For those who look to update - proceed with caution!
bloomfielderic said:
Already opened an issue on GitHub but looks like the dev got a long backlog. If anyone has a fix I'd really appreciate it.
I experienced the following when updating TWRP to 3.5.0_90:
- long loading time: takes ~20s to finish initialization
- when I deal with anything that supposedly work with the /system partition the device will freeze and shutdown. Tried: wipe system+data; flash magisk; flash gapps. Somehow dirty flashing a rom worked just fine (manipulating /data is fine I guess?)
Tried reversing to 3.4.0 and won't be able to properly mount existing partitions. Guess I should just wait for a fix. For those who look to update - proceed with caution!
Click to expand...
Click to collapse
Only install twrp-3.5.0_90. It does not work! twrp-3.4.0-0-clover. The same is true. Only twrp-3.3.1-0-clover can be returned
agreed... v3.5.0-9 just boot to black screen recovery... this is a bug...
v3.4.0 need to format data to be able to read it properly.... this is not bug...
I installed latest twrp on mi pad 4 and now it gets stuck on the twrp logo screen also i cannot boot my system just keeps going to the twrp screen ive tried installing different recoveries but same issue just gets stuck on recovery logo screen is there a fix for this ?
bloomfielderic said:
Already opened an issue on GitHub but looks like the dev got a long backlog. If anyone has a fix I'd really appreciate it.
I experienced the following when updating TWRP to 3.5.0_90:
- long loading time: takes ~20s to finish initialization
- when I deal with anything that supposedly work with the /system partition the device will freeze and shutdown. Tried: wipe system+data; flash magisk; flash gapps. Somehow dirty flashing a rom worked just fine (manipulating /data is fine I guess?)
Click to expand...
Click to collapse
Can confirm, just experienced the same with v3.5.1_9-0 coming from v3.3.1. And when I tried to proceed flashing RR, was dumped into shutdown and then fastboot.
Used fastboot to re-flash recovery and upon issuing 'fastboot reboot recovery' was again dumped into shutdown (and then back to fastboot).
UPDATE: tried flashing different TWRP versions (the ones linked in the LineageOS 17.1 and crDroid threads, plus an old Mokee I had on file) without success. Fastboot doesn't throw any errors, but the copying phase appears to me overly fast and upon reboot all it does is go back to fastboot. Well, the device is soft-bricked as it is, looks like I'll have to try the MiFlash route.
UPDATE2: I did use MiFlash succesfully and am now on LOS 17.1. OrangeFox (found here, as well as the TWRP linked in the LOS 17.1 thread) were the ones that worked for me in the end...