Problems with root and TWRP - Samsung Galaxy Note 8 Questions and Answers

I have a N950F and rooted it today by watching Max Lee High on Android videos. Flashing TWRP with ODIN,
formatting data, flashing OEM unlock zips and Magisk v16.0 ALL USING TWRP
after reboot and setup I boot to recovery because root was unstable so I wanted to reflash it
TWRP says 0MB, 0 memory in sdcard and I cannot flash anything. Also unable to mount anything except System which is RO, Cache, EFS.
Someone help me root my phone and add stereo, v4a and dolby :fingers-crossed:

Try to usw twrp from note 8 Forum here. The thread ist named twrp builder. Has you used a encryption ZIP to encrypt Data Partition?
Gesendet von meinem SM-N950F mit Tapatalk

Senichan said:
Try to usw twrp from note 8 Forum here. The thread ist named twrp builder. Has you used a encryption ZIP to encrypt Data Partition?
Gesendet von meinem SM-N950F mit Tapatalk
Click to expand...
Click to collapse
I didnt encrypt anything by myself, and I would not like to do this process again, I would like to look for a fix of this recovery, thanks

xperiaking247 said:
I didnt encrypt anything by myself, and I would not like to do this process again, I would like to look for a fix of this recovery, thanks
Click to expand...
Click to collapse
then try to install the Builder TWRP (https://forum.xda-developers.com/galaxy-note-8/development/recovery-galaxy-note-8-t3832962). It works like a charm. Other TWRP (like the one what you can download from the TWRP website for note 8) are outdatet and buggy on OREO roms

Go into recovery>wipe>format storage and type "yes" (that will delete all data in your phone) after that flash magisk and reboot.
The reason of unstability the root is Magisk Hide, you should turn it off from the settings. You can use magisk hide when you need it, but avoid shutting down your phone when it on.
Sorry for bad English ..
تم الإرسال من SM-N950F باستخدام Tapatalk

Whats the status of your phone now? Got it working?

I flashed my phone ... what 10-15? times yesterday before i got it right ....
as i have a European phone with Exynos i followed this
https://forum.xda-developers.com/galaxy-note-8/how-to/guide-how-to-root-note8-efs-backup-t3677038 part 1
with this twrp https://eu.dl.twrp.me/greatlte/ version 3.2.3
only exception to the guide was that i formated the /data twice (got errors first time)
Then i waited and waited (5-10-15min someting with powercord in phone)
then when i log to the phone for the first time i skip pin and password (ie no security enableing at first boot)
It worked fine.

Related

Why do I lose "system" (mount) in TWRP?

Guys, I just don't get it. No matter how many times I do a TOTAL clean install (ADB or via USB-OTG) with full format etc., after some times, in TWRP, my "System" is not mounted (unchecked). I can check it, and it looks like [V] too. But after a reboot in TWRP it's gone again. It makes me crazy and I can't work like this.
Because every Nandroid fails (back up looks fine, but after putting it back and rebooting I get bootloops because of this).
Well, I could start the whole process again but did it already 3 times. And for some reason, I can't explain, after a period of time it's gone again. I am running Stock 4.1.3, rooted with SuperSU, running Magisk, TWRP.
Because TWRP unmounts /system on reboot. Normal operations there. And that should have no effect on restoring backups. Something else is wrong. What version of TWRP are you using.
Sent from my OnePlus 3T using XDA Labs
Wipe internal storage using adb flash twrp using adb and wipe internal storage again but using twrp all will be fine. I highly sugest you to use the latest twrp by eng.stk
I'm using the 3.0.1-4 TWRP.
So when I reboot, system should be unchecked in TWRP? I don't think it was like that before...
System is always unchecked in twrp unless you manually check it.
Don't know about others but I have seen it just like this
exis_tenz said:
I'm using the 3.0.1-4 TWRP.
So when I reboot, system should be unchecked in TWRP? I don't think it was like that before...
Click to expand...
Click to collapse
I would suggest getting the latest blu_spark TWRP from @eng.stk blu_spark kernel thread. It is up to date and works well. But, yes, TWRP will unmount /system on a reboot.
Sent from my OnePlus 3T using XDA Labs

[HELP] Pixel Fastboot Magisk Patched Boot.img Installation

I downloaded the boot.img from the files that matched my version on the Google developers page. I loaded the boot.img and ran the Magisk Manager install option.
Took the patched_boot.img and flashed it to my Pixel then rebooted. Magisk Manager didn't show it was installed. Then I remembered I have slot A and B. So I went back installed, swapped to the other slot and installed again. Boot took a little longer this time. After the boot finished Magisk Manager still didn't show installed.
Any ideas on what steps I missed? Any successful Pixel 1/2 owners who have installed without TWRP or previous root?
I'm unrooted but have my bootloader unlocked from when I was using TWRP/SuperSU long ago. I wanted to move to Android 8 for the security updates and features. Now I want Magisk because I miss having root options.
Which versions are we talking about? Log?
Why open a new thread instead of posting in an existing one?
Gesendet von meinem Moto G 2014 LTE mit Tapatalk
gothicVI said:
Which versions are we talking about? Log?
Why open a new thread instead of posting in an existing one?
Gesendet von meinem Moto G 2014 LTE mit Tapatalk
Click to expand...
Click to collapse
Beta v14.3, didn't see one fitting my specific issue but I also probably didn't search well enough, and I will have to get/find the logs.
Are you referring to logs from Magisk itself or do I need to turn on logging in the developer menu somewhere and try to reflash the patched boot.img?
Zaf9670 said:
Beta v14.3, didn't see one fitting my specific issue but I also probably didn't search well enough, and I will have to get/find the logs.
Are you referring to logs from Magisk itself or do I need to turn on logging in the developer menu somewhere and try to reflash the patched boot.img?
Click to expand...
Click to collapse
I asked for versions (pl!) for a reason: there are many. You forgot to mention the manager and eventually twrp.
Simply post in the beta thread with a the available information and including a magisk log.
Gesendet von meinem Moto G 2014 LTE mit Tapatalk
Zaf9670 said:
I downloaded the boot.img from the files that matched my version on the Google developers page. I loaded the boot.img and ran the Magisk Manager install option.
Took the patched_boot.img and flashed it to my Pixel then rebooted. Magisk Manager didn't show it was installed. Then I remembered I have slot A and B. So I went back installed, swapped to the other slot and installed again. Boot took a little longer this time. After the boot finished Magisk Manager still didn't show installed.
Any ideas on what steps I missed? Any successful Pixel 1/2 owners who have installed without TWRP or previous root?
I'm unrooted but have my bootloader unlocked from when I was using TWRP/SuperSU long ago. I wanted to move to Android 8 for the security updates and features. Now I want Magisk because I miss having root options.
Click to expand...
Click to collapse
The quickest and easiest way is to download the 14.3 zip on your phone, then boot into TWRP via fastboot/ADB on your computer. Once in TWRP find the zip file and install. Then reboot. That is what I did and it took no time at all. Keeps stock recovery allowing OTA updates.

Chinese Mi8 to Global Instructions

So you bought a shiny new Chinese model, and want to convert to Global or EU version?
I had bought the Chinese version also, and couldn't find a solid method for converting to the Global or EU ROMs. I was worried i would brick my device like so many others! After finding bits and pieces in lots and lots of xda threads, MIUI forums, and finding some mis-information, i decided to put a working method all in one place!
**WARNING***
I am NOT responsible for anything that goes wrong or you have issues with the information i have provided, it worked for me and proceed at your own risk!
FIRST
Unlock your bootloader locked Chinese version phone! (It's a LONG wait)
see official unlock page here-->http://en.miui.com/thread-246705-1-1.html
After Bootloader Unlock
1.) Download TWRP from the page here-->https://forum.xda-developers.com/mi-8/development/recovery-twrp-3-2-3-0-mi-8-t3837745
-- RENAME YOUR DOWNLOADED RECOVERY FILE TO "recovery.img"
2.) Download the DM Verity Disabler here-->https://androidfilehost.com/?fid=3700668719832238534
3.) Download the Region Fix here-->https://www.androidfilehost.com/?fid=1322778262904000068
4.) Download a Global ROM / EU ROM of your choice!
Installing the TWRP Recovery:
Make sure you have a working copy of FASTBOOT on your computer compatible with Mi8 (I used the one in the directory from the Bootloader UNLOCK program)
1.) Copy all of your downloaded files to the Bootloader Unlocker main directory (or a directory with the Fastboot.exe file)
2.) Open a DOS shell prompt on your computer and change the directory to the Bootloader Unlock directory (or Fastboot.exe directory)
3.) Put your phone in to Fastboot Mode (Turn on phone and hold the Volume Down while also holding Power Button)
4.) Connect your phone via USB cable to your computer
5.) In your DOS shell prompt enter this between the quotes "fastboot.exe boot recovery.img"
6.) After your phone boots up with the TWRP, copy the recovery.img file to the main directory of your SDCard
(Your recovery should allow you to open your phones internal storage on your computer)
7.) Install from the TWRP recovery menu (choose IMG file on bottom right, and select the recovery.img from your storage, and choose the Recovery partition to flash to)
8.) After successful TWRP flashing to your recovery partition, Reboot to RECOVERY
Preparing & Flashing Your Downloaded ROM:
1.) Format your data (must be done from the wipe directory where you have to type the word "yes")
2.) after the format, once again reboot to your RECOVERY
3.) Copy your chosen ROM zip file, recovery.img file, Region Fix file, and DM Verity disabler file to your internal phone storage
4.) Install your chosen ROM (flash through TWRP)
5.) Flash your recovery.img file again! (choose IMG file on bottom right of screen, and select the recovery.img from your storage, and choose the Recovery partition to flash to)
6.) Flash the Region Fix file
** Optional of flashing Magisk (v17.1) now if you want **
7.) Flash the DM Verity disabler file
8.) Format DATA again (this removes all of your file from internal storage, so copy them back if you want after the format is done)
9.) Reboot to SYSTEM and Enjoy!
Some steps may be redundant or not needed, however -i spent countless hours in bootloops, reflashes, testing. This method works, and is what i follow every new ROM i install. I am now on the latest Miui10.8.9.6 Global.
Additional Notes:
DON'T downgrade versions of ROMs (ex, miui10 to 9, or miui9 to 8) Anti-Rollback isn't enabled to brick yet (it's only "1")
If you don't flash the Region fix on a Chinese phone, it will constantly reboot, during initial rom setup or won't even make it that far (wish i knew this before, it would have saved me many hours in bootloops)
If you want to STAY on Chinese rom versions with the bootloader locked, you CAN flash miui Chinese developer edition (ex miui10.8.30) using the internal software updater without issues (i did this while waiting for unlocking delay).
Placeholder
Holding
Great job ! A good idea for us
Thanks a lot.
I finally could install miui.eu.
Unfortunately i flash magisk but it doesn't root my phone.
Two questions:
First do i just have to flash magisk and dm verity after?
Then for flash another rom do i have to do all the steps again?
Adeline
Envoyé de mon ONEPLUS A3003 en utilisant Tapatalk
bidouille1 said:
Thanks a lot.
I finally could install miui.eu.
Unfortunately i flash magisk but it doesn't root my phone.
Two questions:
First do i just have to flash magisk and dm verity after?
Then for flash another rom do i have to do all the steps again?
Adeline
Envoyé de mon ONEPLUS A3003 en utilisant Tapatalk
Click to expand...
Click to collapse
Yes, you have to flash dm verity after magisk. After you are booted, if magisk is installed did you try to update magisk from the app? It worked on global ROM for me.
I would forward all steps again, but up to you. If you report back a shorter method that works j can modify instructions.
I am also working on a fix for the Chinese region that keeps coming back with reboot. I know what needs done, and have fixed mine, i just need to modify the region fix zip.
Agimax said:
Yes, you have to flash dm verity after magisk. After you are booted, if magisk is installed did you try to update magisk from the app? It worked on global ROM for me.
I would forward all steps again, but up to you. If you report back a shorter method that works j can modify instructions.
I am also working on a fix for the Chinese region that keeps coming back with reboot. I know what needs done, and have fixed mine, i just need to modify the region fix zip.
Click to expand...
Click to collapse
I flash again magisk and it works.
Thanks for all
Envoyé de mon MI 8 en utilisant Tapatalk
Thanks for this as it really saves time reading bits of information. I took time to change the ROM as I didn't want to brick my phone. Some knowledgeable people on here will even be annoyed if you ask for clarifications and tell you to read! I basically followed most of the steps mentioned.
Hi,
Can I relock bootloader after change from chinese to global version?
johnny1836 said:
Hi,
Can I relock bootloader after change from chinese to global version?
Click to expand...
Click to collapse
Unfortunately, Xiaomi made a stupid rule, which is that you can't lock global roms with chinese phones. Starting with Mi 8.
Is this goin to work for phones already unlocked by seller account? Is it possible to use my account after this procedure?
@HugoYe
I thought it is solution for lock after flash CN -> Global.
@johnny1836
What do you exactly mean by fixing the problem. I'm still trying to find a solution for this. Keeping the BL open is really bothering me, as I am using the Official Global rom.
Any trick to not wait 720 hours for unlock?
ricksmad said:
Any trick to not wait 720 hours for unlock?
Click to expand...
Click to collapse
Flashing the Developer Chinese ROM took my wait down to 340 hours while i was locked.......
Agimax said:
Flashing the Developer Chinese ROM took my wait down to 340 hours while i was locked.......
Click to expand...
Click to collapse
Do you have a link? Thanks
Sent from my MI 8 using Tapatalk
ricksmad said:
Do you have a link? Thanks
Sent from my MI 8 using Tapatalk
Click to expand...
Click to collapse
I just used the official Chinese ROM link, back then it was miui10 8.8.30 and let the updater in the phone do it.
here is the official CHINESE DEVELOPER BETA of Miui10 8.8.31-->http://bigota.d.miui.com/8.8.31/miui_MI8_8.8.31_b99e4f5263_8.1.zip
http://bigota.d.miui.com/8.9.6/miui_MI8_8.9.6_2e668ca434_9.0.zip
This one?
Sent from my MI 8 using Tapatalk
ricksmad said:
http://bigota.d.miui.com/8.9.6/miui_MI8_8.9.6_2e668ca434_9.0.zip
This one?
Sent from my MI 8 using Tapatalk
Click to expand...
Click to collapse
no, that is a 9.0 beta, i wouldn't touch that one right now. I edited my post above with 8.8.31 ---still 8.1 based.
@Agimax So with your step I can't lock Chinese mi8 variant with global stable or dev rom ?

Magisk 19.1 KILLED my Note 7 4/128 Gb

Stock rom, bought Note 7 4/128 Gb 2 weeks ago and waited till yesterday to unlock bootloader. Without using the phone.
Finally... Flashed TWRP but understood that with stock rom, every time I reboot to system, stock recovery replaces my TWRP.
So... Today I've flashed MAGISK 19.1 and yeah, TWRP remains every time... But...
EVERY TIME I REBOOT INTO SYSTEM, PHONE REQUIRES 4 MINUTES !!!! It stays on Redmi logo, with sign "Unlocked" in the bottom of the screen for more than 3 minutes... Damn And now? What to do?
Download a fastboot flash file for redmi note 7 and flash it via miflash your problem should be fixed
but your bootloader will be locked again
and twrp will be gone
@engloa wrong category
anikbarai123 said:
Download a fastboot flash file for redmi note 7 and flash it via miflash your problem should be fixed
but your bootloader will be locked again
and twrp will be gone
Click to expand...
Click to collapse
R u joking man ?! For what? For waiting other 15 or 30 days in order to unlock again the bootloader? And try again to root this damned phone obtaining this same result? Rather I'll put it in the trash and buy another one, maybe a decent phone this time.
zhad0ws said:
@engloa wrong category
Click to expand...
Click to collapse
Sorry, u've right. I've reported my tread in order to let moderators move it. :good:
PYCON said:
Stock rom, bought Note 7 4/128 Gb 2 weeks ago and waited till yesterday to unlock bootloader. Without using the phone.
Finally... Flashed TWRP but understood that with stock rom, every time I reboot to system, stock recovery replaces my TWRP.
So... Today I've flashed MAGISK 19.1 and yeah, TWRP remains every time... But...
EVERY TIME I REBOOT INTO SYSTEM, PHONE REQUIRES 4 MINUTES !!!! It stays on Redmi logo, with sign "Unlocked" in the bottom of the screen for more than 3 minutes... Damn And now? What to do?
Click to expand...
Click to collapse
Question: do you have a bootloop? Or does your phone simply need 4 minutes to boot up? If so where is the problem?
EZ solution: flash xiaomi.eu rom (which is way better) or flash another AOSP project.
If you really want to stay on stockrom: take the stockrom.zip -> remove the "verification.zip (or whatever it is called)" within the stockrom.zip and flash it via twrp.
Also: you should be able to flash the stockrom fastboot file without locking your bootloader again (since this only happens if you execute respective batch file).
I have magisk 19.1 installed and nothing is bricked, your thread is very misleading. Modding your device to hell and back isn't that difficult! ^^
Edit: when I flashed twrp first my device got encrypted (with no password setup). Everything can be fixed after a while.
MarvinMe said:
Question: do you have a bootloop? Or does your phone simply need 4 minutes to boot up? If so where is the problem?
EZ solution: flash xiaomi.eu rom (which is way better) or flash another AOSP project.
If you really want to stay on stockrom: take the stockrom.zip -> remove the "verification.zip (or whatever it is called)" within the stockrom.zip and flash it via twrp.
Also: you should be able to flash the stockrom fastboot file without locking your bootloader again (since this only happens if you execute respective batch file).
I have magisk 19.1 installed and nothing is bricked, your thread is very misleading. Modding your device to hell and back isn't that difficult! ^^
Edit: when I flashed twrp first my device got encrypted (with no password setup). Everything can be fixed after a while.
Click to expand...
Click to collapse
Question: do you have a bootloop? => NO
Or does your phone simply need 4 minutes to boot up? => YES
If so where is the problem? => these 4 minutes to boot up this phone... that's the problem, I think it's sufficient no?
It doesn't matter what rom I'm using but I need 48 MPixel working so, I suppose, or Global or EU. Not AOSP based. It's correct?
EDIT : just to be more specific... Stock camera app doesn't open anymore after flashing Magisk I get simply a black screen.
PYCON said:
Question: do you have a bootloop? => NO
Or does your phone simply need 4 minutes to boot up? => YES
If so where is the problem? => these 4 minutes to boot up this phone... that's the problem, I think it's sufficient no?
It doesn't matter what rom I'm using but I need 48 MPixel working so, I suppose, or Global or EU. Not AOSP based. It's correct?
EDIT : just to be more specific... Stock camera app doesn't open anymore after flashing Magisk I get simply a black screen.
Click to expand...
Click to collapse
Hi, thanks for the quick reply.
I have a very special tincture for you (except your really like it between scylla and charybdis):
Rom
Debloating - you can delete pretty much everything
#Feel free to flash magisk afterwards
#In case you get and error while completing the setup wizzard: just restart it without having wifi enabled and you are good.
#Best Google camera mod (everything works + focus tracking n'stuff)
It's worth it: I've been on the Stock rom side for years but I think MIUI is superior (GCAM > MIUI cam but doesn't matter) "and all of it just works :fingers-crossed:"
Edit: all of your data will be lost & you have to do the setup of your device again but trust me: it'll be so worth it ^^ just amazing
Follow the instructions on xiaomi.eu (<ROM> link) carefully and you are good.
MarvinMe said:
Hi, thanks for the quick reply.
I have a very special tincture for you (except your really like it between scylla and charybdis):
Rom
Debloating - you can delete pretty much everything
#Feel free to flash magisk afterwards
#In case you get and error while completing the setup wizzard: just restart it without having wifi enabled and you are good.
#Best Google camera mod (everything works + focus tracking n'stuff)
It's worth it: I've been on the Stock rom side for years but I think MIUI is superior (GCAM > MIUI cam but doesn't matter) "and all of it just works :fingers-crossed:"
Edit: all of your data will be lost & you have to do the setup of your device again but trust me: it'll be so worth it ^^ just amazing
Follow the instructions on xiaomi.eu (<ROM> link) carefully and you are good.
Click to expand...
Click to collapse
I'll try this EU rom, hope it'll work fine again Thx for the moment man.
PYCON said:
I'll try this EU rom, hope it'll work fine again Thx for the moment man.
Click to expand...
Click to collapse
In case you need help feel free contact me (DM) ^^ always glad to help :highfive:
Cheers!
https://forum.xda-developers.com/re...oot-redmi-note-7-one-click-root-tool-t3925785
or you can try this. installed twrp and magisk v19 without hassle.
note that everything gets wiped after, but you are ok since you said you didn't use your phone yet.
Did you disable verified boot by flashing dmverity zip? I think that could be causing the problem.
mtencarguez said:
https://forum.xda-developers.com/re...oot-redmi-note-7-one-click-root-tool-t3925785
or you can try this. installed twrp and magisk v19 without hassle.
note that everything gets wiped after, but you are ok since you said you didn't use your phone yet.
Click to expand...
Click to collapse
Thx but why use Rooter? Magisk should do this job...
agenius5 said:
Did you disable verified boot by flashing dmverity zip? I think that could be causing the problem.
Click to expand...
Click to collapse
No! Really? Where's written this step?! Did u try this? In the tread of unlocking bootloader, TWRP and so on, this step is not shown or I haven't seen
PYCON said:
Thx but why use Rooter? Magisk should do this job...
it's a 1-click rooter. if you want root use this. you don't have to do anything but plug your phone to your computer, go to bootloader and click. it installs twrp 3.3 and magisk v19. hassle free, that's what it is.
Click to expand...
Click to collapse
mtencarguez said:
it's a 1-click rooter. if you want root use this. you don't have to do anything but plug your phone to your computer, go to bootloader and click. it installs twrp 3.3 and magisk v19. hassle free, that's what it is.
Click to expand...
Click to collapse
Ok, first I'll try with Xiaomi EU rom but then I'll try this too.
I hope that there's a way to unbrick the phone if something goes wrong
No, I have to wait 2 more days. I used to flash it with redmi 5a. I don't know why this step is not there with rn7.
Just some little info, before flashing EU.
1) EU tutorial reports to wipe Dalvik / Cache / Data but NOT System before flashing rom... Really?! So strange
2) If Magisk involves issues, maybe it's possible to use SuperSU instead. Or not? It's too old?
3) If after flashing EU rom something goes wrong, my Bootloader remains unlocked? Or not? Just to be sure.
4) If after flashing EU rom something goes wrong, my TWRP will remain? In order to try other ways.
5) If after flashing EU rom something goes wrong, it's possible to restore a Nandroid backup with TWRP? All partitions? Or I've to skip some partition?
PYCON said:
Just some little info, before flashing EU.
1) EU tutorial reports to wipe Dalvik / Cache / Data but NOT System before flashing rom... Really?! So strange
2) If Magisk involves issues, maybe it's possible to use SuperSU instead. Or not? It's too old?
3) If after flashing EU rom something goes wrong, my Bootloader remains unlocked? Or not? Just to be sure.
4) If after flashing EU rom something goes wrong, my TWRP will remain? In order to try other ways.
5) If after flashing EU rom something goes wrong, it's possible to restore a Nandroid backup with TWRP? All partitions? Or I've to skip some partition?
Click to expand...
Click to collapse
1) it's not strange at all, as xiaomi.eu ROM is a system partition image. So no need to wipe a partition that will be overwritten seconds later.
2) no doubt your issue happened after you flashed magisk, as you stated it, but magisk is most probably not the main cause of the issue. It's the safest way to get root, SuperSU should not be used/trusted anymore as it is not maitained by chainfire anymore (iirc he sold his app long ago to some company)
I'm currently using my rn7 4/64 xiaomi.eu + magisk 19.1 with no issue nor boot delay.
Before that I had global eeu stock rom.
Xiaomi.eu is based on Xiaomi stock, but is not provided by Xiaomi, so it's actually more a custom rom than stock, so...
3) bootloader will stay unlocked
4) TWRP will stay there
5) I don't know, I did not do it yet. I would not overwrite any partition other than system, data and cache without knowing exactly what I'm doing
Well, firstly... Thank u all :good:
It seems I solved. I've followed these steps:
* boot into TWRP
* from TWRP, Format Data
* reboot into TWRP
* from TWRP, Full Wipe ( Dalvik / Cache / Data / System )
* copy Xiaomi EU ZIP into Internal Memory ( TWRP MTP ) => Release 9.4.25
* copy Magisk into Internal Memory ( TWRP MTP ) => Release 19.1
* from TWRP, flash Xiaomi EU ZIP
* reboot System
* configure initial setup wizard ( language, country, etc )
* reboot into TWRP
* from TWRP, flash Magisk ZIP
* from TWRP, Wipe ( Dalvik / Cache )
That's all. System boots in few seconds, as normal :highfive:
* ROOT => OK
* TWRP => remains (OK)
* BOOTLOADER => remains unlocked (OK)
PYCON said:
Well, firstly... Thank u all :good:
It seems I solved. I've followed these steps:
* boot into TWRP
* from TWRP, Format Data
* reboot into TWRP
* from TWRP, Full Wipe ( Dalvik / Cache / Data / System )
* copy Xiaomi EU ZIP into Internal Memory ( TWRP MTP ) => Release 9.4.25
* copy Magisk into Internal Memory ( TWRP MTP ) => Release 19.1
* from TWRP, flash Xiaomi EU ZIP
* reboot System
* configure initial setup wizard ( language, country, etc )
* reboot into TWRP
* from TWRP, flash Magisk ZIP
* from TWRP, Wipe ( Dalvik / Cache )
That's all. System boots in few seconds, as normal :highfive:
* ROOT => OK
* TWRP => remains (OK)
* BOOTLOADER => remains unlocked (OK)
Click to expand...
Click to collapse
can you give me the link of "Xiaomi EU ZIP " file you used, i can't find that !?
aka70 said:
can you give me the link of "Xiaomi EU ZIP " file you used, i can't find that !?
Click to expand...
Click to collapse
Yes, I think it's possible to post links of Xiaomi EU here.
10.4 Release is 9.4.25 => https://xiaomi.eu/community/threads/9-4-25-26.50275/
Older releases, like 10.3 => https://xiaomi.eu/community/threads/miui-10-0-10-1-10-2-10-3-stable-release.47170/

[Guide] Decrypt OnePlus 7 Pro

In this guide I will show you how to decrypt this phone
You might be asking:
(What are the advantages of decrypting?)
Well, it is much easier to switch between custom roms when you are decrypted and you don't have to wipe internal storage everytime you flash a new rom and there may be a performance increase (Maybe).
(What are the disadvantages of decrypting?)
If your phone gets stolen.. The stealer can access all of your data and can even remove the pattern by just rebooting to twrp and deleting a few files so your phone will not have any protection whatsoever.
Downloads:
Disable Dm-Verity
Magisk
Instructions:
1- You have to be on clean oos without any mods or kernels.
2- Reboot Recovery
3- Format data (Go to wipe - Format data and click yes)
4- Reboot Recovery
4- Flash No Verity Mod
5- Flash Magisk
6- Reboot System
Now you are decrypted!!
Keep Decrypt between OS updates:
-Reboot Recovery
-Flash FULL ZIP in TWRP
-Without booting the OS: Flash TWRP Recovery, reboot recovery, Flash No Verity Mod, Flash Magisk, Reboot System.
Keep Decrypt between Roms:
-Wipe Data only in twrp!!! (NEVER WIPE SYSTEM OR - VENDOR ON OP7P)
-Flash Rom
-Flash TWRP
-Reboot Recovery
-Flash any other zips you want like Gapps-Kernels- ex.....
-Flash No Verity Mod
-Flash Magisk
-Reboot System
Credits:
@topjohnwu
@Zackptg5
How would I know if I'm decrypted or not?
mlock420 said:
How would I know if I'm decrypted or not?
Click to expand...
Click to collapse
Settings, security, down towards the bottom it tells you
OK so I'm encrypted... Am I secured somewhat from theft correct? And yes I know it's not 100% but it is safer than decrypted?
Another question let's say I don't mind being encrypted because I have a flash drive with otg and all that... Is that good enough? Or should I go decrypted all the way so I can start backing up on twrp and restoring twrp without errors which would mean no use for flash drive...
I know it's my choice just trying to make things easier and to understand a little more
mlock420 said:
OK so I'm encrypted... Am I secured somewhat from theft correct? And yes I know it's not 100% but it is safer than decrypted?
Another question let's say I don't mind being encrypted because I have a flash drive with otg and all that... Is that good enough? Or should I go decrypted all the way so I can start backing up on twrp and restoring twrp without errors which would mean no use for flash drive...
I know it's my choice just trying to make things easier and to understand a little more
Click to expand...
Click to collapse
If you are really concerned about your data and you are OK with wiping internal storage, then I don't recommend decrypting and just leave it encrypted.
I have oos decrypted via disable force encrypt!
Today I went through the following process to update to the latest version of OOS.
1. Flash full oos & twrp
2. reboot to recovery
3. Flash magisk
4. flash disable force encrypt
5. reboot
rebooted, but back to TWRP,,,
there was a "0" directory in sdcard and inside it my data was in it.
Do you know the solution?
thx
download link is not working for the file.
cylent said:
download link is not working for the file.
Click to expand...
Click to collapse
XDA thread:
https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
Downloads:
https://zackptg5.com/android.php#disverfe
https://zackptg5.com/downloads/Disable_Dm-Verity_ForceEncrypt_12.27.2019.zip
Hi omar2005
May i ask you a quetion?
I just will get my oneplus 7 pro.
Under android 10.
During first time rooting and twrp install. Should i reboot recovery and flash decrypter or first finishing rooting than rebooting system and than do the steps like you said in your Instructions?
Thank you for orientation and greetings ivifly
You have to flash dfe before booting system. Once system boots, you'll be encrypted
Avril09 said:
You have to flash dfe before booting system. Once system boots, you'll be encrypted
Click to expand...
Click to collapse
What is DFE?
Sent from my OnePlus7Pro using XDA Labs
---------- Post added at 09:18 AM ---------- Previous post was at 09:17 AM ----------
Is there a way I could reencrypt(due to security concerns) without having to wipe my data? The option in security is greyed out :/.
Thank you
Sent from my OnePlus7Pro using XDA Labs
fp1707 said:
What is DFE?
Sent from my OnePlus7Pro using XDA Labs
---------- Post added at 09:18 AM ---------- Previous post was at 09:17 AM ----------
Is there a way I could reencrypt(due to security concerns) without having to wipe my data? The option in security is greyed out :/.
Thank you
Sent from my OnePlus7Pro using XDA Labs
Click to expand...
Click to collapse
DFE is Disable Force Encryption also known as dmverity in some cases.
And yea you can reencrypt without losing data but it takes time depending on the size of files you have.
omar2005 said:
In this guide I will show you how to decrypt this phone
You might be asking:
(What are the advantages of decrypting?)
Well, it is much easier to switch between custom roms when you are decrypted and you don't have to wipe internal storage everytime you flash a new rom and there may be a performance increase (Maybe).
(What are the disadvantages of decrypting?)
If your phone gets stolen.. The stealer can access all of your data and can even remove the pattern by just rebooting to twrp and deleting a few files so your phone will not have any protection whatsoever.
Downloads:
https://zackptg5.com/downloads/Disable_Dm-Verity_ForceEncrypt_05.21.2019.zip
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Instructions:
1- You have to be on clean oos without any mods or kernels.
2- Reboot Recovery
3- Format data (Go to wipe - Format data and click yes)
4- Reboot Recovery
4- Flash No Verity Mod
5- Flash Magisk
6- Reboot System
Now you are decrypted!!
Keep Decrypt between OS updates:
-Reboot Recovery
-Flash FULL ZIP in TWRP
-Without booting the OS: Flash TWRP Recovery, reboot recovery, Flash No Verity Mod, Flash Magisk, Reboot System.
Keep Decrypt between Roms:
-Wipe Data only in twrp!!! (NEVER WIPE SYSTEM OR - VENDOR ON OP7P)
-Flash Rom
-Flash TWRP
-Reboot Recovery
-Flash any other zips you want like Gapps-Kernels- ex.....
-Flash No Verity Mod
-Flash Magisk
-Reboot System
Credits:
@topjohnwu
https://forum.xda-developers.com/member.php?u=4470081
@Zackptg5:
https://forum.xda-developers.com/member.php?u=6037748
Click to expand...
Click to collapse
can we use this method for boot dual os (oos+custom) , when we install dual os twrp by @Zackptg5 we face problem with encryption and password protection on one of the os.
is it possible this method help this problem???
This does not work for my OP7Pro, when you say boot into Recovery and wipe data. Is that the stock recovery or TWRP? When I try decrypting using the instructions using TWRP, when I reboot the phone, it boots into the boot animation. But the animation is slow and the phone just gets stuck there and won't boot any further. Trying to decrypt so it's easier to get LineageOS installed. My phone seems to have problems when on the B partition reading the internal storage.
Scotsman828 said:
This does not work for my OP7Pro, when you say boot into Recovery and wipe data. Is that the stock recovery or TWRP? When I try decrypting using the instructions using TWRP, when I reboot the phone, it boots into the boot animation. But the animation is slow and the phone just gets stuck there and won't boot any further. Trying to decrypt so it's easier to get LineageOS installed. My phone seems to have problems when on the B partition reading the internal storage.
Click to expand...
Click to collapse
Are you running an open beta build? OnePlus did something dumb with the beta builds where this no longer works. I've been racking my brain trying to find a way to decrypt a beta too. For now, only the main builds of OOS are decryptable.
H4X0R46 said:
Are you running an open beta build? OnePlus did something dumb with the beta builds where this no longer works. I've been racking my brain trying to find a way to decrypt a beta too. For now, only the main builds of OOS are decryptable.
Click to expand...
Click to collapse
No, my phone was on a main build. Just wasn't having any luck and gave up. I'm on LineageOS now but spent an entire day trying to get that installed and working properly. Something was weird, slot A could read my internal storage, but when I switched to slot B the internal storage just disappeared. Once I got TWRP and LOS installed on both slots, the problem disappeared. But I still haven't attempted to decyrpt for fear of messing up my current setup.
H4X0R46 said:
Are you running an open beta build? OnePlus did something dumb with the beta builds where this no longer works. I've been racking my brain trying to find a way to decrypt a beta too. For now, only the main builds of OOS are decryptable.
Click to expand...
Click to collapse
It still works for me to this day tbh, on any rom i flash except some problems with android 11 roms ...
H4X0R46 said:
Are you running an open beta build? OnePlus did something dumb with the beta builds where this no longer works. I've been racking my brain trying to find a way to decrypt a beta too. For now, only the main builds of OOS are decryptable.
Click to expand...
Click to collapse
I'm on OOS 11 Beta 1 and decryption works fine for me. I was on 10.3.7 (decrypted) before.
Do you have to be on OOS? Or could any clean flashed rom work?
who can help. i cant decrypt my op7t pro. Well, let's start with the fact that when formatting dalvik cache and data, I have an error and nothing is formatted. as with (Go to wipe - Format data and click yes). Formatted this data via adb, installed No Verity Mod and now I have bootloop

Categories

Resources