Database Users

Cm12.1 optimized

Hi.
I am not quite sure how to proceed even after going through some threads.
I've got Antares CM12.1 (12.1-20150428-NIGHTLY-jfltexx) on my S4 GT-I9505 plus
CWM v6.0.4.4
Does it make sense to upgrade to CM12.1 optimized or wait for the final version?
It is recommended to use TWRP Recovery v2.8.6.0 instead of CWM.
Can I just flash the TWRP zip via CWM and It'll be fine? (TWRP replaces CWM?)
I don't want to do a clean install, just upgrade.
Thanks!

PePeMoke said:
Hi.
I am not quite sure how to proceed even after going through some threads.
I've got Antares CM12.1 (12.1-20150428-NIGHTLY-jfltexx) on my S4 GT-I9505 plus
CWM v6.0.4.4
Does it make sense to upgrade to CM12.1 optimized or wait for the final version?
It is recommended to use TWRP Recovery v2.8.6.0 instead of CWM.
Can I just flash the TWRP zip via CWM and It'll be fine? (TWRP replaces CWM?)
I don't want to do a clean install, just upgrade.
Thanks!
Click to expand...
Click to collapse
It's not really an upgrade. They are different roms. Sure, they are both by the same developer. But on is stock AOSP and one has Optimizations to make it faster and smoother, I guess.
Doing a clean installation is recommended to avoid issues and bugs. You can, of course, dirty flash, but don't complain about problems
I would recommend you TWRP. It's easier to use and I haven't had any problems with it so far. I use version 2.8.3.0.
Flashing it using the zip should be fine.

GDReaper said:
It's not really an upgrade. They are different roms. Sure, they are both by the same developer. But on is stock AOSP and one has Optimizations to make it faster and smoother, I guess.
Doing a clean installation is recommended to avoid issues and bugs. You can, of course, dirty flash, but don't complain about problems
I would recommend you TWRP. It's easier to use and I haven't had any problems with it so far. I use version 2.8.3.0.
Flashing it using the zip should be fine.
Click to expand...
Click to collapse
Thanks mate!
The TWRP Recovery v2.8.6.0 I've got installed will convert to F2FS automatically?
Because in the instructions it says "To convert cache and data partitions to F2FS look in post above post."
But in the next line it says "System partition is automatically converted to F2FS at ROM's installation"
So I just flash the ROM via TWRP and it will do so?

PePeMoke said:
Thanks mate!
The TWRP Recovery v2.8.6.0 I've got installed will convert to F2FS automatically?
Because in the instructions it says "To convert cache and data partitions to F2FS look in post above post."
But in the next line it says "System partition is automatically converted to F2FS at ROM's installation"
So I just flash the ROM via TWRP and it will do so?
Click to expand...
Click to collapse
F2FS is optional. You don't have to convert. You can just flash it with your default file system (ext4).
But you if do want to convert and flash that rom, then use the recovery provided by the rom developer. There is a link in the thread that takes you to a modified version of TWRP I think
Note: Converting will wipe the internal memory..

GDReaper said:
F2FS is optional. You don't have to convert. You can just flash it with your default file system (ext4).
But you if do want to convert and flash that rom, then use the recovery provided by the rom developer. There is a link in the thread that takes you to a modified version of TWRP I think
Note: Converting will wipe the internal memory..
Click to expand...
Click to collapse
Ok got that.
I flashed the suggested TWRP for that ROM.
But it says in red "System partition is automatically converted to F2FS at ROM's installation"
So doesn't that mean that it will do the converting anyway?
It's the Antares cm12.1 optimized build by the way.

PePeMoke said:
Ok got that.
I flashed the suggested TWRP for that ROM.
But it says in red "System partition is automatically converted to F2FS at ROM's installation"
So doesn't that mean that it will do the converting anyway?
It's the Antares cm12.1 optimized build by the way.
Click to expand...
Click to collapse
As I said, using the TWRP recovery suggested by the developer will convert your file system to F2FS.
IF you WANT to convert, use that one.
IF you DO NOT WANT to convert, then download TWRP from their site or somewhere else. One that is not modified

GDReaper said:
As I said, using the TWRP recovery suggested by the developer will convert your file system to F2FS.
IF you WANT to convert, use that one.
IF you DO NOT WANT to convert, then download TWRP from their site or somewhere else. One that is not modified
Click to expand...
Click to collapse
The OP is right, my 12.1 Optimized automatically converts /system to F2FS at ROM's installation. I will soon revert this to let the user choose between ext4 and F2FS and to fix installation issues on recoveries that don't have mkfs.f2fs binary inside ramdisk
TWRP 2.8.6.0 is suggested because it has the maximum compatibility with Android 5.1
Differences between official TWRP and my F2FS-compatible? Just a plus: management support for this file system, the other things are identical
Inviato dal mio GT-I9505

AntaresOne said:
The OP is right, my 12.1 Optimized automatically converts /system to F2FS at ROM's installation. I will soon revert this to let the user choose between ext4 and F2FS and to fix installation issues on recoveries that don't have mkfs.f2fs binary inside ramdisk
TWRP 2.8.6.0 is suggested because it has the maximum compatibility with Android 5.1
Differences between official TWRP and my F2FS-compatible? Just a plus: management support for this file system, the other things are identical
Inviato dal mio GT-I9505
Click to expand...
Click to collapse
I know he's right.
I was just trying to figure out if he really wants to convert or not.
To me it seemed as if he thought F2FS is obligatory in order to run your rom. So I made sure he gets the point that it isn't

AntaresOne said:
The OP is right, my 12.1 Optimized automatically converts /system to F2FS at ROM's installation. I will soon revert this to let the user choose between ext4 and F2FS and to fix installation issues on recoveries that don't have mkfs.f2fs binary inside ramdisk
TWRP 2.8.6.0 is suggested because it has the maximum compatibility with Android 5.1
Differences between official TWRP and my F2FS-compatible? Just a plus: management support for this file system, the other things are identical
Inviato dal mio GT-I9505
Click to expand...
Click to collapse
Thank you for the answer first of all.
I wanted to root my device again after the 12.1 optimized build installed,
but when I flash the matching tar file (cf-autoroot bye chainfire) via Odin SuperSU is not installed and
when I download it from the playstore it cannot update the binary..
you know why is that?

Ok I've got root access by installing the SUperSU update via TWRP.
But why doesn't it work the other way?
I had no problems with doing so in your 12.1 nightly..
Bye the way, great ROMs!!

PePeMoke said:
Ok I've got root access by installing the SUperSU update via TWRP.
But why doesn't it work the other way?
I had no problems with doing so in your 12.1 nightly..
Bye the way, great ROMs!!
Click to expand...
Click to collapse
The rom is already rooted. But you have to enable root first. The rom developer (AntaresOne in this case) posted instructions in the rom thread on how to do that.
But installing SuperSU from the market or via a flashable zip is also good. I've had problems with the CM Superuser app.

PePeMoke said:
Thank you for the answer first of all.
I wanted to root my device again after the 12.1 optimized build installed,
but when I flash the matching tar file (cf-autoroot bye chainfire) via Odin SuperSU is not installed and
when I download it from the playstore it cannot update the binary..
you know why is that?
Click to expand...
Click to collapse
CF auto-root is only for stock rom. It's NOT for CM 12.1. I would reflash CM 12.1 without wiping just to make sure CF auto-root is gone.
Every CM rom contains root. You just have to enable it like GDReaper told you.

Thanks guys!
Runs smooth and I have root access via cm.

[Q] error excecuting updater binary in zip with twrp

hi guys when I try to flash a rom appears the message "error excecuting updater binary in zip" someone know how to solve it?
Sorry for my bad english

Your English is fine. Check to make sure there are no spaces in the file name, and if there are, replace them with dashes or underscores. Then try running the zip again.

Strephon Alkhalikoi said:
Your English is fine. Check to make sure there are no spaces in the file name, and if there are, replace them with dashes or underscores. Then try running the zip again.
Click to expand...
Click to collapse
there is no space in the name :\ maybe can be a problem of the recovery's version ?

I mentioned it because the presence of spaces was the reason my copy of Optimized CM12 failed to install. What version of TWRP are you running?

2.8.5.0

Upgrade. 2.8.6.0 is available from the TWRP homepage (once the page comes back up), though I believe a customized copy is available for Alucard and Antares One's Optimized CM12 build in I9505 Original Android Development.
EDIT: 2,8.6.0 can be downloaded from here.

AntaresOne's TWRP will convert the system to F2FS automatically when flashing a rom. He said he was going to make it a choice in a future update. Don't know if he gotten around doing so.

GDReaper said:
AntaresOne's TWRP will convert the system to F2FS automatically when flashing a rom. He said he was going to make it a choice in a future update. Don't know if he gotten around doing so.
Click to expand...
Click to collapse
This problem started when I tried to flash cyano 12 based on 5.1.1 (by AntaresOne) before doing this everything was fine. Maybe the recovery couldn't convert system to F2FS, can be this?

Strephon Alkhalikoi said:
Upgrade. 2.8.6.0 is available from the TWRP homepage (once the page comes back up), though I believe a customized copy is available for Alucard and Antares One's Optimized CM12 build in I9505 Original Android Development.
EDIT: 2,8.6.0 can be downloaded from here.
Click to expand...
Click to collapse
Thank you, I will try it

eleonora97100 said:
Thank you, I will try it
Click to expand...
Click to collapse
It doesn't necessarily needs to be converted. It can run with the default ext4 too. Problem with converting is that it will wipe your internal storage. So that into account.

I had the binary updater issue occur on a flashable zip I made. The cause? I accidentally deleted the line that told TWRP to mount the system partition. Restoring the line solved the issue, so check the script. The developer may have accidentally missed a line.

thank you guys I upgraded the recovery and now it works fine thank you very much

[GUIDE][6045]How to Restore Android MM TWRP BACKUP

Hello Everyone
This is A Guide how to restore the TWRP BACKUP OF ANDROID 6.0 Marshallow for Idol 3 5.5
They are TWO Backups of MM 6045i update
1.Here's Marionette Backup (System Img,Boot img,Data)
2.Here's Masterdex Backup(System Img,Boot img)
1. First of all you must install TWRP on your Idol 3 5.5", Link for TWRP
2.Download and unpack archive in a separate folder
3.Boot in TWRP and make backup of your current firmware
4.. Make Wipe through TWRP menu
5.After you make your backup on external microSD or USB-OTG
TWRP -> Backups -> xxxxyyyy,
(xxxxyyyy is a "number", It's unique for each device.)
6.Copy this folder 2016-06-17--13-51-57_MMB29M_release-keys from archive to xxxxyyyy folder on microSD or USB-OTG and choose Restore in TWRP.
After finished Restoring you need new partitions to work System (if you don't flash the system will not boot )..so they are two zips flash it !
Here's ZIP by me
It takes 15-20 minutes to Boot
Thats all,Enjoy
Credits:
Thanks to @Famewolf @The Marionette and @masterdex for TWRP BACKUP​

Thanks Alex, now we have fully functional android 6.0.1 on our devices.
WIFI and BT works, android 6.0.1 is very fast, almost no lag os.

Well, So @Alek Dev I have a question
If we flash the new partition zip to make the system boot, we won't be able to restore any 5.0.2 backup, since the partitions layout will have changed?
Why do we flash this zip after having restored? I seems illogical to me. Since the system will have been restored, don't the zip risk to cause the system being erased? I just need explanation for that

frankee207 said:
Well, So @Alek Dev I have a question
If we flash the new partition zip to make the system boot, we won't be able to restore any 5.0.2 backup, since the partitions layout will have changed?
Why do we flash this zip after having restored? I seems illogical to me. Since the system will have been restored, don't the zip risk to cause the system being erased? I just need explanation for that
Click to expand...
Click to collapse
If you flash the Zip system will Boot and work....You can restore Twrp backup of 5.0.2 If you don't flash the System will not boot.The zip has included new partitions..There's no RISK about installing...

Alek Dev said:
If you flash the Zip system will Boot and work....You can restore Twrp backup of 5.0.2 If you don't flash the System will not boot.The zip has included new partitions..There's no RISK about installing...
Click to expand...
Click to collapse
Yes, I have understood that well. I was just wondering that if the partition layout has changed, which seems to be the case, I don't understand how we can go back to 5.0.2, wich doesn't use the same partitions. And as far as I know, the partitions layout are not backed up when backing up.
And be reassured, I DO believe you when you say it works it's just the point above I am wondering about. If could explain to me...

frankee207 said:
Yes, I have understood that well. I was just wondering that if the partition layout has changed, which seems to be the case, I don't understand how we can go back to 5.0.2, wich doesn't use the same partitions. And as far as I know, the partitions layout are not backed up when backing up.
And be reassured, I DO believe you when you say it works it's just the point above I am wondering about. If could explain to me...
Click to expand...
Click to collapse
Twrp works so if you have Twrp backup you can restore or Mobile upgrade q or Panasonic Firmware Tool can restore you back....if you restore Twrp backup .of 5.0.2 the system will work good with newer partitions... So you will can't have any problems ??

Will this work on the 60450 Cricket phones.

Jimhackthorn said:
Will this work on the 60450 Cricket phones.
Click to expand...
Click to collapse
Yes works with every model

Root?

MoRRLiNsS said:
Root?
Click to expand...
Click to collapse
https://download.chainfire.eu/751/SuperSU/
Just flash it with Twrp !

Dosent work anyway dude gonna wait for a real dev to release MM

MoRRLiNsS said:
Dosent work anyway dude gonna wait for a real dev to release MM
Click to expand...
Click to collapse
You must do something wrong ..even Masterdex solved the problem with MM...

Alek Dev said:
You must do something wrong ..even Masterdex solved the problem with MM...
Click to expand...
Click to collapse
I think its because it cant mount system for some reason it mounts it when it wants

MoRRLiNsS said:
I think its because it cant mount system for some reason it mounts it when it wants
Click to expand...
Click to collapse
Go to twrp go to WIpe then Advanced Wipe then select system and then Repair or change system and then Repair file system
and then read again the thread and try again!

WIFI Not Working
My WiFi is not working I have Cricket 60450 model I just flashed and it works great fast smooth and stable only problem is my WiFi does not work it could be the baseband. is there a flashable baseband for this or please let me know if there is a fix for it. This is the 6045i model and could be the problem different baseband the the 60450 cricket model please help alek dev and thanks for your support.

Jimhackthorn said:
My WiFi is not working I have Cricket 60450 model I just flashed and it works great fast smooth and stable only problem is my WiFi does not work it could be the baseband. is there a flashable baseband for this or please let me know if there is a fix for it. This is the 6045i model and could be the problem different baseband the the 60450 cricket model please help alek dev and thanks for your support.
Click to expand...
Click to collapse
I had the same issues with wifi but try again with this thread ..for me helped and i'm having WIFI AND BT ON MY IDOL 3 with MM
Here's instructions
1.,WIPE EVERYTHING
2.Download and Flash this
3.Restore one of the Backups
4.And Reboot

wifi and BT still not working
I still don't have wifi working i flashed the partitions but it want mount them it seems like the baseband may be incompatible becouse this is for the international version the rom works great but there needs be flashable partition for the baseband that is comparable with the 60450 cricket model the rom works great if i could get the right flashable partitions becouse the one that you told me to try alek dev does not mount. I have picture but i am not able to add a picture in the post or attachment here below is the error it is generating if you have way for me to send the picture to you i will send it so you are able to see the problem. thanks and i hope this can be solved for all cricket models.
unmount of /persist failed; no such volume
unmount of /system failed; no such volume​

Jimhackthorn said:
I still don't have wifi working i flashed the partitions but it want mount them it seems like the baseband may be incompatible becouse this is for the international version the rom works great but there needs be flashable partition for the baseband that is comparable with the 60450 cricket model the rom works great if i could get the right flashable partitions becouse the one that you told me to try alek dev does not mount. I have picture but i am not able to add a picture in the post or attachment here below is the error it is generating if you have way for me to send the picture to you i will send it so you are able to see the problem. thanks and i hope this can be solved for all cricket models.
unmount of /persist failed; no such volume
unmount of /system failed; no such volume​
Click to expand...
Click to collapse
Send me PM i will try to help you

wifi and BT still not working
Here is the picture of it failing to mount.

Jimhackthorn said:
Here is the picture of it failing to mount.
Click to expand...
Click to collapse
Before installing unmount system and try again?

[Deprecated] Universal DM-Verity, ForceEncrypt, Disk Quota Disabler [11/2/2020]

Hi all!
For the past couple of months, I've been looking into making a more universal solution to disable dm-verity and forceencrypt. Needing to take different zips, modify them for different devices, and then cross your fingers when you switch between custom and stock roms simply wasn't good enough for me. After lots of searching around, failed attempts, and some guidance by @Xennet, @osm0sis, and @nathanchance (thank you all for your help), I finally got a working solution. Ironically, it was under my nose the whole time.
@topjohnwu figured much of this out a while ago with his magiskboot binary - just modify the fstabs. Magiskboot only works for fstabs in the ramdisk though and dm-verity and forceencrypt are only disabled under certain conditions (when you create a .magisk file with the variables set to false and place it in the proper location). So I made an installker with AK3 by @osm0sis and used a combination of sed patches by @jcadduono in addition to others I found for fstabs not in the ramdisk, modified magiskboot with some extra entries I found need to be removed on some devices, and added some stuff of my own like the creation of .magisk and .supersu files in the right location with the proper contents.
The end result: a zip that will remove dm-verity and/or forceencrypt from all fstabs on your device
It can also remove disk quota if you choose. This may be needed if you have an older twrp and/or want to downgrade to Nougat. More info here: https://source.android.com/devices/storage/faster-stats
Instructions:
The zipname tells the installer what to do. Here are the current options:
Add 'enfec' or en'forceencrypt' to zipname to keep forceencrypt enabled if present
Add 'fec' or 'forceencrypt' to zipname to disable forceencrypt (zipname already has this so remove these if you want to keep it enabled)
Add 'quota' to zipname to disable disc quota
Note that verity is always disabled - it has to be for any modifications with this mod
If you're currently encrypted:
BACKUP YOUR INTERNAL STORAGE TO YOUR PC
Format data (this is NOT the same as Wipe data) (In TWRP: Wipe -> Format Data)
Reboot back into recovery
Follow the directions below for when you're not encrypted
If you're not encrypted: flash all of your stuff, then FLASH THIS ZIP LAST
Some extra details for Slot devices:
Flash ROM
Flash TWRP Installer Zip
Reboot into TWRP
Flash everything else
Flash this zip
Only difference here is the twrp zip and the recovery reboot, main principle is the same - FLASH THIS ZIP LAST
Troubleshooting:
Take a recovery log after flashing this zip (thanks to @aIecxs for the imgs):
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If the zip isn't patching any fstabs that it should be, then it's possible that the previous zip(s) didn't unmount system and/or vendor properly. Either unmount them in twrp, or just reboot back into recovery and flash this zip again
Compatibility: Any android device
Source: https://github.com/Zackptg5/Disable_Dm-Verity_ForceEncrypt
Download

Zackptg5 said:
Hi all!
For the past couple of months, I've been looking into making a more universal solution to disable dm-verity and forceencrypt. Needing to take different zips, modify them for different devices, and then cross your fingers when you switch between custom and stock roms simply wasn't good enough for me. After lots of searching around, failed attempts, and some guidance by @Xennet, @osm0sis, and @nathanchance (thank you all for your help), I finally got a working solution. Ironically, it was under my nose the whole time.
@topjohnwu figured much of this out a while ago with his magisk installer. However, dm-verity and forceencrypt (fec) are only disabled under certain conditions (when you create a .magisk file with the variables set to false and place it in the proper location). This would be fine for magisk users, but not for everyone else. So I took Magisk 16.6 beta zip, modified it to add fstab patches by @jcadduono, added some stuff of my own, and then gutted all of the magisk stuff unrelated to this.
The end result: a zip that will remove dm-verity and fec from your boot img and fstab files (without installing magisk, I took all of that out).
Instructions:
If you're currently encrypted: BACKUP YOUR INTERNAL STORAGE TO YOUR PC. Then format data. Reboot back into recovery
After doing that or if you're not encrypted: Flash your rom, custom kernel and/or root (like magisk or supersu), then this zip.
This zip should probably be flashed after anything that modifies your boot img (magisk, supersu, other root solutions, custom kernel, etc.).
Compatibility: Any device magisk is compatible with
Source:https://github.com/Zackptg5/Disable_Dm-Verity_FEC
Click to expand...
Click to collapse
Hi!
Just to be sure, does this remove the need to flash patched boot.img files when updating stock ROMs with root?
Thanks!
Sent from my OnePlus 3T using XDA Labs

@Zackptg5 Thanks for the zip! I trust this will work for both -- Treble and non-Treble ROMs, yes?

rippledrums said:
Hi!
Just to be sure, does this remove the need to flash patched boot.img files when updating stock ROMs with root?
Thanks!
Click to expand...
Click to collapse
Not sure what you mean. This does patch the boot img to remove verity/fec though if that's what you're getting at
shadowstep said:
@Zackptg5 Thanks for the zip! I trust this will work for both -- Treble and non-Treble ROMs, yes?
Click to expand...
Click to collapse
Yup

Zackptg5 said:
Not sure what you mean. This does patch the boot img to remove verity/fec though if that's what you're getting at
Click to expand...
Click to collapse
I found this because I saw your post in @Xennet's thread for OP3/3T Oxygen OS patched boot.img files.
Currently every time I update OOS I flash a boot.img patched by him and also a zip by him as well. What I'm asking is if your zip would be enough?
Sent from my OnePlus 3T using XDA Labs

rippledrums said:
I found this because I saw your post in @Xennet's thread for OP3/3T Oxygen OS patched boot.img files.
Currently every time I update OOS I flash a boot.img patched by him and also a zip by him as well. What I'm asking is if your zip would be enough?
Click to expand...
Click to collapse
Oh, gotcha. Ya, this zip handles that so you don't need to flash the boot img anymore

Zackptg5 said:
Oh, gotcha. Ya, this zip handles that so you don't need to flash the boot img anymore
Click to expand...
Click to collapse
Awesome, thanks! :laugh:
Sent from my OnePlus 3T using XDA Labs

@Zackptg5 First of all, great job. This looks very impressive and I appreciate the work you've done. I know this will be very useful for people trying things like the P GSI image then going back to no treble ROMs back on Oreo. I was just wondering though, as I have no intention on trying any treble ROMs, is there any benefit to using this over the old no verity V2 zip for someone that will only use non-treble Oreo ROMs. Thank you

DEVILOPS 007 said:
@Zackptg5 First of all, great job. This looks very impressive and I appreciate the work you've done. I know this will be very useful for people trying things like the P GSI image then going back to no treble ROMs back on Oreo. I was just wondering though, as I have no intention on trying any treble ROMs, is there any benefit to using this over the old no verity V2 zip for someone that will only use non-treble Oreo ROMs. Thank you
Click to expand...
Click to collapse
It really depends on the rom. If you're on a custom rom the old zip is probably fine (but not always, lots of variation there). If you're on a stock or stock based rom however, this is needed (unless you flash a patched boot.img - but why flash 2 things when you can flash 1?). This zip works with treble and nontreble roms by the way and the old zip can be easily modified the same way (I have one floating around xda somewhere).
Assuming you're on a custom rom which already has dm-verity disabled, the benefit to this zip is that not only does it disable force encryption in the vendor fstabs (like the old zip), but it also disables it in the boot img which some roms have

Zackptg5 said:
It really depends on the rom. If you're on a custom rom the old zip is probably fine (but not always, lots of variation there). If you're on a stock or stock based rom however, this is needed (unless you flash a patched boot.img - but why flash 2 things when you can flash 1?). This zip works with treble and nontreble roms by the way and the old zip can be easily modified the same way (I have one floating around xda somewhere).
Assuming you're on a custom rom which already has dm-verity disabled, the benefit to this zip is that not only does it disable force encryption in the vendor fstabs (like the old zip), but it also disables it in the boot img which some roms have
Click to expand...
Click to collapse
So basically it is a more well-done version if you want to put it that way. Works on stock and custom ROMs including treble no matter what it is or if there is dm-verity enabled or not is what I'm understanding from this. I'm using treskmod currently which is basically OmniRom. I'll give it a go when I get back off holiday so I can clean flash. Thanks again?

DEVILOPS 007 said:
So basically it is a more well-done version if you want to put it that way. Works on stock and custom ROMs including treble no matter what it is or if there is dm-verity enabled or not is what I'm understanding from this. I'm using treskmod currently which is basically OmniRom. I'll give it a go when I get back off holiday so I can clean flash. Thanks again?
Click to expand...
Click to collapse
I wouldn't call it more well done but rather more complete
And yup, should work on any rom/device magiskboot is able to work with (which is most of them). Dm-verity will be removed too by this mod by the way

@Zackptg5 hi. Tell me please how need me right do. I am on LOS 15.1 on my Samsung Tab A SM-T585.now. And with dm-verity and fec are all right. But when i go on custom rom based on stock 8.0(port) i got dm-verity and fec issue. After installation this rom and start i can see all files of internal memory in file explorer. But only i reboot to recovery internal memory have size 0mb. So my question: i need do fomat data before installtion rom and your zip or only install zip?

Zackptg5 said:
I wouldn't call it more well done but rather more complete
And yup, should work on any rom/device magiskboot is able to work with (which is most of them). Dm-verity will be removed too by this mod by the way
Click to expand...
Click to collapse
@DEVILOPS 007 I just flashed latest 20180719 tresk and tried this zip and got sent back to TWRP. Immedietly flashed v2 and it booted. It worked on AOSiP earlier though so not sure what could cause it to fail here.
Sent from my OnePlus5T using XDA Labs

repey6 said:
@Zackptg5 hi. Tell me please how need me right do. I am on LOS 15.1 on my Samsung Tab A SM-T585.now. And with dm-verity and fec are all right. But when i go on custom rom based on stock 8.0(port) i got dm-verity and fec issue. After installation this rom and start i can see all files of internal memory in file explorer. But only i reboot to recovery internal memory have size 0mb. So my question: i need do fomat data before installtion rom and your zip or only install zip?
Click to expand...
Click to collapse
You'll need to format data. Then flash rom and kernel, then this after
bdwilk said:
@DEVILOPS 007 I just flashed latest 20180719 tresk and tried this zip and got sent back to TWRP. Immedietly flashed v2 and it booted. It worked on AOSiP earlier though so not sure what could cause it to fail here.
Click to expand...
Click to collapse
Can you send a recovery log? What all did you flash when that happened and in what order? Thanks

Zackptg5 said:
You'll need to format data. Then flash rom and kernel, then this after
Can you send a recovery log? What all did you flash when that happened and in what order? Thanks
Click to expand...
Click to collapse
Format data everytime or just once for this to work or format because of treble or what? I'm curious as to when formatting is required and why exactly.

Zackptg5 said:
You'll need to format data. Then flash rom and kernel, then this after
Can you send a recovery log? What all did you flash when that happened and in what order? Thanks
Click to expand...
Click to collapse
I'll do it again and get a log for you another time.
ROM, magisk 16.6, vanced installer (YouTube), universal dm-verity (ROM has built-in gapps)
Got sent back to TWRP and hit reboot to system one more time for science, and got sent back to TWRP again.
Flashed dm-verity v2 and it booted fine.
OnePlus 5t
DEVILOPS 007 said:
Format data everytime or just once for this to work or format because of treble or what? I'm curious as to when formatting is required and why exactly.
Click to expand...
Click to collapse
I believe he's just telling dude how to decrypt for the first time.
Sent from my OnePlus5T using XDA Labs

bdwilk said:
I'll do it again and get a log for you another time.
ROM, magisk 16.6, vanced installer (YouTube), universal dm-verity (ROM has built-in gapps)
Got sent back to TWRP and hit reboot to system one more time for science, and got sent back to TWRP again.
Flashed dm-verity v2 and it booted fine.
OnePlus 5t
I believe he's just telling dude how to decrypt for the first time.
Click to expand...
Click to collapse
Oh I thought he was responding to you. My bad lol

DEVILOPS 007 said:
Oh I thought he was responding to you. My bad lol
Click to expand...
Click to collapse
Ya, you just need to format data to decrypt

Zackptg5 said:
You'll need to format data. Then flash rom and kernel, then this after
Click to expand...
Click to collapse
This is a copypaste from Samsuyng Tab A thread:
repey6 said:
Hi. You can to try Universal DM-Verity and ForceEncrypt Disabler by Zackptg5 from this thred https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
Click to expand...
Click to collapse
blaz3gamingHD said:
Does this work?
---------- Post added at 09:52 PM ---------- Previous post was at 09:20 PM ----------
I've tested it and it doesn't work, still encrypted.
Click to expand...
Click to collapse

repey6 said:
This is a copypaste from Samsuyng Tab A thread:
Click to expand...
Click to collapse
Of course he's still encrypted this zip isn't going to decrypt your phone. It's for once your decrypted and flashing a rom it will not allow the rom zip to encrypt your device and will allow it to boot decrypted and without the insecure verity check blocking boot.
Sent from my ONEPLUS A5010 using Tapatalk

How to do Android Q GSI Installation

Can someone tell me Completly How to install Android Q GSI Version On Oneplus5. I tried But i went to stock fastboot mode. can't boot.
things i did
1. install mokee rom
2. wipe data, system, Cache
3.flash the image file
4.mount vendor then format data
5. then reboot system.
its went to fastboot mode. is it correct method??

radirajjj said:
Can someone tell me Completly How to install Android Q GSI Version On Oneplus5. I tried But i went to stock fastboot mode. can't boot.
things i did
1. install mokee rom
2. wipe data, system, Cache
3.flash the image file
4.mount vendor then format data
5. then reboot system.
its went to fastboot mode. is it correct method??
Click to expand...
Click to collapse
Hello Radirajjj,
I'm also trying to install it Right now I can't flash the GSI because apparently my phone doesn't support Project Treble. I'm actually using OB29.
Here what I get when I play :
Code:
adb shell getprop ro.treble.enabled
Code:
false
Did you pass this step ?

Khwaja7 said:
Hello Radirajjj,
I'm also trying to install it Right now I can't flash the GSI because apparently my phone doesn't support Project Treble. I'm actually using OB29.
Here what I get when I play :
Did you pass this step ?
Click to expand...
Click to collapse
I installed treble check app, and it says my device support treble.
And just now run this command and it says "True"

radirajjj said:
I installed treble check app, and it says my device support treble.
And just now run this command and it says "True"
Click to expand...
Click to collapse
Ok. Going to install Mokee and check if my device is compatible with Treble too.

Khwaja7 said:
Ok. Going to install Mokee and check if my device is compatible with Treble too.
Click to expand...
Click to collapse
By updating to the newest oos build, your phone will make a vendor partition and support treble...I haven't tried to flash beta 2 due to reported bugs and secured wifi issues, but wiping all data and internal storage, using stock vendor and boot images, you should be able to boot
Someone please correct me if I'm wrong

Khwaja7 said:
Ok. Going to install Mokee and check if my device is compatible with Treble too.
Click to expand...
Click to collapse
did you install?? Treble supported??

There is now a Semi-GSI Q! Should be easier to install. Did anyone tried? (With or without mokee).
https://forum.xda-developers.com/pr...ment/rom-android-p-developer-preview-t3816659

BakedTator said:
By updating to the newest oos build, your phone will make a vendor partition and support treble...I haven't tried to flash beta 2 due to reported bugs and secured wifi issues, but wiping all data and internal storage, using stock vendor and boot images, you should be able to boot
Someone please correct me if I'm wrong
Click to expand...
Click to collapse
I did install the newest stable OOS build, I can see the Vendor partition AND Treble Check app is saying my phone does support Treble. However, the command to check it through ADB is still saying "false".
radirajjj said:
did you install?? Treble supported??
Click to expand...
Click to collapse
I did install Mokee too, but for me it isn't supporting Treble (command to check Treble still saying "false" as well).
furious.builder said:
There is now a Semi-GSI Q! Should be easier to install. Did anyone tried? (With or without mokee).
https://forum.xda-developers.com/pr...ment/rom-android-p-developer-preview-t3816659
Click to expand...
Click to collapse
Thank you, going to give it a try !
Can't tell what I do wrong, if you have any clue please let me know

@Khwaja7, I think that to have a full A/B support through MoKee you have to fully format /Data but for semi GSI I don't think full A/B is required

furious.builder said:
@Khwaja7, I think that to have a full A/B support through MoKee you have to fully format /Data but for semi GSI I don't think full A/B is required
Click to expand...
Click to collapse
Is all treble roms are have voLTE bug???

furious.builder said:
@Khwaja7, I think that to have a full A/B support through MoKee you have to fully format /Data but for semi GSI I don't think full A/B is required
Click to expand...
Click to collapse
Okay, I did follow the instructions you gave us in your previous post; however, I can't get it working.
Sometimes when booting, it only powers the notification light in blue, and nothing happens. Sometimes, it has a bootloop showing "Android" .
I tried to flash every single img in this Mega repository :
https://mega.nz/#F!CYQxgCDK!Dl4kKANVDRy5kOFkNsuMVw
I think OP5 has A/B partition, but I'm not sure about this so I tried each one.
Can you help me to install this ? I just want to give it a try Did you install it ? @furious.builder

I really think it's A only, but I may be wrong
A friend tried many techniques on his 5T and soft bricked his phone... I think we need an updated Vendor even if it should work on 8.1/9's vendors :/

furious.builder said:
I really think it's A only, but I may be wrong
A friend tried many techniques on his 5T and soft bricked his phone... I think we need an updated Vendor even if it should work on 8.1/9's vendors :/
Click to expand...
Click to collapse
Ok, I see. Thanks for your comment.
So I think we should just wait instead of trying strange techniques :angel:
Did your friend tried this technique, but with a Q semi-GSI ? https://forum.xda-developers.com/oneplus-5/how-to/guide-install-aosp-pie-9-0-via-project-t3833961
radirajjj said:
Is all treble roms are have voLTE bug???
Click to expand...
Click to collapse
VoLTE is always listed as an issue, so I guess yes I can't try, so I can't tell, sorry !

use latest coltos vendor, this work install Q gsi on op5
but need system patch

jahidinbedod said:
use latest coltos vendor, this work install Q gsi on op5
but need system patch
Click to expand...
Click to collapse
Did you try it on op5?
Please explain what do you mean by system patch and also tell us what major bugs you are facing if using on an op5.
Edit: looking at the baseband, thats an op5
Will be thankful if you list the procedure for helping others.

jahidinbedod said:
use latest coltos vendor, this work install Q gsi on op5
but need system patch
Click to expand...
Click to collapse
Thanks ! Going to try it
brajesh.sharma87 said:
Did you try it on op5?
Please explain what do you mean by system patch and also tell us what major bugs you are facing if using on an op5.
Edit: looking at the baseband, thats an op5
Will be thankful if you list the procedure for helping others.
Click to expand...
Click to collapse
System patch is flashing the GSI system img, I think

install this file after install Permissiver_v2 and FixZygote
only decrypted devices
op5 is Aonly

jahidinbedod said:
install this file after install Permissiver_v2 and FixZygote
only decrypted devices
op5 is Aonly
Click to expand...
Click to collapse
And what does this do?

wifi works on android Q GSI ?

Chiku7 said:
wifi works on android Q GSI ?
Click to expand...
Click to collapse
Works on Erfans newest build, atleast with ob28 vendor