Database Info

Root and Tools for Oreo

Does anybody know, if the following is working on Oreo:
- TWRP
- SuperSU (Root)
- SoundMod
- Systemless DevBase
Thanks in Advance

profi_fahrer said:
Does anybody know, if the following is working on Oreo:
- TWRP
- SuperSU (Root)
- SoundMod
- Systemless DevBase
Thanks in Advance
Click to expand...
Click to collapse
So far I've attempted to flash the S7 nougat dual speaker mod and the phone just ended up with no sound at all. I also tried flashing S8 oreo dual speaker mod and that also failed. Looks like we just have to wait until someone comes out with a dual speaker mod for oreo on the S7.

Thanks for the reply

i used twrp image 3.2.1.0
and for rooting magisk 16.0

profi_fahrer said:
Does anybody know, if the following is working on Oreo:
- TWRP
- SuperSU (Root)
- SoundMod
- Systemless DevBase
Thanks in Advance
Click to expand...
Click to collapse
As they work for any Oreo ROMs (and they could), you'll have no problem with this install .zip!
SuperSU is garbage for Stock, try Magisk instead of it

Magisk wasn't good for me in the past. At first, one Update for Magisk failed, and the Phone encrypted my Data. With the second attempt, it works, but the boot time was very long. About 3-5 Minutes. Since i deleted Magisk and install SuperSU everything is fine

boooggy said:
i used twrp image 3.2.1.0
and for rooting magisk 16.0
Click to expand...
Click to collapse
how do you proceed?
Thank you

Interesting topic
I read many failure topics about the s7 and oreo and root. Samsung seems to make it very difficult to root these days?
Latest twrp seems to have a mounting problem. So wich twrp is stable enough for an oreo update?
And if skipping twrp, (Because of ota and i use titanium for app settings and backup) has someone succes with magisk patched boot image and flash this with odin?)

fred.eric said:
how do you proceed?
Thank you
Click to expand...
Click to collapse
first flashed btu nougat firmware with odin
then installed oreo (i did this before full oreo image appeared)
after instalation finished i turned off and installed via odin twrp 3.2.1.1.
it restatrted to recovery where i format data. then conected phone to pc and copied no-verity-opt-encrypt-6.0.zip and magisk,zip.
then installed both from recovery. rebooted and thats was all

Do you think, this will work: (Now I have root)
1. Backup everything
2. Flash 8.0 System with Odin
3. Boot into recovery to apply CSC
4. Flash TWRP
5. Install root + Systemless DevBase and other mods
6. Wipe Cache + Dalvik
7. Boot normal to system and keep the Data from Android 7
Thanks in advance

problem with no-verity-opt-encrypt-6.0.zip
root is working, but I am not able to access /data in recovery mode just after booting to system.
It was working before. I tried reboot to recovery or poweroff off/start recovery.
After flashing TWRP, I restart in recovery mode,
format data,
reboot into recovery,
then install magisk and opt-encrypt
Did I miss a step? Is there an order to flash magisk and opt-encrypt?
Thank you

I don't think that the /data pertition in encrypted, because the first boot with old Data took very short. Maybe TWRP can't read it with oreo.

profi_fahrer said:
I don't think that the /data pertition in encrypted, because the first boot with old Data took very short. Maybe TWRP can't read it with oreo.
Click to expand...
Click to collapse
Of course DATA partition is encrypted, that is where user sensitive information and data is stored, it gets decrypted each time the device boots
--
Android employs a straightforward block-level encryption of the data partition. Pre-Lollipop devices were using the old insecure encryption scheme that was relatively easy to break. Since Android 5.0, Google switched to new full-disk encryption that became significantly more secure. By default, the decryption key is stored in the hardware-backed storage using Trusted Execution Environment’s (TEE) signing capability (such as in a TrustZone). The data partition is decrypted with that key automatically once the device reboots.
https://blog.elcomsoft.com/2017/05/android-encryption-demystified/

It is encryped without root, but with root it is decrypted.
I can't access the /data partition with TWRP in Android 8, but with Android 7 it works. Both with root.

boooggy said:
i used twrp image 3.2.1.0
and for rooting magisk 16.0
Click to expand...
Click to collapse
Didn't work for me, please elaborate how?

fix twrp /data access
After reading this thread [ROM][8.0.0] Dylan's S7 Oreo ROM V4 https://forum.xda-developers.com/galaxy-s7/development/rom-dylan-s-s7-oreo-rom-t3784715
I used SuperSU instead of Magisk and no-verity-opt-encrypt-6.0.zip works

How to Restore backup || TWRP

Greetings,
after restoring back up from official TWRP the device soft-bricked like our friend here
https://forum.xda-developers.com/oneplus-6/help/soft-brick-restoring-backup-twrp-t3805112
the device won't even boot to fastboot from hardware button but from adb on recovery mode which hang on twrp logo screen.
what I saw on log is that /system partition structure need cleaning (and can not be mounted)
my backup contains all partition.
so my steps to restore the backup
boot to recovery
from PC into CMD "adb reboot bootloader"
wait until boot to bootloader (fastboot)
boot temporary into twrp "fastboot boot twrp.img" make sure you have twrp img
restore all partition except /system
then restore /system alone
reboot to system
everything's works like charm
I know it seems hideous but this is how I fix it ( and I can confirm I've done it twice)
:good:
UPDATED:
After some testing the problem only occurs when i take back up for all partitions which isn't mandatory, but when i take back for (system, boot, data) which is enough for working backup and the restoring process is flawless
I did not disable security (PIN code) and restoring was successful
Short answer:
Only take backup for data, system, boot

R1skNt said:
Greetings,
after restoring back up from official TWRP the device soft-bricked like our friend here
https://forum.xda-developers.com/oneplus-6/help/soft-brick-restoring-backup-twrp-t3805112
the device won't even boot to fastboot from hardware button but from adb on recovery mode which hang on twrp logo screen.
what I saw on log is that /system partition structure need cleaning (and can not be mounted)
my backup contains all partition.
so my steps to restore the backup
boot to recovery
from PC into CMD "adb reboot bootloader"
wait until boot to bootloader (fastboot)
boot temporary into twrp "fastboot boot twrp.img" make sure you have twrp img
restore all partition except /system
then restore /system alone
reboot to system
everything's works like charm
I know it seems hideous but this is how I fix it ( and I can confirm I've done it twice)
:good:
Click to expand...
Click to collapse
Sounds great, but it doesn't work for me. I posted the following comment in another thread:
----------------------------------
I'm having the same problem. I simply cannot restore a TWRP backup. It always produces an error 255.
No, I do not have any "999" folder/files, nor do I have any lockscreen security. I also do not have parallel apps or anything involving multi-user.
I'm extremely experienced at flashing ROMs, as well as performing Nandroids and restoring them.
Nothing I've done is working. As I said, I simply cannot restore the data partition. That's when I get the 255 error. System restores fine, but that's it.
Any ideas?
----------------------------------
Thank you,
Peter

R1skNt said:
Greetings,
after restoring back up from official TWRP the device soft-bricked like our friend here
https://forum.xda-developers.com/oneplus-6/help/soft-brick-restoring-backup-twrp-t3805112
the device won't even boot to fastboot from hardware button but from adb on recovery mode which hang on twrp logo screen.
what I saw on log is that /system partition structure need cleaning (and can not be mounted)
my backup contains all partition.
so my steps to restore the backup
boot to recovery
from PC into CMD "adb reboot bootloader"
wait until boot to bootloader (fastboot)
boot temporary into twrp "fastboot boot twrp.img" make sure you have twrp img
restore all partition except /system
then restore /system alone
reboot to system
everything's works like charm
I know it seems hideous but this is how I fix it ( and I can confirm I've done it twice)
:good:
Click to expand...
Click to collapse
What about security? Did you have to disable all security before the backup?

I did not disable security (PIN code) and restoring was successful.

R1skNt said:
I did not disable security (PIN code) and restoring was successful.
Click to expand...
Click to collapse
These are the backup settings that I am using. Can you please tell me if you use the same, or if not please share the ones you are using.

lollyjay said:
These are the backup settings that I am using. Can you please tell me if you use the same, or if not please share the ones you are using.
Click to expand...
Click to collapse
Please see the 1st post (update)

PeterGuru said:
Sounds great, but it doesn't work for me. I posted the following comment in another thread:
----------------------------------
I'm having the same problem. I simply cannot restore a TWRP backup. It always produces an error 255.
No, I do not have any "999" folder/files, nor do I have any lockscreen security. I also do not have parallel apps or anything involving multi-user.
I'm extremely experienced at flashing ROMs, as well as performing Nandroids and restoring them.
Nothing I've done is working. As I said, I simply cannot restore the data partition. That's when I get the 255 error. System restores fine, but that's it.
Any ideas?
----------------------------------
Thank you,
Peter
Click to expand...
Click to collapse
For what it's worth, I think I found a solution to why I couldn't restore the data partition. I can't explain why, but now it's working.
Previously, and historically, whenever I did a restore, I always wiped my device: system, data, boot.
This time; however, I did not wipe the device. I simply did the restore and everything worked. Therefore, the problem is somehow associated with the wipe.
Peter

I did a nanroid backup (boot, system, data only as per the instructions) of 5.1.8, rooted with magisk 16.6, ROM, installed lineage OS, than restored my backed up OOS ROM the restore process completed successfully but got stuck on boot logo, flashed magisk again along with the custom kernel but all to no joy, keeps bootlooping, however lineage restored fine and booted, any help be much appreciated, cheers.

joemossjr said:
You guys are crazy and I feel I need to answer your questions. So here we go. So just becuase there's multiple partitions doesn't mean you can dual boot or set up other things. So the way it works is the userdata partition is one partition. There are 2 system partitions for seamless updates two boot partitions for seamless and two firmware slots. In theory yes you can have two roms on both slots. Will they work? No. They will both use the same userdata partitions. So it will be incompatible.now you could in theory have lineage on one slot and oos on the other and if you ever want to go back just format userdata and fastboot --set-active=other to get to the other slot. But that doesn't really seem like a good idea. If you guys have other questions feel free to ask me!
Click to expand...
Click to collapse
This is from another thread here, my understanding is you have to format userdata partition, but please read it by self.

Bonito77 said:
This is from another thread here, my understanding is you have to format userdata partition, but please read it by self.
Click to expand...
Click to collapse
totally irrelevant to this thread, cheers.

"fastboot boot twrp.img
cannot load 'twrp.img': No such file or directory"
What is wrong?

bannannn said:
"fastboot boot twrp.img
cannot load 'twrp.img': No such file or directory"
What is wrong?
Click to expand...
Click to collapse
I assume you're in the directory twrp.img is in and are using the img file instead of the zip file? Also you renamed the img file to twrp.img?

after 6 hours of head banging . i stumbled across this thread. and i got my renovate backup. Since new to oneplus 6 have shifted from samsung S9+. The first post correctly resolved my headache. I have learned.
1. Only Backup sytem , data, boot other partitions of twrp restore needed. not need to restore others
2. Had to format the internal storage as it become fully corrupted with lot of folders with strange names
3. Had to re install full OOS rom zip then boot into sytem
4. reflash twrp via fastboot, install twrp offical .img from twrp.
5 NO WIPES( I think wiping system and then restoring vendor and other partitions was creating issues)
6 Only Restoring Boot , System, Data. and then straight away booting back phone to system worked perfect. didnt require to flash magisk
thanks a lot for this thread OP. :good:
i am an experienced flasher. but i guess to comeback to oxygen OS from other roms you have to install stock full OOS Rom again.

kingwicked said:
after 6 hours of head banging . i stumbled across this thread. and i got my renovate backup. Since new to oneplus 6 have shifted from samsung S9+. The first post correctly resolved my headache. I have learned.
1. Only Backup sytem , data, boot other partitions of twrp restore needed. not need to restore others
2. Had to format the internal storage as it become fully corrupted with lot of folders with strange names
3. Had to re install full OOS rom zip then boot into sytem
4. reflash twrp via fastboot, install twrp offical .img from twrp.
5 NO WIPES( I think wiping system and then restoring vendor and other partitions was creating issues)
6 Only Restoring Boot , System, Data. and then straight away booting back phone to system worked perfect. didnt require to flash magisk
thanks a lot for this thread OP. :good:
i am an experienced flasher. but i guess to comeback to oxygen OS from other roms you have to install stock full OOS Rom again.
Click to expand...
Click to collapse
I followed your guide. But I'm stuck at the boot animation...

RheinPirat said:
I followed your guide. But I'm stuck at the boot animation...
Click to expand...
Click to collapse
well i have found new method which works every time
if stuck in boot animation
1. install the version stock OOS e.g 6.0.2 of which u have backup as well. again oem unlock process
2. install twrp
3 . reboot twrp
4.instal verity for phone being always decrypted
5. install magisk
6. reboot into system once
if you still have twrp
6 reboot to twrp
8. restore ONLY Data from twrp backup of SAME rom.
9. install twrp
10 reboot twrp install verity zip and magisk
remember
both rom installed and backup have to be of same OS. for e.g OOS 6.0.2 stable. only same backup can be restored as they have same security patch date
if you have a backup of for example OOS 5.1.11 then only rest ore data on a 5.1.11 rom
and flash magisk after backup restoee if ur backup had magisk. otherwise you will be stuck in boot animation
if you made backup with pin see the main OOS guide it has instructions how to remove pin after twrp restore
from twrp
Dont do any wipes before or after restoring data from twrp only magisk with verity zip is required if you had root
i always use the twrp bluespark as i had issues with stock twrp
thia methodology has worked always for me
best of luck

kingwicked said:
well i have found new method which works every time
if stuck in boot animation
1. install the version stock OOS e.g 6.0.2 of which u have backup as well. again oem unlock process
2. install twrp
3 . reboot twrp
4.instal verity for phone being always decrypted
5. install magisk
6. reboot into system once
if you still have twrp
6 reboot to twrp
8. restore ONLY Data from twrp backup of SAME rom.
9. install twrp
10 reboot twrp install verity zip and magisk
remember
both rom installed and backup have to be of same OS. for e.g OOS 6.0.2 stable. only same backup can be restored as they have same security patch date
if you have a backup of for example OOS 5.1.11 then only rest ore data on a 5.1.11 rom
and flash magisk after backup restoee if ur backup had magisk. otherwise you will be stuck in boot animation
if you made backup with pin see the main OOS guide it has instructions how to remove pin after twrp restore
from twrp
Dont do any wipes before or after restoring data from twrp only magisk with verity zip is required if you had root
i always use the twrp bluespark as i had issues with stock twrp
thia methodology has worked always for me
best of luck
Click to expand...
Click to collapse
I was on 9.0.2
I restored the phone with the MSM tool and updated the ROM to 9.0.2 via manual system update like before.
Question:
Is it not possible to restore the whole system? Or only Data like you said under point 8?
Do I need verity? Because I think my phone is encrypted (flashed never a verity file)
Could I restore the whole system from a full TWRP (all partitions included) - only select data, system?

restoring system and other never worked for me. always failed. but only restoring data partition always worked
when you restore only data. your all apps. settings messages everything will restore even magisk modules.
im not sure about encrypted because. encrypted phone when restoring twrp messed up my whole internal memory. and i had no choice but to wipe it.
so there is no issue with no verity. as it helps not to scramble the internal memory of your device and you wull not loose any data or get stuck on qualcomm dump mode
but remember the steps to verity when installed on already used rom with data. you have to format data to remove encryption
only restoring data is the best option. you can try without no verity to restore i think may work but follow all options i mentioned
but i dont recommend to use with no verity.since using no verity i have never got to wipe my internal memory

I've bricked my device twice after trying to restore and always resorted to just a clean flash of stock using the MSMDownloadTool... wish I'd found this thread sooner as you just solved my third backup restore soft-brick!
I'll also remember to just backup system/data/boot going forward...
Thanks!

kingwicked said:
well i have found new method which works every time
if stuck in boot animation
1. install the version stock OOS e.g 6.0.2 of which u have backup as well. again oem unlock process
2. install twrp
3 . reboot twrp
4.instal verity for phone being always decrypted
5. install magisk
6. reboot into system once
if you still have twrp
6 reboot to twrp
8. restore ONLY Data from twrp backup of SAME rom.
9. install twrp
10 reboot twrp install verity zip and magisk
remember
both rom installed and backup have to be of same OS. for e.g OOS 6.0.2 stable. only same backup can be restored as they have same security patch date
if you have a backup of for example OOS 5.1.11 then only rest ore data on a 5.1.11 rom
and flash magisk after backup restoee if ur backup had magisk. otherwise you will be stuck in boot animation
if you made backup with pin see the main OOS guide it has instructions how to remove pin after twrp restore
from twrp
Dont do any wipes before or after restoring data from twrp only magisk with verity zip is required if you had root
i always use the twrp bluespark as i had issues with stock twrp
thia methodology has worked always for me
best of luck
Click to expand...
Click to collapse
Thanks buddy, It worked like a charm.
About the pin removal, as you siad there is a good tutorial in below link which can be used.
https://www.howtogeek.com/240657/how-to-fix-pin-errors-after-restoring-from-twrp-android-backups/

Thank you!!!
You saved my phone (and life).
I can confirm your procedure is working with my back up made on 10.3.2 using a usb c key.
I just restored the DATA. Nothing else!
Thank you so much!
kingwicked said:
well i have found new method which works every time
if stuck in boot animation
1. install the version stock OOS e.g 6.0.2 of which u have backup as well. again oem unlock process
2. install twrp
3 . reboot twrp
4.instal verity for phone being always decrypted
5. install magisk
6. reboot into system once
if you still have twrp
6 reboot to twrp
8. restore ONLY Data from twrp backup of SAME rom.
9. install twrp
10 reboot twrp install verity zip and magisk
remember
both rom installed and backup have to be of same OS. for e.g OOS 6.0.2 stable. only same backup can be restored as they have same security patch date
if you have a backup of for example OOS 5.1.11 then only rest ore data on a 5.1.11 rom
and flash magisk after backup restoee if ur backup had magisk. otherwise you will be stuck in boot animation
if you made backup with pin see the main OOS guide it has instructions how to remove pin after twrp restore
from twrp
Dont do any wipes before or after restoring data from twrp only magisk with verity zip is required if you had root
i always use the twrp bluespark as i had issues with stock twrp
thia methodology has worked always for me
best of luck
Click to expand...
Click to collapse

Files are gibberish

I was on Havoc OS and tried to go back to stable OS throught TWRP. The plan was to flash stock OOS 9.04 then TWRP blu spark then reboot to recovery again and flash again stock OOS 9.04 and again TWRP and then reboot again to recovery to do a wipe and finally boot up and setup. The problem is that after flashing OOS over Havoc and then TWRP, when I selected to reboot to recovery it did but all files seem to be gibberish. I think this means that the device is encrypted cause when entering TWRP it doesn't ask me for my password. I know that if I do a full wipe it will 99% fix but I want my files in data/media. Is there a solution???
Please help!

I had this happen to me after a failed rom update, all the directories were numbers and hex code, there was no way for me to fix it other than flash using the bricktool
Sorry

eltarod said:
I was on Havoc OS and tried to go back to stable OS throught TWRP. The plan was to flash stock OOS 9.04 then TWRP blu spark then reboot to recovery again and flash again stock OOS 9.04 and again TWRP and then reboot again to recovery to do a wipe and finally boot up and setup. The problem is that after flashing OOS over Havoc and then TWRP, when I selected to reboot to recovery it did but all files seem to be gibberish. I think this means that the device is encrypted cause when entering TWRP it doesn't ask me for my password. I know that if I do a full wipe it will 99% fix but I want my files in data/media. Is there a solution???
Please help!
Click to expand...
Click to collapse
Probably because the Security Patch level was higher on Havoc.
You could try flashing Havoc again, but i don't know how since your storage is encrypted ...
Last time i tried this, it failed to boot, and switched slots, booting into the old ROM.
But if you flashed OOS two times, it's impossible.

There must be a way since I know the password to decrypt the files... Right?
I did flash Havoc successfully again with sideload method but doesn't seem to work. Maybe install Gapps too?

Ok so I flashed havoc+gapps. Phone booted up and I was in working condition but folders and files stayed encrypt and can't be moved with PC or anything. Should I give up and go to MsmDownloadTool ?

eltarod said:
Ok so I flashed havoc+gapps. Phone booted up and I was in working condition but folders and files stayed encrypt and can't be moved with PC or anything. Should I give up and go to MsmDownloadTool ?
Click to expand...
Click to collapse
No need to use Msmdownloadtool, you can use fastboot ROM and boot the phone in fastboot mode. You will lose your files as always (the moment the encription broke you lost your key and the files are permanently encripted), but the procedure is much less painful than the Msmdownloadtool.

Just format your internal storage (using format data) in twrp and you can flash oos and boot into the rom without any issues. I do that all the time whenever I need to flash back oos from custome roms. No need for those msmtool or even fastboot rom..

eltarod said:
There must be a way since I know the password to decrypt the files... Right?
I did flash Havoc successfully again with sideload method but doesn't seem to work. Maybe install Gapps too?
Click to expand...
Click to collapse
Did you try flashing Havoc, then going back to TWRP ? I worked for me when i had the issue, having the good ROM flashed and active on the slot allowed me to enter my password in Blu_Spark TWRP.
By the way, MSMDownloadTool will just Format Everything and flash OOS, so if you're stuck, better just flash OOS from recovery and Format Data, same result, less hassle.

You should solve with last beta cause It has the same patch security.

Just boot TWRP recovery through fastboot (via a PC!) , works for me when encryption messes up.
P.S. - Always have a backup before flashing ANYTHING.
---------- Post added at 10:20 AM ---------- Previous post was at 10:15 AM ----------
eltarod said:
Ok so I flashed havoc+gapps. Phone booted up and I was in working condition but folders and files stayed encrypt and can't be moved with PC or anything. Should I give up and go to MsmDownloadTool ?
Click to expand...
Click to collapse
If my last post before doesn't work, try switching boot slots.

Thanks for all the replies. Didn't have the time to try what all of you suggested. Finally I formated everything and lost a couple of things but I couldn't stay without a phone.

[TWRP][OFFICIAL] TWRP 3.3.x for UMIDIGI One Max [MT6763]

This TWRP recovery is compiled from source & not official yet
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Code:
#include <std_disclaimer.h>
/*
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
Prerequisites
1. Unlocked bootloader.
Bugs
1. No bugs
2. If you have found a bug, please consider posting it to my GitHub Issues.
Instructions
1. Go to the fastboot mode.
2. Download the recovery.img and transfer it to the adb folder.
3. Open the cmd/terminal and change directory into the adb folder.
4. Now confirm/check that device is connected by typing:-
Code:
fastboot devices
If you got your device seriel number there then you are ready to continue otherwise try connecting device again and make sure USB debugging is on and you have granted permission to the PC to debug.
5. After that we will flash this TWRP recovery to the recovery partition by below command:-
Code:
fastboot flash recovery twrp-name.img
BooM ! TWRP flashed successfully.
6. Now unplug your device and then hold power button untill the phone turned off,after that press power button while holding vol down(-) button simultaneously and you will boot into TWRP recovery mode.
Enjoy !
Downloads
Official TWRP Website : https://twrp.me/umidigi/onemax.html
GitHub Release : Here (release name : TWRP-UMIDIGI-One_Max)
Version Information
ROM OS Version: 8.1.x Oreo
Source Code: Device Tree
Based On: TWRP
Credits
Omni Team for minimal TWRP source
@chankruze (myself) for device tree and compilation.
SUPPORT
Official Telegram Group
Official Telegram Channel

Hey ! Good job ! I tried building my own TWRP today but then noticed someone already did it ! Does encryption work ? I cant seem to decrypt the partition after flashing your TWRP.
EDIT : Couldn't wait, ended up formatting with encryption disabled via a zip + magisk
I've then proceeded to flash some GSI for Android 9 (even tried Q Beta 3) and if we want 9.0 one day, some heavy work will be needed : Cellular doesn't work; other than that, it all seems fine to me, camera is only 12mpx, front is 13mpx. Haven't tested more, i'm back to stock
EDIT 2: After comparing camera from stock and gsi, GSI wins easily. The camera is not as slow as stock.

Are there any decent ROMs yet for this phone? LineageOS would be fantastic.

@kgoerbig not to my knowledge. Maybe I'll try porting a 9.0 GSI soon.

I'm not sure if this is helpful or not, but Umidigi posts stock ROM on there forum. Can ROMs be ported based on there code? Or is it more complicated then that?
https://community.umidigi.com/m/?a=viewthread&tid=18692

_cab13_ said:
Hey ! Good job ! I tried building my own TWRP today but then noticed someone already did it ! Does encryption work ? I cant seem to decrypt the partition after flashing your TWRP.
EDIT : Couldn't wait, ended up formatting with encryption disabled via a zip + magisk
I've then proceeded to flash some GSI for Android 9 (even tried Q Beta 3) and if we want 9.0 one day, some heavy work will be needed : Cellular doesn't work; other than that, it all seems fine to me, camera is only 12mpx, front is 13mpx. Haven't tested more, i'm back to stock
EDIT 2: After comparing camera from stock and gsi, GSI wins easily. The camera is not as slow as stock.
Click to expand...
Click to collapse
I have tested LineageOS 16.0 GSI Android 9.0 (and many others ...) and it works well, even GSM and Camera.
The only thing I cannot have is a complete root : I install Magisk 19.3 correctly, but applications cannot get root permission (Titanium Backup cannot have su permission)

Hi to all!!!
I've unlocked bootloader, flashed twrp in post but when I power Off and On+Vol - my device doesn't power up...
Also if I make fastboot reboot recovery, my device reboot in fastboot mode again...
What's wrong??? I would test Descendant_ThreeDotZero_arm64_aonly rom!!!!
Pls Help me!!!!

silviuss82 said:
Hi to all!!!
I've unlocked bootloader, flashed twrp in post but when I power Off and On+Vol - my device doesn't power up...
Also if I make fastboot reboot recovery, my device reboot in fastboot mode again...
What's wrong??? I would test Descendant_ThreeDotZero_arm64_aonly rom!!!!
Pls Help me!!!!
Click to expand...
Click to collapse
If you use the stock boot.img with an GSI system image, it will not boot, you must first flash Magisk.zip before reboot!
It will disable dm-verity, and you can boot after.
If it continue reboot in bootloader mode, use spflashtool to flash a stock rom and all will be right
Or if you have a TWRP backup, restore all partitions except boot/recovery/cache/system/data and you can boot

@ dreambo Can you make a writeup of properly unlocking the bootloader/rooting? Or did you use these methods?
https://community.umidigi.com/forum.php?mod=viewthread&tid=17376
https://www.youtube.com/watch?v=xM_M5XP--Z8&t=176s
I should be receiving my Umidigi One Max in a day or so, and do not want to bork anything up! I have SPflash installed both on a Win10 laptop, and on a Ubuntu Linux machine.
dreambo said:
If you use the stock boot.img with an GSI system image, it will not boot, you must first flash Magisk.zip before reboot!
It will disable dm-verity, and you can boot after.
If it continue reboot in bootloader mode, use spflashtool to flash a stock rom and all will be right
Or if you have a TWRP backup, restore all partitions except boot/recovery/cache/system/data and you can boot
Click to expand...
Click to collapse

kgoerbig said:
@ dreambo Can you make a writeup of properly unlocking the bootloader/rooting? Or did you use these methods?
https://community.umidigi.com/forum.php?mod=viewthread&tid=17376
https://www.youtube.com/watch?v=xM_M5XP--Z8&t=176s
I should be receiving my Umidigi One Max in a day or so, and do not want to bork anything up! I have SPflash installed both on a Win10 laptop, and on a Ubuntu Linux machine.
Click to expand...
Click to collapse
You do not need to unlock you phone, mine is rooted with Magisk and have TWRP installed without unlock bootloader.
Just use spflashtool to flash a stock rom, but replace the recovery by TWRP and the boot.img by magisk_patched.img one.
Here how I do exactly:
1- in my running stock rom, I install MagiskManager and install Magisk by choosing the last option (patch existing boot.img)
2- give it your stock boot.img (extracted from stock rom) and it create for you /sdcard/Download/magisk_patched.img
3- use this to replace your stock boot.img and use also TWRP.img to replace stock recovery.img and flash the whole rom with SPFlashTool

Can you backup with TWRP with a locked bootloader? Isn't write access blocked with a locked bootloader?
dreambo said:
You do not need to unlock you phone, mine is rooted with Magisk and have TWRP installed without unlock bootloader.
Just use spflashtool to flash a stock rom, but replace the recovery by TWRP and the boot.img by magisk_patched.img one.
Here how I do exactly:
1- in my running stock rom, I install MagiskManager and install Magisk by choosing the last option (patch existing boot.img)
2- give it your stock boot.img (extracted from stock rom) and it create for you /sdcard/Download/magisk_patched.img
3- use this to replace your stock boot.img and use also TWRP.img to replace stock recovery.img and flash the whole rom with SPFlashTool
Click to expand...
Click to collapse

kgoerbig said:
Can you backup with TWRP with a locked bootloader? Isn't write access blocked with a locked bootloader?
Click to expand...
Click to collapse
If you can run the TWRP with a locked bootloader (and you can in case of umidigi one max) you can do any thing

dreambo said:
If you can run the TWRP with a locked bootloader (and you can in case of umidigi one max) you can do any thing
Click to expand...
Click to collapse
One last question. =)
Which boot file from stock did you use to patch with?
Downloadable from: https://community.umidigi.com/forum.php?mod=forumdisplay&fid=211
UMIDIGI One Max V1.0
or
UMIDIGI One Max E V1.0

kgoerbig said:
One last question. =)
Which boot file from stock did you use to patch with?
Downloadable from: https://community.umidigi.com/forum.php?mod=forumdisplay&fid=211
UMIDIGI One Max V1.0
or
UMIDIGI One Max E V1.0
Click to expand...
Click to collapse
I have used the European one, UMIDIGI One Max E V1.0

So I just received my One Max today. I was able to patch the boot image, and root the phone. I also, installed TWRP, but I'm running into an issue. From TWRP, I formatted with a normal wipe, It asked "Do you want to do this, it wipes data encryption Etc". I typed yes, and it did it's thing. Rebooted. Setup my basic settings on the phone. I rebooted back into TWRP, and it immediatly asked for a "decryption" password. It also won't allow me to mount internal partitions or sdcard. This even after I rooted via a patched boot file, and verified root access while booted in android (with root verify app). What am I doing wrong for TWRP to gain access to storage?

"Couldn't wait, ended up formatting with encryption disabled via a zip + magisk"
How did you format without encryption? I try to format from TWRP, type 'yes' , to verify, and encryption is still active. I'd like to disable encryption, so that I can properly backup everything from TWRP.

kgoerbig said:
So I just received my One Max today. I was able to patch the boot image, and root the phone. I also, installed TWRP, but I'm running into an issue. From TWRP, I formatted with a normal wipe, It asked "Do you want to do this, it wipes data encryption Etc". I typed yes, and it did it's thing. Rebooted. Setup my basic settings on the phone. I rebooted back into TWRP, and it immediatly asked for a "decryption" password. It also won't allow me to mount internal partitions or sdcard. This even after I rooted via a patched boot file, and verified root access while booted in android (with root verify app). What am I doing wrong for TWRP to gain access to storage?
Click to expand...
Click to collapse
Search in xda forum a zip that you can flash with TWRP before installing the Magisk zip from TWRP.
its name is disable_dm_verity????.zip, it disable in the boot.img the encryption.
After that format the data partition (format and not wipe, it's important!) and reboot normally, and your data partition will not be encrypted

dreambo said:
Search in xda forum a zip that you can flash with TWRP before installing the Magisk zip from TWRP.
its name is disable_dm_verity????.zip, it disable in the boot.img the encryption.
After that format the data partition (format and not wipe, it's important!) and reboot normally, and your data partition will not be encrypted
Click to expand...
Click to collapse
I eventually found all the correct files to remove encryption. I also installed AOSP. I'm kind of torn between the stock and AOSP. AOSP has better performance, but one annoying aspect is that I cannot find anywhere in the settings to switch the navigation buttons in AOSP (Back button is on the far left, I like it on the right side). Seems trivial, but it's annoying. I can now fully backup & restore in TWRP, which makes life a lot easier.

kgoerbig said:
I eventually found all the correct files to remove encryption. I also installed AOSP. I'm kind of torn between the stock and AOSP. AOSP has better performance, but one annoying aspect is that I cannot find anywhere in the settings to switch the navigation buttons in AOSP (Back button is on the far left, I like it on the right side). Seems trivial, but it's annoying. I can now fully backup & restore in TWRP, which makes life a lot easier.
Click to expand...
Click to collapse
Which AOSP ? where do you found it ?

dreambo said:
Which AOSP ? where do you found it ?
Click to expand...
Click to collapse
This thread:
https://forum.xda-developers.com/android/development/umidigi-one-max-custom-rom-modding-t3942521
This Rom
https://github.com/phhusson/treble_experimentations/releases
Do a complete backup of stock from TWRP onto microsd or USB first! System, data, modem, nvram partitions etc. That way you can restore from TWRP, and not lose os, data, or nvram (IMEI).
Specifically, system-arm64-aonly-gapps-su.img.xz
1. Download and extract file you downloaded, onto your phone.
2. Do a format (type yes)
3. Install from TWRP as "image".

[Q] DM-Verity

Hey. Does anyone know in what ways dm verity can be a problem? Like boot problems or anything else?
Since the preserve dm verity box in magisk has been checked for me fore some reason I don't know (but it happened after updating TWRP) and I can't seem to disable it with the disable dm-verity script and I'm worried now that with the next OOS Ota my device won't boot or something?
Does anyone have the knowledge to clarify this for me? It would be very much appreciated :angel:

kewinhw said:
Hey. Does anyone know in what ways dm verity can be a problem? Like boot problems or anything else?
Since the preserve dm verity box in magisk has been checked for me fore some reason I don't know (but it happened after updating TWRP) and I can't seem to disable it with the disable dm-verity script and I'm worried now that with the next OOS Ota my device won't boot or something?
Does anyone have the knowledge to clarify this for me? It would be very much appreciated :angel:
Click to expand...
Click to collapse
No problems for me here nothing but smiles. It will auto uncheck but first you need to format data and flash verity_op6.zip and magisk after :good:

Blunts47 said:
No problems for me here nothing but smiles. It will auto uncheck but first you need to format data and flash verity_op6.zip and magisk after :good:
Click to expand...
Click to collapse
Do I need to format data again? When I first flashed to get the setup I have now I did a clean flash and disable dmcerity+forceencrypt script along with it. And both preserve forceencryption and dm verity were unchecked. Then I installed the new 3.3.1-0 TWRP that's when preserve dm verity got checked again.
The order was: TWRP - > magisk then I saw when flashing magisk progress it said keep dm verity so I flashed the script. And it was still showing checked dm verity. So you mean that with next OOS ota it will get unchecked or do you mean that with next ota I need to do format data?

kewinhw said:
Do I need to format data again? When I first flashed to get the setup I have now I did a clean flash and disable dmcerity+forceencrypt script along with it. And both preserve forceencryption and dm verity were unchecked. Then I installed the new 3.3.1-0 TWRP that's when preserve dm verity got checked again.
The order was: TWRP - > magisk then I saw when flashing magisk progress it said keep dm verity so I flashed the script. And it was still showing checked dm verity. So you mean that with next OOS ota it will get unchecked or do you mean that with next ota I need to do format data?
Click to expand...
Click to collapse
These are my steps and worked perfectly for me for about a month.
1. Flash OOS, TWRP, reboot recovery
2. Flash OOS, TWRP, reboot recovery
3. Flash havoc, TWRP, reboot recovery
4. Flash havoc, TWRP, reboot recovery
5. Flash gapps, magisk
6. Flash No_Verity_Mod_For_OP6.zip
7. Reboot System

Blunts47 said:
You are making it more complicated than it is. Just use blue spark twrp 9.91 or whatever, then after you have twrp and OOS on both slots format data in twrp reboot to recovery once then flash no_verity-op6.zip and flash magisk right after and you are good to go. Nothing else is needed.
Click to expand...
Click to collapse
As per thread tutorial https://forum.xda-developers.com/oneplus-6/how-to/tutorial-decrypt-flash-rom-pie-oreo-roms-t3838643 always flash no verity mod last, before rebooting to system. But if your procedure still worked, no question with that.
Just follow strictly the instructions and you will not fail. (As per my experience)

tiga016 said:
As per thread tutorial https://forum.xda-developers.com/oneplus-6/how-to/tutorial-decrypt-flash-rom-pie-oreo-roms-t3838643 always flash no verity mod last, before rebooting to system. But if your procedure still worked, no question with that.
Just follow strictly the instructions and you will not fail. (As per my experience)
Click to expand...
Click to collapse
**** that's what I meant sorry! been a long day and been a few weeks since i followed that guide.

Blunts47 said:
These are my steps and worked perfectly for me for about a month.
1. Flash OOS, TWRP, reboot recovery
2. Flash OOS, TWRP, reboot recovery
3. Flash havoc, TWRP, reboot recovery
4. Flash havoc, TWRP, reboot recovery
5. Flash gapps, magisk
6. Flash No_Verity_Mod_For_OP6.zip
7. Reboot System
Click to expand...
Click to collapse
tiga016 said:
As per thread tutorial https://forum.xda-developers.com/oneplus-6/how-to/tutorial-decrypt-flash-rom-pie-oreo-roms-t3838643 always flash no verity mod last, before rebooting to system. But if your procedure still worked, no question with that.
Just follow strictly the instructions and you will not fail. (As per my experience)
Click to expand...
Click to collapse
I looked in the other thread and it said remove lock screen security so I did and I flashed the disable dm verity forceencrypt script followed by magisk and now preserve dm verity is unchecked horray :victory: