Develop Bugs

How to flash official nougat without wiping internal storage?

Hello all!
I am currently on OOS 3.2.8, and official TWRP. I have read all the instructions on the forums but all lead to one option, formatting internal memory. So, my question are:
1. Will flashing oos 4.0 work with official TWRP or 8 have to use modified 28 version?
2. How can I flash oos 4 with modified TWRP and not have to wipe internal memory?
I would appreciate all the responses. Thanks

I was the same predicament as you. I finally took the plunge and now I have Nougat running on my OP3. Here is what I did :
Start: OOS 3.2.8 w/ custom kernel and modified TWRP
1. Flash stock recovery (Google for a forum post in the OP3 forums on downloading the stock recovery and flash it through fastboot)
2. Reboot and let 3.2.8 start
3. Download Snap VPN and change the country to Canada. You will be prompted for the system update.
4. Let the update download (~1 GB)
5. Install the update. You may see an error of the installation may fail as your phone is rooted. Ignore and go ahead.
6. The installer will now boot to stock recovery and reboot with Nougat. All settings and apps will be maintained
The only catch is that you may have ext4 instead of f2fs. I am okay with it for now... But your mileage may vary
All the best!

Edit : Nougat running on my op3.

abhibnl said:
Hello all!
I am currently on OOS 3.2.8, and official TWRP. I have read all the instructions on the forums but all lead to one option, formatting internal memory. So, my question are:
1. Will flashing oos 4.0 work with official TWRP or 8 have to use modified 28 version?
2. How can I flash oos 4 with modified TWRP and not have to wipe internal memory?
I would appreciate all the responses. Thanks
Click to expand...
Click to collapse
Are you rooted? Are you encrypted? What file systems are you using for your partitions? You're not giving full information. Why is formatting not an option if it'll give you the results you want?

To get to F2fs (I do recommend it)
Take a backup of your Data partition. , copy it to your pc with "adb pull /sdcard/Twrp/whatever".
Now go to Twrp>Wipe>Advanced select data and click on change file system. Change it to F2fs. Now restore your backup (Reader the guide all info is there). Profit!

anshulajain said:
I was the same predicament as you. I finally took the plunge and now I have Nougat running on my OP3. Here is what I did :
Start: OOS 3.2.8 w/ custom kernel and modified TWRP
1. Flash stock recovery (Google for a forum post in the OP3 forums on downloading the stock recovery and flash it through fastboot)
2. Reboot and let 3.2.8 start
3. Download Snap VPN and change the country to Canada. You will be prompted for the system update.
4. Let the update download (~1 GB)
5. Install the update. You may see an error of the installation may fail as your phone is rooted. Ignore and go ahead.
6. The installer will now boot to stock recovery and reboot with Nougat. All settings and apps will be maintained
The only catch is that you may have ext4 instead of f2fs. I am okay with it for now... But your mileage may vary
All the best!
Click to expand...
Click to collapse
I don't have any issues with ext4, infact i do feel ext4 is more stable than f2fs so file system is my last concern. Thanks for your method, but then how did u root again? Installing nougat is fine but what after that? I have read that you can't use modified twrp without formatting internal memory first, as it'll show you the pin issue. Let me know how do you propose a safe method to achieve root.
Renosh said:
Are you rooted? Are you encrypted? What file systems are you using for your partitions? You're not giving full information. Why is formatting not an option if it'll give you the results you want?
Click to expand...
Click to collapse
Yes i am encrypted, rooted, stock OOS 3.2.8 + Franco kernel. Official TWRP(not modified). I am using ext4, never used f2fs at all. The time to backup data and then to restore it all back is the reason formatting is not an "preferred" option for me. I can do it, but i would have to wait until i find enough time to do the whole process. I am in a full time job, so i hope you would understand.
Puddi_Puddin said:
To get to F2fs (I do recommend it)
Take a backup of your Data partition. , copy it to your pc with "adb pull /sdcard/Twrp/whatever".
Now go to Twrp>Wipe>Advanced select data and click on change file system. Change it to F2fs. Now restore your backup (Reader the guide all info is there). Profit!
Click to expand...
Click to collapse
Well this again defeats the purpose of my original question, but thanks mate. I would definitely read the guide if decide to switch to f2fs.

@abhibnl. BTW your encrypted. So the modified TWRP won't work.
How to fix:
Wipe Userdata with Fastboot / fastboot erase UserData
Boot into Twrp modified twrp.
Flash OOS 4.0 flash SuperSU and let it boot
You should be decrypted DO NOT install a boot password since you will be encrypted again.

I haven't rooted my phone again. My only reason to root is to install Adaway to block all ads. With DNS66 and Adguard, I have little incentive to root my stock nougat install.
Edit : I had encryption during 3.2.8 and it carried over to 4.0

Puddi_Puddin said:
@abhibnl. BTW your encrypted. So the modified TWRP won't work.
How to fix:
Wipe Userdata with Fastboot / fastboot erase UserData
Boot into Twrp modified twrp.
Flash OOS 4.0 flash SuperSU and let it boot
You should be decrypted DO NOT install a boot password since you will be encrypted again.
Click to expand...
Click to collapse
Thanks a lot for informing me mate. I really don't want to decrypt my storage as of now. I guess flashing stock recovery is the only solution now. Will hope someone would pick up the twrp and update it.

anshulajain said:
I haven't rooted my phone again. My only reason to root is to install Adaway to block all ads. With DNS66 and Adguard, I have little incentive to root my stock nougat install.
Edit : I had encryption during 3.2.8 and it carried over to 4.0
Click to expand...
Click to collapse
Seems like stock recovery is the best way as of now. Seems like I'll have to love without root until someone updates twrp to support encrypted storage.

I haven't updated to Nougat yet, but I looked over Chainfire's SuperSU changelog and its installation script and both of them confirm that from March installing SuperSU prevents forced encryption. Also many guides suggest installing it as way for disabling forced encryption. Of course you have to flash SuperSU just after flashing ROM, before booting the system.

abhibnl said:
Hello all!
I am currently on OOS 3.2.8, and official TWRP. I have read all the instructions on the forums but all lead to one option, formatting internal memory. So, my question are:
1. Will flashing oos 4.0 work with official TWRP or 8 have to use modified 28 version?
2. How can I flash oos 4 with modified TWRP and not have to wipe internal memory?
I would appreciate all the responses. Thanks
Click to expand...
Click to collapse
Very simple indeed...
1. Switch on wifi
2. Download OTA and click install whem finished
3. Once installation completed, flash twrp .28 and latest su
4. Reboot and ignore any errors, youwill beup and running fine...

Zielony360 said:
I haven't updated to Nougat yet, but I looked over Chainfire's SuperSU changelog and its installation script and both of them confirm that from March installing SuperSU prevents forced encryption. Also many guides suggest installing it as way for disabling forced encryption. Of course you have to flash SuperSU just after flashing ROM, before booting the system.
Click to expand...
Click to collapse
That i already knew mate. But i WANT my storage to remain encrypted. And that's the issue with modified TWRP. You can't enter into recovery on that if your storage is encrypted.
kpmohamedhussain said:
Very simple indeed...
1. Switch on wifi
2. Download OTA and click install whem finished
3. Once installation completed, flash twrp .28 and latest su
4. Reboot and ignore any errors, youwill beup and running fine...
Click to expand...
Click to collapse
Again, "You can't enter into recovery on modified TWRP if your storage is encrypted." So i won't be able to enter into twrp in the first place, let alone flash anything.

abhibnl said:
Hello all!
I am currently on OOS 3.2.8, and official TWRP. I have read all the instructions on the forums but all lead to one option, formatting internal memory. So, my question are:
1. Will flashing oos 4.0 work with official TWRP or 8 have to use modified 28 version?
2. How can I flash oos 4 with modified TWRP and not have to wipe internal memory?
I would appreciate all the responses. Thanks
Click to expand...
Click to collapse
In the same boat as you. I have OOS 3.2.8 encrypted, rooted and TWRP 3.0.2-1.26. I too would like to update but have way to much stuff on my phone to back it all up and restore it. Hope you or someone come's up with a solution. I will be following your thread.
Thanks.

Go to twrp. Press backup. Select only data. Save to PC youre backup for safety..
3.2.8 it's Android 6, 4.0 it's Android 7. Some apps might not work from base to base.
If you want to change to F2FS it will format youre phone, wipe phone full internal memory. If you want to change it back to ext4, same.
Clean flash, full wipe it's always better.

dmoses1969 said:
In the same boat as you. I have OOS 3.2.8 encrypted, rooted and TWRP 3.0.2-1.26. I too would like to update but have way to much stuff on my phone to back it all up and restore it. Hope you or someone come's up with a solution. I will be following your thread.
Thanks.
Click to expand...
Click to collapse
My suggestion (and my steps are in #1), install stock recovery, install snap VPN, download the update and install (ignore any errors on root). Once done, you will have Nougat with stock recovery, encryption maintained and all app data also intact.

anshulajain said:
My suggestion (and my steps are in #1), install stock recovery, install snap VPN, download the update and install (ignore any errors on root). Once done, you will have Nougat with stock recovery, encryption maintained and all app data also intact.
Click to expand...
Click to collapse
This is the last resort brother. With this method, unfortunately I won't have any root available. The only way now is to wait for updated twrp.

abhibnl said:
This is the last resort brother. With this method, unfortunately I won't have any root available. The only way now is to wait for updated twrp.
Click to expand...
Click to collapse
I dont know. I found this on Oneplus forum. May be worth trying. Just not 100% sure.....

Thanks! Will try and let you know

abhibnl said:
Thanks! Will try and let you know
Click to expand...
Click to collapse
Well, I tried something, waiting on it to finishing booting and see how it went.
I flashed twrp-3.0.2-1.28-oneplus3p version,
Flashed the OnePlus3Oxygen_16_OTA_035_all_1612310359_e10cadfb2af7.zip inside TWRP,
Flashed SR1-SuperSU-v2.79-SR1-20161221223537.zip right after flashing OTA zip.
Its rebooting and says Android is upgrading. Fingers crossed.
EDIT: Its booted and I am on Nougat, didnt lose my data and phone is still encrypted!
Edit: Ended up having issues with settings app locking up. So, I went a different route and its all working great now.
Downloaded the stock recovery image and renamed it to recovery.img
Make sure after you rename it its not named recovery.img.img, If you have show file extensions enabled on your pc you should already see the file extension.
Rebooted to bootloader - adb flash recovery recovery.img
Using the volume keys and power button selected - reboot recovery.
Now in stock recovery - flashed OnePlus3Oxygen_16_OTA_035_all_1612310359_e10cadfb2af7.zip
After rom is done flashing, went right back into bootloader. Did not let my phone reboot to start the OS.
Renamed twrp-3.0.2-1.28-oneplus3p.img to recovery.img
adb flash recovery recover.img
Powered off phone and Manually boot it into recovery by holding Power + Volume Down button.
Phone booted into TWRP
Flashed SR1-SuperSU-v2.79-SR1-20161221223537.zip
Wiped cache / dalvik
Rebooted system from TWRP and waited. System is really smooth now, no issues yet. Been playing with it for awhile now.
During the booting up process it might take a minute and it will reboot twice. Dont get nervous like I did thinking it was going to start bootlooping. It booted just fine. I read in a nother thread that SuperSU is what causes it to boot twice.
So......Now I have OOS 4.0 Nougat, Rooted, Encrypted and everything seems to be working fine.

DM verity

In the Oneplus 3T forum it is reported that flashing the bootloader resets the dm verity. Can we get the bootloader for Oneplus 3 to try the fix?

wrong forum body...
there's a specific forums for questions & requests.

Hi,
I had also this problem on my OP3 (not T version).
Solved with this :
1- on Freedom OS 1.7 (any rom should work), rebooted to TWRP (Official)
2- wiped everything including internal storage. (if already on .28 TWRP wiping data to f2fs and wiping internal storage normally may save you some steps later on)
3- fastbooted the official recovery (v1 downloaded from OP site)
4- rebooted to official recovery and started install from ADB.
5- sideloaded beta 9
6- rebooted to beta 9 ( booted perfectly with no issues)
7- reboot back to official recovery (now it will be v2)
8- wipe cahce (and data if available)
9- reboot to fastboot and fast boot mod TWRP .28
10 - on TWRP the password issue might appear but it';; be fixed after this step
11- on TWRP wipe Data to f2fs (even if it was f2fs) and wipe internal storage (it may show it as 0 size)
12- reboot to system
13- reboot back to TWRP and now it can access internal storage , flash SuperSU (sr5)
finaly reboot to system.
Regards,
Ted

Stop with this thread there are already specific threads for dm.

I Made an Backup with flashfire (fastboot flashable). And then restored it. After that the warning was away.

i still not get it, what the big problem is with this warning?
Have it since it came out, and cant find any issue with it?! Or do i miss something?

MultiCulti said:
i still not get it, what the big problem is with this warning?
Have it since it came out, and cant find any issue with it?! Or do i miss something?
Click to expand...
Click to collapse
There's technically no problem other than the annoyance of seeing the warning and using an extra 5 secs

I asked this issue on OnePlus online chat. They said that flashing open beta 7 firmware can solve this issue. I've tryed this and dm-verity error has been gone.

qhsusb_bulk said:
I asked this issue on OnePlus online chat. They said that flashing open beta 7 firmware can solve this issue. I've tryed this and dm-verity error has been gone.
Click to expand...
Click to collapse
And then flashed back OOS 4.02?? It is still gone

panther124 said:
I Made an Backup with flashfire (fastboot flashable). And then restored it. After that the warning was away.
Click to expand...
Click to collapse
Worked like a charm! Thanks for the tip

fuarkgl3 said:
Worked like a charm! Thanks for the tip
Click to expand...
Click to collapse
can u tell me how to restore backup file from flashfire.

phanipk said:
can u tell me how to restore backup file from flashfire.
Click to expand...
Click to collapse
Transfer your backup to your computer and extract the zip, then put your phone in fastbooot mode and click flash-all.bat

there have been so many threads on how to remove DM V. just use the search function dude...

There is no need to flash or erase anything.
Just use these two fastboot commands and the dm-verity notification is gone:
fastboot oem disable_dm_verity (this command is not needed)
fastboot oem enable_dm_verity

snippem said:
And then flashed back OOS 4.02?? It is still gone
Click to expand...
Click to collapse
Sorry for late reply. Yes now i am using OOS 4.0.2 with open beta 7 firmware. Firstly flashed full OOS zip with twrp, secondly i flashed OB7 firmware.

Thanks Sniperle
sniperle said:
There is no need to flash or erase anything.
Just use these two fastboot commands and the dm-verity notification is gone:
fastboot oem disable_dm_verity
fastboot oem enable_dm_verity
Click to expand...
Click to collapse
This was just the right trick
No more DM verity mumbo-jumbo.
THANKS!!!

So those two commands can also be used instead of the dm-verify.zip for those that want to make changes to their system partition (by mounting it in twrp) WITHOUT root?

Rastko said:
This was just the right trick
No more DM verity mumbo-jumbo.
THANKS!!!
Click to expand...
Click to collapse
sniperle said:
There is no need to flash or erase anything.
Just use these two fastboot commands and the dm-verity notification is gone:
fastboot oem disable_dm_verity
fastboot oem enable_dm_verity
Click to expand...
Click to collapse
Can i use this with TWRP, Custom ROM and Root activated? Or is this only possible with original bootloader and recovery?

bensen from hell said:
Can i use this with TWRP, Custom ROM and Root activated? Or is this only possible with original bootloader and recovery?
Click to expand...
Click to collapse
I'm using TWRP, LineageOS, phh root and it works
---------- Post added at 11:13 ---------- Previous post was at 10:59 ----------
sjaak1234 said:
So those two commands can also be used instead of the dm-verify.zip for those that want to make changes to their system partition (by mounting it in twrp) WITHOUT root?
Click to expand...
Click to collapse
The ZIP is for the previous use to not trigger dm-verity at all.
The fastboot commands should disable the message if you have already triggered dm-verity.

Ahhh nice, thanks. I thought that is only work with original bootloader and recovery because the OEM in the command. I'll try it at Weekend.

How Can Install Montly Updates without loose Root and Custom Recovery

Hi dudes! Im trying to find a way to install Monthly Updates without loose the root and the custom recovery, some body can tell me how? Because im really want update to Oreo but i want be root user and dont have to make a clean install system every month... exist the way? Please help.... And Thanks!

What I do is flash all the updated partition images individually using "fastboot flash", then let it boot and settle for a few minutes (at the very least until the "performing updates" notification completes).
I then reboot into bootloader and from there boot into TWRP (without installing it) using "fastboot boot twrp.img" and then reinstall Magisk zip. None of Magisk's settings or modules are lost by doing it this way.
If you uninstall Magisk before updating the system, you risk losing its settings.

You can use Flashfire.

nowster said:
What I do is flash all the updated partition images individually using "fastboot flash", then let it boot and settle for a few minutes (at the very least until the "performing updates" notification completes).
I then reboot into bootloader and from there boot into TWRP (without installing it) using "fastboot boot twrp.img" and then reinstall Magisk zip. None of Magisk's settings or modules are lost by doing it this way.
If you uninstall Magisk before updating the system, you risk losing its settings.
Click to expand...
Click to collapse
Okey, but using adb?

fnldstntn said:
You can use Flashfire.
Click to expand...
Click to collapse
How dude? Can you tech me please?

Aijen said:
How dude? Can you tech me please?
Click to expand...
Click to collapse
https://youtu.be/WxWRYnzI1O4
Now it is competible with magisk and if you want magisk instead of supersu on installation process you can disabel the installation of supersu and ad magisk to flash afterwards. you can also use the factory images or full ota zips from googles website.

Yes, you can use TWRP's "Advanced" adb sideload feature to install Magisk zip.
"adb" only works when Android is running (or some recovery images are running). When the phone is in bootloader mode the tool you need is "fastboot".

fnldstntn said:
Now it is competible with magisk and if you want magisk instead of supersu on installation process you can disabel the installation of supersu and ad magisk to flash afterwards. you can also use the factory images or full ota zips from googles website.
Click to expand...
Click to collapse
Thanks a lot! I will tried to do it!

fnldstntn said:
Now it is competible with magisk and if you want magisk instead of supersu on installation process you can disabel the installation of supersu and ad magisk to flash afterwards. you can also use the factory images or full ota zips from googles website.
Click to expand...
Click to collapse
Are you do that method without problems?

Aijen said:
Are you do that method without problems?
Click to expand...
Click to collapse
Yes it worked for me. But if you have twrp make a nandroid backup.

fnldstntn said:
Yes it worked for me. But if you have twrp make a nandroid backup.
Click to expand...
Click to collapse
Another thing....the last. Did you maintain the Custom Recovery or Flash it again?

fnldstntn said:
https://youtu.be/WxWRYnzI1O4
Now it is competible with magisk and if you want magisk instead of supersu on installation process you can disabel the installation of supersu and ad magisk to flash afterwards. you can also use the factory images or full ota zips from googles website.
Click to expand...
Click to collapse
dude! one last need reflash Magisk every time the OTA comes or Magisk survival the OTA flash with Magisk? THANKS A LOT WORKS!!!!

Aijen said:
Another thing....the last. Did you maintain the Custom Recovery or Flash it again?
Click to expand...
Click to collapse
i dont remember
Aijen said:
dude! one last need reflash Magisk every time the OTA comes or Magisk survival the OTA flash with Magisk? THANKS A LOT WORKS!!!!
Click to expand...
Click to collapse
i dont know.

Aijen said:
dude! one last need reflash Magisk every time the OTA comes or Magisk survival the OTA flash with Magisk?
Click to expand...
Click to collapse
Magisk embeds itself in the boot partition. This prevents OTA from working.
Replacing the stock recovery partition also stops OTA from working.
The only reliable way to upgrade is by flashing the partitions again from the new factory image zip file, then reinstalling TWRP and Magisk afterwards.

fnldstntn said:
You can use Flashfire.
Click to expand...
Click to collapse
Any ideas what will happen to ElementalX after flashing OTA using Flashfire?

zo1021 said:
Any ideas what will happen to ElementalX after flashing OTA using Flashfire?
Click to expand...
Click to collapse
Using the logic need to reflash it again

nowster said:
Magisk embeds itself in the boot partition. This prevents OTA from working.
Replacing the stock recovery partition also stops OTA from working.
The only reliable way to upgrade is by flashing the partitions again from the new factory image zip file, then reinstalling TWRP and Magisk afterwards.
Click to expand...
Click to collapse
Sounds logic to me....

FlashFire is saying that the update will likely fail because the OTA update is a block level update. Suggestions on how to get around this?

[STOCK] [H932] [20p] [Oreo] T-Mobile LG V30 Stock Collection (Debloated Added)

T-Mobile V30 H932 20P Stock Collection
Based on OEM 20P KDZ. Extracted and Repacked.
DISCLAIMER
Proceed at your own risk. I am not responsible for any damage to your device.
Flashing LAF WILL REMOVE TWRP from your laf partition and restore stock DL Mode
Bins in these packages are unmodified and you may need to flash no-verity-opt-encrypt and rctd remover after to keep force-encryption away.
REQUIRED
TWRP on LAF or Recovery
Latest Magisk Zip (if performing clean flash)
no-verity-opt-encrypt
rctd remover
FILE BREAKDOWN
None of these Zips flash the Recovery partition.
Besides StockLAF, these Zips DO NOT flash the LAF partition.
If you want to restore DL Mode and Stock LAF, you must flash the StockLAF package separately.
​
Bootloader: 20p Stock Bootloader ONLY
FullStock: Full 20p Stock Firmware Only (bootloader, modem, boot, system) - Instructions in Section A
FullStock w/Magisk: Full 20p Stock Firmware + Magisk Root - Instructions in Section B
Debloated w/Magisk: Boot+Debloated System + Magisk Root (force enc & dm-verity removed) - Instructions in Section C
StockLAF: Individual LAF image for returning to stock DL mode
Global Instructions​
Always make a backup first
If device has been encrypted, see encryption notes at the bottom before continuing.
A - FullStock
If coming from Nougat, Clean Flash is Recommended
Wipe Dalvik, System, Data, Cache... then flash
If coming from previous Oreo versions, Dirty Flash works fine. OS and Apps are updated.
Copy All Zips to SDCard
Flash h932_FullStock.zip
Flash Magisk
Flash no-verity-opt-encrypt
Flash rctd remover
Reboot to system and install Magisk Manager (if not installed)
B - FullStock with Magisk
This zip just cuts out the step of flashing magisk manually.
This zip should be dirty flashed on a system that already has magisk. or Magisk may not flash successfully
If this zip is clean flashed, pay close attention to flash logs. If magisk fails to repack the boot image during flash, flash Magisk again.
Flash h932_FullStock_Magisk.zip
Flash no-verity-opt-encrypt
Flash rctd remover
Wipe Dalvik+Cache
Reboot
C - Debloated with Magisk
Be aware
This ROM does NOT flash LAF, recovery, bootloader or modem firmware directly.
If you are coming from an older version of android, this rom does not include the complete device firmware, which you may want.
For those included above, you should flash FullStock before flashing this to make sure all of your device firmware is up to date.
Boot image has been patched to remove force encryption and dm-verity
This ROM has had several pre-loaded and system apps removed. If someone wants to send me a list of any additional apps that can be safely removed, i can update the rom to include them.
system/app/CloudPrint
system/app/Drive
system/app/Duo
system/app/EditorsDocs
system/app/EditorsSheets
system/app/Gmail2
system/app/GooglePay
system/app/LGAccount
system/app/LGAirDrive
system/app/LGAmazonAssistant
system/app/LGAmazonAttribution
system/app/Maps
system/app/Music2
system/app/Photos
system/app/YouTube
system/priv-app/CloudHub
system/priv-app/CollageWallpapers
system/priv-app/facebook-installer
system/priv-app/LG360VideoWallpaper
system/priv-app/LG360Wallpaper
system/priv-app/LGEasyHome
system/priv-app/LGEmail
system/priv-app/LGExchange
system/priv-app/LGQHelpService
system/priv-app/LGVVM
system/priv-app/NameID
system/priv-app/TMO_MyAccount
system/priv-app/xtra_t_app
system/vendor/app/facebook-appmanager
system/vendor/overlay/com.lge.easyhome
system/vendor/overlay/com.lge.email
system/vendor/overlay/com.lge.exchange
system/vendor/overlay/com.lge.lgworld
system/vendor/overlay/com.lge.qhelp
system/vendor/overlay/com.lge.qhelp.application
system/vendor/overlay/com.lge.qmemoplus
For best results a clean flash is recommended for this package
Format data, and remove any apps installed to external sd. Then wipe system, dalvik, cache, data, internal storage
This will ensure no lingering apps are left behind.
If coming from Nougat, Clean Flash is Highly Recommended
Wipe Dalvik, System, Data, Cache... then flash
If coming from previous Oreo Versions
Wipe Dalvik, Cache, and System, and optionally data and internal storage
If you do not perform a clean flash, you may need to manually remove the apps left behind after flashing
Flash h932_Debloated_Magisk.zip
Reboot
DOWNLOADS
Stable v1.0
Project files are hosted on SourceForge​
Bootloader - md5:45d8897c317b2e2e7b02d0766a93556c
FullStock ROM - md5:092585a169b54f067cec27d57b0c041c
FullStock w/Magisk - md5:6854a34ed956e9b30fb8e59c34de6b39
Debloated w/Magisk - md5:5a11334c8e42dfe55f2a71bbb0820612
StockLAF - md5:9090ee8645f2018c6bd88c9169c52c1b
*************************************************************************************************************​
Encryption Notes
In Android, a stock device will have it's data encrypted. Often when working in TWRP on an encrypted device, you will be greeted by prompt asking for a passcode in order to decrypt the device. Unless that port of TWRP has been written for your specific device and supports decryption, you will not be able to decrypt the data on your phone. If you cannot decrypt the data, then TWRP cannot mount system and/or other partitions it needs to mount in order to safely flash anything. In order to solve this problem, sadly, you have to format the data partition on your phone (losing all personal data accumulated on the internal storage, so back it all up manually) The steps for this process are Format Data in TWRP, Reboot to recovery (to mount partitions), then flash your rom and root. There are a few tools out there to disable force encryption on your device. See the Required section above for links for this device.
​
Packages have been successfully tested VIA the methods outlined above.
If anyone has any issues with one or more of these packages, please let me know. Thank you!
-weakNPCdotCom​​
XDA:DevDB Information
[STOCK] h93220p, ROM for the LG V30
Contributors
weakNPCdotCom
Source Code: https://sourceforge.net/projects/t-mobile-v30-firmware/files/h932/20p/
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.x
Based On: 20p KDZ
Version Information
Status: Stable
Created 2018-12-20
Last Updated 2018-12-28

would it be possible for you to make a "debloated" stock rom?? all stuff we can "technically" reinstall from play store. Something close to stock android as possible.

This did not work. I used the zip with magisk. Magisk was and is not installed I lost TWRP and download mode doesnt work and just reboots to system after a minute.
Anyway to fix this? It boots fine but i dont have fastboot and download mode shows only the download mode screen then reboots

Andi32790 said:
This did not work. I used the zip with magisk. Magisk was and is not installed I lost TWRP and download mode doesnt work and just reboots to system after a minute.
Anyway to fix this? It boots fine but i dont have fastboot and download mode shows only the download mode screen then reboots
Click to expand...
Click to collapse
Verify that you did download "h93220p_fullStock_wMagisk.zip". It worked fine for me, and I can confirm it has magisk as I was on 17.3 on 20o and magisk manager says I'm on 18.
Also, were you coming from 20o?

[Cruzer] said:
would it be possible for you to make a "debloated" stock rom?? all stuff we can "technically" reinstall from play store. Something close to stock android as possible.
Click to expand...
Click to collapse
Yes, I can make a debloated ROM. Gimme a day or two and I'll try to add one to the OP.

Andi32790 said:
This did not work. I used the zip with magisk. Magisk was and is not installed I lost TWRP and download mode doesnt work and just reboots to system after a minute.
Anyway to fix this? It boots fine but i dont have fastboot and download mode shows only the download mode screen then reboots
Click to expand...
Click to collapse
Sorry M8, but i tested this zip and verified that it flashes all partitions and then flashes magisk all in one go. I think maybe you downloaded the package without magisk by mistake.
This zip does not flash LAF, so if you had TWRP on LAF before flashing this, you should be able to just boot to download mode using the usb cable and reflash TWRP to recovery.

Andi32790 said:
This did not work. I used the zip with magisk. Magisk was and is not installed
Click to expand...
Click to collapse
After further testing, I discovered that after wiping and doing a clean flash of FullStock w Magisk, Magisk failed to repack the boot image. I had to flash magisk a second time for it to complete the process.
I will update the OP. Thank you for bringing this to my attention. I hope you are able to get back into TWRP

weakNPCdotCom said:
After further testing, I discovered that after wiping and doing a clean flash of FullStock w Magisk, Magisk failed to repack the boot image. I had to flash magisk a second time for it to complete the process.
I will update the OP. Thank you for bringing this to my attention. I hope you are able to get back into TWRP
Click to expand...
Click to collapse
No recovery was not in LAF and was overwritten and I don't have fastboot and download mode doesn't seem to work right. Phone works just no root I guess. I should have paid more attention to what was going on when I flashed it.

Andi32790 said:
No recovery was not in LAF and was overwritten and I don't have fastboot and download mode doesn't seem to work right. Phone works just no root I guess. I should have paid more attention to what was going on when I flashed it.
Click to expand...
Click to collapse
Im sorry man. I honestly have no idea why download mode was affected because these zips don't touch it at all. If you go through the root process again, I recommend keeping a copy of TWRP on both LAF and Recovery.

weakNPCdotCom said:
Im sorry man. I honestly have no idea why download mode was affected because these zips don't touch it at all. If you go through the root process again, I recommend keeping a copy of TWRP on both LAF and Recovery.
Click to expand...
Click to collapse
No worries man I still have a phone plus thats why you all add the disclaimer. Idk just looking for a fix at this point.

[Cruzer] said:
would it be possible for you to make a "debloated" stock rom?? all stuff we can "technically" reinstall from play store. Something close to stock android as possible.
Click to expand...
Click to collapse
I'm having an issue with my kitchen, but as soon as I'm able to solve what's going on ill cook up this ROM

Thanks weakNPCdotCom. I dirty flashed over 20o and it's working great.

weakNPCdotCom said:
I'm having an issue with my kitchen, but as soon as I'm able to solve what's going on ill cook up this ROM
Click to expand...
Click to collapse
No worries take your time. Appreciate the work your doing

I just want to make sure if I dirty flash FullStock w/Magisk that I wont loose TWRP because I dont have back up in LAF.

SIMONAK said:
I just want to make sure if I dirty flash FullStock w/Magisk that I wont loose TWRP because I dont have back up in LAF.
Click to expand...
Click to collapse
I just did it and didn't loose TWRP.

It worked thank you.

SIMONAK said:
I just want to make sure if I dirty flash FullStock w/Magisk that I wont loose TWRP because I dont have back up in LAF.
Click to expand...
Click to collapse
Just pay attention to the flash logs and make sure everything flashes properly

[Cruzer] said:
No worries take your time. Appreciate the work your doing
Click to expand...
Click to collapse
Ok, so I cooked up a debloated and deodexed ROM, but when I tested it, it was really laggy and some system apps crashed all the time.
I think I might be able to get away with not deodexing it for better performance, and probably keeping a few of the apps I removed. Id rather not publish it until it's smooth and stable, so I'll keep working on it.
let me know if you are interested in trying the unstable build and ill upload it but it has issues

weakNPCdotCom said:
Ok, so I cooked up a debloated and deodexed ROM, but when I tested it, it was really laggy and some system apps crashed all the time.
I think I might be able to get away with not deodexing it for better performance, and probably keeping a few of the apps I removed. Id rather not publish it until it's smooth and stable, so I'll keep working on it.
let me know if you are interested in trying the unstable build and ill upload it but it has issues
Click to expand...
Click to collapse
Yah I'll wait til you have all the bugs worked out. Side note when I was "trying" to debloat. I removed chrome from system. It broke a few system apps. Maybe that will help. Thanks again for your work

[Cruzer] said:
Yah I'll wait til you have all the bugs worked out. Side note when I was "trying" to debloat. I removed chrome from system. It broke a few system apps. Maybe that will help. Thanks again for your work
Click to expand...
Click to collapse
I did remove chrome in the ROM so ill keep that in mind when I try again tonight. I don't think I'm going to deodex it either unless I get a smooth running build.. I'm not sure the advantage in oreo anyway since it's vdex now. but ill give it another go

[ROOT] Galaxy S9 Exynos 9.0 Android Pie

Hi, It seems this is not compatible with me...
I followed the same procedure as Oreo :
-Unlock OEM
-Twrp through Odin v3.13.1 > format Data
-no-verity-opt-encrypt-samsung-1.0
-Magisk 18
Then the root work but there is problem with security, I cannot log into samsung account, cannot configure fingerprint, Iris detection, face detection. When I configure a pin password, he seems to save a wrong password.
Finally if I try to configure samsung account and reboot, the phone boot correctly but stuck at start screen( and get hot like an infinite loop)
Someone got an idea? I saw that some person don't got problem maybe you used supersu and not magisk ?

Same happened to me, i think i missed a certain zipfile for RMM. Which resulted in not able to login to my samsing account and after restart a bootloop with the message "Only official firmares may be flashed"

I have exactly the same issue and symptoms when going with no-verity-opt-encrypt-samsung-1.0.
And when I try no-verity-opt-encrypt-6.0 from https://build.nethunter.com/android-tools/no-verity-opt-encrypt/, I get stuck in a bootloop even before the system starts.
My guess is, we need a different no-verity patch.

Siema89 said:
I have exactly the same issue and symptoms when going with no-verity-opt-encrypt-samsung-1.0.
And when I try no-verity-opt-encrypt-6.0 from https://build.nethunter.com/android-tools/no-verity-opt-encrypt/, I get stuck in a bootloop even before the system starts.
My guess is, we need a different no-verity patch.
Click to expand...
Click to collapse
Maybe it would work with an Android Pie compatible Kernel such as ElementalX 2.01. I didn't have the time to try it..

danw84 said:
Maybe it would work with an Android Pie compatible Kernel such as ElementalX 2.01. I didn't have the time to try it..
Click to expand...
Click to collapse
with this kernel the root works great, thanks a lot for sharing this kernel. All security works again with magisk

Could you be so kind to tell me the order, too install everything and have Magisk in my Samsung S9+ Pie?
Thanks in advance.
Best regards

Not sure it works with s9+
-Flashed the last pie build with Odin
-enabled unlock OEM
-flashed TWRP
-flashed no verity opt
-flashed kernel elemental
-flashed magisk
The phone stuck one or two times at boot, I restarted it each times and he continued the process.

Maho007 said:
Not sure it works with s9+
-Flashed the last pie build with Odin
-enabled unlock OEM
-flashed TWRP
-flashed no verity opt
-flashed kernel elemental
-flashed magisk
The phone stuck one or two times at boot, I restarted it each times and he continued the process.
Click to expand...
Click to collapse
Tried this and I can confirm this worked for me.

Thanks for your help. I guess I'm doing something wrong.
---------- Post added at 01:53 PM ---------- Previous post was at 01:39 PM ----------
Here I detail my process:
-Flashed the last pie build with Odin
-enabled unlock OEM
-flashed TWRP with Odin
*** Reboot recovery to TWRP, swipe to allow modifications.
*** Wipe- Format yes
Reboot recovery - Read Only
-flashed no verity opt (which version 1 or 6???)
-flashed kernel elemental
-flashed magisk
Reboot system
I did try with this, but I guess still doing something wrong, please, could you check to see if I miss something or i do something wrong?.
Thanks in advance

I used version 6, I don't made more, try the kernel Without root for testing.

For the record. Upon opening TWRP for the first time I swiped to allow system modifications.
For the verity file i used no-verity-opt-encrypt-samsung-1.0

Maho007 said:
I used version 6, I don't made more, try the kernel Without root for testing.
Click to expand...
Click to collapse
Thaks, that worked for me too.

I do have some problems with galaxy apps, some odd restarts... I hope we can have a cleaner way to root soon.
Root works, but is not very stable.

Mickyman said:
For the record. Upon opening TWRP for the first time I swiped to allow system modifications.
For the verity file i used no-verity-opt-encrypt-samsung-1.0
Click to expand...
Click to collapse
Hi Mickyman, what do you mean, like this?
-Flashed the last pie build with Odin
-enabled unlock OEM
-flashed TWRP with Odin
*** Reboot recovery to TWRP, swipe to allow modifications.
*** Wipe- Format yes
Reboot recovery - Read Only Allow modifications and install everything allowing modifications?
-flashed no verity opt (which version 1 or 6???)
-flashed kernel elemental
-flashed magisk
Reboot system

i do it but my knox status is now:
0x1
please help me i wnat to use samsung secure folder...
is any way to reset it to 0x0?

Sorry, mate. You'll have to buy another phone.
You have tripped Knox flag. No way back.

Maho007 said:
Not sure it works with s9+
-Flashed the last pie build with Odin
-enabled unlock OEM
-flashed TWRP
-flashed no verity opt
-flashed kernel elemental
-flashed magisk
The phone stuck one or two times at boot, I restarted it each times and he continued the process.
Click to expand...
Click to collapse
i can confirm this works for me as well

I can confirm this worked for new too.

Hello NICOMONI, will you tell me how did you do root?
I followed all the tutorials and it worked for the root but could not connect to my samsung account. thank you

NICOMONI said:
I do have some problems with galaxy apps, some odd restarts... I hope we can have a cleaner way to root soon.
Root works, but is not very stable.
Click to expand...
Click to collapse
True, I got crash too.