Related
Update: The latest TWRP is already capable of decrypting data. This method is now unnecessary and depreciated. Use factory reset in TWRP menu instead
Disclaimer: This mod will wipe your data. I am not responsible for data loss after using this mod.
I tested on my device several times, it's working for me so internal storage is always preserved, but I cannot guarantee if anything is messed up on your side. Please read the post carefully before using this mod!
Always backup your important data before modifying your phone's software!
To compensate the mistake I have done in the modified SuperSU script (I fixed it eventually though ), I decided to release a mod I consider quite useful for most people.
I've used the 10 for quite some time, and I've been messing with it from day 1.
Since the encryption is required for the phone to have proper radio signal (more info here), we are forced to keep our devices encrypted.
And because HTC uses proprietary encryption method, TWRP is unable to decrypt our data partition, which causes the recovery unable to read anything from data.
This is actually quite a big problem. If you want to full wipe and clean flash your favorite custom rom, the "Factory Reset" option in TWRP is not available, so you are forced to wipe the whole data partition, which will cause all your personal files stored in internal storage to be removed.
If you're a flashaholic like I am, you are forced not to store anything important in the phone storage because it will be wiped every time trying to clean flash a rom.
To breakthrough this inconvenience, I created this flashable zip to accomplish something similar to the "Factory Reset" option in TWRP.
Requirement: You have to use the systemless root of SuperSU to use this mod. If you want to flash the wipe script with SuperSU, flash SuperSU first, then flash the wipe script.
Important: If you have chosen "Require PIN/password/pattern to start device" in the "Secure startup" page during the initial setup, you CANNOT use this mod!
If you have to enter your PIN/password/pattern before your device booted up, this means that you have secure startup enabled. You CANNOT use this mod!
If secure startup is enabled and you flash this zip, your encryption will be messed up and you will have to format the whole data partition eventually to make your phone working again.
After flashing the mod, your data will not be wiped immediately in recovery because we cannot do so. It will wipe the data AFTER you rebooted back to system. It will reboot again after the wipe is done. If you flashed SuperSU at the same time with this mod, you will experience 2 consecutive reboot loops. This is normal behavior, don't panic.
If devs are interested in including this zip into your rom, you can use it in the same way as SuperSU:
Code:
package_extract_dir("wipe", "/tmp/wipe");
run_program("/sbin/busybox", "unzip", "/tmp/wipe/wipe.zip", "META-INF/com/google/android/*", "-d", "/tmp/wipe");
run_program("/sbin/busybox", "sh", "/tmp/wipe/META-INF/com/google/android/update-binary", "dummy", "1", "/tmp/wipe/wipe.zip");
For those who are interested in what this zip actually do, here is a brief explanation:
If secure startup is disabled, data will be decrypted as soon as the device booted up. We can only access data after it is decrypted. So our only choice is to wipe data after the device has booted up.
I created a script to wipe all data except SuperSU app, su binary image, and your internal storage.
SuperSU will automatically run scripts inside the directory /su/su.d, so after putting the script into the folder, SuperSU will the wipe script at boot time.
The problem is: su.img is also located in /data, how can we push files into the image? Fortunately, our master Chainfire has thought of this problem. The image /cache/su.img will be merged with /data/su.img during boot. So I just need to place the script into /cache/su.img, then Chainfire's script will do all the rest of the work automatically. If you're interested in the merging process, take a look at launch_daemonsu.sh in the ramdisk of a SuperSU modified boot for more details.
Is this helpful in regards to initial routing and flashing a rom or only afterwards to flash a new one?
topjohnwu said:
Disclaimer: This mod will wipe your data. I am not responsible for data loss after using this mod.
I tested on my device several times, it's working for me so internal storage is always preserved, but I cannot guarantee if anything is messed up on your side. Please read the post carefully before using this mod!
Always backup your important data before modifying your phone's software!
To compensate the mistake I have done in the modified SuperSU script (I fixed it eventually though ), I decided to release a mod I consider quite useful for most people.
I've used the 10 for quite some time, and I've been messing with it from day 1.
Since the encryption is required for the phone to have proper radio signal (more info here), we are forced to keep our devices encrypted.
And because HTC uses proprietary encryption method, TWRP is unable to decrypt our data partition, which causes the recovery unable to read anything from data.
This is actually quite a big problem. If you want to full wipe and clean flash your favorite custom rom, the "Factory Reset" option in TWRP is not available, so you are forced to wipe the whole data partition, which will cause all your personal files stored in internal storage to be removed.
If you're a flashaholic like I am, you are forced not to store anything important in the phone storage because it will be wiped every time trying to clean flash a rom.
To breakthrough this inconvenience, I created this flashable zip to accomplish something similar to the "Factory Reset" option in TWRP.
Requirement: You have to use the systemless root of SuperSU to use this mod. If you want to flash the wipe script with SuperSU, flash SuperSU first, then flash the wipe script.
Important: If you have chosen "Require PIN/password/pattern to start device" in the "Secure startup" page during the initial setup, you CANNOT use this mod!
If you have to enter your PIN/password/pattern before your device booted up, this means that you have secure startup enabled. You CANNOT use this mod!
If secure startup is enabled and you flash this zip, your encryption will be messed up and you will have to format the whole data partition eventually to make your phone working again.
After flashing the mod, your data will not be wiped immediately in recovery because we cannot do so. It will wipe the data AFTER you rebooted back to system. It will reboot again after the wipe is done. If you flashed SuperSU at the same time with this mod, you will experience 2 consecutive reboot loops. This is normal behavior, don't panic.
If devs are interested in including this zip into your rom, you can use it in the same way as SuperSU:
Code:
package_extract_dir("wipe", "/tmp/wipe");
run_program("/sbin/busybox", "unzip", "/tmp/wipe/wipe.zip", "META-INF/com/google/android/*", "-d", "/tmp/wipe");
run_program("/sbin/busybox", "sh", "/tmp/wipe/META-INF/com/google/android/update-binary", "dummy", "1", "/tmp/wipe/wipe.zip");
For those who are interested in what this zip actually do, here is a brief explanation:
If secure startup is disabled, data will be decrypted as soon as the device booted up. We can only access data after it is decrypted. So our only choice is to wipe data after the device has booted up.
I created a script to wipe all data except SuperSU app, su binary image, and your internal storage.
SuperSU will automatically run scripts inside the directory /su/su.d, so after putting the script into the folder, SuperSU will the wipe script at boot time.
The problem is: su.img is also located in /data, how can we push files into the image? Fortunately, our master Chainfire has thought of this problem. The image /cache/su.img will be merged with /data/su.img during boot. So I just need to place the script into /cache/su.img, then Chainfire's script will do all the rest of the work automatically. If you're interested in the merging process, take a look at launch_daemonsu.sh in the ramdisk of a SuperSU modified boot for more details.
Click to expand...
Click to collapse
Is the systemless one the one you patched?
Sent from my LG-H830 using XDA-Developers mobile app
stonew5082 said:
Is this helpful in regards to initial routing and flashing a rom or only afterwards to flash a new one?
Click to expand...
Click to collapse
It functions the same as "Factory Reset" in TWRP, which means it will wipe all data, but your personal files stored in internal storage will remain on the device.
StickyEyez said:
Is the systemless one the one you patched?
Sent from my LG-H830 using XDA-Developers mobile app
Click to expand...
Click to collapse
Actually you can use the original version. But I suggest you to use my patched one, in case you accidentally wiped your whole data partition (this mod will not do this), you will stay encrypted, and your data signal will be fine
Hi topjohnwu
@ jollywhitefoot suggested you might be able to help to wipe userdata from download mode.
My phone will not get passed message "Your phones is encrypted" "TO DECRYPT YOUR PHONE. ENTER YOUR SCREEN LOCK PASSWORD" I had no screen lock password... i have different passwords to decrypt . Each time i put a password in it resest phone and does factory rest and then reboots straight into Bootloader again.
Phone has no recovery " Failed to boot into recovery mode" red writing on a black screen.
Phoned has OEM Relocked ....cant fastboot or unlock bootloader again
Please can you help
tailor999 said:
Hi topjohnwu
@ jollywhitefoot suggested you might be able to help to wipe userdata from download mode.
My phone will not get passed message "Your phones is encrypted" "TO DECRYPT YOUR PHONE. ENTER YOUR SCREEN LOCK PASSWORD" I had no screen lock password... i have different passwords to decrypt . Each time i put a password in it resest phone and does factory rest and then reboots straight into Bootloader again.
Phone has no recovery " Failed to boot into recovery mode" red writing on a black screen.
Phoned has OEM Relocked ....cant fastboot or unlock bootloader again
Please can you help
Click to expand...
Click to collapse
You can try to unlock your bootloader again.
If you cannot unlock it, then I regret to say that your phone might be doomed.
Never try to relock your phone if it's not in 100% stock condition and perfectly working.
topjohnwu said:
You can try to unlock your bootloader again.
If you cannot unlock it, then I regret to say that your phone might be doomed.
Never try to relock your phone if it's not in 100% stock condition and perfectly working.
Click to expand...
Click to collapse
I have tried unlocking boot loader again. The log shows oem needs to be unlocked.
When a RUU comes out, would that help recover the phone?
Sent from my ONE A2003 using XDA-Developers mobile app
tailor999 said:
Hi topjohnwu
@ jollywhitefoot suggested you might be able to help to wipe userdata from download mode.
My phone will not get passed message "Your phones is encrypted" "TO DECRYPT YOUR PHONE. ENTER YOUR SCREEN LOCK PASSWORD" I had no screen lock password... i have different passwords to decrypt . Each time i put a password in it resest phone and does factory rest and then reboots straight into Bootloader again.
Phone has no recovery " Failed to boot into recovery mode" red writing on a black screen.
Phoned has OEM Relocked ....cant fastboot or unlock bootloader again
Please can you help
Click to expand...
Click to collapse
Assuming you have a stock recovery image..
Boot to bootloader then recovery.
Long press power for a few seconds then tap volume up.
You can then factory reset in stock recovery
LeeDroid said:
Assuming you have a stock recovery image..
Boot to bootloader then recovery.
Long press power for a few seconds then tap volume up.
You can then factory reset in stock recovery
Click to expand...
Click to collapse
Oh dam it, just seen your post a bit late. Car phone warehouse has just collected my handset :silly: - im sure they'll send it back saying ive lost warranty :crying:
tailor999 said:
Oh dam it, just seen your post a bit late. Car phone warehouse has just collected my handset :silly: - im sure they'll send it back saying ive lost warranty :crying:
Click to expand...
Click to collapse
Oh dear....
topjohnwu said:
Requirement: You have to use the systemless root of SuperSU to use this mod. If you want to flash the wipe script with SuperSU, flash SuperSU first, then flash the wipe script.
Important: If you have chosen "Require PIN/password/pattern to start device" in the "Secure startup" page during the initial setup, you CANNOT use this mod!
If you have to enter your PIN/password/pattern before your device booted up, this means that you have secure startup enabled. You CANNOT use this mod!
If secure startup is enabled and you flash this zip, your encryption will be messed up and you will have to format the whole data partition eventually to make your phone working again.
Click to expand...
Click to collapse
the thing is i have selected no for secure boot but whenever i setup a fingerprint and boot then it gets enabled again even if i had disabled it...
any way around or am i missing on something.. currently on lee's rom
SacredDeviL666 said:
the thing is i have selected no for secure boot but whenever i setup a fingerprint and boot then it gets enabled again even if i had disabled it...
any way around or am i missing on something.. currently on lee's rom
Click to expand...
Click to collapse
you're talking about something different that he is. secure boot is a pin before you ever get the system loaded. you are talking about lockscreen pin/password, which, is mandatory if you use fingerprint scanner.
jollywhitefoot said:
you're talking about something different that he is. secure boot is a pin before you ever get the system loaded. you are talking about lockscreen pin/password, which, is mandatory if you use fingerprint scanner.
Click to expand...
Click to collapse
cool thank you...
I'm confused a bit. So every time I want to clean flash a rom, I can flash this script and it will wipe everything (system, data, cache etc.) except internal storage? Would dirty flashing a rom have any affect?
Ndaoud360 said:
I'm confused a bit. So every time I want to clean flash a rom, I can flash this script and it will wipe everything (system, data, cache etc.) except internal storage? Would dirty flashing a rom have any affect?
Click to expand...
Click to collapse
+1
Ndaoud360 said:
I'm confused a bit. So every time I want to clean flash a rom, I can flash this script and it will wipe everything (system, data, cache etc.) except internal storage? Would dirty flashing a rom have any affect?
Click to expand...
Click to collapse
It will only wipe data without internal storage.
You should flash this zip after you flash a rom.
It will wipe data after the device boots up.
topjohnwu said:
It will only wipe data without internal storage.
You should flash this zip after you flash a rom.
It will wipe data after the device boots up.
Click to expand...
Click to collapse
Ok so the process would be wipe system, cache, flash rom, flash data wipe script?
Ndaoud360 said:
Ok so the process would be wipe system, cache, flash rom, flash data wipe script?
Click to expand...
Click to collapse
Why would you wipe system this will be done by the rom installation, just flash the rom then flash the script & job done
LeeDroid said:
Why would you wipe system this will be done by the rom installation, just flash the rom then flash the script & job done
Click to expand...
Click to collapse
huh? Ever since I began rooting phones, I would wipe system, data and cache before a clean flash of a rom. I guess I never knew the rom does it for you. I thought the rom just over wrote the system possibly leaving remnants of the old system which could lead to issues which is why devs advise to full wipe when switching roms.
Ndaoud360 said:
huh? Ever since I began rooting phones, I would wipe system, data and cache before a clean flash of a rom. I guess I never knew the rom does it for you. I thought the rom just over wrote the system possibly leaving remnants of the old system which could lead to issues which is why devs advise to full wipe when switching roms.
Click to expand...
Click to collapse
Ah, a full wipe is only applicable to data buddy, if a rom dev doesn't wipe system before their installation, they need a good slap with a frozen kipper.
Cache is entirely optional
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.
Hello
After rooting my G3, I installed an AOSP-based custom rom via TWRP. Then later on, encrypted the phone (& sdcard).
Recently, decided to install a LG stock-based rom (Clean Rom 2.8), but can't get passed a white screen asking for a password at first boot. This appears to be something to do with encryption? (From what I recall, there's no password to set when encrypting the phone). I factory-wiped, and wiped via advanced options of TWRP before installing this rom, so thought the phone has been decrypted.
After reading around, I tried flashing the latest LineageOS rom, and it worked fine. Notably, the phone indicates it's still encrypted! though the sdcard isn't as I can access it outside of the phone. I read about this problem with some ROMs not being able to boot past a password/white screen, but CM/LineageOS not having this issue.
Anyhow, how do I fully decrypt the LG phone? I've read various advice, but confused (especially about bootloaders).
Any help appreciated.
I dont own the device right now (in the future i wil) but i think i can help u whit that.... (it happened me with other phones)
The thing is if you have encription in the phone the only way to dencrypt the device is format the data partition through twrp THIS WILL ERASE ALL OF YOUR FILES LIKE PHOTOS AND MUSIC PLEASE DO A BACKUP BEFORE TRYING THIS
Boot to twrp, press the wipe button, in the wipe screen you will see a button that say "Format data" (in the top corner above the switch saying "swipe to factory reset") then twrp ask you to type yes, you do it and this will format the data partition erasing the files and the encription....
For the sd is the same but you can do it from a computer if you want or other way
I hope that this can help u
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
The so far...
Installed TWRP
Noticed I could not boot into factory ROM - TWRP boot loop?
Tried to factory reset from TWRP - failed; Data could not be mounted.
Changed the file system of Data to extf2; Repaired Data; Changed Data back to extf4
Factory Reset - completed
Still could not enter factory ROM - TWRP boot loop?
ADB sideload PixelExperience Custom ROM - allowed TRP to push app; boots into ROM to initial setup (G with progress bar) but doesn't advance after 15 minutes
Vol down + power -> Menu > Recovery
TWRP asks for password to decrypt data (**Edit - this is TWRP's initial screen after Logo)
*Edit* at no point in the life of this device (I bought it brand new) was it ever encrypted
At no point did I ever set a password or try to encrypt data. How do I fix this?
OvrTehBottm said:
The so far...
Installed TWRP
Noticed I could not boot into factory ROM - TWRP boot loop?
Tried to factory reset from TWRP - failed; Data could not be mounted.
Changed the file system of Data to extf2; Repaired Data; Changed Data back to extf4
Factory Reset - completed
Still could not enter factory ROM - TWRP boot loop?
ADB sideload PixelExperience Custom ROM - allowed TRP to push app; boots into ROM to initial setup (G with progress bar) but doesn't advance after 15 minutes
Vol down + power -> Menu > Recovery
TWRP asks for password to decrypt data (**Edit - this is TWRP's initial screen after Logo)
*Edit* at no point in the life of this device (I bought it brand new) was it ever encrypted
At no point did I ever set a password or try to encrypt data. How do I fix this?
Click to expand...
Click to collapse
TWRP Asking for password. Please help. I've never set a password
TWRP is asking for password. I've never set a password. Please help me.
forum.xda-developers.com
.
Did not work.
Take a breathe...
In TWRP mount internal storage and select all toggles... Back to TWRP main menu select wipe / format data - type ´yes´
To wipe the rest go back to wipe / select all toggles and wipe it
Now you can flash like your way... If you want to sideload you must activate it in TWRP by Sideload /ADB... otherwise you can flash from external storage i.e. USB stick or whatever you want....
Format data partition is important to decrypt and wipe possible encryptions...
In future pls don´t change the data formats i.e. extf2 / exft4 or let repair them in TWRP in case you can´t handle it via ADB... TWRP is a nice tool but too many ppl bricked several devices by using this method or use unofficial shady versions...
If you try to flash PE you can push the rom on internal storage after fullwipe and after a recovery restart you can install it from internal storage...
I remember some strange TWRP times where we have to mount internal storage and partitions - and yes - before installing some stuff I´ve take a look on mounting points