Can't root after latest firmware update :( - Samsung Galaxy A3, A5, A7 (2017) Questions & Answe

Hello guys, i have an a5 2k17(sm-a520f), i flashed the latest firmware for the phone after being stuck in a bootloop(ksa firmware)
And the problem is that i tried many root methods like cf auto root which after flashing it the phone asks me to factory reset (no other options after booting)
And the cf auto root package generated by firmware.mobi gives nothing (not working i guess)
Also tried to flash the twrp recovery and then flash the supersu zip file after and i get the same messege i that verification failed and i have to factory reset, any help or ideas please?
Thank you

ahmad_salahat said:
Hello guys, i have an a5 2k17(sm-a520f), i flashed the latest firmware for the phone after being stuck in a bootloop(ksa firmware)
And the problem is that i tried many root methods like cf auto root which after flashing it the phone asks me to factory reset (no other options after booting)
And the cf auto root package generated by firmware.mobi gives nothing (not working i guess)
Also tried to flash the twrp recovery and then flash the supersu zip file after and i get the same messege i that verification failed and i have to factory reset, any help or ideas please?
Thank you
Click to expand...
Click to collapse
Have you used Odin?

moozer said:
Have you used Odin?
Click to expand...
Click to collapse
Yes of course :3

ahmad_salahat said:
Yes of course :3
Click to expand...
Click to collapse
Did you format data after flashing TWRP and then flash the Ashyx patch?

moozer said:
Did you format data after flashing TWRP and then flash the Ashyx patch?
Click to expand...
Click to collapse
Can't format data from twrp, because /data can't be mounted

ahmad_salahat said:
Can't format data from twrp, because /data can't be mounted
Click to expand...
Click to collapse
It's fine. You can. Your data has become encrypted.
Go here and download the patch : https://www.androidfilehost.com/?fid=24591000424951049
Save it to your external SD card
1. Enter recover
2. Format Data partition (Note: This will wipe the internal storage and ALL data contained within)
go to "Wipe" - tap "Format Data" button - type the word "yes" (without quotes) - tap the tick - go back to main screen​3. Check DATA is mountable.
go to Mount and check it is selected. Back tio mauin screen.​4. Flash root (Magisk or SU)
5. Flash boot image patch above.
6. Reboot into recovery
7. Flash your ROM and GAPPS. Have fun

moozer said:
It's fine. You can. Your data has become encrypted.
Go here and download the patch : https://www.androidfilehost.com/?fid=24591000424951049
Save it to your external SD card
1. Enter recover
2. Format Data partition (Note: This will wipe the internal storage and ALL data contained within)
go to "Wipe" - tap "Format Data" button - type the word "yes" (without quotes) - tap the tick - go back to main screen
3. Check DATA is mountable.
go to Mount and check it is selected. Back tio mauin screen.
4. Flash root (Magisk or SU)
5. Flash boot image patch above.
6. Reboot into recovery
7. Flash your ROM and GAPPS. Have fun
Click to expand...
Click to collapse
Thanks will try it tomorrow after i backup my data

ahmad_salahat said:
Thanks will try it tomorrow after i backup my data
Click to expand...
Click to collapse
How did you get on?

I has same problem. After update laters firmware patch date november. My phone can't flash custom recovery. Odin failed

Dr. Phone said:
I has same problem. After update laters firmware patch date november. My phone can't flash custom recovery. Odin failed
Click to expand...
Click to collapse
Do you have Developer Options enabled in settings?

Yes. OEM, USB has tick. But same problem

Dr. Phone said:
Yes. OEM, USB has tick. But same problem
Click to expand...
Click to collapse
Can you boot into TWRP?

Flash latest firmware then wait for the blue android screen that says installing updates etc etc...
After that screen immedietly boot into download mode and flash twrp then restart and again immedietly boot into twrp
---------- Post added at 02:52 PM ---------- Previous post was at 02:50 PM ----------
Just dont let phone boot into android
With this trick you should get /data decrypted so no needed to wipe and not need for no verity no encrypt patch because it lags your phone

ChARCOOL said:
Flash latest firmware then wait for the blue android screen that says installing updates etc etc...
After that screen immedietly boot into download mode and flash twrp then restart and again immedietly boot into twrp
---------- Post added at 02:52 PM ---------- Previous post was at 02:50 PM ----------
Just dont let phone boot into android
With this trick you should get /data decrypted so no needed to wipe and not need for no verity no encrypt patch because it lags your phone
Click to expand...
Click to collapse
Lags?

No verity no encrypt slowes your phone and it causes lock screen lag

ChARCOOL said:
No verity no encrypt slowes your phone and it causes lock screen lag
Click to expand...
Click to collapse
Erm...no it doesn't
---------- Post added at 20:07 ---------- Previous post was at 19:56 ----------
ChARCOOL said:
No verity no encrypt slowes your phone and it causes lock screen lag
Click to expand...
Click to collapse
Oh...hang on. Is it laggy on pin lock? That's different. I don't have that enabled on my device and just use swipe.
I don't have any lags or micro lags on my device at all and have flashed the zip.

It lags with no verity no encrypt

ChARCOOL said:
It lags with no verity no encrypt
Click to expand...
Click to collapse
HIGHLY unlikely considering it is encryption itself which causes lag. An unencrypted device isn't going to introduce lag.
It is more likely root has caused the issue.

ashyx said:
HIGHLY unlikely considering it is encryption itself which causes lag. An unencrypted device isn't going to introduce lag.
It is more likely root has caused the issue.
Click to expand...
Click to collapse
I was using your patch before I found this trick and it was lagging in lock screen with the patch and magisk.
After that I tried supersu still lags in lock screen. (because it's unencrypting phone like your patch)
Then i tried only magisk without any verity disabled force encrypt disabled patch.
And bum! no lock screen lags no verity error.

I have the same problem. I stitched A520FXXU2BQK1 firmware. (latest). After that The vendor disabled recovery. And now it is impossible to stitch others. For this reason I cannot stitch Twrp, Cwm and root.
Recovery msg : Only official released binar ies are allowed to be flashed (RECOVERY)
I also tried to stitch the previous firmwares to return root and twrp.. It did not help. I tried to return on the android 6 - he is not stitched

Related

Encryption issues on Nougat firmware

Hi guys,
just nowadays I installed OxygenOS Open Beta 10.
I was upgrading from Open Beta 7, but since I unlocked bootloader after doing that, we can say that I did a clean install (everyone should know that fastboot oem unlock erase all data).
However, I'm having troubles both with stock recovery and TWRP v3.0.2-1.28: pattern won't to be recognized.
If I disable pattern requiring at bootup, in recovery I need to type "a password" (that obviously is wrong in any case).
I tried to reinstall more times the firmware, also did factory reset both via stock/TWRP recovery and fastboot commands.
But nothing has changed.
System is working, but I can't access to recovery anyway.
You could try with other TWRP versions? Say 3.0.2-22
It's a known issue
Use twrp v3.0.2-1.19
Works with no issues, except a mouse pointer in the middle of the twrp. It does not interfere with anything, it is just there (a bug).
Simone98RC said:
Hi guys,
just nowadays I installed OxygenOS Open Beta 10.
I was upgrading from Open Beta 7, but since I unlocked bootloader after doing that, we can say that I did a clean install (everyone should know that fastboot oem unlock erase all data).
However, I'm having troubles both with stock recovery and TWRP v3.0.2-1.28: pattern won't to be recognized.
If I disable pattern requiring at bootup, in recovery I need to type "a password" (that obviously is wrong in any case).
I tried to reinstall more times the firmware, also did factory reset both via stock/TWRP recovery and fastboot commands.
But nothing has changed.
System is working, but I can't access to recovery anyway.
Click to expand...
Click to collapse
go to fastboot..
fastboot erase recovery
fastboot flash stock recovery (Open Beta 8)
reboot to recovery
wipe data
flash OOS 4.0 via sideload
reboot..skip setup..reboot to fastboot
fastboot flash twrp (modified)
reboot to recovery
wipe data
advance wipe data to f2fs
reboot
No dm-verity and no encryption
If you are on f2fs and encrypted, the blu spark kernel dev released a new recovery that supports f2fs decryption in TWRP. It may save you all the hassle. All you need to do is flash that updated recovery from fastboot and then try to decrypt. It should work fine.
All you have to do is wipe data partition. Reformat it as f2fs, all in TWRP and then reboot system and proceed with setup. Done!
atulclassic said:
go to fastboot..
fastboot erase recovery
fastboot flash stock recovery (Open Beta 8)
reboot to recovery
wipe data
flash OOS 4.0 via sideload
reboot..skip setup..reboot to fastboot
fastboot flash twrp (modified)
reboot to recovery
wipe data
advance wipe data to f2fs
reboot
No dm-verity and no encryption
Click to expand...
Click to collapse
Cannot find Open Beta 8 Recovery on the download link mentioned above. Looked else where but cannot locate.
Also I flashed recovery_OBT7.img (presumably Open Beta 9 recovery) and followed as mentioned above but DM Verity error does not vanish and TWRP also still asks for password.
Password I hope can be managed with the new modified TWRP mentioned below by @abhibnl but I am more concerned with the dm verity message not going...
---------- Post added at 12:37 AM ---------- Previous post was at 12:30 AM ----------
jim262 said:
All you have to do is wipe data partition. Reformat it as f2fs, all in TWRP and then reboot system and proceed with setup. Done!
Click to expand...
Click to collapse
confirmed password request gone...
dm-verity still exist...
phone does not boot past oneplus logo..can boot into recovery or fastboot but no system loading..
---------- Post added at 12:40 AM ---------- Previous post was at 12:37 AM ----------
jim262 said:
All you have to do is wipe data partition. Reformat it as f2fs, all in TWRP and then reboot system and proceed with setup. Done!
Click to expand...
Click to collapse
confirmed password request gone...
dm-verity still exist...
phone does not boot past oneplus logo..can boot into recovery or fastboot but no system loading..
now i am sideloading os from twrp
mnishamk said:
You could try with other TWRP versions? Say 3.0.2-22
Click to expand...
Click to collapse
It's not working, because modded TWRP from .18 to .23 are designed for Marshmallow community builds.
dbabaev21 said:
Use twrp v3.0.2-1.19
Works with no issues, except a mouse pointer in the middle of the twrp. It does not interfere with anything, it is just there (a bug).
Click to expand...
Click to collapse
What I've said above (tried .19 too with same unsuccessful result).
atulclassic said:
go to fastboot..
fastboot erase recovery
fastboot flash stock recovery (Open Beta 8)
reboot to recovery
wipe data
flash OOS 4.0 via sideload
reboot..skip setup..reboot to fastboot
fastboot flash twrp (modified)
reboot to recovery
wipe data
advance wipe data to f2fs
reboot
No dm-verity and no encryption
Click to expand...
Click to collapse
Probably it would be risolutive, however I want to stay on latest Community Build.
I can say that sideload won't work with Open Beta 10: it can be flashed only via recovery (both TWRP and stock).
jim262 said:
All you have to do is wipe data partition. Reformat it as f2fs, all in TWRP and then reboot system and proceed with setup. Done!
Click to expand...
Click to collapse
That would be easy! The hoped behaviour
Obviously I've just tried with unsuccessful result.
abhibnl said:
If you are on f2fs and encrypted, the blu spark kernel dev released a new recovery that supports f2fs decryption in TWRP. It may save you all the hassle. All you need to do is flash that updated recovery from fastboot and then try to decrypt. It should work fine.
Click to expand...
Click to collapse
Are you referring to this recovery?
Yeah, I would be in love both with you and the developer, if it works properly
Tomorrow I should try, I'll keep you updated :good:
UPDATE: I've always loved Magisk, since v7 (when I've started using it).
Magisk is the workaround for encryption: just today I've flashed it together with Open Beta 10.
Now encryption is disabled, so goodbye to recovery troubles.
However the issue can't be considered solved because of a stupid workaround, this is not the right approach: I will try @abhibnl solution (re-enable encryption, then install latest blu_spark recovery).
Thanks all for answering.
badmaash said:
Cannot find Open Beta 8 Recovery on the download link mentioned above. Looked else where but cannot locate.
Also I flashed recovery_OBT7.img (presumably Open Beta 9 recovery) and followed as mentioned above but DM Verity error does not vanish and TWRP also still asks for password.
Click to expand...
Click to collapse
The recovery should be linked in the official OB10 download page @ oneplus.net
Simone98RC said:
Are you referring to this recovery?
Yeah, I would be in love both with you and the developer, if it works properly
Tomorrow I should try, I'll keep you updated :good:
UPDATE: I've always loved Magisk, since v7 (when I've started using it).
Magisk is the workaround for encryption: just today I've flashed it together with Open Beta 10.
Now encryption is disabled, so goodbye to recovery troubles.
However the issue can't be considered solved because of a stupid workaround, this is not the right approach: I will try @atulclassic solution (re-enable encryption, then install latest blu_spark recovery).
Thanks all for answering.
Click to expand...
Click to collapse
Yes i was referring to that recovery. 1 user has responded that it worked fine on his f2fs encrypted storage, so i believe it's worth trying. I am not on f2fs so i personally can't test it for you. But i would advise you to atleast give it a try. You never know when you by mistake boot right after a fresh stock rom install with stock kernel, and it will immediately encrypt your storage. So, you can't always just keep formatting internal memory. A proper TWRP recovery is indeed required for both ext4 and f2fs. All i am waiting for is updated kernel sources for recovery devs to work on.
For the many having issues, here's a step by step:
step by step install for OOS 4.0 and twrp-3.0.2-1.28-op3.img
Have OOS stock recovery installed on your phone. You must also have adb installed on your computer.
connect your phone to your computer via usb and open a dos command session on your computer.
On your phone, reboot into fastboot (bootloader).
From adb command on computer, type fastboot boot twrp-3.0.2-1.28-op3.img.
First make a backup and copy it to a safe location.
Now wipe everything - Internal, system, data, cache.
Reboot to Recovery. This is the stock OOS recovery!
Go to install from USB and then enter sideload mode.
On your computer dos prompt, type adb sideload (path)OnePlus3Oxygen_16_OTA_035_all_1612310359_e10cadfb2af7.zip
Allow the long and slow process to complete and reboot.
Upon reboot, it is encrypting the data partition as EMMC.
Upon bootup, enter setup and go through it quickly as you will have to enter it again so do not waste time configuring it.
Once setup is complete, reboot into fastboot.
From DOS command, enter adb and type command fastboot boot twrp-3.0.2-1.28-op3.img.
TWRP will boot up asking for encryption password. Hit cancel and then swipe to allow modifications.
Go into mount. Only the system and cache will appear. Back out and select WIPE.
select ADVANCED WIPE and data partition only.
Modify the data parition by selecting Repair or Change file system.
It will list the current mount point as emmc. Select Change File System.
Select F2FS and swipe.
This will wipe current data partition and reformat it.
Once you have done this, while in TWRP, select the ADVANCED button on the main menu.
Now select ADB SIDELOAD and swip to start sideload.
On your computer in ADB, type command adb sideload SR1-SuperSU-v2.79-SR1-20161221223537.zip.
Now reboot system and go through the usual setup and your done.
TWRP v11: the definitive solution
abhibnl said:
If you are on f2fs and encrypted, the blu spark kernel dev released a new recovery that supports f2fs decryption in TWRP. It may save you all the hassle. All you need to do is flash that updated recovery from fastboot and then try to decrypt. It should work fine.
Click to expand...
Click to collapse
FINAL UPDATE: the specified recovery is working with Open Beta 10 decryption.
Thanks all for answering :good:

Root issues in Oreo

I'm installing twrp but whenever i try to boot into twrp all my data is wiped and twrp is unable to mount it
"Could not mount /data and unable to find crypto footer"
I need to manually change the filesystem and then again change to ext4 for twrp to mount data.
Main issue is i want to use snapchat and for that i need to boot into OS, login into snapchat and then root in twrp
but again as soon as i boot into twrp my data partition is not mountable. I have flashed no_encrypt_no_verity.dm_ashyx to disable dm-verity.
Flashed various twrp version from 3.0 to 3.2
Also did a clean OS flash from odin but still no luck.
Any suggestion and help will be appreciated.
jfk999 said:
I'm installing twrp but whenever i try to boot into twrp all my data is wiped and twrp is unable to mount it
"Could not mount /data and unable to find crypto footer"
I need to manually change the filesystem and then again change to ext4 for twrp to mount data.
Main issue is i want to use snapchat and for that i need to boot into OS, login into snapchat and then root in twrp
but again as soon as i boot into twrp my data partition is not mountable. I have flashed no_encrypt_no_verity.dm_ashyx to disable dm-verity.
Flashed various twrp version from 3.0 to 3.2
Also did a clean OS flash from odin but still no luck.
Any suggestion and help will be appreciated.
Click to expand...
Click to collapse
https://forum.xda-developers.com/sa...w-to/guide-root-install-twrp-samsung-t3747535
Baseminge said:
https://forum.xda-developers.com/sa...w-to/guide-root-install-twrp-samsung-t3747535
Click to expand...
Click to collapse
Tried that too , same issue still.
It seems that data partition gets corrupted whenever i boot into twrp everytime.
No way out
jfk999 said:
I'm installing twrp but whenever i try to boot into twrp all my data is wiped and twrp is unable to mount it
"Could not mount /data and unable to find crypto footer"
I need to manually change the filesystem and then again change to ext4 for twrp to mount data.
Main issue is i want to use snapchat and for that i need to boot into OS, login into snapchat and then root in twrp
but again as soon as i boot into twrp my data partition is not mountable. I have flashed no_encrypt_no_verity.dm_ashyx to disable dm-verity.
Flashed various twrp version from 3.0 to 3.2
Also did a clean OS flash from odin but still no luck.
Any suggestion and help will be appreciated.
Click to expand...
Click to collapse
have you wiped data(TWRP/wipe data/type YES in the keyboard)?
and use superuser for root cause magisk can t mount data at the moment.
broky said:
have you wiped data(TWRP/wipe data/type YES in the keyboard)?
and use superuser for root cause magisk can t mount data at the moment.
Click to expand...
Click to collapse
As soon as i boot in twrp, data is not mountable. So I then go to
wipe-->adv wipe-->(select data partition)repair or change partition-->change partition format-->fat
TWRP then wipes it to fat filesytem,then i change it to ext4 (which is readable by OS)
then only data partition is mounted.
Afterwards I flash no-verity-no-encryption_ashyx and RMM patch
Boots normal to OS
Again boot to twrp i get error unable to mount /data
I had this issue in nougat but it used to happen only once.After flashing patch i used to not get this error repeated
jfk999 said:
As soon as i boot in twrp, data is not mountable. So I then go to
wipe-->adv wipe-->(select data partition)repair or change partition-->change partition format-->fat
TWRP then wipes it to fat filesytem,then i change it to ext4 (which is readable by OS)
then only data partition is mounted.
Afterwards I flash no-verity-no-encryption_ashyx and RMM patch
Boots normal to OS
Again boot to twrp i get error unable to mount /data
I had this issue in nougat but it used to happen only once.After flashing patch i used to not get this error repeated
Click to expand...
Click to collapse
Twrp/above factory reset on right side there is an option format data.
Press on this option and a keyboard rises.type YES and select format data.
After this check data partition,should be mounted.
After this flash SU zip and last Ashyx s patch.
Idonel this many times never had a problem even in Orsi.
Hope it works I can t think of something else.
broky said:
Twrp/above factory reset on right side there is an option format data.
Press on this option and a keyboard rises.type YES and select format data.
After this check data partition,should be mounted.
After this flash SU zip and last Ashyx s patch.
Idonel this many times never had a problem even in Orsi.
Hope it works I can t think of something else.
Click to expand...
Click to collapse
Which twrp version are you using?
Try...
The universal "no verity opt encrypt".
Magisk for the above, or safetynet evasion.
Backing up snapchat in /data/data/ and /sdcard/Android/data/, and load the backup. By PC or external sdcard, or load the backup later.
jfk999 said:
Which twrp version are you using?
Click to expand...
Click to collapse
look in 1:13
this is the step i mean:
format data/type:yes
https://www.youtube.com/watch?v=iOjnmGQ14fc&t=41s
broky said:
look in 1:13
this is the step i mean:
format data/type:yes
https://www.youtube.com/watch?v=iOjnmGQ14fc&t=41s
Click to expand...
Click to collapse
Tried it but still same issue.
Bryan48765 said:
Try...
The universal "no verity opt encrypt".
Magisk for the above, or safetynet evasion.
Backing up snapchat in /data/data/ and /sdcard/Android/data/, and load the backup. By PC or external sdcard, or load the backup later.
Click to expand...
Click to collapse
Tried the universal version for samsung and applied RMM patch, unfortunately same issue again.
I think that this has to do with SEpolicy. In nougat i used to get a small red warning at the edge of screen while booting to twrp. That time i did not face this
issue. Now I dont get any warning..boots into twrp with data partition corrupted.
I dont know, ive tried everything possible but no luck.
This is how I did and it works on my A320FL:
1. I installed Ashyx's version of TWRP via odin.
2. Boot into TWRP and "Format Data" from "Wipe" menu.
3. Flash SuperSu.
4. Flash Ashyx's patch.
5. Reboot phone(into recovery again).
6. Update TWRP with McFy's version.
jfk999 said:
Tried it but still same issue.[/QUO
I think I have the same issue.
May was your phone branded when you bought it?
Click to expand...
Click to collapse
Baseminge said:
jfk999 said:
Tried it but still same issue.[/QUO
I think I have the same issue.
May was your phone branded when you bought it?
Click to expand...
Click to collapse
I bought it from official store..Also i bought it jus few months after launch..
Which carrier are you using?
Click to expand...
Click to collapse
jfk999 said:
Baseminge said:
I bought it from official store..Also i bought it jus few months after launch..
Which carrier are you using?
Click to expand...
Click to collapse
So I think is something concerning the MM firmware that was not fixed with the N and O updates, 'cause I bought it very close to his launch too. I solved it by flashing a custom rom, so I think the problem was in official MM firmware or something went wrong in the OTA updates
Click to expand...
Click to collapse
Baseminge said:
jfk999 said:
So I think is something concerning the MM firmware that was not fixed with the N and O updates, 'cause I bought it very close to his launch too. I solved it by flashing a custom rom, so I think the problem was in official MM firmware or something went wrong in the OTA updates
Click to expand...
Click to collapse
Well ya..from MM to N, I did Odin update but from N to O i did ota update..since then im facing this issue..
But i still dont get it..i did a clean install and downloaded firmware from sammobile..yet this issue persist
Click to expand...
Click to collapse
jfk999 said:
Baseminge said:
Well ya..from MM to N, I did Odin update but from N to O i did ota update..since then im facing this issue..
But i still dont get it..i did a clean install and downloaded firmware from sammobile..yet this issue persist
Click to expand...
Click to collapse
At this point the only advice I can give you is to do a full wipe including "Internal Storage" (if you didn't) before flashing with Odin.
I really don't guess it will solve the problem on an official firmware, but there's no harm in trying
Click to expand...
Click to collapse
Still no luck...
At this point i have lost hopes
jfk999 said:
Still no luck...
At this point i have lost hopes
Click to expand...
Click to collapse
No matter what you try at this point you're data will always encrypt and will need to be formatted. TWRP will always reset.
This requires a whole different route and needs you to edit system files.
I'll get back to you with details.
---------- Post added at 11:25 PM ---------- Previous post was at 10:39 PM ----------
jfk999 said:
I'm installing twrp but whenever i try to boot into twrp all my data is wiped and twrp is unable to mount it
"Could not mount /data and unable to find crypto footer"
I need to manually change the filesystem and then again change to ext4 for twrp to mount data.
Main issue is i want to use snapchat and for that i need to boot into OS, login into snapchat and then root in twrp
but again as soon as i boot into twrp my data partition is not mountable. I have flashed no_encrypt_no_verity.dm_ashyx to disable dm-verity.
Flashed various twrp version from 3.0 to 3.2
Also did a clean OS flash from odin but still no luck.
Any suggestion and help will be appreciated.
Click to expand...
Click to collapse
This method requires intermediate knowledge of Windows and CMD commands....I've tried to simplify it and hope it is easy enough to go through
The files that need editing are the ramdisk fstab files.
Basically you are going to unpack boot.img, edit the files and repack it.
Here's how you do it:
In windows...From the firmware, open the AP file with WinRAR. Extract boot.img.lz4 and save it to your desktop
Go here https://github.com/lz4/lz4/releases/download/v1.8.2/lz4_v1_8_2_win64.zip
Extract it then just place your boot.img.lz4 to directory of lz4
Next open up cmd as admin and cd to the location where lz4.exe is located
In cmd type lz4.exe boot.img.lz4
This will unpack the lz4 file.
Now download http://www.mediafire.com/file/93a3f4bikaxh6tj/MTK_Extractor_V2.6.3.zip
Just open exe go to boot tab select the unpacked boot.img
This will extract the files you need and it will create folder called "initrd" and it will contain the contents of boot.img.
Make sure you have Notepad++ installed to edit the files.
Go to the MTK folder where your files have been extracted
Right click Fatah.goldfish and select open with Notepad++
Next find the phrase ",encryptable=userdata"
Delete it
Close the tab in Notepad++ and click to save
Back to MTK folder and right click fstab.ranchu. Open with Notepad++
Find the phrase ",quota,forceencrypt=/dev/block/vdd"
Delete it
Find the phrase ",encryptable=userdata"
Delete it
Close the tab in Notepad++ and click to save
Back to MTK folder and right click fstab.samsungexynos7880. Open with Notepad++
Find the phrase ",verify"
Delete it
Find the phrase ",forceencrypt=footer,quota"
Delete it.
Close the tab in Notepad++ and click to save
Next, go back to the MTK program and press the repack button
This will create your new boot.img file
Go back to the MTK folder. You should see your old boot.img file saved as "boot-old.img" and your new file as "boot.img"
Install 7-zip
Back to MTK right click your new boot.img. select 7-zip then select "add to archive"
This will open up another window. Simply select "tar" from the dropdown menu for "Archive format"
Press OK
This will create a new file "boot.tar"
Flash this via Odin with phone in Download mode
The boot will now be patched and you can set up TWRP as you need.
This whole process will need repeating if a new AP is flashed

I need root on oreo 8.1 stock OTA

Hi, yesterday i've got OTA on stock rom, i reflash stock because i was rooted before, and after succesfully update, i tried to flash no verity from twrp 3.2.3.0 and magisk. I booted ok, the root is present, everything is fine but the phone is encrypted. I knew that no verity decrypt the phone but for me doesnt. Somebody knows or tried to root oreo stock? Thank you
To start with flashing magisk should mean you don't need to flash the no verity zip
Also only the official twrp from my thread will support encryption
Also if you change roms you must format data to remove encryption else the phone will boot to the encryption screen & will tell you the password is wrong
You can either format data in twrp - wipe format data (not advanced wipe. The option to the right of advanced wipe)
Or in fastboot enter the command
fastboot erase userdata
Note this will format everything on internal storage
Once you have booted the new rom you can encrypt again
I have official twrp 3.2.3.0, the phone is encrypted and rooted, but i want to be decrypted and i can't do that. I formated all phone, all data, in magisk appear checked preserved encryption.
I don't want to change rom, I only want stock and root, but not encryption
woozie.2007 said:
I don't want to change rom, I only want stock and root, but not encryption
Click to expand...
Click to collapse
If it was previously encrypted you still need to format data
This will remove encryption and everything on internal storage will be deleted
Then it should just be a case of flashing the latest version of Magisk
I don't have this device so I can't test it
The stock kernel may require forced encryption so you may not have a choice with stock but I can't check that
I just update ota 8.1, after that i flashed twrp via fastboot, then magisk 15.3. latest magisk didnt work, but i tried to flash no verity but the encryption still there even i formated all data and i configured the phone from zero
woozie.2007 said:
I just update ota 8.1, after that i flashed twrp via fastboot, then magisk 15.3. latest magisk didnt work, but i tried to flash no verity but the encryption still there even i formated all data and i configured the phone from zero
Click to expand...
Click to collapse
If you formatted data in twrp
Wipe - select option on right
Or
Format data as a different partition type then format it back to what it was
Will remove encryption
Also
fastboot erase userdata
Should do the same
You should get no prompt to enter decrypt key as device should no longer be encrypted
TheFixItMan said:
If you formatted data in twrp
Wipe - select option on right
Or
Format data as a different partition type then format it back to what it was
Will remove encryption
Also
fastboot erase userdata
Should do the same
You should get no prompt to enter decrypt key as device should no longer be encrypted
Click to expand...
Click to collapse
doesn't work...
woozie.2007 said:
doesn't work...
Click to expand...
Click to collapse
Without your device I can only put it down to user error as that's how I've always removed encryption
TheFixItMan said:
Without your device I can only put it down to user error as that's how I've always removed encryption
Click to expand...
Click to collapse
i know and i understand, i do it for many times on nougat, but now on oreo doesnt works, anyway thank you for help me
So, every method i tried i didnt succeed to make the phone unencrypted. I root it with magisk 17.1, in play store appears to be not certified. Is any problem? I mention before with 7.0 and magisk the phone was certified. Sugestions? Thanks
woozie.2007 said:
So, every method i tried i didnt succeed to make the phone unencrypted. I root it with magisk 17.1, in play store appears to be not certified. Is any problem? I mention before with 7.0 and magisk the phone was certified. Sugestions? Thanks
Click to expand...
Click to collapse
Change the device fingerprint
https://forum.xda-developers.com/apps/magisk/module-magiskhide-props-config-t3789228
Install above magisk module
In a terminal emulator (playstore) run the following
su
props
Select option to change fingerprint & change to a working moto g5 (or similar) fingerprint
Restart phone
Thank you sir, now appear certified in play, is still encrypted but rooted, i think is ok, right?

[Guide] How to Remove Device Encryption to Flash Custom ROMs

The Issue
The device does not allow to use the newly flashed Custom ROM as it is Encrypted thereby asking for Password every time the phone boots up and wiping Data Partition with a Custom Recovery also does not work.
The Solution
Step 1 - Type anything as Password when the device asks for it after booting up. Be Quick as the device will shut down if you don't type anything within a few seconds.
Step 2 - Check whether it says Decryption was successful but the data is corrupted and also instructs to do a factory reset by tapping the Reset button. If Yes then go to the next step as the subsequent steps will resolve the issue. If No then this guide can not help you.
Step 3 - Do not touch that Reset button and reboot the device to Recovery by long pressing the Power button and then pressing Power and Volume Down simultaneously and choosing to go to Recovery from the Fastboot/Bootloader Menu.
Step 4 - Now connect the phone to your PC and transfer everything from your internal storage (if you didn't do it before flashing the Custom ROM) using MTP as the next steps will wipe the internal storage. Eject your SD Card from the device.
Step 5 - Download the Platform Tools from the link : [url]https://drive.google.com/open?id=1LEcF5iAjRdno2_aPKv9DYdOYtviC5xB7[/URL] and after extracting the folder place it in the C drive.
Step 6 - Install Motorola Device Manager from the link : [url]https://drive.google.com/open?id=12k2joSx5G08oourGlYLdtLEdTuOC9CVb[/URL] on your PC.
Step 7 - Download the Stock Recovery from the link : [url]https://drive.google.com/file/d/1_gogMT_GgSvg6FKpe2q4Z51gh22ftUdt/view[/URL] and place it in the platform-tools folder.
Step 8 - Assuming that your phone is still connected to the PC go to the Fastboot/Bootloader menu on the device by using Reboot to Bootloader option from the Recovery.
Step 9 - Go to the platform-tools folder on the C drive of your PC and open a Command Prompt window there by holding Shift key while Right clicking on the mouse and choosing the option. Enter the command fastboot devices to ensure that your phone is connected to the PC.
Step 10 - Enter the command fastboot flash recovery recovery.img to flash the Stock Recovery on the phone.
Step 11 - Reboot the device and enter anything as Password when the device asks for it. Now tap the Reset button to do Factory Reset. The phone will reboot to Stock Recovery and ask you to perform Factory Reset. Choose Yes to proceed and it will take a few seconds to do so. Voila!!! Your phone is successfully Decrypted and now you can boot into the Custom ROM you flashed.
Step 12 - As the phone is already Decrypted there is no need to keep the Stock Recovery. You can flash the Custom Recovery of your choice by going to the proper website and following the instructions to flash it on your device.
N.B : It took me a couple of hours to figure out the solution to this issue when I faced it and I wrote this guide so that it will help people who face the same issue in future. A Thanks! is much appreciated .
I work with "format data" in twrp
kuzo said:
I work with "format data" in twrp
Click to expand...
Click to collapse
That didn't work in my case.
Otherwise it's the easiest way to do so.
I also do not work the "format data" the first time. you have to do it once and gives error, then restart , go to twrp and do it again and there if it works. and reinstall the rom again ... after that you can change rom normally
kuzo said:
I also do not work the "format data" the first time. you have to do it once and gives error, then restart , go to twrp and do it again and there if it works. and reinstall the rom again ... after that you can change rom normally
Click to expand...
Click to collapse
I did it at least four or five times and was unsuccessful.
The phone was only booting up normally with Stock ROM but always asked for Password if any custom ROM was flashed.
Then only I came up with the idea I posted here and was successful to remove the encryption.
data on the phone will not be deleted?
whitetornado said:
data on the phone will not be deleted?
Click to expand...
Click to collapse
Step 7: ". . . the next steps will wipe the internal storage. Eject your SD Card from the device."
You should expect that data will be deleted.
whitetornado said:
data on the phone will not be deleted?
Click to expand...
Click to collapse
Yes!
Step 10 will wipe the Internal Storage and the SD Card too if it is still in the device.
It's a safe practice to eject the SD Card before doing any operations.
Is this still required for Pie ROMs? I've unlocked my bootloader, installed TWRP and called it a day, didn't have to change anything, but I'm still on stock Oreo.
io_gh0st said:
Is this still required for Pie ROMs? I've unlocked my bootloader, installed TWRP and called it a day, didn't have to change anything, but I'm still on stock Oreo.
Click to expand...
Click to collapse
If you're still on stock and haven't flashed any custom ROMs in the past or decrypted your data by using the "format data" command in TWRP after unlocking the BL (like I did) your data partition should be still encrypted. Most custom ROMs, regardless if they're Oreo or Pie don't work with an encrypted data partition. If the developer of the ROM you'd like to flash doesn't recommend anything else you can decrypt by using the format data option in TWRP (the one you have to confirm with "yes") or maybe by following this guide, for me that was never necessary, you just may have to use "format data" twice to make it stick.
To prevent your system from re-encrypting you can flash magisk or use a disabled dm verity force encrypt zip:
https://yadi.sk/d/HLr5vjnkA8gaqw
This one can be found on
https://zackptg5.com/android.php
Sent from my Moto G5 Plus using XDA Labs
Wolfcity said:
If you're still on stock and haven't flashed any custom ROMs in the past or decrypted your data by using the "format data" command in TWRP after unlocking the BL (like I did) your data partition should be still encrypted.
Click to expand...
Click to collapse
The only time I've formatted /data was when I unlocked my bootloader. Immediately after this I've flashed TWRP, booted into it, installed magisk and restarted my device. It didn't asked for password or anything, this is why I'm confused. Since I haven't formatted using TWRP, it should be encrypted, right?
Wolfcity said:
Most custom ROMs, regardless if they're Oreo or Pie don't work with an encrypted data partition. If the developer of the ROM you'd like to flash doesn't recommend anything else you can decrypt by using the format data option in TWRP (the one you have to confirm with "yes") or maybe by following this guide, for me that was never necessary, you just may have to use "format data" twice to make it stick.
To prevent your system from re-encrypting you can flash magisk or use a disabled dm verity force encrypt zip:
https://yadi.sk/d/HLr5vjnkA8gaqw
This one can be found on
https://zackptg5.com/android.php
Sent from my Moto G5 Plus using XDA Labs
Click to expand...
Click to collapse
So since I installed magisk, then it shouldn't be encrypted, is that it? Sorry to sound soo noobish, but its been a while that I'm not flashing stuff and the last time I would just flash anything with no issues with encryption.
io_gh0st said:
The only time I've formatted /data was when I unlocked my bootloader. Immediately after this I've flashed TWRP, booted into it, installed magisk and restarted my device. It didn't asked for password or anything, this is why I'm confused. Since I haven't formatted using TWRP, it should be encrypted, right?
So since I installed magisk, then it shouldn't be encrypted, is that it? Sorry to sound soo noobish, but its been a while that I'm not flashing stuff and the last time I would just flash anything with no issues with encryption.
Click to expand...
Click to collapse
If you look into Settings->Security (see attached screenshots) what do you see there? (Mine is rooted and decrypted).
Edit: Check screenshots in the next post
Sent from my Moto G5 Plus using XDA Labs
Wolfcity said:
If you look into Settings->Security (see attached screenshots) what do you see there? (Mine is rooted and decrypted).
Click to expand...
Click to collapse
Sorry, wrong screenshots.
Sent from my Moto G5 Plus using XDA Labs
Wolfcity said:
If you look into Settings->Security (see attached screenshots) what do you see there? (Mine is rooted and decrypted).
Sent from my Moto G5 Plus using XDA Labs
Click to expand...
Click to collapse
It shows that my device is encrypted. So, to decrypt it, I have to wipe /data from TWRP, right? To make sure that it won't get encrypted again I have to wipe twice, or just flash the script you linked?
io_gh0st said:
It shows that my device is encrypted. So, to decrypt it, I have to wipe /data from TWRP, right? To make sure that it won't get encrypted again I have to wipe twice, or just flash the script you linked?
Click to expand...
Click to collapse
To decrypt it format/ data (not wipe, that's not enough, it's the option where you have to confirm with "yes"). As I did that I formatted data and after that flashed magisk. It doesn't work at first attempt so I went into TWRP and did it again.
Normally magisk should prevent your device from re - encrypting, if not flash the attached zip.
Sent from my Moto G5 Plus using XDA Labs
Wolfcity said:
To decrypt it format/ data (not wipe, that's not enough, it's the option where you have to confirm with "yes"). As I did that I formatted data and after that flashed magisk. It doesn't work at first attempt so I went into TWRP and did it again.
Normally magisk should prevent your device from re - encrypting, if not flash the attached zip.
Sent from my Moto G5 Plus using XDA Labs
Click to expand...
Click to collapse
By 'the attached zip' I believe you meant the one you've talked about a few posts ago?
io_gh0st said:
By 'the attached zip' I believe you meant the one you've talked about a few posts ago?
Click to expand...
Click to collapse
Exactly. Here's the latest one:
https://zackptg5.com/downloads/Disable_Dm-Verity_ForceEncrypt_05.21.2019.zip
Sent from my Moto G5 Plus using XDA Labs
Link is broken but I got the one from the other link made just a few months prior... Was there much a difference between that and the latest?
Thanks
itcanbdone said:
Link is broken but I got the one from the other link made just a few months prior... Was there much a difference between that and the latest?
Thanks
Click to expand...
Click to collapse
@Zackptg5 seems to have changed his side a bit, here's the actual link:
https://zackptg5.com/downloads/Disable_Dm-Verity_ForceEncrypt_08.18.2019.zip
Sent from my Moto G5 Plus using XDA Labs
Wolfcity said:
To decrypt it format/ data (not wipe, that's not enough, it's the option where you have to confirm with "yes"). As I did that I formatted data and after that flashed magisk. It doesn't work at first attempt so I went into TWRP and did it again.
Normally magisk should prevent your device from re - encrypting, if not flash the attached zip.
Sent from my Moto G5 Plus using XDA Labs
Click to expand...
Click to collapse
Do I need to select "Format Data" under "Wipe" to decrypt it? On TWRP, I see Wipe -> Format Data. If yes, do I need to remove SD card that has my system backup and custom ROM? Thanks.
---------- Post added at 03:14 AM ---------- Previous post was at 03:02 AM ----------
kuzo said:
I also do not work the "format data" the first time. you have to do it once and gives error, then restart , go to twrp and do it again and there if it works. and reinstall the rom again ... after that you can change rom normally
Click to expand...
Click to collapse
Are you referring to the "Format Data" tab under "Wipe" (that is, Wipe -> Format Data next to Advanced Wipe)? If yes, do I need to take out a SD card where I have a backup and custom ROM? Thanks.

Oreo Installation - Differences to Nougat?

Hello guys,
I'm a bit confused now from reading through different posts, each describing different methods.
Why can't we just Flash the IMG of Oreo like we would do with Stock Nougat?
Is this because it's still soak and hasn't really been released yet or am I missing something?
Also, where's the difference to just flash Stock Nougat and update to Oreo via the System Update button in the settings (that's called OTA, right?)?
Also I read "Flashing bootloader of equal or minor version will hardbrick your device"
Does that mean if I Flash that 2 times I Flash the same bl Version and I hardbrick my device?
I'm from Germany btw.
NPPS25.137.7 2.4 (I read, I have to be on 137.93.2.5 but I can just either flash it directly or flash an earlier stock and update until I'm there I guess?)
XT1676
Boot loader: B8.23
Note: I thought it would be better to post that in q&a instead of the reply section of the stock Oreo fastboot update post, since this are kind of general questions to the Oreo update topic.
Greetings,
7080
Flashing an oero stock rom firmware image is exactly the same as flashing a nougat stock rom firmware image (although there's a few more img_sparsechunks to flash)
You won't brick your phone if the firmware you are flashing the the same or newer
You will brick your phone if you try and flash a gpt & bootloader that is lower than the version currently on your phone
You can downgrade by flashing everything except these parts
There's no difference to flashing an ota via stock recovery to doing it via system update - however you must be on a fully unmodified stock rom else it will fail and potentially brick your phone
Don't confuse flashing an ota with flashing a complete stock rom firmware image
And ota must meet certain requirements - eg must be on a certain stock firmware version
A stock firmware image (complete stock firmware) can be flashed on any device (to which the image is for) that has the same or older bootloader version
TheFixItMan said:
Don't confuse flashing an ota with flashing a complete stock rom firmware image
And ota must meet certain requirements - eg must be on a certain stock firmware version
A stock firmware image (complete stock firmware) can be flashed on any device (to which the image is for) that has the same or older bootloader version
Click to expand...
Click to collapse
Thank you!
It took me some time to find out that OTA's only apply from one specific version to an other (the post from "tfwboredom" with all OTA's he was able to catch was a big help) and when i didnt get any OTA's (after flashing stock Nougat) i did an OTA update via adb. After that, my phone offered me OTA's again and i could upgrade until Oreo --.13 i guess. I rediscovered a thread with the full fastboot stock Oreo firmware --.16 then (forgot i already had downloaded it with my phone to my sd ^^) and flashed this then with the computer.
My Problem right now is the thing with the auto encryption.
Im on OPP28.85-16 now with TWRP64bit installed and was also able to get root by flashing newest Magisk (18.0) and the f2fs-loopback-bug-workaround (I dont really know for what that is) and installing MagiskManager v6.1 after booting system.
However, when i return to twrp after booting into system it asks me for a password to disable encryption and also wont flash things properly until i format data or do a factory reset. But after booting into system this encryption will be applied again. Flashing no-verity-encrypt didnt solve the problem.
What i want to find out now is:
1. Why is it automatically encrypting again and how can i disable that?
2. When i disabled that, can i encrypt my phone in the settings and use that password then to unlock twrp?
3. Where is the difference between this auto encryption and when i click in system settings on encrypt phone?
As far as i understood, in Nougat no-verity-encrypt was to prevent the dm-verity...thing to encrypt your phone but i could still enable encryption in the system settings.
(4. what is the purpose of f2fs bug fix?) - and has it enything to do with encryption?
G5-User7080 said:
Thank you!
It took me some time to find out that OTA's only apply from one specific version to an other (the post from "tfwboredom" with all OTA's he was able to catch was a big help) and when i didnt get any OTA's (after flashing stock Nougat) i did an OTA update via adb. After that, my phone offered me OTA's again and i could upgrade until Oreo --.13 i guess. I rediscovered a thread with the full fastboot stock Oreo firmware --.16 then (forgot i already had downloaded it with my phone to my sd ^^) and flashed this then with the computer.
My Problem right now is the thing with the auto encryption.
Im on OPP28.85-16 now with TWRP64bit installed and was also able to get root by flashing newest Magisk (18.0) and the f2fs-loopback-bug-workaround (I dont really know for what that is) and installing MagiskManager v6.1 after booting system.
However, when i return to twrp after booting into system it asks me for a password to disable encryption and also wont flash things properly until i format data or do a factory reset. But after booting into system this encryption will be applied again. Flashing no-verity-encrypt didnt solve the problem.
What i want to find out now is:
1. Why is it automatically encrypting again and how can i disable that?
2. When i disabled that, can i encrypt my phone in the settings and use that password then to unlock twrp?
3. Where is the difference between this auto encryption and when i click in system settings on encrypt phone?
As far as i understood, in Nougat no-verity-encrypt was to prevent the dm-verity...thing to encrypt your phone but i could still enable encryption in the system settings.
(4. what is the purpose of f2fs bug fix?) - and has it enything to do with encryption?
Click to expand...
Click to collapse
You need to format data to remove encryption
Wipe - option on the right
If you encrypt again once booted you need to use a twrp that supports encryption - the 64bit version posted in most rom threads don't support encryption but I did post the source code to my test version which someone compiled which may have encryption support
You can try it
https://drive.google.com/file/d/1kgFyYfjEyqAEXOGjg_UfeedlQwaLVF1F/view
All you should need to do is flash magisk - try version 17
You probably will need to change the device fingerprint to pass CtsProfile
Use this module
https://forum.xda-developers.com/apps/magisk/module-magiskhide-props-config-t3789228
TheFixItMan said:
You need to format data to remove encryption
Wipe - option on the right
Click to expand...
Click to collapse
- Yes, i did that, but when i boot system after it and return to twrp its again encrypted, but ill try a clean stock oreo flash -> twrp -> format data -> reboot -> return to twrp
If you encrypt again once booted you need to use a twrp that supports encryption - the 64bit version posted in most rom threads don't support encryption but I did post the source code to my test version which someone compiled which may have encryption support
You can try it
https://drive.google.com/file/d/1kgFyYfjEyqAEXOGjg_UfeedlQwaLVF1F/view
Click to expand...
Click to collapse
- Oh ok, i switched to 64bit version because of efs backup when still on Nougat, but i read somewhere that the 32bit version has that now, too, so could i also go just back to 32bit twrp?
As far as i remember, i never had a Problem with encryption on Nougat with 64bit.
- What does that mean that twrp supports encryption, when data gets encrypted every time, how should twrp be able to read that then?
All you should need to do is flash magisk - try version 17
Click to expand...
Click to collapse
- why 17 and not 18? i mean 18 worked when i tried it?
You probably will need to change the device fingerprint to pass CtsProfile
Use this module
https://forum.xda-developers.com/apps/magisk/module-magiskhide-props-config-t3789228
Click to expand...
Click to collapse
- I have currently no lock enabled, because i want to do a twrp backup after everything is done, what is the problem with fingerprint and what is CtsProfile?
I'll try that things out, thank you, and edit this when i find some things out
What i want at the end is a rooted Oreo (done) with a working twrp, where i can still flash and backup and restore without wiping data every time and if possible i want to use the normal encryption (the one when i boot system and set it up in settings).
I still dont really get what this auto encryption is.
As far I was aware the 64bit twrp cannot decrypt data apart from the test one I posted
If you don't have a twrp that supports data encryption your phone will still work, you just won't be able to use/flash zips to the data partition or backup/restore that partition
If you get a decrypt data when you boot your phone normally and it doesn't decrypt then you must remove encryption and boot the rom first before applying encryption again
My official 32bit twrp does support data encryption and will work on any 32bit rom including stock oero
Use any version of Magisk that works for you - I no longer own this device & only tested with magisk 17
Everything worked pretty well until i wanted to restore an older backup, I tried to format data before doing the restore but it failed.
After i flashed twrp (official 32bit this time) i did a factory reset to remove decryption and rebooted recovery to prevent the system fromr eplacing it. But when i use format data after that (or already in first place, could be that i tried that, too) it fails, it sais data successfully decrypted and continues and then theres an error. And when i try then a factory reset, too it fails, too.
However, after changing file system to ext4 and than formatting again (i dont remember exactly) i endet up with a working f2fs data partition and was able to use format data and restore backup,...
I am very confused now, because i dont get at all what the heck is the problem, should i not format data and do factory reset or does this happen when i flash the f2fs bug workaround before or is it because i booted the system and begun to change the settings, i have no idea,.. but ill try out and write you when i find something out!
EDIT:
Ok i found some things out, still dont understand at all, but it seems that
format data fails after booting into system
but works after rebooting twrp again
factory reset fails after format data fails
but works after format data works
works not after rebooting twrp, only if format data was successfull before (bec that works again after rebooting twrp)
rebooting system after format data failed will result into a bootloop into recovery with error when trying to enter recovery after manually going to bootloader -> recovery it works
It may help to see it in a table:
After flashing Oreo(boots up) and then twrp:
format data failed
factory reset failed
After flashing Oreo(boots up) and twrp and rebooting twrp:
format data successfull
factory reset successfull
reboot system
reboot twrp
format data failed
factory reset failed
reboot system results in bootloop into recovery with error
reboot twrp
factory reset failed
format data successull
reboot system
reboot twrp
factory reset successull
format data failed
factory reset failed
reboot twrp
factory reset failed
format data successull
factory reset successull
Output when format data fails:
Code:
[CODE]Data successfully decrypted, new block device: '/dev/block/dm-0'
Updating partition details...
...done
Successfully decrypted with default password.
Updating partition details...
...done
Full SELinux support is present.
MTP Enabled
I guess thats the log from twrp start and what followes is the one for format data
Code:
Formatting Data using mkfs.f2fs...
mkfs.f2fs -t 0 /dev/block/mmcblk0p54 process ended with ERROR: 255
Unable to wipe Data.
Unable to format to remove encryption.
Updating partition details...
Failed to mount '/data' (Device or resource busy)
...done
Unable to mount Storage
[/CODE]
And for factory reset after it:
Code:
Failed to mount '/data' (Device or resource busy)
Formatting Cache using make_ext4fs...
Updating partition details...
Failed to mount '/data' (Device or resource busy)
...done
Unable to mount storage
Try a
fastboot erase userdata
Type this in cmd on pc with phone connected via USB in bootloader mode
This will erase everything on internal
TheFixItMan said:
Try a
fastboot erase userdata
Type this in cmd on pc with phone connected via USB in bootloader mode
This will erase everything on internal
Click to expand...
Click to collapse
when should i do that?
Instead of using frmat data?
So when i flash twrp and boot into it first thing i should do is format data right? So i should just after flashing erase userdata and THEN enter twrp or what?
I'll copy in my reply from an other thread where 2 ppl tried to help me.
G5-User7080 said:
hmm, i did as follows:
flash stock (oreo) be sure sparsechunk 0-8 are ALL flashed
let phone start and turn it off again
flash twrp
boot recovery and factory reset
reboot recovery
flash magisk 18
reboot system
install magisk 6.1 apk
The thing is, when i dont reboot recovery after its installation the system will overwrite it with stock recovery and as far as i understood i need to reboot twrp for that.
I just did as i did for Nougat there regarding the post from 'Johny Cipeli':
6. In the Decrypt /data screen, press cancel, then "Swipe to Allow Modifications"
7. Go to WIPE, then "Swipe to Factory Reset"
8. Come back to TWRP main menu, go to REBOOT, then RECOVERY, then DO NOT INSTALL
So should i do then:
flash stock (oreo) be sure sparsechunk 0-8 are ALL flashed
let phone start and turn it off again
flash twrp
boot recovery
reboot recovery
format data
flash magisk 18
reboot system
install magisk 6.1 apk
or is this irrelevant if i first format data, then reboot twrp and then flash magisk?
Why do you flash no-verity? I tried that out earlier but it made no difference on the standard encryption.
I tryed a bit around with the data errors and found some things out, would you mind switching to this thread for the following?
Thank you for helping me, I just get totally confused by the Oreo process,.. worked so easy on nougat
Click to expand...
Click to collapse
As I rooted the device it was on Oreo OPS28.85-13-3 by OTA and I did it like this:
flash latest official twrp 3.2.3.1
make a backup of EFS and persist
boot recovery (now it prompts you to give in a decryption code, just press skip)
format data (F2FS)
don't reboot now
flash magisk 18 (I flashed 17.2 and updated later, no clue why)
reboot to system
install magisk 6.1 apk (if it's missing, in my case it was present)
if you reboot to twrp now it shouldn't prompt you to give in a decryption key anymore
G5-User7080 said:
when should i do that?
Instead of using frmat data?
So when i flash twrp and boot into it first thing i should do is format data right? So i should just after flashing erase userdata and THEN enter twrp or what?
I'll copy in my reply from an other thread where 2 ppl tried to help me.
Click to expand...
Click to collapse
It's the same as format data in twrp
To have it all in one Thread:
Wolfcity said:
So if you can't decrypt your data partition by formatting it (F2FS) and flashing magisk right after it without a reboot in between it may be possible that the bug is still present.
In that case you can give it a try and flash the fix from TWRP, maybe one of the older versions because the latest ones doesn't work for everyone.
Click to expand...
Click to collapse
hmm, i did as follows:
flash stock (oreo) be sure sparsechunk 0-8 are ALL flashed
let phone start and turn it off again
flash twrp
boot recovery and factory reset
reboot recovery
flash magisk 18
reboot system
install magisk 6.1 apk
The thing is, when i dont reboot recovery after its installation the system will overwrite it with stock recovery and as far as i understood i need to reboot twrp for that.
I just did as i did for Nougat there regarding the post from 'Johny Cipeli':
6. In the Decrypt /data screen, press cancel, then "Swipe to Allow Modifications"
7. Go to WIPE, then "Swipe to Factory Reset"
8. Come back to TWRP main menu, go to REBOOT, then RECOVERY, then DO NOT INSTALL
So should i do then:
flash stock (oreo) be sure sparsechunk 0-8 are ALL flashed
let phone start and turn it off again
flash twrp
boot recovery
reboot recovery
format data
flash magisk 18
reboot system
install magisk 6.1 apk
or is this irrelevant if i first format data, then reboot twrp and then flash magisk?
woozie.2007 said:
i dont think so, I rooted in that method, after update to oreo 8.1 stock, i flash official terp, then I flashed no verity 6.0 adn then format data partition. After that i booted in android, it say is encrypted, i can't decrypt it, but it works very well. I rooted two moto g5 stock oreo in that mode. Good luck
Click to expand...
Click to collapse
Why do you flash no-verity? I tried that out earlier but it made no difference on the standard encryption.
woozie.2007 said:
i flashed no verity because i want to decrypt the phone, but i didnt do that, not works, but works twrp for flashing, backup and restore without any problems. I cant say because of no verity or not, but it works. My phone is encrypted, but rooted with magisk 18.0 and i can install any module i want
Click to expand...
Click to collapse
As far as i know from 'TheFixItMan', he said that the 32bit twrp is able to surpass the encryption somehow.
But i guess this is kind of a standard encryption and not the "real encryption" could that be?
Because, i thought encryption means, you have to enter a password on boot to decrypt it.
When you set up your password under security you can choose to enter it on boot and then it will ask you for this password everytime BEFORE booting your system, and this will also be your password to decrypt data for twrp then. But i dont know if thats the "real encryption" or that standatd thing is, too, but just decrypts automatically on boot.
Thank you for helping me, I just get totally confused by the Oreo process,.. worked so easy on nougat
in security option, the phone appear to be encrypted, in nougat after flash no verity the phone was decrypted. In oreo i dont know why is appear encrypted and i cant decrypt with no verity....
Wolfcity said:
As I rooted the device it was on Oreo OPS28.85-13-3 by OTA and I did it like this:
flash latest official twrp 3.2.3.1
make a backup of EFS and persist
boot recovery (now it prompts you to give in a decryption code, just press skip)
format data (F2FS)
don't reboot now
flash magisk 18 (I flashed 17.2 and updated later, no clue why)
reboot to system
install magisk 6.1 apk (if it's missing, in my case it was present)
if you reboot to twrp now it shouldn't prompt you to give in a decryption key anymore
Click to expand...
Click to collapse
I dont have the option to backup efs,.. im using twrp 3.2.3-0 (the latest i could get from official twrp site) but i already did backup efs and persist in nougat, isnt that enough? DO i have to do that again on Oreo?
Also its not asking me for a decryption code, are you using 64bit twrp then?
And i remember that twrp got overwritten 2 or 3 times by stock recovery, and i thought that was because i didnt rebooted twrp again, since i rebooted twrp after formatting data it didnt happen again.
Also it did work for me using the 1. method i wrote earlier, i successfully rooted my phone, im just wondering now which is the "better" or "correct method to either
boot recovery, reboot recovery, format data and flash magisk
boot recovery, format data, reboot recovery, flash magisk
boot recovery, format data, flash magisk, boot system (but i guess next time you enter twrp it gets overwritten by stock recovery then)
boot recovery, format data, flash magisk, reboot recovery and boot system
or stay in bootloader (after flashing twrp) fastboot erase userdata, boot recovery, -data, -magisk, -system
or -recovery, -bootloader fastboot erase userdata, -recovery, -magisk, - system,.... you get the idea
woozie.2007 said:
in security option, the phone appear to be encrypted, in nougat after flash no verity the phone was decrypted. In oreo i dont know why is appear encrypted and i cant decrypt with no verity....
Click to expand...
Click to collapse
Because theres some sort of auto encryption which everytime reencrypts your phone.
I just dont get the sense of formatting data if it gets reencrypted anyway and twrp can surpass encryption.
G5-User7080 said:
After flashing Oreo(boots up) and then twrp:
format data failed
factory reset failed
After flashing Oreo(boots up) and twrp and rebooting twrp:
format data successfull
factory reset successfull
. . .
Click to expand...
Click to collapse
Had to correct that!
So in general after booting system, formatting data fails, maybe it works with fastboot erase userdata (didnt test it, cause i dont want to reflash Oreo again, i wanna go to bed.
But just rebooting recovery after booting first time in twrp works, so after that format data works. Works not..
Now im confused,.. after being in system and returning to twrp format data fails, but it seems when you fail it and then reboot recovery then it works...
So boot recovery, reboot recovery -> format data wont work BUT
boot recovery, format data fails, reboot recovery, format data will work WTF
So i guess either do factory reset instead of formatting data (thats also fine, or not?) or use fastboot erase userdata after flashing twrp in bootloader (i mean i do this while flashing oreo,.. so i dont really get why i have to do that again but i also dont really get why i have to format data a all)
Good night guys, thank you for your help,.. ill continue tomorrow.
G5-User7080 said:
Had to correct that!
So in general after booting system, formatting data fails, maybe it works with fastboot erase userdata (didnt test it, cause i dont want to reflash Oreo again, i wanna go to bed.
But just rebooting recovery after booting first time in twrp works, so after that format data works. Works not..
Now im confused,.. after being in system and returning to twrp format data fails, but it seems when you fail it and then reboot recovery then it works...
So boot recovery, reboot recovery -> format data wont work BUT
boot recovery, format data fails, reboot recovery, format data will work WTF
So i guess either do factory reset instead of formatting data (thats also fine, or not?) or use fastboot erase userdata after flashing twrp in bootloader (i mean i do this while flashing oreo,.. so i dont really get why i have to do that again but i also dont really get why i have to format data a all)
Good night guys, thank you for your help,.. ill continue tomorrow.
Click to expand...
Click to collapse
Latest official TWRP recovery is 3.2.3.1 for potter:
https://eu.dl.twrp.me/potter/
It has the ability to backup EFS and persist (see attached screenshot). I would make a backup just to be on the safe side.
To prevent the device from encrypting again the trick is to flash magisk after formatting data and before rebooting, it deactivates the "force encryption" flag (unless you tick the "keep force encryption" box in magisk manager).
Also I hadn't any problems to make TWRP stick.
Edit: A factory reset won't reformat data.
If you want your data partition decrypted or not depends on your needs. Encrypted is safe but you're not able to access it to make any changes unless you decrypt it again....
Wolfcity said:
Latest official TWRP recovery is 3.2.3.1 for potter:
https://eu.dl.twrp.me/potter/
It has the ability to backup EFS and persist (see attached screenshot). I would make a backup just to be on the safe side.
To prevent the device from encrypting again the trick is to flash magisk after formatting data and before rebooting, it deactivates the "force encryption" flag (unless you tick the "keep force encryption" box).
Also I hadn't any problems to make TWRP stick.
Edit: A factory reset won't reformat data.
If you want your data partition decrypted or not depends on your needs. Encrypted is safe but you're not able to access it to backup data or make any changes unless you decrypt it again....
Click to expand...
Click to collapse
I have the G5 not plus, theres no 3.2.3.1 yet. (Aber lustig, dass du auch aus deutschland bist (denk ich mal) ).
Ahh so i have to flash magisk right after decrypting by formatting data? But i cant successfully format data when i come from system as i wrote earlier so the question is if it works when i fastboot erase userdata to decrypt data and if data doesnt get reencrypted when i boot then twrp.
I guess if the force encryption reencrypts when i boot recovery, too it wont work, then i guess the only way is to enter recovery, do a failed attempt, reboot recovery, and successfully format data.
Edit:
It deactivates the "force encryption" flag (unless you tick the "keep force encryption" box).
Click to expand...
Click to collapse
Also after installing magisk and booting system it still says encrypted in settigns so i thought its not removing the force encrypt. And i dont have found that switch yet..
Wolfcity said:
To prevent the device from encrypting again the trick is to flash magisk after formatting data and before rebooting, it deactivates the "force encryption" flag (unless you tick the "keep force encryption" box in magisk manager).
Click to expand...
Click to collapse
Hi,
If i already have the phone encrypted and rooted with magisk, "keep force encryption" is tick, if I will untick the option will booting decrypted?
G5-User7080 said:
I have the G5 not plus, theres no 3.2.3.1 yet. (Aber lustig, dass du auch aus deutschland bist (denk ich mal) ).
Ahh so i have to flash magisk right after decrypting by formatting data? But i cant successfully format data when i come from system as i wrote earlier so the question is if it works when i fastboot erase userdata to decrypt data and if data doesnt get reencrypted when i boot then twrp.
I guess if the force encryption reencrypts when i boot recovery, too it wont work, then i guess the only way is to enter recovery, do a failed attempt, reboot recovery, and successfully format data.
Edit:
Also after installing magisk and booting system it still says encrypted in settigns so i thought its not removing the force encrypt. And i dont have found that switch yet..
Click to expand...
Click to collapse
Ah ok, I thought your device is a potter.
The checkbox is found inside magisk manager but it is unticked by default so the device should decrypt.
Have you tried the official twrp instead of the 64bit unofficial version?
Maybe try magisk 17.2 too as I did.
And yes, I'm from good old Germany too.
woozie.2007 said:
Hi,
If i already have the phone encrypted and rooted with magisk, "keep force encryption" is tick, if I will untick the option will booting decrypted?
Click to expand...
Click to collapse
I think you will have to decrypt data by formatting it, unticking the checkbox just prevents the device from encrypting itself again. You should find some additional informations:
https://www.didgeridoohan.com/magisk/MagiskInstallationIssues

Categories

Resources