Ok guys, im at the end and need your help. I searched for this Problem since yesterday but couldnt find what describes my problems.
I think i did mistake after mistake, and yes im a noob, so feel free to dump on me what you got
Yesterday i wanted to update Sultan's CM ROM on my OPX, so i downloaded it and tried to install it over TWRP what gives me error messages. I made a factory wipe and installed OxygenOS 2.2.3 and then updated my TWRP to Sultan's new one (Version 3.0.2.3). After i flashed the .img, TWRP wasnt booting anymore, it was stuck on the 1+ Screen, but i was able to get to the System. So i get Root access over the SuperSU App and then flashed the TWRP zip over the Rashir App and TWRP worked again, then i flashed the new OxygenOS (3.1.3) what was successful. But now, TWRP wont work again. When i try to boot into recovery, it just show the 1+ Screen and Vibrates for maybe 1 second, but than it skips and boot automatically into System. The SuperSU App says its no SU File installed and can't be installed. Fastboot didnt't work either. When i connect it and type in ADB devices it shows me the ID. But with Fastboot devices nothing happens and im unable to do anything over it. (Drivers are correctly installed, without Signature check by windows etc.)
I know, i probably made some huge mistakes with all that. Do you guys have any solutions to get the Bootloader working again?
Thanks for any helps!
best regards
That recovery was for new BL and you flashed it over Old one.
Follow this guide http://forum.xda-developers.com/oneplus-x/general/guide-mega-unbrick-guide-hard-bricked-t3272108
Adesh15 said:
That recovery was for new BL and you flashed it over Old one.
Follow this guide http://forum.xda-developers.com/oneplus-x/general/guide-mega-unbrick-guide-hard-bricked-t3272108
Click to expand...
Click to collapse
Ok i will do that.
But just to be sure. After ive done this, im updating Oxygen to the newest Version and then install Sultan's newest TWRP and CM ROM?
Like i said, im not a Pro with it and i just dont want to fu** it up again.
Thank you.
Ulman2033 said:
Ok i will do that.
But just to be sure. After ive done this, im updating Oxygen to the newest Version and then install Sultan's newest TWRP and CM ROM?
Like i said, im not a Pro with it and i just dont want to fu** it up again.
Thank you.
Click to expand...
Click to collapse
Yup.
Will work fine.
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??
Hello, first of all i am sorry for my english.
I beg you to help me.
I wanted to do an update from my Cuoco92 to Lineage ( https://forum.xda-developers.com/le...x-lineageos-15-1-oreo-leeco-le-max-2-t3771577 ) and i surely made something wrong because the phone was litteraly stuck.
So, i waited 1 hours... and nothing happened. Then, I decided to force the reset. Recovery told me that no rom was installed.
Then, i tried to install several roms from the website (cuoco, linegae, small eui...) but there are some issue :
- google play doesnot want to work at all.
- most of the time, the phone is saying something like "data corrupted. Put in it factory mode" and even when i reset my phone in factory mode, it is still telling me that.
Now, i am giving up because sideload said me "Error 7" each time i try to install something new.
I need your help. I beg you, i can give you with a steam game or something like that but i want to fix that...
Someone want to skype or i dont know?
Thank you!!
in TWRP please go to wipe > format data > yes.
then install any rom.
Heyyo, please upgrade to the latest version of TWRP. 3.2.1-2. it has fixed ADB sideload where as older versions it is broken.
https://twrp.me/leeco/leecolemax2.html
Also, another option is to use ADB push which tbh I always prefer over sideload so that the full zip is on the device.
IE...
adb push NameOfFile.zip /sdcard/
That will copy that zip to the sdcard folder which is the root of the data partition so it can be easily deleted once you are fully booted into the ROM.
For Gapps? I recommend MindTheGapps arm64. It's fully compatible to LineageOS and Oreo ROMs in general where as OpenGapps for Oreo is still of beta quality.
Lastly, I recommend upgrading your device firmware. X820 30s is the latest stable but arguably 466D has a newer timestamp for the modem portion of the firmware so in theory it should have better cellular connectivity.
All links can be found in the LineageOS 15.1 for x2 thread.
Good luck!
Hi all,
Sorry bit of a noob here - looking to install Pie or Pixel ROM on my pocoF1 - I have fastboot and TWRP now set up but slight complication when I go to wipe and install - the tutorials I have seeen shows an img file - where as the downloads I have see so far has been files within the zip folder.
Not sure what to do here ?
Thanks
DS
So since TWRP is already set up this means that your data has already been wiped so no need to worry about that.
Grab the latest vendor-firmware from here and/or here . Flash in TWRP
and reboot. If all goes well reboot into TWRP, else PANIC! (just kidding...). Now flash latest PE. Note PE comes in two
flavours. I use AOSP. Some people prefer CAF. I would suggest trying both and settling on the one you prefer.
NOTE: I haven't mentioned DFE. That's because I don't use it.
Reboot, and all should be well. If you need Magisk, download it and install together with the Magisk Manager.
Note that some people have reported problems with v19.3 so download both 19.3 and 19.2.
Good luck and happy flashing.
Thanks !
Thats great ! thanks for the help will give it a go !
DS
@deathstalker19 well, how did it go???
guhvanoh said:
@deathstalker19 well, how did it go???
Click to expand...
Click to collapse
hmmm used beryllium-9.6.10-9.0-vendor-firmware then tried to flash PixelExperience_beryllium-9.0-20190604-0502-OFFICIAL came up with error 7 error installing zip file ??? using twrp
Its stuck in vendor firmware now.
Must have done something obviously wrong !
Thanks
DS
*UPDATE* got lineage OS 16 working - pixel didnt work as I dont think I had the latest kernall (?)
Ok I dont like Lineage lol - look to install stock android on here not sure how (yet) !
* UPDATE 2 *
good news the MUI version was older that I thought so I used the latest vendor firmware (the one used wasnt the latest) then used Pixel experience and got the encryption unsuccesful message- twrp'd changed the folder data type to Ex4 - restart - now ok !
Steepish learning curve - now I think I can try it with other phones !
Good to see you've gotten somewhat... Enjoy...
Hello community, so I have successfully done it as in title,
but I still have some steps which not very clear and would hope xda community could enlighten me about it.
so my steps are like this:
1. unlock bootloader with Mi unlock tool
2. flash stock MIUI10.3.8 android 9 rom
2.1 transfer 'Disable force encryption treble' and 'Magisk 19.4' to phone storage
3. fastboot, adb flash twrp 3.2.3-1, boot into twrp 3.2.3-1
4. install the 2 zip files in twrp
reboot system, and it went through..
I know I was lucky, so got some questions here:
1. TWRP mention it's necessary to do dm-verify disable. but I review seems I never did it and got no warning message or error about it. I wonder reason for this? is it because I never modify system partition anyway.
2. 'Disable force encryption treble' file has Magisk built in. I was surprised to see it in log, but nevertheless went to flash higher version 19.4 file. all went through I wonder any issue could be caused from this.
3. I review and realize didn't do the 'wipe data/cache' step before install the 2 zip files. It went through without issue surprisingly.. I wonder the reason for this.
3.1 and if I follow the guide to wipe data and cache first, the 2 zip files will still be there? kind of weird not sure how the emulated storage works..
3.2 Is this 'Disable force encryption treble' file step necessary? I read TWRP can auto settle this encryption thing in newer versions.
and I also wonder whether it means my current phone state is 'not encrypted' state. I check in settings 'encrypt with lock screen password' is off.
Thanks in advance guys
poor me no reply and magisk hide to be punched by safetynet enhance..
phileasx said:
poor me no reply and magisk hide to be punched by safetynet enhance..
Click to expand...
Click to collapse
You followed and old guide.
The latest stable for the poco is 11.0.6 (Android 10)
and the latest magisk is 20.3
Dfe is needed only if you don't want encryption. Otherwise it's not.
The question is what do you want to do.
Custom ROMs/stock ROMs, Android 9/10 there's a different procedure for each one.
sotosgolf said:
You followed and old guide.
The latest stable for the poco is 11.0.6 (Android 10)
and the latest magisk is 20.3
Dfe is needed only if you don't want encryption. Otherwise it's not.
The question is what do you want to do.
Custom ROMs/stock ROMs, Android 9/10 there's a different procedure for each one.
Click to expand...
Click to collapse
Thanks for your reply. Yep I used an older version as I needed something proven working. I'm fine with just MIUI10 android 9 and magisk 19.x.
Do you know about the Dm-verify thing, is it optional also?
phileasx said:
Thanks for your reply. Yep I used an older version as I needed something proven working. I'm fine with just MIUI10 android 9 and magisk 19.x.
Do you know about the Dm-verify thing, is it optional also?
Click to expand...
Click to collapse
Keeping dm-verity is an extra barrier for your device to not be exploited.
If you don't have any reason to turn it off, leave it as it is.