Related
I have been trying to flash oxygen os open beta 9 on my oneplus 3
first i tried the official steps mentioned on the oneplus site
I flashed stock oxygen os recovery
but when i boot into recovery mode it asks for a pattern which upon entering does not decrypt
I then flashed official TWRP and tried to flash the full open beta .zip file but it shows this package is for oneplus 3 this is a ""
also if i try to flash the modified TWRP 28 then also it cannot decrypt the phone
I would prefer not to format the phone if at all possible
aaditya98 said:
I have been trying to flash oxygen os open beta 9 on my oneplus 3
first i tried the official steps mentioned on the oneplus site
I flashed stock oxygen os recovery
but when i boot into recovery mode it asks for a pattern which upon entering does not decrypt
I then flashed official TWRP and tried to flash the full open beta .zip file but it shows this package is for oneplus 3 this is a ""
also if i try to flash the modified TWRP 28 then also it cannot decrypt the phone
Click to expand...
Click to collapse
Hi, I think you should try to format data. Probabby via fastboot, then install TWRP.
Not sure which are the correct commands for the full format, so have a look around or someone else will help.
Otherwise there is the unbrick guide here in the forums to try.
I'm having a similar issue. So any advice would be great. Just updated to most recent unofficial TWRP (having been on a previous version). Now when entering my pin to decrypt it is not accepted. Would prefer not to have to format data.
aaditya98 said:
I have been trying to flash oxygen os open beta 9 on my oneplus 3
first i tried the official steps mentioned on the oneplus site
I flashed stock oxygen os recovery
but when i boot into recovery mode it asks for a pattern which upon entering does not decrypt
I then flashed official TWRP and tried to flash the full open beta .zip file but it shows this package is for oneplus 3 this is a ""
also if i try to flash the modified TWRP 28 then also it cannot decrypt the phone
I would prefer not to format the phone if at all possible
Click to expand...
Click to collapse
unfortunately no choice other than wiping everything.....
antisoma said:
I'm having a similar issue. So any advice would be great. Just updated to most recent unofficial TWRP (having been on a previous version). Now when entering my pin to decrypt it is not accepted. Would prefer not to have to format data.
Click to expand...
Click to collapse
I believe the decrypt is a known issue with TWRP and OB8/OB9 with F2FS /data partition. I don't think there's a work around at this time without formatting /data and rooting to prevent encryption.
Hw4ng3r said:
I believe the decrypt is a known issue with TWRP and OB8/OB9 with F2FS /data partition. I don't think there's a work around at this time without formatting /data and rooting to prevent encryption.
Click to expand...
Click to collapse
So do you think there would be workaround in future?
0xelectron said:
So do you think there would be workaround in future?
Click to expand...
Click to collapse
Hopefully there will be, but it doesn't look promising right now. @eng.stk is the one that was modding the TWRP, but has since stopped doing TWRP dev.
kipue said:
Hi, I think you should try to format data. Probabby via fastboot, then install TWRP.
Not sure which are the correct commands for the full format, so have a look around or someone else will help.
Otherwise there is the unbrick guide here in the forums to try.
Click to expand...
Click to collapse
But I'm on official 3.2.8 with ext4 partition
Do you guy know where to get the stock recovery for openbeta 9? I downloaded somewhere a file recovery_OBT8N.img, but it still shows dm-verity issue.
nqk said:
Do you guy know where to get the stock recovery for openbeta 9? I downloaded somewhere a file recovery_OBT8N.img, but it still shows dm-verity issue.
Click to expand...
Click to collapse
Fastboot Format system and data
Then fastboot flash stockrecovery
Then boot to system
Sideload rom
Then fastboot boot twrp28
Then wipe data and install superuser in one go
candiesdoodle said:
Fastboot Format system and data
Click to expand...
Click to collapse
you mean: fastboot erase userdata?
Btw, I just ignore the dm-verity message to enter stock recovery, and do adb sideload openbeta9.zip and when it boots up again, the dm-verity message is no longer there.
I would try to format (erase userdata) data and flash the modded twrp.
nqk said:
you mean: fastboot erase userdata?
Btw, I just ignore the dm-verity message to enter stock recovery, and do adb sideload openbeta9.zip and when it boots up again, the dm-verity message is no longer there.
I would try to format (erase userdata) data and flash the modded twrp.
Click to expand...
Click to collapse
Yeah fastboot Format userdata
But since you don't have the dm-verity you can skip the fastboot Format. Boot into the modd twrp and when it asks for password, hit cancel and then format data (you will have to type 'yes').
Then flash SuperSU or superuser in the same session without booting. This will ensure dm-verity doesn't come up again as it will start in enforcing mode, thanks to SuperSU/superuser.
You may be able to flash twrp afterwards but I haven't tried it.
I'm currently running my OP3 on Resurrection Remix 5.7.4 (MM 6.01), the phone has the latest version of TWRP and I've flashed other ROMs in the past without any issue
RR has proven to be quite unstable for me, the system UI keeps crashing, which renders the phone unusable until after a reboot so I wanted to flash Freedom OS as that worked quite well for me previously. When I tried to flash the ROM in TWRP the ROM seemed to flash successfully but when I rebooted, only the boot logo showed and then the screen went black and the phone refused to respond at all for about two hours, after that exactly the same thing happened. I managed to boot into recovery and tried flashing a different ROM but the result was the same every time, the only way to get the phone to work normally was to flash RR again/restore from a Nandroid backup, either way, the result is the same, I'm stuck on an unstable ROM and I don't know why, the last time I flashed these ROMs they worked fine, I followed all of the instructions for flashing said ROMs to the letter, I have the latest version of TWRP, etc.
Also it seems TWRP can't mount /system, in TWRP under "mount", system is unchecked, I checked it and tried again but found that whenever I rebooted the phone or attempted to flash a new ROM, it would always uncheck itself and flashing the ROM would fail, however strangely flashing the same version of RR was always successful. Is this why the flashing keeps failing and does anyone know what the problem could be?
Thanks!
bronderb said:
Go into your bootloader and format system, cache, and userdata (This will wipe EVERYTHING so be sure to backup). Then latest official flash stock rom and reboot. This should fix it. If this helped hit thanks!
Click to expand...
Click to collapse
Bootloader? There is no option in the bootloader to delete everything as far as I can see, do you mean in recovery? And if I wipe everything off the phone, how do I get the stock ROM onto the phone to flash it? When you say wipe userdata do you mean wipe internal storage or am I misunderstanding and you're telling me to wipe the usual dalvik, cache and data as you would for a normal clean flash?
bronderb said:
No, go into fastboot and plug into pc. Open cmd and type "fastboot format userdata" "fastboot format cache" "fastboot format system"
Click to expand...
Click to collapse
Okay, thanks, and then what? Do I flash TWRP then push the stock ROM to the phone and flash that? And exactly how do I do that?
bronderb said:
You just go into twrp (no need to reflash) then adb sideload oxygen os
Click to expand...
Click to collapse
Thank you, I am now running OOS, hopefully everything else will go smoothly now, planning to go back to FOS again
I didn't even have to use the fastboot commands to format, just sideloading the OOS file wiped everything anyway
Turns out the issue isn't actually fixed, "system" still appears unchecked in TWRP. Could the fact that I didn't actually format everything first have made a difference, given everything was wiped in the process anyway?
Looks like I'm going to be living the sideloading life...
Edit: Sideloading freedom OS failed, ended up having to restore from my TWRP backup. I don't know what I'm going to do, my main reason for using custom ROMs is installing a black theme, and OOS doesn't support Layers or Substratum fully so I can't stay on that
Is the thing that says "mount system as read-only" enabled in the mounts menu? /System isn't ever mounted when TWRP starts, you have to manually mount it, but as long as the updater-script tells /system to mount, it will. However, if that option to make it read-only is enabled, then nothing will ever write to /system. Last resort is deleting the .twrps file from /sdcard/TWRP folder to remove current TWRP preferences and then when you boot into TWRP, that first screen has the swiper to allow modifications, and you'll swipe that
frickinjerms said:
Is the thing that says "mount system as read-only" enabled in the mounts menu? /System isn't ever mounted when TWRP starts, you have to manually mount it, but as long as the updater-script tells /system to mount, it will. However, if that option to make it read-only is enabled, then nothing will ever write to /system. Last resort is deleting the .twrps file from /sdcard/TWRP folder to remove current TWRP preferences and then when you boot into TWRP, that first screen has the swiper to allow modifications, and you'll swipe that
Click to expand...
Click to collapse
It isn't set to read only, I have tried updating and resetting TWRP but nothing has helped, in fact it's got worse, I managed to sideload OOS but my attempted install of FOS failed so I tried to restore from a backup and that also failed, something which didn't happen back when I was on RR.
evilkitty69 said:
It isn't set to read only, I have tried updating and resetting TWRP but nothing has helped, in fact it's got worse, I managed to sideload OOS but my attempted install of FOS failed so I tried to restore from a backup and that also failed, something which didn't happen back when I was on RR.
Click to expand...
Click to collapse
Which version of TWRP are you running? The official 3.1.0-0 is good for OOS and OOS based ROMs only. Try eng.stk's version.
Use the latest eng-stk twrp.
https://forum.xda-developers.com/devdb/project/?id=15934#downloads
In recovery go to Wipe > Format data (this will wipe ALL in youre phone).
It's youre Data in F2FS? If yes you must change it to ext4, in recovery Wipe > Change file system. Reboot recovery. Check if it's changed.
Reboot to Bootloader (Fastboot). From PC reflash recovery.
Now copy Oos rom to the phone memory. Flash rom. Reflash recovery (the rom will overwrite the recovery). Reboot to recovery to see if it works. If not do it again.
I sugest to NOT restore old data. This way you'll have all new in youre phone.
tnsmani said:
Which version of TWRP are you running? The official 3.1.0-0 is good for OOS and OOS based ROMs only. Try eng.stk's version.
Click to expand...
Click to collapse
I was running 3.0.2-2 when the issue started, I updated to 3.0.3 and 3.1.0-0 but nothing changed. Thanks for the suggestion, I will give it a try
null0seven said:
Use the latest eng-stk twrp.
https://forum.xda-developers.com/devdb/project/?id=15934#downloads
In recovery go to Wipe > Format data (this will wipe ALL in youre phone).
It's youre Data in F2FS? If yes you must change it to ext4, in recovery Wipe > Change file system. Reboot recovery. Check if it's changed.
Reboot to Bootloader (Fastboot). From PC reflash recovery.
Now copy Oos rom to the phone memory. Flash rom. Reflash recovery (the rom will overwrite the recovery). Reboot to recovery to see if it works. If not do it again.
I sugest to NOT restore old data. This way you'll have all new in youre phone.
Click to expand...
Click to collapse
Help! I attempted to do this and the process failed, I didn't manage to wipe data because "/data could not be mounted as device or resource is busy"
Edit: Device now has nothing but TWRP and fastboot, no OS, no ADB, no data, no internal storage
If you can reflash twrp from PC. If not reflash recovery from twrp recovery : Instal > Image > Select Recovery (you must have TWRP.img in youre phone memory )
I managed to get hold of a few factory images and attempted to flash system.img through fastboot, resulting error was
"target reported max download size of 536,870,912 bytes" (system image is 3080 MB)
"invalid sparse file format at header magi"
null0seven said:
If you can reflash twrp from PC. If not reflash recovery from twrp recovery : Instal > Image > Select Recovery (you must have TWRP.img in youre phone memory )
Click to expand...
Click to collapse
I reflashed the modified TWRP successfully. The second suggestion wouldn't have worked, given my phone has no internal storage
You can't see internal storage because of the recovery does not work write.
If you have a working recovery you can do all you want.
null0seven said:
You can't see internal storage because of the recovery does not work write.
If you have a working recovery you can do all you want.
Click to expand...
Click to collapse
The recovery was working at this point, the issue turned out to be the data partition, system was formatted to ext4 but I didn't realise data was in f2fs which caused the problem in the first place. I formatted to ext4 and everything worked, I was able to install paranoid android and everything worked...
...until I flashed the wrong firmware and now I've hard bricked it! I'm going to try the hard brick toolkit
Edit: After 12 hours of being an unresponsive brick, the phone suddenly booted, system doesn't work but it has recovery. Unfortunately I seem to be back to square one, if I try to flash something it appears to succeed but then the phone doesn't boot up into system
So I am now back to the original issue of system not mounting, in terminal if I type "mount /system" I get following error:
"mounting /dev/block/sde20 on /system failed: Device or resource is busy"
Anyone know how to solve this?
I formatted everything, reflashed recovery and tried to flash OOS, got following error:
Code:
[FONT="Courier New"]"This package is for OnePlus3 devices, this is a oneplus3t" (it isn't)
"Updater process ended with ERROR: 7
Error installing zip file /sdcard/OOS3.2.6.zip" [/FONT]
Issue was "solved" by flashing PA, GApps and the correct firmware
Hopefully that's the end of all this drama, thanks to everyone for their suggestions
Hi, I'm pretty new at rooting and I seem to have a similar error. I'm getting the "can't mount /system" error in TWRP. I am able to boot into OOS 4.1.3 and run the nandroid backup but, I keep getting the same error and am unable to select "system" when choosing the mount option in TWRP.
Do I need to have all partitions in f2fs? My system partition is in ext4. Is this what solved your issue?
It seems my phone is functional even with the error active but, I've been trying to get systemless SuperSU and MagiskHide working and I think that's what is preventing me from doing so.
I recently unlocked my bootloader after waiting for 1440 hours. I am/was currently on MIUI 10.0.1.0 but wanted to install a custom rom like lineage 15.1. I installed Red Wolf TWRP and then tried to install the rom. I went to Advanced Wipe section of the recovery and checked Dalvik, Cache, Data and System but not Vendor and Internal Storage. It wiped those partitions without any error. But after that i tried to install the rom but halfway through install it ended with "Update Process Ended with Error 7" and a line saying "Failed to Mount /system (Invalid Argument)" and changed the system partition size to zero. I had to repair it and flash MIUI back using fastboot.
I did this same process over and over with different recoveries ( RED WOLF, ORANGE WOLF and even official TWRP) and different builds of lineage (rom zip was never corrupted) and even with ressurection remix but still failed and same thing happened again and again. Am I doing something wrong in the process? I didn't flash lazyflasher as I read in multiple threads that it is not necessary if flashing a custom rom. Please guide?
I hope it works for my English.
1- mount > select all > restart recovery
2- full wipe > install rom and gapps > format data
prospektus said:
I hope it works for my English.
1- mount > select all > restart recovery
2- full wipe > install rom and gapps > format data
Click to expand...
Click to collapse
Thanks for replying. You said full wipe. Should I include vendor as well or just regular (Dalvik, Cache, Data and System)?
thrustaxehandle said:
Thanks for replying. You said full wipe. Should I include vendor as well or just regular (Dalvik, Cache, Data and System)?
Click to expand...
Click to collapse
yes.. delete internal memory. rom board. format data.
thrustaxehandle said:
I recently unlocked my bootloader after waiting for 1440 hours. I am/was currently on MIUI 10.0.1.0 but wanted to install a custom rom like lineage 15.1. I installed Red Wolf TWRP and then tried to install the rom. I went to Advanced Wipe section of the recovery and checked Dalvik, Cache, Data and System but not Vendor and Internal Storage. It wiped those partitions without any error. But after that i tried to install the rom but halfway through install it ended with "Update Process Ended with Error 7" and a line saying "Failed to Mount /system (Invalid Argument)" and changed the system partition size to zero. I had to repair it and flash MIUI back using fastboot.
I did this same process over and over with different recoveries ( RED WOLF, ORANGE WOLF and even official TWRP) and different builds of lineage (rom zip was never corrupted) and even with ressurection remix but still failed and same thing happened again and again. Am I doing something wrong in the process? I didn't flash lazyflasher as I read in multiple threads that it is not necessary if flashing a custom rom. Please guide?
Click to expand...
Click to collapse
You need to upgrade to a higher version for twrp. 3.2.2
prospektus said:
yes.. delete internal memory. rom board. format data.
Click to expand...
Click to collapse
OK. I will try your method and will report back.
Update: I tried your method but still failed. Any other solution will be appreciated.
esiv129 said:
You need to upgrade to a higher version for twrp. 3.2.2
Click to expand...
Click to collapse
I'm already using TWRP version 3.2.3
thrustaxehandle said:
OK. I will try your method and will report back.
Update: I tried your method but still failed. Any other solution will be appreciated.
I'm already using TWRP version 3.2.3
Click to expand...
Click to collapse
try again unlock
prospektus said:
try again unlock
Click to expand...
Click to collapse
I again tried the process as follows:
Flashed MIUI 9.6.4.0 with MiFlash using clean and lock option.
Then I unlocked it again using miunlock.
Then I flashed RedWolf v28 beta recovery by booting it and flashing it from inside recovery.
This time I flashed lazyflasher and checked options disable dm-verity and force encrypt in recovery and installed magisk. It did it perfectly.
Then I went to Advanced Wipe Section of Wipe tab and checked all the option required like cache, dalvik, data, system and even vendor. It wiped it without any problems like always.
But here the same problem starts to arise: when I again tried to install lineage 15.1 (downloaded latest build this time too) it starts but after halfway through it says Updater process ended with Error 7
Cannot install sdcard/lineage-build date and version
and Unable to mount /system (invalid argument)
When i restart recovery system partition size changes to zero and I have to repair it by changing the file system option.
Currently now I'm on MIUI 9.6.4.0 with RedWolf recovery (options disable dm-verity and force encrypt are enabled) and lazyflasher and Magisk installed. I can use my phone when I flash MIUI 9 or 10 using but it not letting me to install any custom rom. I'm really frustrated.
thrustaxehandle said:
I again tried the process as follows:
Flashed MIUI 9.6.4.0 with MiFlash using clean and lock option.
Then I unlocked it again using miunlock.
Then I flashed RedWolf v28 beta recovery by booting it and flashing it from inside recovery.
This time I flashed lazyflasher and checked options disable dm-verity and force encrypt in recovery and installed magisk. It did it perfectly.
Then I went to Advanced Wipe Section of Wipe tab and checked all the option required like cache, dalvik, data, system and even vendor. It wiped it without any problems like always.
But here the same problem starts to arise: when I again tried to install lineage 15.1 (downloaded latest build this time too) it starts but after halfway through it says Updater process ended with Error 7
Cannot install sdcard/lineage-build date and version
and Unable to mount /system (invalid argument)
When i restart recovery system partition size changes to zero and I have to repair it by changing the file system option.
Currently now I'm on MIUI 9.6.4.0 with RedWolf recovery (options disable dm-verity and force encrypt are enabled) and lazyflasher and Magisk installed. I can use my phone when I flash MIUI 9 or 10 using but it not letting me to install any custom rom. I'm really frustrated.
Click to expand...
Click to collapse
When you get the mount error, come to the home page and get to the mount. speak enable all options enable all options. speak restart recovery restart recovery. make format data
Not sure if the link is forbidden? I can't tell you sorry. https://www.youtube.com/watch?v=dzrWkjOfndA&t=501s
I have read replies and everyone is sharing his bit of suggestions, here are mine
1. boot redwolf as FASTBOOT BOOT recovery.img - (if you arent already)
2. change file type of /data partition to-from (xFat to ext4) and wipe all partitions (internal storage can be skipped)
3. instead of linage15.1 same package, try downloading some other custom rom, i recomend DotOS2.5 or Crdroid4.6.2
4. uncheck enforce md5 bla bla while flashing zip.
i hope you will succeed
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
I'm facing some permissions problems and thus being unable to install Paranoid Android Q5. I was using MIUI 12 (Xiaomi.EU).
The steps I took to change the ROM:
Formated data (errors started right away) then I did the usual wipes (cache, dalvik, data)
Whenever I try to wipe or format data I get error messages like: Error opening /data/XXX (Operation not permitted).
System is always mounted read-only no matter what I try and after I install any ROM many of these error messages pop up.
Orange Fox gives some error about key.
Flashing of the ROM suceeds, but system cannot boot, loading screen forever.
Can anyone point me some directions?
Thanks in advance and sorry about any possible bad grammar.
[ ]s
;-)
Mount system, vendor and data manually and then try. If fails then try with pitchblack recovery.
Pavello said:
Mount system, vendor and data manually and then try. If fails then try with pitchblack recovery.
Click to expand...
Click to collapse
Well , i have the same problem..and used pitch black also
Any update on this?
I still had those problems. I don't know if it is a problem with the TWRP or something similar. Is there any progress to solve this problem? I wanted to try the pixel experience betas with Android 11 but because of this problem with the TWRP I have not succeeded (in case I have Android 10 under MIUI 12.0.3 and RN8 Ginkgo model and obviously unlocked bootloader)
jordyx20 said:
I still had those problems. I don't know if it is a problem with the TWRP or something similar. Is there any progress to solve this problem? I wanted to try the pixel experience betas with Android 11 but because of this problem with the TWRP I have not succeeded (in case I have Android 10 under MIUI 12.0.3 and RN8 Ginkgo model and obviously unlocked bootloader)
Click to expand...
Click to collapse
i gusse thats a problem in miui12.0.3
i was using pixel experience 10 then i flash miui 12.0.3 in fastboot when i tryd to flash orange fox i had the same problem
so i gusse u can downgred to miui 11 and flash twrp and it will work
I solved this by downgrading to 12.0.1
jordyx20 said:
I still had those problems. I don't know if it is a problem with the TWRP or something similar. Is there any progress to solve this problem? I wanted to try the pixel experience betas with Android 11 but because of this problem with the TWRP I have not succeeded (in case I have Android 10 under MIUI 12.0.3 and RN8 Ginkgo model and obviously unlocked bootloader)
Click to expand...
Click to collapse
Format data ..(backup first if u need ) .. the boot to recovery again ... Should decrypt the data ... Worked for me ...
I am having this exact problem.
Under internal storage (sdcard) I see a bunch of hashed folders I cannot open.
Format data returns a multitude of "Error opening '/data/somefolder/asdf/asdf' (Operation not permitted) and marks the wipe as Failed. The attempted formatting also mentions "E:Error making /sdcard/Fox directory: Required key not available." "Failed to unmount '/data' (Device or resource busy)
I can wipe anything except Data. I also tried downgrading to 12.0.1 firmware but it does not fix it for me.
The ROM can be booted into, and magisk managed to be installed, but no google apps were installed.
Dibbo Sarker said:
Format data ..(backup first if u need ) .. the boot to recovery again ... Should decrypt the data ... Worked for me ...
Click to expand...
Click to collapse
I tried this, but no luck on my side.
Recovery download link on description. Only for Note 8/8T.
I flashed it with fastboot and works fine!
A problem like this was the one I had since TWRP had the device encrypted but it did not inform me and it did not give me any sign that I had to write a password (password that I have no idea what it is).
What I did so that it did not give me an error was to install Orangefox and while there delete everything and install a file of these that I got from google.
I had to try one by one and restart to see if it asked me for a password in orangefox, luckily one worked and it no longer asked me to decrypt the files and I could install the rom and gapps normally
jonatasgabriel76 said:
Recovery download link on description. Only for Note 8/8T.
I flashed it with fastboot and works fine!
Click to expand...
Click to collapse
Thank youuuuuuuu! You have rescued my phone!
jonatasgabriel76 said:
Recovery download link on description. Only for Note 8/8T.
I flashed it with fastboot and works fine!
Click to expand...
Click to collapse
THANK YOU!
Why is my orange fox is not showing Vendor, System Etc ? How can i fix this ? I really need to wipe those as well..
Jona'san - sama said:
Why is my orange fox is not showing Vendor, System Etc ? I really need to wipe those as well..
Click to expand...
Click to collapse
if you need to do something to system or vendor go to ofox menu/mount and choose what partition to mount
Jona'san - sama said:
I really need to wipe those as well..
Click to expand...
Click to collapse
if you want to flash a rom = yes
loopypalm said:
if you need to do something to system or vendor go to ofox menu/mount and choose what partition to mount
if you want to flash a rom = yes
Click to expand...
Click to collapse
Can't wipe it still, I already try the Mount > ✓ Vendor ✓ System.. but in formatting it say's "Cant Mount the....blah..blah.."
I try to uncheck the "Mount System vendor, system as read-only" from the settings of mount.. but for some reason, if you go back to Mount options again, you can't check the system, vendor now
loopypalm said:
if you need to do something to system or vendor go to ofox menu/mount and choose what partition to mount
if you want to flash a rom = yes
Click to expand...
Click to collapse
Yes, I need it to flash a ROM
try this it worked
Had the same issue.
1. I installed twrp via ADB
2. Restarted to recovery mode into twrp
3. Installed the latest OrangeFox and restarted into recovery again.
4. It asked me for a password which is the pin I set then proceeded to format data.
5. After formatting data I restarted again to recovery.
Then I was able to install custom roms.
I am using derpfest Android 12 on my Poco x3 pro. I want to install magisk.zip through orange fox recovery installed on my phone. But I am not getting storage data on recovery, only a fox folder is there. Can somebody tell me is it a glitch or any Android 12 restrictions or something.