{
"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"
}
YOUR WARRANTY WILL BE VOID
I AM NOT responsible for anything that may happen to your phone while attempting to follow this guide.
You are doing so at your own risk, and you take full responsibility for your decisions and actions.
You are not to blame me or XDA, or any of it's respected developers.
Anyways, now that that is out of the way. Those of us who have been in the Axon 7 forums know that information is quite scattered about. So it can be difficult for any newcomers to find everything they need before making any leaps or dives with their device. This guide’s purpose is to centralize the quickest and easiest steps to follow in order to get Treblized and to get on a stable Pie GSI build that can be used as a home base before experimenting further with other ROMs and/or GSIs.
Even if you are not satisfied with the Havoc Pie GSI, your device will still be in an optimal state to try the latest Oreo 8.1 ROMs, such as LOS 15.1 or DotOS 2.5, or to try any of the other Pie GSIs in the Treble forums.
Things you will sacrifice:
No VOLTE
No Encryption
No Dolby
No Daydream
No AK4490 DAC (will default to AK4491)
Camera Flash out of sync (Use OpenCamera for flash shots)
Not able to set password for Hotspot (Open connection only)
Again, if you don't find using a Pie GSI worth these sacrifices after trying it out, you can easily move to an Oreo ROM like LOS 15.1 or DotOS 2.5, which have more functioning features.
----------------------------------------
DOWNLOAD
----------------------------------------
(NOTE: The below setup will be fluid as discussion in this thread finds more stability with newer vendor builds and newer HavocOS 2.0 GSI builds)
After completion of this guide, your device will be setup with the following (might as well download everything):
Oki's TWRP 3.2.3.0 Lab's Mod v1.3
B20 Bootstack by DrakenFX - Modified by Verequies (Splash or NoSplash)
Oreo Modem (U, G, or Chinese)
DotOS 2.5 boot.img (This also contains the DotOS vendor, if you wish to use it)
LOS 15.1 vendor (20181110) build
HavocOS 2.0 Pie GSI (20181027) build - NOTE: Most GSIs are provided compressed. You must extract the .img file from the downloaded file.
Your preferred GApps ( https://opengapps.org/ ) (ARM64, 9.0, Micro or below only)
Also download OrdenKrieger's TWRP 3.2.3.0, going to need it handy to flash the vendor img.
And the NFC_Hotspot Fix by Kountry83 (You will need this for almost every GSI you try)
----------------------------------------
FAQ
----------------------------------------
WHATS UP WITH THE BOOTSTACKS?
The bootstacks that are currently available for the Axon are somewhat of a mess, if not careful, you can easily brick your device.
For Pie GSI setups, I recommend the B20 bootstack by DrakenFX that has been modified by Verequies, Splash version.
Verequies has asked that I also link the NoSplash version in case some users have issues with the Splash version, but many testers have had no problems with the Splash version on this setup.
Unlike the DrakenFX B20 bootstack, these modified versions do not flash the modem, so there is no need to flash modem again when switching between them. Sometimes will need to Unlock Password in TWRP when switching though, it will say not recognized.
Splash
Ability to have Read/Write access in system.
Nice three logo splash screen, replacing bootloader warning screen.
No bootloader warning screen means not able hit volume button during boot to get menu for Recovery, Fastboot, etc.
Which also means you will have to use power button + volume up combo to enter Recovery, or reboot to recovery from the ROM.
No EDL three button combo.
Can't charge without booting system or TWRP.
NoSplash
Read Only access in system. (Which will break Magisk)
Ugly bootloader warning screen.
Able hit volume button during boot to get menu for Recovery, Fastboot, etc.
Able to use EDL three button combo.
Allows offline charging without booting into system.
WHY EDL?
Starting out with Oki’s LOS 15.1 EDL package just makes it easier for everyone. It’s easier for you because there will be less steps needed to get treblized, which will also mean less room for error. It’s easier for me because it makes for a much shorter guide, and it’s easier to find answers to issues if we all started on the same page. However, if there are enough requests, I’ll make a longer guide without the use of EDL.
If you are already treblized you won’t necessarily need to EDL (in most cases), but if you run into issues please don’t comment until you’ve tried starting with first step.
----------------------------------------
GUIDE
----------------------------------------
STEP 1:
Please follow Oki’s Easy Guide to EDL LOS15.1
IT IS IMPORTANT TO FOLLOW EVERY STEP
Try not to boot into system while going through the steps if possible, but it’s ok if you do.
You can use @djkuz Axon 7 EDL Tool, instead of MiFlash, if you are more familiar with that.
Also, in step 12, it states to format to F2FS, but I recommend to format to EXT4 for the best compatibility with GSIs. As a precaution, to make sure your partitions will read correctly, format the partitions to F2FS per the instructions, then format them back to EXT4.
You can always test if F2FS works for you later.
Thank you @Oki for this wonderful starting point for new Treble users.
CONGRATULATIONS - You are now TREBLIZED and should never have to do Step 1 again.
STEP 2:
Once done with Oki’s guide, stay in TWRP
Wipe Dalvik, Cache, Vendor, System and Data.
Flash the bootstack you chose.
Flash the appropriate modem for your variant.
CONGRATULATIONS - You should never have to flash those again, unless changing bootstack for whatever reason.
STEP 3:
In TWRP make sure System and Vendor partitions are mounted.
Flash the DotOS Vendor flashable.
(It doesn’t have DotOS in the file name, so it should be named something like “Vendor_Flashable_GSI…”)
In TWRP go to Install and in the bottom right select Install Image
Now we flash the Havoc GSI image you extracted, selecting the System partition.
DO NOT BOOT TO SYSTEM - We need to use OrdenKrieger’s TWRP 3.2.3.0 to flash the LOS 15.1 vendor.img
(If you wish to use the DotOS vendor, you can skip to Step 5. You will still need to reboot to Recovery, so don't skip that.)
STEP 4:
Flash TWRP 3.2.3.0 to Recovery partition and then reboot to Recovery
You should now be in TWRP 3.2.3.0
Flash the LOS 15.1 vendor.img to the Vendor partition
DO NOT BOOT TO SYSTEM - We need to restore Oki’s TWRP and flash GApps.
STEP 5:
Flash Oki’s TWRP 3.2.3.0 Lab’s Mod to Recovery partition and then reboot to Recovery
You should now be in Oki’s TWRP 3.2.3.0 Lab’s Mod
Flash GApps
Make sure System and Vendor are mounted
Flash the NFC_Hotspot Fix
NOW BOOT SYSTEM
I will wait here while you setup your device.
DONE? GOOD. Lets set up Magisk and pass SafetyNet
STEP 5:
At this time I recommend Magisk 17.2
Find it, download it, and flash it in TWRP
Once booted, in Magisk search for the module “MagiskHide Props Config” and install it.
Then search for BusyBox module by Osmosis and install it.
Reboot
Using a terminal app (not in TWRP) like Termux, type “su”
Grant root privileges
Then type “props”
You should be greeted with a menu
Select 1 to Edit fingerprint
Select F to Pick a Certified fingerprint
Then follow the menu to select ZTE and Axon 7
Then yes and yes to reboot.
Everything should be good to go now. ENJOY!!
To add just a few more options to your setup without overdoing it with a heavy launcher, I highly recommend:
Lean Launcher Optimized
I will surely be adding to this guide and modifying it as the situation evolves. So feel free to give me any input on how to improve it.
----------------------------------------
THANKS
----------------------------------------
Thanks to @raystef66 and all of the testers in the [SUMMARY][PIE] BEST PIE ROMS to TRY thread, as well everyone in the "Axon7 (s)GSI trebleSHOOT" Telegram group, for testing, "trebleSHOOTing" and reporting your findings.
Thanks to @Oki again for his easy guide and LOS 15.1 EDL package.
Thanks to @Unjustified Dev for uploading separate vendors for us GSI users, and for all of the work he's done on LOS and his help in the LOS threads.
Thanks to @Verequies for creating the two modified versions of @DrakenFX 's B20 bootstacks, and of course @DrakenFX for his B20 and B12 bootstacks.
Thanks to @SaintZ93 for his work on DotOS and for providing a flashable for boot and vendor only.
Thanks to @SaintZ93 and @Skrem339 for their great work on the Schwifty kernel.
And thanks to @hundeva for his work on Lean Launcher.
----------------------------------------
GUIDE EDIT LOG
----------------------------------------
11/22 - Updated that it is optional to stay with DotOS vendor and skip a step.
11/30 - Changed Step 1 to recommend EXT4 for best compatibility. Also to format from EXT4 to F2FS, then back to EXT4, to avoid internal storage error some are getting.
12/10 - Props Config module now requires BusyBox module, updated Step 5.
Thanks for the guide!
On step 4, The vendor partition doesn't show up on orden's twrp. You probably already know you can't flash with Okis twrp. Skipped this step and it booted anyway.
Don't beat me up about this but for those of us with the 50% battery bug, it happens with this method.
JKSurf said:
Thanks for the guide!
On step 4, The vendor partition doesn't show up on orden's twrp. You probably already know you can't flash with Okis twrp. Skipped this step and it booted anyway.
Don't beat me up about this but for those of us with the 50% battery bug, it happens with this method.
Click to expand...
Click to collapse
Please make sure you redownload Ordens TWRP. There are two of them with the same name out there. The one I linked should allow you to see Vendor partition. I should list this step as optional, as the DotOS vendor works, Ive just found the LOS vendor to show improvement personally. I also wanted to teach how to flash vendor.img, as there is only one way atm, using Ordens TWRP.
The vendor setup in this guide is all based off LOS sources, so any issues LOS is having that are vendor related will carry over to this setup. Sorry.
Really nice guide, sadly I just flashed but one thing that I like is that you try to explain why you choose what you choose and I would really like if you could elaborate more on that for example why DotOS boot image and kernel or why LOS 15.1 vendor.
And also is there a way for me (or anyone on havoc), already on havoc but got there differently, to painlessly migrate to your setup?
I am using this gsi for a week and I like it a lot. It has better battery life than LOS 16 right now and you can customise so much.
And btw for me daydream works normally and I installed the ported pixel camera with night sight, which seems to work normal, too.
Mousman said:
Really nice guide, sadly I just flashed but one thing that I like is that you try to explain why you choose what you choose and I would really like if you could elaborate more on that for example why DotOS boot image and kernel or why LOS 15.1 vendor.
And also is there a way for me (or anyone on havoc), already on havoc but got there differently, to painlessly migrate to your setup?
Click to expand...
Click to collapse
I found minor things to work better with the LOS vendor, such as GPS locking and Bluetooth not freezing display data in my car. Of course this can vary from user to user. And my preference changes as well when I find improvements with other vendors.
The DotOS vendor flashable is provided as it's the easiest way to get an up to date vendor. Otherwise you would have to download and flash an entire ROM, or extract the boot.img from that ROM, or modify the install script. Unjustified didn't provide the LOS vendor in combo with the boot.img, so the DotOS flashable is the best option as of now.
If you're already on the Havoc GSI, then you can just flash the bootstack, wipe vendor, flash DotOS vendor flashable, flash LOS vendor.img if you want (using Ordens TWRP), flash Magisk. Then boot.
It will feel like a dirty flash, but it's not, thanks to Treble.
Please do a full backup before doing so, as I think if your vendor partition was created differently, pulled from data, it might not work.
Kleva94 said:
I am using this gsi for a week and I like it a lot. It has better battery life than LOS 16 right now and you can customise so much.
And btw for me daydream works normally and I installed the ported pixel camera with night sight, which seems to work normal, too.
Click to expand...
Click to collapse
I don't use Daydream, I only know what was reported by others. If more people want to test and report that it's working, I'll gladly remove it from the sacrifices.
EBeatFLA said:
I don't use Daydream, I only know what was reported by others. If more people want to test and report that it's working, I'll gladly remove it from the sacrifices.
Click to expand...
Click to collapse
Re. sacrificing encryption, I thought LOS 15.1 vendor supports it. Is that not enough?
In other words, do you need vendor + system + rom for encryption to work? Or just system + rom? Or...?
Thx for all your work.
piet8stevens said:
Re. sacrificing encryption, I thought LOS 15.1 vendor supports it. Is that not enough?
In other words, do you need vendor + system + rom for encryption to work? Or just system + rom? Or...?
Thx for all your work.
Click to expand...
Click to collapse
This particular setup will sacrifice encryption. Getting encryption on a GSI would be another path. The TWRP and bootstack options we have for our device play a part in why I find encryption to be a mess right now, and chose to move forward without it.
I'm kinda having issues flashing LOS 15.1 vendor.img. I flashed Ordens TWRP, the one you provided but I do not get an option to flash to vendor partition when I choose to flash that LOS 15.1 vendor.img
g0dzstar said:
I'm kinda having issues flashing LOS 15.1 vendor.img. I flashed Ordens TWRP, the one you provided but I do not get an option to flash to vendor partition when I choose to flash that LOS 15.1 vendor.img
Click to expand...
Click to collapse
JKSurf said:
Thanks for the guide!
On step 4, The vendor partition doesn't show up on orden's twrp. You probably already know you can't flash with Okis twrp. Skipped this step and it booted anyway.
Don't beat me up about this but for those of us with the 50% battery bug, it happens with this method.
Click to expand...
Click to collapse
OMG guys, so sorry, was linking to the wrong TWRP. Link updated. It's not on AFH, so if you don't trust it's a legit link and want to check, it's the same link in the LOS16 op.
Thanks for testing.
Did everything from guide, but it seems like i don't have access to internal storage in havoc os and still accesible in twrp. Any suggestion what i did wrong?
Reakleases said:
Did everything from guide, but it seems like i don't have access to internal storage in havoc os and still accesible in twrp. Any suggestion what i did wrong?
Click to expand...
Click to collapse
Make sure to follow all of the steps in Oki's guide. Also, if you used the NoSplash bootstack, that might be it. But I'm pretty sure it's a missed step in his guide.
did everything again without success, but something of that helped, tried chmod 755 on root directory and fix contexts.
Really nice guide, thanks!
Having an issue flashing the DotOS vendor file. Getting the error 7. Edited the file with Notepadd ++ and took out the assert line and deleted the empty line. Resaved and recompressed zip and tried to flash and still getting the error. Followed all the steps to this point no issues.
juniorD said:
Having an issue flashing the DotOS vendor file. Getting the error 7. Edited the file with Notepadd ++ and took out the assert line and deleted the empty line. Resaved and recompressed zip and tried to flash and still getting the error. Followed all the steps to this point no issues.
Click to expand...
Click to collapse
Make sure system and vendor are mounted before flashing.
juniorD said:
Having an issue flashing the DotOS vendor file. Getting the error 7. Edited the file with Notepadd ++ and took out the assert line and deleted the empty line. Resaved and recompressed zip and tried to flash and still getting the error. Followed all the steps to this point no issues.
Click to expand...
Click to collapse
Wrong bootstack,flash bootstack again!
Also i read in previous post,people are not wiping correctly the system with clean flash
Predatorhaze said:
Wrong bootstack,flash bootstack again!
Also i read in previous post,people are not wiping correctly the system with clean flash
Click to expand...
Click to collapse
Thanks for the reply.
I flashed the bootstack in the EDL package uploaded in the guide using MiFlash went through fine. Also did a clean wipe of everything and formatted my Internal Storage before I flashed the package.
---------- Post added at 07:51 AM ---------- Previous post was at 07:50 AM ----------
EBeatFLA said:
Make sure system and vendor are mounted before flashing.
Click to expand...
Click to collapse
Yup did that and checked a second time to make sure I did. They were mounted.
---------- Post added at 07:52 AM ---------- Previous post was at 07:51 AM ----------
EBeatFLA said:
Make sure system and vendor are mounted before flashing.
Click to expand...
Click to collapse
Yup did that and checked a second time to make sure I did. They were mounted.
Related
About this project
This project provides repackaged Stock Oreo roms that can be flashed by TWRP. Modifications from stock are listed below.
As we are now moving into the Oreo world, I've decided that now is a good time to make a few changes to how things were done previously with Nougat. Please pay attention to the next few sections.
Modifications from stock
Note - It seems that I can't get DM-verity nor forced encryption disabled. The location of the fstab.qcom file is no longer in the Boot image. I found a similar file in the system image, but changing that appears to have had no effect. In order to disable these, use Magisk. UPDATE - Resolved since soak test 2, and soak test 1 with Aroma installer
DM-verity is disabled
Forced encryption of the data partition is disabled. It is still possible to encrypt the partition if you wish (optional with Aroma installer)
The partition table and boot loader are not included, which makes it safer to up/down-grade.
Do not attempt to apply standard OTAs over these builds. They'll probably fail, worst case they will brick your phone
Differences from previous Nougat builds
These roms are suitable for all channels. Previously there was separate firmware for different regions (e.g. retin had a separate build from retus), but as a general rule you are safe with any region's firmware.
I have now started using the Aroma installer for Oreo builds. Some of the below is now customisable at install time. Aroma installer zips will have "-aroma" in their filename.
The modified boot logo will no longer be included in the rom download. A separate zip will be provided to just flash the modified logo.
EFS will be erased on install! If your persist is intact, EFS will recreate itself. With the amount of exposure that the lost IMEI issue has had, all should be very familiar with the importance of backing up persist and EFS. And those that have had a compromised persist, will know that they should be hanging on to their EFS backups for dear life. Full details of the issue and solution (for those with intact persist) is here: Fix Persist, resolve IMEI=0, Volte, 4G, Explanation, Requirements From my perspective, the EFS is erased installing OTAs for a reason. I don't know what it is myself, but the folks at Motorola build it into their OTAs and they know far better than I do.
As a mitigation to the risk of people forgetting/losing their EFS and / or Persist backups, I will have a very crude backup system integrated into the zips. However, it will take some skill / knowledge to restore from these backups, and they should not be relied upon over the long term. Refer to the second post for more details.
Important information if downgrading to Nougat and Custom Oreo roms
The Oreo roms will change the ownership of specific files and folders in the /persist folder. As a result of this, stock Nougat will have issues such as lost IMEI, no Volte, no 4G, etc. In order to overcome these issues, either follow the instructions in the link above, or flash the following zip in TWRP.
potter-stock-persist-fix.zip
Additionally, the latest Nougat builds with the Aroma installer will apply the persist fix when installed.
Another potential issue is that, as a result of various partitions being updated, the new Oreo blobs may not be compatible with existing Nougat roms (stock or custom), or even current Custom Oreo roms. This may result in issues such as the fingerprint reader not working, etc.
UPDATE: Some custom roms are now using the Oreo blobs. However, if you require the older Nougat blobs, you can downgrade through one of the following methods:
1) install one of the latest Stock Nougat TWRP flashables. This will ensure that all affected partitions are compatible with Stock Nougat and Custom Oreo roms. You can get these from this thread here:
[Nougat][Stock][Rom] TWRP Flashable Stock Builds
2) install one of the firmware-only zips from the below folders. Note that if this results in other odd behaviour, you may need to install and boot into a full stock Nougat firmware as above. The main benefit of these zips is that they are much smaller, ~50MB rather than ~1.4GB.
https://www.androidfilehost.com/?w=files&flid=273039
potter-firmware-92-14.zip is for retin, retla, retbr
potter-firmware-93-14.zip is for retus, retapac, reteu
Out of respect for the purpose of this thread, please keep questions about whether or not to use Nougat or Oreo firmware for particular custom ROMs in the thread for the custom ROM you are trying to use. I do not support other custom ROMs - the maintainers of those custom ROMs should provide guidance.
Usage
Steps to flash
Ensure you have the latest TWRP
Download an appropriate zip from one of the links below
Copy to the phone or SD card
BACKUP YOUR DATA, INCLUDING EFS AND PERSIST
Flash the zip via TWRP
Optionally flash Magisk etc - NOTE - in order to disable dm-verity and forced encryption you must flash magisk before rebooting Resolved since Soak Test 2 and Soak Test 1 Aroma installer, Magisk is optional
Reboot
Profit?
How you can help with new builds
If your phone gets an OTA notification for a build that has not been released, please pull it and share it in this thread:
When the notification is received, allow your phone to download the OTA
Power off and boot into recovery
Go to Advanced -> File Manager
Navigate to /cache
There will be a file Blur_Version_x.y.z.potter.blah.zip - Note - Oreo OTAs may not be named this way, they may be named according to the version of the rom that is currently installed
Copy it to internal storage or the sdcard
Copy to PC (optional)
Upload to Mega, Google Drive, wherever
Share the link
You can also remove the file from the /cache folder to prevent any auto-updates from happening.
Latest versions
The 85-13 series is released to most channels except retus, and the last update was to 85-17-2.
The 85-17 series is released to the retus channel.
However, all releases can be used with all channels.
Official Oreo OPSS28.85-17-6-2 (Oreo 8.1, 1 February 2019 security patches) - Aroma Installer
Android File Host - potter-twrp-flashable-OPSS28.85-17-6-2-aroma.zip
Official Oreo OPSS28.85-17-6 (Oreo 8.1, 1 February 2019 security patches) - Aroma Installer
Android File Host - potter-twrp-flashable-OPSS28.85-17-6-aroma.zip
All versions that I have created will be placed in this folder (or the Archive sub-folder) at Android File Host:
Android File Host - Potter TWRP Flashable Stock Oreo
Modified Boot Logo
Optional, only needs to be flashed once. Replaces the warning screen with the standard logo. Can't hide the N/A. If you want to hide the N/A, go to the themes forum.
potter-logo.zip
Kernel Sources
Kernel sources are provided by Motorola:
https://github.com/MotorolaMobilityLLC/kernel-msm/
XDA:DevDB Information
Potter Oreo TWRP Flashable, ROM for the Moto G5 Plus
Contributors
NZedPred
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.x
Version Information
Status: Stable
Created 2018-08-17
Last Updated 2019-12-28
FAQs
Frequently Asked Questions
What is the 'very crude backup system integrated into the zips'?
This is a script that is run at the start of the install. It's purpose is very simple - it creates "dd backups" (i.e. bit-perfect images) of the modemst1/2 and persist partitions. They are stored in your sdcard as "backup_yyyymmddHHMMSS_modemst1.img", etc., where yyyymmddHHMMSS represents the date and time the script was run.
For this to work, your data partition must be mounted. I haven't included any checks for this (I'm not really a shell script person - it would take me hours to get this sort of thing right) - this is what puts the "crude" in "very crude backup system". UPDATE - the aroma installers now check that data is mounted, and abort the install if not. Most of the time the data partition will be mounted in TWRP, so this will work 99% of the time. Caution should still be applied, and you should still copy these or any other backups to cloud storage to be safe.
OK, so if I needed to use these backups, how do I restore them?
To restore these, you will have to reboot into TWRP and open up a shell or use adb. The commands to restore each partition are as follows (replacing yyyymmddHHMMSS with the appropriate values of course):
Code:
dd if=/sdcard/backup_yyyymmddHHMMSS_modemst1.img of=/dev/block/bootdevice/by-name/modemst1
dd if=/sdcard/backup_yyyymmddHHMMSS_modemst2.img of=/dev/block/bootdevice/by-name/modemst2
dd if=/sdcard/backup_yyyymmddHHMMSS_persist.img of=/dev/block/bootdevice/by-name/persist
Note that these commands are very powerful, and applied incorrectly can result in you bricking your phone if you overwrite the wrong partition.
So are dm-verity and forced encryption now not able to be disabled?
OK some history... Nougat had fstab (file system table) in the boot image. So in those days, I would open up the image, and edit the fstab.qcom file, do the appropriate changes, repack the boot image, and all is fine.
Now, under Oreo, the fstab file is not in the boot image, it's under /system/vendor/etc/fstab.qcom or similar. Editing that file appears to have no effect. For now, Magisk is the easiest way of disabling both, but you must make sure to install it immediately after installing the rom and before rebooting.
Update - this is now resolved in the second Oreo soak test download. dm-verity is still disabled in the boot image, but a completely different way. Once this is done, disabling forced encryption works as expected.
Which partitions are modified?
The short of it is this - boot, system and 'firmware'-related partitions. None of the bootloader partitions are updated. The full list of partitions that are written is:
modem
fsg
dsp
boot
system
oem
Note that this list applies to the Nougat and Oreo flashable zips.
TWRP is no longer installed after flashing this
I believe this is related to dm-verity (see above). You will have to first reinstall TWRP via fastboot. When TWRP is back, install magisk immediately after installing the rom, and before rebooting.
I'm having problems with an Oreo custom rom after installing this rom, what can I do?
Refer to the OP, the section about downgrading to Nougat - the same approach applies. Oreo Custom roms will have been based upon the available Nougat blobs that were available. As the blobs have been updated in the Oreo release, the issue is that they are not compatible. So install a full TWRP Nougat zip and then install your Oreo Custom rom.
Dirty or clean flash?
I did a dirty flash, as I came from the latest Nougat stock rom. Keep in mind that this is nothing more than the OTA applied to the previous Nougat build and packaged into a TWRP zip. So, as long as you have come from (the latest) Stock Nougat, you should be able to dirty flash, as that would be the use-case for the OTA. If you were on another rom, clean flash required.
Once you are on one of these builds, you can dirty flash subsequent builds. Again, this would be just like flashing one OTA after the other. Also note that these builds are complete in their own right, you don't need to incrementally flash - you can flash the latest to get the full install.
My device was encrypted, and I really need to decrypt it. How can I do this?
Sorry, but the only way is to format the data partition. That means you will need to backup your data, and your internal storage as well (/sdcard). After backing up, use TWRP to format the partition. From the TWRP main menu, select Wipe > Format Data. Then follow the on-screen instructions.
Is it 32 bit or 64 bit
32 bit. We've known this would be the case for a long time.
How can I create flashable zips myself?
I created the guide below, and it has been updated for Oreo. A word of warning, it is not for the faint of heart. You will need to have a good understanding of the Linux command line, and be able to understand the techniques that are being taught, rather than expecting that the process is a 'step-by-step'. Adaptability is key here.
[GUIDE] Creating TWRP Flashbale Stock roms
What are the new Aroma zips?
The aroma zips use the Aroma installer. Some of you may have seen the Aroma installer for Open Gapps. The key here is that I, as the packager, can build in selection options into the installer. It's all available as a nice GUI for the users to pick and choose from the options I've provided. Here are the options that are available:
Do backups - does the backups as mentioned earlier in the FAQs.
Erase EFS - erases modemst1 and modemst2, as described in the first post. Also DDR is erased, but I'm not sure what purpose that has but it may as well go together with these.
Install Firmware - installs the following partitions - modem, fsg, dsp; each of these has something to do with hardware / connectivity.
Install System - Installs the following partitions - boot, system, oem.
Apply patches - as long as Install System is selected, will install the patched boot image with dm-verity disabled, and will edit the fstab (filesystem table) to disable forced encryption.
On soak test 2 or later, I have my IMEI but no signal. What can I do?
In all cases where this has happened, the user's phone has relied upon an EFS backup for IMEI, due to flashing another persist. In these cases, it appears that the only way to get a signal is to use the firmware (i.e. modem, fsg, dsp - refer previous FAQ) from soak test 1. We're probably seeing here that the EFS does in fact need to be recreated to be valid. Unfortunately for these users, by not having their own persist, they are stuck with an old EFS and the newer firmwares appear to not work.
To do this
if you are already on Soak Test 2 or later, download the Soak Test 1 firmware download at either of these links:
Android File Host - oreo-soak1-firmware.zip
Dropbox - oreo-soak1-firmware.zip
If you are on Soak Test 1, install Soak Test 2 or later / official aroma installer and de-select firmware
My fingerprint is not working on my custom ROM
Refer to the thread for your custom ROM, and ask questions there. In short, Nougat and Oreo firmware are not compatible with each other. Many custom ROMs are now using Oreo firmware, whereas previously (before October 2018) pretty much all custom ROMs were using Nougat firmware. It's messy now, but please ask the questions in the right place (which is NOT this thread).
My touchscreen isn't working after flashing, even within TWRP
This seems to happen somewhat rarely, although I don't know what the cause is. As it affects TWRP as well, and TWRP uses the 'modem' partition for getting its firmware blobs, I guess it's possible that this particular partition is getting a conflicting modification whilst flashing, which is causing problems (but this is purely speculation on my part).
To solve, fastboot flashing the stock ROM appears to work. It may also be possible whilst in TWRP to manually flash the partitions via ADB, but that takes a bit of work and knowledge. Until someone can truly work out what's happening and the minimum required to fix it, stick with fastboot.
Update - refer to post #3 for the latest information about this issue.
Touch screen unresponsive even in TWRP
The below post has the latest information on the Touch Screen Unresponsive issue
Likely Cause
From the testing that I've done to reproduce the issue, as far as I can tell the issue is that Stock Oreo is not able to be safely applied over the top of old builds of Stock Nougat. Furthermore, it doesn't seem to matter if you were on Custom ROMs after you were last on Stock Nougat, just what Stock Nougat build you were on last.
Avoiding the Issue
Again the key here is what build of Stock you were on last (and I guess booted into). So, if you were never on Stock Oreo, and you aren't sure what version of Stock Nougat you were on last, then the safest path to getting these builds working is to first flash the latest Nougat Stock ROM.
Get the latest from this thread: [Nougat][Stock][Rom] TWRP Flashable Stock Builds
Once you have flashed the latest Nougat, boot once to make sure everything is working. After that, you should be able to safely upgrade to Oreo.
Fixing the Issue
If you have been affected by the issue, most people have been able to get back the touch screen functionality by flashing a fastboot version of the ROM. However, as long as you have a PC handy you will be able to flash using TWRP as well via adb, using the steps detailed below. A third option is to connect a USB Mouse via an USB OTG adapter.
Note that for either method via TWRP, you cannot use the versions of the ROM with the Aroma installer, as the mouse is not supported within, and there is no way of providing input by adb.
Downloads
The 92-14 or 93-14 versions should be suitable. They are in these links (these do not erase EFS, so for the paranoid, you will retain your IMEI):
twrp-flashable-potter-NPNS25.137-92-14-no-erase-modemst.zip
twrp-flashable-potter-NPNS25.137-93-14-no-erase-modemst.zip
TWRP Commands
Once in TWRP, connect your USB cable. To copy the downloaded file into your internal storage (adapt the filename for the version you downloaded):
Code:
adb push twrp-flashable-potter-NPNS25.137-92-14-no-erase-modemst.zip /sdcard/
If you want to backup, you can do this via the command line as well. I haven't tested this myself, but the commands are available here: https://www.pocketables.com/2014/10/using-twrps-new-adb-interface.html
The example provided uses the following to back up system, data and boot, and compress:
Code:
adb shell twrp backup SDBOM
You will need to do a clean flash, so these commands will wipe data / factory reset and then install
Code:
adb shell
twrp wipe data
twrp install /sdcard/twrp-flashable-potter-NPNS25.137-92-14-no-erase-modemst.zip
reboot
After the reboot, you should have your touch screen functionality back. Then reboot to recovery, and install Oreo as normal. If for any reason the Oreo flash doesn't work, try the steps again, but rather than installing the latest Oreo, install an earlier one.
Awesome bro...
You Rock...
you even included auto backup of efs and persist ... wow thats very thoughtfull and nice of you...
hatsoff..
:good::good:
Thanks dude, downloading
Edit: working like a charm, again thanks.
{
"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"
}
Thanks for uploading. Two questions though...
1. which one would be suitable for retin? (India)
2. Are there any bugs?
working for retin also thnx
Question: I'd like to flash this, but I'm planning to roll back in the future to take the OTA back up to O. If I restore nougat system, boot, persist, recovery, oem will that still be possible? I see some other stuff in the zip like adspo.bin, fsg.mbn, and modem. Not sure if those it lead to OTA failures or a brick.
also, nice job on the persist/efs script!
Worked on retin also thanks. Great work!!!!
I'm pretty sure forced encryption of the data partition is still enabled.
pfonck said:
I think forced encryption of the data partition is still enabled (formatting the data partition in TWRP does not help).
Click to expand...
Click to collapse
If that's the case magisk is probably needed to turn it off. Sorry, but I've only tested it with magisk installed. Moto have changed the fstab location, I thought I got it but maybe it's cosmetic and doesn't do anything. Will update OP when I get a chance.
NZedPred said:
If that's the case magisk is probably needed to turn it off. Sorry, but I've only tested it with magisk installed. Moto have changed the fstab location, I thought I got it but maybe it's cosmetic and doesn't do anything. Will update OP when I get a chance.
Click to expand...
Click to collapse
Yes, when you do;
rom installation > format data > flash magisk
everything is okay
verified.
Did Moto make Oreo 64bit?
redbeard1083 said:
Question: I'd like to flash this, but I'm planning to roll back in the future to take the OTA back up to O. If I restore nougat system, boot, persist, recovery, oem will that still be possible? I see some other stuff in the zip like adspo.bin, fsg.mbn, and modem. Not sure if those it lead to OTA failures or a brick.
also, nice job on the persist/efs script!
Click to expand...
Click to collapse
Good question, and this is something that I needed to consider before doing this, in case everyone installed this and we'd have no path to get to official Oreo.
Refer to the section in the OP "Important information if downgrading to Nougat". Basically you need to follow all of that to be able to get notification of the OTAs. Once the official public Oreo OTA is available, I will then put together a zip based upon the pre-requisite nougat rom with the official Oreo OTA.
I also believe that one or both of the 1 July 2018 and/or 1 August 2018 patches were announced, but neither were for Oreo. I do intend to keep Nougat up to date as well in its thread.
NZedPred said:
Good question, and this is something that I needed to consider before doing this, in case everyone installed this and we'd have no path to get to official Oreo.
Refer to the section in the OP "Important information if downgrading to Nougat". Basically you need to follow all of that to be able to get notification of the OTAs. Once the official public Oreo OTA is available, I will then put together a zip based upon the pre-requisite nougat rom with the official Oreo OTA.
I also believe that one or both of the 1 July 2018 and/or 1 August 2018 patches were announced, but neither were for Oreo. I do intend to keep Nougat up to date as well in its thread.
Click to expand...
Click to collapse
How did a recovery come in? with volume - and power enters and I say without command
JC Pzy said:
How did a recovery come in? with volume - and power enters and I say without command
Click to expand...
Click to collapse
I've only just added something to the FAQ (post 2) that covers this. Sorry, it was unexpected and didn't come up when I was testing as I always had magisk installed. Follow these steps:
TWRP is no longer installed after flashing this
I believe this is related to dm-verity (see above). You will have to first reinstall TWRP via fastboot. When TWRP is back, install magisk immediately after installing the rom, and before rebooting.
NZedPred said:
I've only just added something to the FAQ (post 2) that covers this. Sorry, it was unexpected and didn't come up when I was testing as I always had magisk installed. Follow these steps:
TWRP is no longer installed after flashing this
I believe this is related to dm-verity (see above). You will have to first reinstall TWRP via fastboot. When TWRP is back, install magisk immediately after installing the rom, and before rebooting.
Click to expand...
Click to collapse
I do not have a PC to reinstall the recovery
NZedPred said:
Good question, and this is something that I needed to consider before doing this, in case everyone installed this and we'd have no path to get to official Oreo.
Refer to the section in the OP "Important information if downgrading to Nougat". Basically you need to follow all of that to be able to get notification of the OTAs. Once the official public Oreo OTA is available, I will then put together a zip based upon the pre-requisite nougat rom with the official Oreo OTA.
I also believe that one or both of the 1 July 2018 and/or 1 August 2018 patches were announced, but neither were for Oreo. I do intend to keep Nougat up to date as well in its thread.
Click to expand...
Click to collapse
Maybe I'll try tweaking the zip to see if we can run it without the stuff we can't easily backup/restore with twrp. I'll take a stab at it shortly and let you know what happens if we flash just system, boot, and OEM.
redbeard1083 said:
Maybe I'll try tweaking the zip to see if we can run it without the stuff we can't easily backup/restore with twrp. I'll take a stab at it shortly and let you know what happens if we flash just system, boot, and OEM.
Click to expand...
Click to collapse
You can give it a go, but I've already done some very brief testing. Using the Nougat modem partition on the Oreo system results in things like 3G only, fingerprint not working.
JC Pzy said:
I do not have a PC to reinstall the recovery
Click to expand...
Click to collapse
I'm guessing you don't have root either? If you did, you could try installing it from a shell from within the rom:
Code:
su
dd if=/path/to/twrp.img of=/dev/block/bootdevice/by-name/recovery
As we(in the TG group) have tested a bunch of Pie9.0 (s)GSI Roms on the XDA forum (https://forum.xda-developers.com/project-treble/trebleenabled-device-development) I was asked to make a guide/summary of what there was already been tested and in our opinion the better ones out of the Pie-list.
It’s not to be intented to be ‘the’list but only to give you a guidance to what there is at the moment. And most of, it’s very easy to install
The ones that I will list are the ones WITHOUT call bugs on our Axon 7. As you wish you can vote for your favorite of the listed ones above.
Note : the LOS16 PPR2 is not the same as the one under ROM section (Ordenkrieger)
LIST AVAILABLE : (not in a specific order and more to come)
1. HavocOS : based on https://forum.xda-developers.com/pr...-device-development/rom-havoc-os-8-1-t3819050
Latest stable : https://sourceforge.net/projects/havoc-os/files/arm64aonly/
2. BenzoROM : based on https://forum.xda-developers.com/pr...device-development/gsi-benzo-rom-9-0-t3837127
Latest stable : https://forum.xda-developers.com/showpost.php?p=78312149&postcount=284
3. PixelExperience : based on https://forum.xda-developers.com/pr...ce-development/9-0-pixelexperience-p-t3833294
Latest stable : https://github.com/EnesSastim/Downloads/releases/tag/PE-A-2018-09-05
4. LOS16.0 PPR2 : based on https://forum.xda-developers.com/pr...vice-development/9-0-lineage-os-16-0-t3840801
Latest stable : https://mega.nz/#F!3XwFlAaC!VdzCKlrR-f6D-a8oEz9JkQ!DD4z0AhA . More info.
5. ArrowOS : based on https://forum.xda-developers.com/pr...abled-device-development/gsi-arrowos-t3835111
Latest stable : https://sourceforge.net/projects/arrow-os/files/arrow-9.x/GSI/7_sep_2018/
6. DescendantOS : https://forum.xda-developers.com/pr...escendant-android-pie-custom-rom-ver-t3840578
7. PixelDust : https://forum.xda-developers.com/showpost.php?p=78184921&postcount=212
8. AEX 6.0 OFFICIAL : https://forum.xda-developers.com/showpost.php?p=78245997&postcount=254
Pre Requisitions :
Unlocked BL, Bootstack B12 NFound or your preferred one
Vendor partition by @djkuz or your preferred one
TWRP3218-treble under the hood @NFound or your preferred one
Installation : or your own preferred method as this is just an example
Wipe System. Data, Vendor, cache dalvik (although data does the job)
Flash the v1.1 NFound
Flash the .img that you have extracted and if needed renamed to system.img
And just….reboot
After installation there can be applied some fixes :
a* Use the aroma COMBIFIX v3.1 to fix the NFC/HS general lag, choose button reverse, flash new kran framework overlay, magisk and gapps
update : for magisk 18.1 use the latest Combifix v5.1 or with Magisk 19.0 you can use Combifix v6.0 or the latest one with magisk 19.1 and latest MHPC : COMBIFIX 6.1
a. NFC when laggy or not working combined with Hotspot : Pie_NFC /Hotspot fix by @kountry83
On ArrowOS and Benzo they both work after applying the fix although the Hotspot works on ArrowOS and Benzo die to v105 phh
b. GCAM when default one isn’t working
c. Camera fix if you have a settings bug
d. Reverse BACK/RECENT (mount system / vendor) or A2017X_softkey_reverse_module
e. System settings color accents
f. DarkMode & SettingsColorAccents thnx @kountry83
g. safetynet issues
Misc :
* A2017X-MoKee_vendor_boot_combo
* AEX bootanimation
* Havoc bootanimation
* There is no need to an incall fix as all of the listed are free of the bug.
* Also no problems with SD card or booting the roms.
* In some cases the package provided by the dev is GAPPS included. If no gapps provided you can simply flash the OFFICIAL GAPPS.
* All roms have NFC working. Hotspot isn’t reliable and mostly not working.
* Some Pie Roms do have more customization as to the other. Up to you to vote which one you do prefer. When voting it would be good when you make your vote based on ‘most stable/most customs/best battery life’
* Substratum works (tested on Benzo and NOS...)
I’m not going get into detail about each rom. I’ll leave that up to you to discuss further on. Perhaps if voting leads us to a one of a kind, we can focus on that in the future.
It would be much appreciated as you add your input even with your fixes or additions you want to point out.
This is something that is growing on XDA and all the input is welcome to improve what we have.
ENJOY !
@Oki, thnx for your guidance on flashing back and forth between (treble) roms
Credits to all mentioned in the thread and to all members for testing and improving it on TG !
Feel free to join us too on Axon7-trebleshoot
-----
Havoc P seems to be a good option. Im voting for havoc.
nays_pl said:
Havoc P seems to be a good option. Im voting for havoc.
Click to expand...
Click to collapse
A good one. As for me the Benzo, Los16PPR2 and Havoc are the best to this point.
Especially smoothness, battery life and customization are more then ok atm.
Updates will follow and improve things where needed.
Thanks @raystef66 ! Took some time away from flashing and was a bit lost of where to go on my axon after moving to aex5.8 and how to do. Good that you also have the instructions
Was on benzo for a week or so...was pretty stable but the battery life wasnt that great even with the schwifty kernel. It lacked some of the customizations that i use so i am back at AEX 5.8...pretty sure these gsi will become more stable over time...will be worth the wait
Axebladewarrior said:
Was on benzo for a week or so...was pretty stable but the battery life wasnt that great even with the schwifty kernel. It lacked some of the customizations that i use so i am back at AEX 5.8...pretty sure these gsi will become more stable over time...will be worth the wait
Click to expand...
Click to collapse
Thnx for the input !
True, as for me too, the AEX Oreo has a bunch of customs that Benzo still hasnt. But out of all GSI's Benzo and a couple others have the most.
Even on some Pie GSI's the displayed features aren't even working.
Batterylife as on NOS gave me 4-5 SOT on average use.
Anyway, like you said, still building up....
raystef66 said:
@Oki, if you want to guide the users on your method to flash a (s)GSI from scratch with your PartyTool, be our guest
Click to expand...
Click to collapse
Sure! more people testing means more options explored and better outcome for everyone. You are doing a great job testing and bringing Android 9 ROMs to the Axon 7 scene. I have been very busy the last couple of weekends preparing my version of the TWRP for the Axon 7, the TWRP 2.3.2-0L Labs Mod. It has been for me the key for fast switching between the testing environment and the daily driver configuration in a matter of minutes and without requiring a computer at all. It can backup/restore internal storage, create and remove the vendor partition and even create firmware zip packages able to be flashed using TWRP or MiFlash. I'll create the guide this afternoon on how to switch back and forth from Nougat or Oreo to Pie.
Cheers!
Oki said:
Sure! more people testing means more options explored and better outcome for everyone. You are doing a great job testing and bringing Android 9 ROMs to the Axon 7 scene. I have been very busy the last couple of weekends preparing my version of the TWRP for the Axon 7, the TWRP 2.3.2-0L Labs Mod. It has been for me the key for fast switching between the testing environment and the daily driver configuration in a matter of minutes and without requiring a computer at all. It can backup/restore internal storage, create and remove the vendor partition and even create firmware zip packages able to be flashed using TWRP or MiFlash. I'll create the guide this afternoon on how to switch back and forth from Nougat or Oreo to Pie.
Cheers!
Click to expand...
Click to collapse
Awesome :highfive:
Oki said:
Sure! more people testing means more options explored and better outcome for everyone. You are doing a great job testing and bringing Android 9 ROMs to the Axon 7 scene. I have been very busy the last couple of weekends preparing my version of the TWRP for the Axon 7, the TWRP 2.3.2-0L Labs Mod. It has been for me the key for fast switching between the testing environment and the daily driver configuration in a matter of minutes and without requiring a computer at all. It can backup/restore internal storage, create and remove the vendor partition and even create firmware zip packages able to be flashed using TWRP or MiFlash. I'll create the guide this afternoon on how to switch back and forth from Nougat or Oreo to Pie.
Cheers!
Click to expand...
Click to collapse
That would be great and much appreciated as you have followed your own guideline next to NFounds ! That's why I asked
I follow what you're trying to achieve and in fact I'm waiting to test the LabMods. Thnx !
As said, I come along with many people asking how to go back and forth between N,O and Pie. I know what to do in such occasions but many don't.
Because of your tools I'll leave the full guide on that up to you
Oki said:
Sure! more people testing means more options explored and better outcome for everyone. You are doing a great job testing and bringing Android 9 ROMs to the Axon 7 scene. I have been very busy the last couple of weekends preparing my version of the TWRP for the Axon 7, the TWRP 2.3.2-0L Labs Mod. It has been for me the key for fast switching between the testing environment and the daily driver configuration in a matter of minutes and without requiring a computer at all. It can backup/restore internal storage, create and remove the vendor partition and even create firmware zip packages able to be flashed using TWRP or MiFlash. I'll create the guide this afternoon on how to switch back and forth from Nougat or Oreo to Pie.
Cheers!
Click to expand...
Click to collapse
Thx. How about adb and encryption for TWRP2. 3.2-0L?
piet8stevens said:
Thx. How about adb and encryption for TWRP2. 3.2-0L?
Click to expand...
Click to collapse
Read his OP in the thread he linked.
piet8stevens said:
Thx. How about adb and encryption for TWRP2. 3.2-0L?
Click to expand...
Click to collapse
I have not developed new kernels but I have taken care of both situations. Just go to the TWRP Labs Mod thread, the info is in the OP and you can ask there too. This thread is all about the Pie implementations, Let's try to keep on topic as much as possible.
really hope MIUI 10 will be stable enough, miss MIUI
HOW TO...
Round Trip from NOUGAT or OREO to PIE GSI
OK, the full instructions to go from Nougat or Oreo to Pie, and back, would be:
Prerequisite
Bootloader Unlocked Axon 7
Install tools and configuration
1. Install TWRP Labs Mod Custom Recovery. Use the B12 version in case you are currently using Oreo encryption. Reboot to recovery.
2. Open the PARTY tool under Advanced > Oki Labs. If you do not have vendor partition you need to create one. Use the default configuration (System, 512MiB, at the end). Accept to reboot recovery. If the vendor partition is there, then just leave PARTY tool and continue with the next step.
Backup your daily driver config:
3. Go to the EDL Backup tool under Advanced > Oki Labs and create the Backup zip choosing FULL. If something goes wrong you will be able to restore your device using TWRP or MiFlash
4. From the Main Menu, backup your Data partition to the External SD.
5. Backup your Internal Storage using the option under Advanced > Oki Labs (Check the available space, the tool is not yet checking for available space, I will add it this weekend)
Prepare Treble configuration:
6. From TWRP Install the special B12 Bootloader with enabled EDL key combo support (The Universal Bootstack leads to DFU mode) and the modem for your region.
7. From the Main Menu, Wipe Vendor
8. Flash Axon 7 Treble ROM v1.1
Flash GSI package:
9. From the Main Menu, Wipe Dalvik / Cache / System / Data
10. From here you have to follow the installation instruction for the Generic System Image (GSI). Usually it is a single img file. So go to Install, press Install_Image button and navigate to the GSI file to flash it. Then just reboot. Some images would require additional ZIPs such as GApps or recommended patches.
Here you test the Pie ROM. If you want to test another Pie ROM you can try just going back to step 9. However, to ensure everything is clean you should start in step 7.
Return to your Daily Driver Config
11. Boot Recovery and flash the backup EDL ZIP you created in step 4. If you bricked your device just extract the contents of the file in your HD, Boot your phone into EDL mode, and use MiFlash. This step restore your original bootstack, modem and OS.
12. From main menu restore your Data partition
13. Go to Advanced > Oki Labs and restore Storage.
14. If you had to create the vendor partition in step 2, just run the PARTY tool again to remove the vendor partition.
15. From the Main Menu, Wipe Dalvik / Cache and reboot to system.
New Builds :A-only !
Pixel Experience seems default camera is working now
ArrowOS
Misc
Magisk Camera Module (MI A2 stock camera for Pie) - tested and works very good. Even flash is synchronised as well.
@Oki, I'm having an issue flashing your B12 bootloader. When I flash I get an error saying the zip is corrupt. I've tried downloading 3 times, and flashed from both internal and external storage. Any suggestions?
raystef66 said:
New Builds :A-only !
Pixel Experience seems default camera is working now
ArrowOS
Click to expand...
Click to collapse
How about hotspot? Is it working now?
privatedoodle said:
@Oki, I'm having an issue flashing your B12 bootloader. When I flash I get an error saying the zip is corrupt. I've tried downloading 3 times, and flashed from both internal and external storage. Any suggestions?
Click to expand...
Click to collapse
I have experienced some problems with AFH server. I have deleted the other version and uploaded it again here.
Oki said:
I have experienced some problems with AFH server. I have deleted the other version and uploaded it again here.
Click to expand...
Click to collapse
This new version works. Thanks!
I'm not responsible for any damage to your device of any sort.
By flashing this you take responsibility of anything that happens.
Process at your own risk!
If you want to check firmware - please make backup.
Notes
The idea of this project treble is to separate the device-dependent part and the system.
The project treble requires a separate /vendor partition for device-dependent part. But unfortunately we do not have it. But we have a /cache partition, which takes about 200mb and there is a /hidden partition, which takes 50-60mb. 200mb is not enough for us, our vendor is about 450mb.
In the first edition I maded for the 825 tablet, I implement an original solution using separate files for the system and the vendor. But this solution was very difficult to understand. Now my good friend @bonuzzz suggested an idea to me using a compressed partition (squashfs with lz4 compression). With this method, our vendor takes 190-195mb and it is possible to write it to the /cache partition. And use the /hidden partition as a /cache.
Now the installation has become much easier, almost like installing the usual lineage.
Installation
1. install twrp version with treble support (this is my special twrp, based on 9.0 with my latest caf kernel with squashfs support)
2. download treble zip and flash it as usual zip. It will flash boot.img and /vendor partition (in /cache)
3. download any treble system (64bit System A-only) image from: https://forum.xda-developers.com/project-treble
extract, you should get .img file, then copy to sdcard/extsd card and then flash image as system_image in twrp (Install - switch to Install Image and flash as System Image)
4. if you wanna back to stock firmware or lineage - you need flash normal twrp version and make full wipe or just flash stock firmware via odin
Links
Firmware
[SM-T820]
1. 20190404: https://drive.google.com/file/d/1hOPdO9UajY7AlJ5lE859Tr6Y7sEpwhTf/view?usp=sharing
[SM-T825]
1. 20190408: https://drive.google.com/file/d/1DokV37D8f2s9OtoAJTCURfdx88tNW788/view?usp=sharing
TWRP
[SM-T820]
1. 20190404: https://drive.google.com/file/d/1gJ50Sg75Vh7PKyiWfejiCPSD0SYCL5p2/view?usp=sharing
[SM-T825]
1. 20190408: https://drive.google.com/file/d/1x_MKQ1PDM6eEbSPsDyFk0DABjXnZfyB4/view?usp=sharing
System images
You can use almost any system image from https://forum.xda-developers.com/project-treble
Our version is: arm64 and a-only image
Magisk
You should use only latest 19.0 beta version from: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Do not use 18.1 or early version - it's dnw, it will corrupt firmware or may be even corrupt recovery (need flash recovery again via odin)
Almost all firmware say about wrong vendor version. This is normal, just press OK.
let's experiment together!
Version for SM-T825 hope will come soon too. I have some ril issues.
Update boot.img
Wow! Thank you for the amazing work. I seriously can't believe no one hasn't gone crazy over this already.
How would I go about adding some libraries to my /vendor partiton now? I want to try a Samsung OneUI GSI image on my tablet but it requires additional libraries.
The files I want to add are in here: https://mega.nz/#!oi52TSTY!2Qy3WU7DjVmafs4zENPF6dlOsbY06JG5NuvsNeDTRn4
How did you build this file in the first place?
EDIT: I noticed that video playback does not work. I see the video starts to buffer, then some ghosting appears, and finally the app crashes (both YouTube and Vimeo). Also, camera apps seem to crash.
cephasara said:
EDIT: I noticed that video playback does not work. I see the video starts to buffer, then some ghosting appears, and finally the app crashes (both YouTube and Vimeo). Also, camera apps seem to crash.
Click to expand...
Click to collapse
With me, YouTube and YouTube Vanced I run without problems and also the camera app works (only the switching times to the front cam take some time).
GSIs
rainman74 said:
With me, YouTube and YouTube Vanced I run without problems and also the camera app works (only the switching times to the front cam take some time).
Click to expand...
Click to collapse
Maybe my /hidden & /cache partitions got corrupt somehow. I tried several GSIs and had the same issue. Thanks for confirming though.
Have you tried an GSIs from non AOSP-based images? Like OneUI or Xperia? I had trouble with those.
rainman74 said:
With me, YouTube and YouTube Vanced I run without problems and also the camera app works (only the switching times to the front cam take some time).
Click to expand...
Click to collapse
Could you let us know which treble rom you used, as I have the same issues with video playback on youtube.
I also want to throw out there I was on the Nougat bootloader when I tried this and had video playback issues. I have not tried it out on Oreo. I would imagine that could make a big difference.
deleted (it sucks none of the sensors function properly)
just installed RR but i think gps not working
https://forum.xda-developers.com/pr...0-resurrection-remix-v7-0-arm64-32-b-t3891636
This is great!
Hey everyone, this project is big news! I am so happy that we can use Treble GSI, using the cache partition via squashfs is a really elegant way for this.
Almost everything works on my T820! I am using Phh-Treble AOSP 9.0 v112, MindTheGapps and Magisk. Even adoptable storage works, I have 256GB for internal storage now (it displays as 256/512 used when empty, but whatever).
The device is certified with magisk and custom prop value.
Contrary to the old Lineage OS from last year, there is no crazy wifi jitter, so Steam Link just works fine. I did not try out the recent Lineage 20190331, so I don't know if it was due to Lineage.
The rotation sensors are not working, for now I am using "Rotation Quick Setting" app from Play Store. Also, the camera app crashes, but I am not using it anyway.
Thank you so much @bonuzzz and @Valera1978 for making this possible! It is stable enough for daily use for me.
BTW, I came from Oreo bootloader, and have no problems regarding video playback (but I use MX Player, not stock)
Mhh.. I get constantly soft reboots if i try to install third party apps or restore my titanium backup on Havoc for treble. Fingerprint is also not working. Seems to be very unstable...
How could I go about adding files to this treblized /vendor partition? Presumably through the zip? If this is the case, how could I do that?
Fair warning to those wanting to try this: treble roms do install and run, but sensor support appears to be lacking. I can't get any input from gps, accelerometer, gyro, or light sensor.
@Valera1978 If anybody has any idea on how to add support for these to the (I'm assuming) vendor partition, I'd love any hint or direction.
usb otg not working
alegru said:
Hey everyone, this project is big news! I am so happy that we can use Treble GSI, using the cache partition via squashfs is a really elegant way for this.
Almost everything works on my T820! I am using Phh-Treble AOSP 9.0 v112, MindTheGapps and Magisk. Even adoptable storage works, I have 256GB for internal storage now (it displays as 256/512 used when empty, but whatever).
The device is certified with magisk and custom prop value.
Contrary to the old Lineage OS from last year, there is no crazy wifi jitter, so Steam Link just works fine. I did not try out the recent Lineage 20190331, so I don't know if it was due to Lineage.
The rotation sensors are not working, for now I am using "Rotation Quick Setting" app from Play Store. Also, the camera app crashes, but I am not using it anyway.
Thank you so much @bonuzzz and @Valera1978 for making this possible! It is stable enough for daily use for me.
BTW, I came from Oreo bootloader, and have no problems regarding video playback (but I use MX Player, not stock)
Click to expand...
Click to collapse
Does Netflix work?
I get a bootloop after installing image and reboot to system. I have followed the instructions and got an error "Updater process ended with ERROR:7" installing the treble-16.0.zip. I flashed the custom TWRP using odin and using stock Pie. Did I do something wrong?
Hey all. Flashed all the relevant files in the relevant order and currently have a tablet sitting on the Tab S3 splash screen. How long does this normally take?
I flashed the custom TWRP,
Rebooted into Recovery,
Flashed the Treble .zip file,
Rebooted into Recovery,
Flashed the latest Havoc OS, then Magisk v20.3
then rebooted and it's stuck here.
Strange thing is, Windows has flashed up saying that it is "setting up Samsung_Android" while it's on the splash screen.
I come from the tweaked T825 ROM.
Anyone else had this issue? Should I have flashed stock first?
ianrobbie said:
Hey all. Flashed all the relevant files in the relevant order and currently have a tablet sitting on the Tab S3 splash screen. How long does this normally take?
I flashed the custom TWRP,
Rebooted into Recovery,
Flashed the Treble .zip file,
Rebooted into Recovery,
Flashed the latest Havoc OS, then Magisk v20.3
then rebooted and it's stuck here.
Strange thing is, Windows has flashed up saying that it is "setting up Samsung_Android" while it's on the splash screen.
I come from the tweaked T825 ROM.
Anyone else had this issue? Should I have flashed stock first?
Click to expand...
Click to collapse
Well I've hard-bricked my tab by flashing the Treble zip so consider yourself lucky. I think you should flash ODIN stock and start from scratch. Flash ashyx's TWRP, follow the instructions there. DO NOT FLASH MAGISK. Then flash Treble TWRP, flash zip, reboot recovery, DO A WIPE DATA / FACTORY RESET, NOT FORMAT, Then flash Havoc OS a only or whatever. After that wipe cache/dalvik and let it boot to ROM, AND THEN flash magisk and stuff.
I hard bricked my tab because Magisk was installed on the device while I flashed Treble. So yeah DON'T DO THAT EITHER
By the way im so sorry for being 2 months late i saw this just now
Looking dangerous. I'd like to try it but uncertain procedures
NullCode said:
Well I've hard-bricked my tab by flashing the Treble zip so consider yourself lucky. I think you should flash ODIN stock and start from scratch. Flash ashyx's TWRP, follow the instructions there. DO NOT FLASH MAGISK. Then flash Treble TWRP, flash zip, reboot recovery, DO A WIPE DATA / FACTORY RESET, NOT FORMAT, Then flash Havoc OS a only or whatever. After that wipe cache/dalvik and let it boot to ROM, AND THEN flash magisk and stuff.
I hard bricked my tab because Magisk was installed on the device while I flashed Treble. So yeah DON'T DO THAT EITHER
By the way im so sorry for being 2 months late i saw this just now
Click to expand...
Click to collapse
would some of the issues seen by others be fixed if one started with non-rooted stock 9.0 and 9.0 bootloader (if it is different from that for Oreo)? thanks anyone
Disclaimer: I'm not a dev, i'm just someone who has a lot of time to do research on Windows, Android... So that i can say i'm quite a talent that stuffs when other don't, may be just know to use Facebook, Youtube or something similar. But when you're here, want to read my topic, i'm happy you're something like me, want your phone yours and yours only, want to do more with your phone. So let's get started.
- My Phone: Redmi 8A -4/64 China Variant, i'm not from China though. Running Xiaomi.eu rom 11.0.4.0 as base to install gsi. I have tried Global Rom but it's incompatible with my phone (random reboot, missing imei, no MAC address...) so please flash another market version with caution.
- Why i write this topic? Because firstly i want to demonstrate how to install a GSI rom. Secondly, i feel somehow wifi speed on MIUI is ridiculous, only 500-600kb/s, it takes me 15 minutes to download a 16mb app; random ping in game, that make the game not enjoyable. This wifi symptom is like on a phone from my country, Vsmart joy 2+, run on the same entry variant 4xx, due to support wifi 2.4 ghz only. (Because bluetooth interfering with wifi 2.4 Ghz and our device doesn't support 5ghz wifi)
Compare to MIUI, Havoc OS has somethings i like:
+ Faster download/upload speed: no delay with wifi bluetooth interference
+ Doesn't have bloatware, you choose what you want to install
+ All known bugs i mentioned in my previous topic are fixed, except Auto Brightness - i don't use it though
+ D2TW needs to be fixed. But i have a workaround using Magisk and root.
And a lot that i dont write all here.
Instructions:
Read my previous topic first, all instructions below will focus on Havoc OS only.https://forum.xda-developers.com/xi...de-how-to-install-magisk-miui-how-to-t4030175
0) Backup Backup Backup, be sure to have a plan in case anything goes wrong. I use a offline disk drive to backup anything important.
1) Unlock Bootloader, Install TWRP or Orange Fox. If you come from stock MIUI, use Volume Up + Power to enter recovery directly after flash with Fastboot, ortherwise, stock recovery will be replaced.
Remember to flash vbmeta.img.
2) Download all the files in my post, download Havoc OS GSI and extract to get system
From Official Havoc OS here: https://sourceforge.net/projects/havoc-os/files/a64-ab/ (Newer Version)
Download Opengapps (optional) from opengapps (10/arm/nano or pico)
Download boot.img from my previous topic, choose the right version matched your phone version.
3) Copy all the files to the phone. I recommend use a micro sd card because internal storage may be encrypted, or you can format data first, your call.
4) Format the following partitions: Cache, Dalvik, Data and System
5) Install system image to system partition.
6) Install permissiver_v5
7) Resize system partition to install opengapps.
8) Install Opengapps or what gapps you choose
9) Flash Certification + Patch
10) Reboot. If bootloop, format data. Not wipe data. Then setup your phone.
11) Install Magisk Manager. Follow the app instructions.
12) Install d2tw module to have d2tw feature. If it doesn't work, then try an alternative way:
Open /vendor/bin/init.qcom.post_boot.sh and add the string:
Code:
sendevent /dev/input/event2 0 1 5
then reboot
13) Enjoy Havoc OS. Install apps, configure settings...
How to Update
- Flash system image over, no wipe require. Just reboot.
Bugs
I don't use the phone often so i can say it's stable enough to be a daily driver rom. If there's any, just comment below so i can add them.
Additions
- Here are all apps i want to install on my phone: Youtube Vanced from https://vancedapp.com/; Bromite for browsing; modded messenger from @evilwombatHere, outdated version but still okay.
- If you don't like stock camera, you can use gcam, here is a working version i download from Telegram group: Here
- To fix Recording, from Misc features -> Force Timestamp Source, choose Clock boottime
And that's all. Now enjoy!
I gifted my sister this phone so i don't have device to test anymore. Still, sometime i'll test if i can. The guide still works so enjoy flashing!!!
Great. I've been using havocOs for almost two months now and it's great. Much quicker and smoother than stock miui. Only problem I've been trying to find a fix for is setting up a lock screen.
Thanks for sharing the dt2w module for magisk. Is there some sort of setting I need to mess with to get it to work? I've installed the module and activated it in magisk but dt2w still won't work. I also activated the dt2w setting that comes with havocOs 3.1 under " xiaomi features " but that never worked from the beginning.
ways2 said:
Great. I've been using havocOs for almost two months now and it's great. Much quicker and smoother than stock miui. Only problem I've been trying to find a fix for is setting up a lock screen.
Thanks for sharing the dt2w module for magisk. Is there some sort of setting I need to mess with to get it to work? I've installed the module and activated it in magisk but dt2w still won't work. I also activated the dt2w setting that comes with havocOs 3.1 under " xiaomi features " but that never worked from the beginning.
Click to expand...
Click to collapse
Did you flash no_encrypt zip? It'll make set up screen password impossible because encryption is disable. I have clean flashed Havoc OS and confirm d2tw module working, despite i don't active the xiaomi option in setting.
Ga_hap_la_chanh said:
Did you flash no_encrypt zip? It'll make set up screen password impossible because encryption is disable. I have clean flashed Havoc OS and confirm d2tw working, despite i don't active the xiaomi option in setting.
Click to expand...
Click to collapse
Yes I believe I did flash no_encrypt. Is there any possible way to re-enable Encryption to set up a screen lock at this point?
ways2 said:
Yes I believe I did flash no_encrypt. Is there any possible way to re-enable Encryption to set up a screen lock at this point?
Click to expand...
Click to collapse
There is a trick, you can enable encryption through Settings -> security -> Encryption and credentials then encrypt phone. If it doesn't work, then read this thread https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
Or you can do the whole process again, clean flash and do as my thread. May be d2tw starts working.
Thank you sir
thanks a lot for this
can you tell me how to upgrade our 32bit os to 64bit
Ga_hap_la_chanh said:
There is a trick, you can enable encryption through Settings -> security -> Encryption and credentials then encrypt phone. If it doesn't work, then read this thread https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
Or you can do the whole process again, clean flash and do as my thread. May be d2tw starts working.
Click to expand...
Click to collapse
I wasn't able to encrypt my phone it would just reboot and nothing change.
So I ended up re-flashing back to MIUI stock firmware.
Flashing OrangeFox and HavocOS 3.1
Flashed all of the other necessary stuff EXCEPT for Disable_ForceEncrypt.
Now my phone is encrypted and able to set up a Screen Lock .
Now I'm still not able to use dt2w for some odd reason. No worries though I'm able to set up tap status bar to lock so that'll help for Now until I can keep dt2w to work.
ways2 said:
I wasn't able to encrypt my phone it would just reboot and nothing change.
So I ended up re-flashing back to MIUI stock firmware.
Flashing OrangeFox and HavocOS 3.1
Flashed all of the other necessary stuff EXCEPT for Disable_ForceEncrypt.
Now my phone is encrypted and able to set up a Screen Lock .
Now I'm still not able to use dt2w for some odd reason. No worries though I'm able to set up tap status bar to lock so that'll help for Now until I can keep dt2w to work.
Click to expand...
Click to collapse
Hi bro
i am new to this
i have 2gb indian varient
can you make a full youtube tutorial of twrp installation
or give correct steps how to do twrp
---------- Post added at 05:48 AM ---------- Previous post was at 05:42 AM ----------
Ga_hap_la_chanh said:
Disclaimer: I'm not a dev, i'm just someone who has a lot of time to do research on Windows, Android... So that i can say i'm quite a talent that stuffs when other don't, may be just know to use Facebook, Youtube or something similar. But when you're here, want to read my topic, i'm happy you're something like me, want your phone yours and yours only, want to do more with your phone. So let's get started.
- My Phone: Redmi 8A -4/64 China Variant, i'm not from China though. Running Xiaomi.eu rom 11.0.4.0 as base to install gsi. I have tried Global 10.3 but it's incompatible with my phone (random reboot, missing imei, no MAC address...) so please flash another market version with caution.
- Why i write this topic? Because firstly i want to demonstrate how to install a GSI rom. Secondly, i feel somehow wifi speed on MIUI is ridiculous, only 500-600kb/s, it takes me 15 minutes to download a 16mb app; random ping in game, that make the game not enjoyable. This wifi symptom is like on a phone from my country, Vsmart joy 2+, run on the same entry variant 4xx.
Compare to MIUI, Havoc 3.1 has somethings i like:
+ Faster download/upload speed: almost the same as the speed of my network
+ Doesn't have some bloatwares, you choose what you want to install
+ All known bugs i mentioned in my previous topic are fixed, except Auto Brightness - i don't use it though
+ D2TW needs to be fixed. But i have a workaround using Magisk.
And a lot that i dont write all here.
Instructions:
Read my previous topic first, all instructions below will focus on Havoc OS only.https://forum.xda-developers.com/xi...de-how-to-install-magisk-miui-how-to-t4030175
0) Backup Backup Backup, be sure to have a plan in case anything goes wrong. I use a offline disk drive to backup anything important to me.
1) Unlock Bootloader, Install TWRP or Orange Fox. If you come from stock MIUI, use Volume Up + Power to enter recovery directly after flash with Fastboot, ortherwise, stock recovery will be replaced.
Remember to flash vbmeta.img.
2) Download all the files in my post, download Havoc OS GSI from ExpressLuke and extract to get system imagehttps://sourceforge.net/projects/expressluke-gsis/files/HavocOS/Ten/A64/AB/
Download Opengapps (optional) from opengapps (10/arm/nano or pico)
Download boot.img from my previous topic, choose the right version matched your phone version.
3) Copy all the files to the phone. I recommend use a micro sd card because internal storage may be encrypted, or you can format data first, your call.
4) Format the following partitions: Cache, Dalvik, Data and System
5) Install system image to system partition.
6) Install permissiver_v5
7) Resize system partition to install opengapps.
8) Install Opengapps or what gapps you choose
9) Flash Certification + Patch
10) Reboot. If bootloop, format data. Not wipe data. Then setup your phone.
11) Install Magisk Manager. Follow the app instructions.
12) Install d2tw module to have d2tw feature.
13) Enjoy Havoc OS. Install apps, configure settings...
Bugs
I don't use the phone often so i can say it's stable enough to be a daily driver rom. If there's any, just comment below so i can add them.
Additions
- Here are all apps i want to install on my phone: Youtube Vanced from vanced.app; Bromite for browsing; modded messenger from @evilwombatHere, outdated version but still okay.
- If you don't like stock camera, you can use gcam, here is a working version i download from Telegram group: Here
And that's all. Now enjoy!
Click to expand...
Click to collapse
Hi
can you make a youtube video of twrp and gsi installation
please man for redmi 8a
eddy law paul king said:
Hi bro
i am new to this
i have 2gb indian varient
can you make a full youtube tutorial of twrp installation
or give correct steps how to do twrp
---------- Post added at 05:48 AM ---------- Previous post was at 05:42 AM ----------
Hi
can you make a youtube video of twrp and gsi installation
please man for redmi 8a
Click to expand...
Click to collapse
I've considered making a complete tutorial on installing recovery, root, & rom installation for this phone. Next time I go back to stock I probably will make a video. Until then you can definitely follow the tutorials on this forum to install a custom recovery and rom. Personally I would recommend installing OrangeFox recovery because TWRP has touchscreen issues sometimes.
You will have to unlock the bootloader first which takes 14 days if you have not already.
The tool to unlock the Bootloader is here: https://en.miui.com/unlock/download_en.html
Once your bootloader is unlocked you're ready to install OrangeFox custom recovery, the files and instructions can be found here:
https://forum.xda-developers.com/xi...t/orangefox-recovery-xiaomi-redmi-8a-t4032583
Once you have OrangeFox recovery installed you can follow this tutorial in this thread to install HavocOS rom or the other thread
https://forum.xda-developers.com/xi...de-how-to-install-magisk-miui-how-to-t4030175
Try it out and then come back and let us know what problems you run into
ways2 said:
I've considered making a complete tutorial on installing recovery, root, & rom installation for this phone. Next time I go back to stock I probably will make a video. Until then you can definitely follow the tutorials on this forum to install a custom recovery and rom. Personally I would recommend installing OrangeFox recovery because TWRP has touchscreen issues sometimes.
You will have to unlock the bootloader first which takes 14 days if you have not already.
The tool to unlock the Bootloader is here: https://en.miui.com/unlock/download_en.html
Once your bootloader is unlocked you're ready to install OrangeFox custom recovery, the files and instructions can be found here:
https://forum.xda-developers.com/xi...t/orangefox-recovery-xiaomi-redmi-8a-t4032583
Once you have OrangeFox recovery installed you can follow this tutorial in this thread to install HavocOS rom or the other thread
https://forum.xda-developers.com/xi...de-how-to-install-magisk-miui-how-to-t4030175
Try it out and then come back and let us know what problems you run into
Click to expand...
Click to collapse
i am very afraid that i brick my devise
so make a video
it is accurate and much helpful and easy to understand
i am waiting
Can I use the attached files for installing gsi in redmi 9 ?
vinith 32 said:
Can I use the attached files for installing gsi in redmi 9 ?
Click to expand...
Click to collapse
no
this is for 8 and 8a only
@Ga_hap_la_chanh
I'm wondering if that d2tw module not working for me has something similar to do with how the touch screen becomes unresponsive in TWRP for some people. What recovery did you use on your redmi?
ways2 said:
@Ga_hap_la_chanh
I'm wondering if that d2tw module not working for me has something similar to do with how the touch screen becomes unresponsive in TWRP for some people. What recovery did you use on your redmi?
Click to expand...
Click to collapse
I used TWRP then moved to Orange Fox. Everything working fine, may be your screen is different. In d2tw module, there's a file called readme.md: Manual usage : - enable $ set-dt2w 1 - disable $ set-dt2w 0
Just try it -))))))))
Great GSI. I have this one problem though. I cannot backup anything from TWRP. Is it really normal because it's encrypted?
createTarFork() process ended with ERROR: 255
Ga_hap_la_chanh said:
Disclaimer: I'm not a dev, i'm just someone who has a lot of time to do research on Windows, Android... So that i can say i'm quite a talent that stuffs when other don't, may be just know to use Facebook, Youtube or something similar. But when you're here, want to read my topic, i'm happy you're something like me, want your phone yours and yours only, want to do more with your phone. So let's get started.
- My Phone: Redmi 8A -4/64 China Variant, i'm not from China though. Running Xiaomi.eu rom 11.0.4.0 as base to install gsi. I have tried Global 10.3 but it's incompatible with my phone (random reboot, missing imei, no MAC address...) so please flash another market version with caution.
- Why i write this topic? Because firstly i want to demonstrate how to install a GSI rom. Secondly, i feel somehow wifi speed on MIUI is ridiculous, only 500-600kb/s, it takes me 15 minutes to download a 16mb app; random ping in game, that make the game not enjoyable. This wifi symptom is like on a phone from my country, Vsmart joy 2+, run on the same entry variant 4xx.
Compare to MIUI, Havoc 3.1 has somethings i like:
+ Faster download/upload speed: almost the same as the speed of my network
+ Doesn't have some bloatwares, you choose what you want to install
+ All known bugs i mentioned in my previous topic are fixed, except Auto Brightness - i don't use it though
+ D2TW needs to be fixed. But i have a workaround using Magisk.
And a lot that i dont write all here.
Instructions:
Read my previous topic first, all instructions below will focus on Havoc OS only.https://forum.xda-developers.com/xi...de-how-to-install-magisk-miui-how-to-t4030175
0) Backup Backup Backup, be sure to have a plan in case anything goes wrong. I use a offline disk drive to backup anything important to me.
1) Unlock Bootloader, Install TWRP or Orange Fox. If you come from stock MIUI, use Volume Up + Power to enter recovery directly after flash with Fastboot, ortherwise, stock recovery will be replaced.
Remember to flash vbmeta.img.
2) Download all the files in my post, download Havoc OS GSI from ExpressLuke and extract to get system imagehttps://sourceforge.net/projects/expressluke-gsis/files/HavocOS/Ten/A64/AB/
Download Opengapps (optional) from opengapps (10/arm/nano or pico)
Download boot.img from my previous topic, choose the right version matched your phone version.
3) Copy all the files to the phone. I recommend use a micro sd card because internal storage may be encrypted, or you can format data first, your call.
4) Format the following partitions: Cache, Dalvik, Data and System
5) Install system image to system partition.
6) Install permissiver_v5
7) Resize system partition to install opengapps.
8) Install Opengapps or what gapps you choose
9) Flash Certification + Patch
10) Reboot. If bootloop, format data. Not wipe data. Then setup your phone.
11) Install Magisk Manager. Follow the app instructions.
12) Install d2tw module to have d2tw feature.
13) Enjoy Havoc OS. Install apps, configure settings...
Bugs
I don't use the phone often so i can say it's stable enough to be a daily driver rom. If there's any, just comment below so i can add them.
Additions
- Here are all apps i want to install on my phone: Youtube Vanced from vanced.app; Bromite for browsing; modded messenger from @evilwombatHere, outdated version but still okay.
- If you don't like stock camera, you can use gcam, here is a working version i download from Telegram group: Here
And that's all. Now enjoy!
Click to expand...
Click to collapse
Bro having oragane fox recovery installed on my redmi 8a device, can you please tell me at which step of flashing gsi we have to flash vbmeta.img and boot. Img
---------- Post added at 03:13 AM ---------- Previous post was at 02:26 AM ----------
ways2 said:
I wasn't able to encrypt my phone it would just reboot and nothing change.
So I ended up re-flashing back to MIUI stock firmware.
Flashing OrangeFox and HavocOS 3.1
Flashed all of the other necessary stuff EXCEPT for Disable_ForceEncrypt.
Now my phone is encrypted and able to set up a Screen Lock .
Now I'm still not able to use dt2w for some odd reason. No worries though I'm able to set up tap status bar to lock so that'll help for Now until I can keep dt2w to work.
Click to expand...
Click to collapse
bro can you tell me that have you flashed the boot.img while flashing the gsi and if yes then at which step..
ItsmeTushar said:
Bro having oragane fox recovery installed on my redmi 8a device, can you please tell me at which step of flashing gsi we have to flash vbmeta.img and boot. Img
---------- Post added at 03:13 AM ---------- Previous post was at 02:26 AM ----------
bro can you tell me that have you flashed the boot.img while flashing the gsi and if yes then at which step..
Click to expand...
Click to collapse
Boot.img and vbmeta are done before flashing the gsi. I'd recommend reading this thread first for better understanding
https://forum.xda-developers.com/xi...de-how-to-install-magisk-miui-how-to-t4030175
Zzzleepy said:
Great GSI. I have this one problem though. I cannot backup anything from TWRP. Is it really normal because it's encrypted?
createTarFork() process ended with ERROR: 255
Click to expand...
Click to collapse
I'm getting the same error with attempting to make a back up in orangefox. After seeing you have the same problem now I'm assuming it is indeed a problem with encryption? I was able to make backups successfully before my phone was encrypted so I still have an old back up on my PC. However it would be nice to be able to make a new fresh back up.
I'm getting the same error with attempting to make a back up in orangefox. After seeing you have the same problem now I'm assuming it is indeed a problem with encryption? I was able to make backups successfully before my phone was encrypted so I still have an old back up on my PC. However it would be nice to be able to make a new fresh back up.
Click to expand...
Click to collapse
That was weird. In stock ROM, I can back up the /data/media just fine even when encrypted. But after having Havoc OS, I cannot do that anymore. Tried on both TWRP and OrangeFox. I can, with an unencrypted phone, but I do not feel comfortable without a lockscreen. Tried all things I have researched on that error. Not one worked. Might as well just stick to Titanium Backup for backups.
Overall, great GSI. Loading is faster than on stock (with the internet too)! Though, I have another issue with regards to the locking of apps, so that the app would not be cleared. Speaking of clearing apps, it is tiring to scroll left just to see the "Clear All" option in Recents. Autostart too.
I know you are not the developer, but just letting you know my concerns.
How to resize system partition for install gapps?
Soerex24 said:
How to resize system partition for install gapps?
Click to expand...
Click to collapse
Reboot to custom recovery > Menu > Manage Partitions > System > Resize or Repair
{
"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"
}
Code:
*** Disclaimer
I am not responsible for any damage you made to your device
You have been warned
crDroid is designed to increase performance and reliability over stock Android for your device also attempting to bringing many of the best features existent today
Features:
https://github.com/crdroidandroid/crdroid_features/blob/10.0/README.mkdn
Downloads
Official Website
Flashing Instructions:
Pre-installation:
TWRP (Download from here)
gapps (Download from here)
Magisk 20.0 or newer for root (after first boot) - (Download from here)
*****Disclaimer*****
Important note before proceeding!!!
The copy A/B partitions zip is crucial in order to prevent bricks. It only needs to be done if you're coming from the stock ROM or you recently restored stock firmware manually. Other wise without it you can brick due to Motorola's A/B partition scheme.
Only use TWRP version 3.3.1-0, it has an advanced option for recovery bootloop fix. Sorry for some hassles with TWRP. It is not ROM related but the version I use works 100% of the time.
My apologies for any confusion/problems flashing!
Preparation for A/B Roms:
01. Download TWRP version 3.3.1-0 (do not use any other version)
02. Remove your google account under Settings > Accounts then factory reset your device as FRP is enforced.
03. Unlock your bootloader
04. Use the terminal to boot the latest twrp.img "fastboot boot twrp.img"
05. While on Slot_A Flash copypartitions.zip (This step only needs to be completed Once only after updating from stock factory firmware.)
06. While in TWRP choose Reboot > bootloader
07. Now you're ready for ROM Steps below
ROM - Installation:
01. Download the ROM.
02. Use terminal to boot latest twrp.img "fastboot boot twrp.img"
03. Wipe data, dalvik, system and internal storage, then format userdata.
04. Flash ROM.zip + TWRP_installer
05. Reboot > Recovery
06.Install Gapps + Magisk (if you choose)
07. Reboot > System
Updating (AKA 'dirty flash'):
01. Download the updated ROM
02. Boot into recovery
03. Install ROM.zip + TWRP_installer
04. Reboot > Recovery
05. flash GAPPS + Magisk (if you choose)
06. Reboot > System
Notes:
Any time your internal storage aka "Userdata" is from a stock install you must "format data" in recovery before using ROMS
Upgrading from earlier version of crDroid:
The only difference between clean flash as above and upgrading is you just wipe system & cache, leaving data. Everything else is the same. ***Remember to always clean flash before reporting problems. Clean flashing is always the best method of ROM install.
SOURCES:
ROM: https://github.com/crdroidandroid
Changelog::
https://raw.githubusercontent.com/crdroidandroid/android_vendor_crDroidOTA/10.0/changelog_ocean.txt
Known issues:
<!-- list here -->
Visit official website @ crDroid.net
crDroid Community Telegram
Donate to help our team pay server costs
© 2020 GitHub, Inc.
XDA:DevDB Information
CrDroid, ROM for the Moto G7 Power
Contributors
Rondeau79
Source Code: https://github.com/Rondeau79/android_kernel_motorola_sdm632
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
ROM Firmware Required: Latest TWRP unlocked bootloader
Based On: AOSP, Lineage OS
Version Information
Status: Stable
Current Stable Version: QQ2A.200305.003
Stable Release Date: 2020-03-22
Created 2020-03-22
Last Updated 2020-06-23
Reserved
Ahh the ole triple posts. Don't you just love it when that happens. lol. Hell of a job on this! Will Android 10 for Ocean device ever be able to have an enforcing kernel or no? Probably waiting for source for 10/Q before messing with all that stuff? I'm just curious and figured I'd ask.. Awesome work!!!! :good:
flash713 said:
Ahh the ole triple posts. Don't you just love it when that happens. lol. Hell of a job on this! Will Android 10 for Ocean device ever be able to have an enforcing kernel or no? Probably waiting for source for 10/Q before messing with all that stuff? I'm just curious and figured I'd ask.. Awesome work!!!! :good:
Click to expand...
Click to collapse
Thanks, this one was a tough task to get done. I don't mind a permissive kernel. I really don't dive too far into the Android system. I am a fan first and a developer second! I still really don't have an understanding of code and stuff. I just go with my instincts.
I performed a 'dirty flash' coming from crDroid 5.12 (based on Android 9).
I did not delete my Google account from the phone prior to flashing. This is the first time I've had problems upgrading crDroid. I realize it's also the first time I've done a major increment to the underlying Android OS.
Upon first boot I saw the new boot animation (it looks great!) but the phone did not complete booting after about ten minutes. I interrupted the boot by holding the power key. I tried wiping data. Later, I also tried re-formatting data partition (including built-internal media). I also tried re-installing the most recent version of crDroid 5.12 with no success with that as well.
Suggestions regarding the best way to correct this would be helpful and appreciated.
In the meantime, I'll look around and trying some other things. I hope it might be corrected without having to resort to ADB / PC connection, but I'll try whatever I can.
I don't know if this result is considered "a brick" because I can boot into TWRP.
danny8 said:
I performed a 'dirty flash' coming from crDroid 5.12 (based on Android 9).
I did not delete my Google account from the phone prior to flashing. This is the first time I've had problems upgrading crDroid. I realize it's also the first time I've done a major increment to the underlying Android OS.
Upon first boot I saw the new boot animation (it looks great!) but the phone did not complete booting after about ten minutes. I interrupted the boot by holding the power key. I tried wiping data. Later, I also tried re-formatting data partition (including built-internal media). I also tried re-installing the most recent version of crDroid 5.12 with no success with that as well.
Suggestions regarding the best way to correct this would be helpful and appreciated.
In the meantime, I'll look around and trying some other things. I hope it might be corrected without having to resort to ADB / PC connection, but I'll try whatever I can.
I don't know if this result is considered "a brick" because I can boot into TWRP.
Click to expand...
Click to collapse
You are not bricked. When coming from one version of android to another a clean flash must be done. You can dirty flash after that. Wipe both boot slots and then go about flashing like normal. First boot takes a while. It won't boot without wiping the system partition.
Excuse my ignorance, where do I have to install the rom, gapps and magisk, in slot A or B? Thank you in advance (sorry bad English)
D13Gho said:
Excuse my ignorance, where do I have to install the rom, gapps and magisk, in slot A or B? Thank you in advance (sorry bad English)
Click to expand...
Click to collapse
With the A/B partitions scene. When you flash a ROM it will be installed to the opposite slot. If you are on A then the zip will be installed to B and vica versa. Gapps are flashed after you reboot to recovery when you are on the boot slot the ROM was installed on same as Magisk.
Thank you, Rondeau79. I got it installed.
It looks great!
I've got every thing installed and running, but after setting up my apps (Chrome, messages, photos) app opening/closing is quite laggy. It become unusable after a couole hours.
Johnfoo19 said:
I've got every thing installed and running, but after setting up my apps (Chrome, messages, photos) app opening/closing is quite laggy. It become unusable after a couole hours.
Click to expand...
Click to collapse
Give it a little time to set in. Usually a fresh install takes a bit.
danny8 said:
Thank you, Rondeau79. I got it installed.
It looks great!
Click to expand...
Click to collapse
You're welcome.
pie had the option of changing colors in the display settings I am not a fan of blue I like black and red. is this in a future update it was the main reason i uninstalled the other android 10 roms
cgrimm9 said:
pie had the option of changing colors in the display settings I am not a fan of blue I like black and red. is this in a future update it was the main reason i uninstalled the other android 10 roms
Click to expand...
Click to collapse
Go to display styles and wallpapers to change to colors.
Is there any way to set the position of the battery bar? like bottom of the screen or lower status bar because where default is top of screen you kinda miss half the bar because of the notch
Has anyone had any issues with mobile data not working after installing this ROM? I was able to make calls and send texts (I have Sprint, phone: Moto G7 Power X1995-5). I reflashed it and OEM locked back to stock firmware since mobile data was not working. Also, I did not have SD card since I don't have one
n00b Samurai said:
Is there any way to set the position of the battery bar? like bottom of the screen or lower status bar because where default is top of screen you kinda miss half the bar because of the notch
Click to expand...
Click to collapse
Sorry there isn't, I can't change the base features of the ROM. However you can change the color and thickness of the bar and it's position on the screen.
You can always adjust the screen in order to account for the notch. It's in the developer settings.
barados742 said:
Has anyone had any issues with mobile data not working after installing this ROM? I was able to make calls and send texts (I have Sprint, phone: Moto G7 Power X1995-5). I reflashed it and OEM locked back to stock firmware since mobile data was not working. Also, I did not have SD card since I don't have one
Click to expand...
Click to collapse
You need an external sdCard for flashing ROMs. Wiping the user partitions properly is essential for a properly working ROM. If you just have internal storage then the installation of an OS won't be done right.
Thanks for the reply! I just bought an SD card and will try it tomorrow and will respond if it worked.
Good morning, guys I tried to install on my MOTO G 7 POWER 3/32 and the rom does not install says it is not compatible with the system. Any tips?