Develop Bugs

AOSP, RR Resurrection Remix, ArrowOS and others

I just wanted to point out that I have been able to boot some treble GSI on my device from different roms like AOSP, RR, ArrowOS in the treble section of XDA and some of them boot fine, but I have found some issues:
PHH PIE GSI doesn't like magisk it breaks wifi and mobile data once magisk is flashed
PHH Oreo AOSP GSI I do not remember any issues besides being too stock for my liking
RR GSI It has so many options almost comparable to what a Venom Rom would be for HTC devices
TWRP it is not able to read encryption on any of this GSIs
AOSP Oreo I don't remember if the other variants GSIs does not read exFAT formatted MicroSD (works on PIE GSI)
https://forum.xda-developers.com/project-treble/trebleenabled-device-development
I would like more users to share their experience here with GSIs
the steps I took to flash this
1. make sure you download an arm64 AB GSI image from your favorite ROM
2. go to TWRP wipe section wipe system, Dalvik cache data & internal
3. go to TWRP wipe section format data, type yes
5. restore stock Vendor.img and stock Boot.img
6. flash GSI
7. reboot & enjoy
first boot might take awhile it encrypts the device, thi is the part that makes TWRP not being able to decrypt data since TWRP decrypts Qualcomm Encryption on our device but no stock android encryption this part it is possible to fix by TWRP team and it will probably come in later

Thanks for sharing. I was planning on trying out a GSI this weekend and see how it goes. Glad it works!

I forgot to save the stock vendor and stock boot file I need these two files Can you help

emrince said:
I forgot to save the stock vendor and stock boot file I need these two files Can you help
Click to expand...
Click to collapse
https://forum.xda-developers.com/u12-plus/how-to/collection-htcu-u12-ruu-firmware-t3794664/page24
Read the OP there

I tried to boot the RR img, no dice.
Backed up modified rom on slot b
Switched to slot a in TWRP, supposedly empty
Wiped system, data, cache, dalvik
Flashed prior stock vendor img and boot img
Flashed RR ab arm64 su gapps Img
Rebooted slot a
Bootloop
Interestingly, after looking 3 times, my phone booted back to slot b by itself back to stock, back up restored just fine
I realize I didn't wipe factory reset with yes

Finally got RR to to boot! It's a very finicky process. I think my problem was I kept trying to "dual" boot, Viper in one slot and the GSI in the other. Turns out it just has to be in the active slot, regardless of which slot you switch to in TWRP. Maybe that's obvious for some. This a/b partition business sure has a learning curve.
Anyway, things I noticed on RR: Lots of customization as usual for RR, very fast and smooth, screen brightness is on max all the time regardless of slider or auto brightness, and I couldn't make phone calls but texting worked. Everything else seemed to work fairly well. I love the fling navbar....on to the next one.

I'm not sure if anyone else is trying the GSI's, this doesn't seem to be a very active thread. So far I have only been able to boot RR 8.1 GSI. I have tried multiple other images without any success. I think the reason I didn't get data and calls didn't work on RR is that I am on Verizon and the HTC u12 does not have CDMA radios. Volte calling was not available on the rom. Oh well. I'm excited for the upcoming developments in the Viper forum. If anyone knows a fix for data on verizon with the GSI's, I'm all ears. Thanks

Anybody successful in making one of this ROMs a daily driver?
Sent from my HTC U12+ using XDA Labs

Resurrection Remix 8.1 is pretty stable if you are on a gsm network. I popped in a Tmobile sim card and it was pretty solid. There are some minor annoyances like the inability to adjust the brightness (always on full), though decreasing screen pixels makes it more dim, vendor mismatch message on boot, and no volte or wifi calling. There may be some other small things like with the camera and bluetooth but I didn't keep it for long as I am on Verizon and don't get data. I could see using it as a DD though. There are probably ways to fix the annoyances I mentioned.

Have any of you tested this version of RR on U12+?
https://forum.xda-developers.com/pr...0-resurrection-remix-v7-0-arm64-32-b-t3891636
For example, face recognition, 4k camera mode, slow motion recording, 3D sound, AudioFocus, bokeh mode etc.?
regards
q

@JEANRIVERA Is i't there any working Android P GSI rom?
Just can't wait anymore HTC for P update =)

nomaj said:
@JEANRIVERA Is i't there any working Android P GSI rom?
Just can't wait anymore HTC for P update =)
Click to expand...
Click to collapse
Original PHH, ArrowOS & DescendantOS all work fine, the only problem is no Magisk support yet

JEANRIVERA said:
Original PHH, ArrowOS & DescendantOS all work fine, the only problem is no Magisk support yet
Click to expand...
Click to collapse
So.. i will missing root? and fixes for google sotre etc ?

JEANRIVERA said:
Original PHH, ArrowOS & DescendantOS all work fine, the only problem is no Magisk support yet
Click to expand...
Click to collapse
I have problem with install ArrowsOS, i have still bootlops.. It's probably related to a / b boot, how to fix this? Twrp say "No OS installed", i set wipe system,data,cache next i flash vendor, boot and system file, i made a mistake?

JEANRIVERA said:
Original PHH, ArrowOS & DescendantOS all work fine, the only problem is no Magisk support yet
Click to expand...
Click to collapse
@JEANRIVERA
Is't this update helpping us?
2019.3.28 Magisk v19.0
https://forum.xda-developers.com/showpost.php?p=79216305&postcount=50https://forum.xda-developers.com/showpost.php?p=79216305&postcount=50

mientus25 said:
I have problem with install ArrowsOS, i have still bootlops.. It's probably related to a / b boot, how to fix this? Twrp say "No OS installed", i set wipe system,data,cache next i flash vendor, boot and system file, i made a mistake?
Click to expand...
Click to collapse
Hey, I'm having the same problem. Did you work out a solution to get any GSI to boot on your U12?

SilentAchiever said:
Hey, I'm having the same problem. Did you work out a solution to get any GSI to boot on your U12?
Click to expand...
Click to collapse
I tried to find a solution for 12 hours and nothing came of it

I's dual sim working on GSI roms?
---------- Post added at 10:38 AM ---------- Previous post was at 10:36 AM ----------
mientus25 said:
I tried to find a solution for 12 hours and nothing came of it
Click to expand...
Click to collapse
1. make sure you download an arm64 AB GSI image from your favorite ROM
2. go to TWRP wipe section wipe system, Dalvik cache data & internal
3. go to TWRP wipe section format data, type yes
5. restore stock Vendor.img and stock Boot.img
6. flash GSI
Did you flashed GSI rom from point 6?

Yes, i follow this instruction and twrp say "OS no installed".

mientus25 said:
Yes, i follow this instruction and twrp say "OS no installed".
Click to expand...
Click to collapse
Check this... wiping
"for GSI it is better to wipe from stock recovery "

Treble Pie GSI Sprint LS998

I no longer have the V30 i now own the V40 this guide should still work tho
I didn't want to clog up the other thread so here goes.
First you want to follow this guide
You have to fix Device not Certified in order to download anything from the Play-store no matter what gapps package you use (Except for in Havoc-OS),
I personally use the Fire Gapps, which happen to also include a audio mod....so 2 birds one stone.....
For the Launcher that you see in the screen shots I'm using Pixel Experience Launcher option 2 from Magisk
And for the app icons i'm using Omoro these are not free but look amazing.
I'm currently using Havoc-OS 2.0 and Benzo Rom 9.0
Here are my steps for having a 99% stable working GSI Rom
1. Wipe everything except for storage.
2. Flash 9.0 Pie GSi.img
3. Flash gapps.
4. Restore Boot and Vendor Partitions from working Treble LineageOS 15 back up.
5. Reboot and see if it works.
6. Go back into twrp and flash anything else.
7. Use the following APN settings to get 4GLTE you will notice "4G+" when getting your fast speeds (i have added a few edits to the APN from the V40)
Name : Sprint
APN : x.ispsn
Proxy : Not Set
Port : Not Set
Username : Not Set
Password : Not Set
Server : Not Set
MMSC : http://mms.sprintpcs.com/servlets/mms or http://mms.sprintpcs.com
MMS Proxy : 68.28.31.7 or oap7.sprintpcs.com
MMS Port : 80
MCC : 310 or 312
MNC : 120 or 530
Authentication Type : Not Set
APN Type : default,supl,hipri,fota,MMS,LTE,ia,ims,cbs (you can try adding dun as well for unlimited tethering)
APN Protocol : IPv4/IPv6
APN Roaming Protocol : IPv4/IPv6
Bearer : Unspecified
MNVO Type : SPN
MVNO value: Sprint
Thanks to kountry83 for uploading a fix for NFC see it in the attachments below
kountry83 said:
I created a NFC fix if you want to try it out, I just tweaked the config file a little bit just now. See if this helps. Let me know the progress please.
Click to expand...
Click to collapse

Do you know if anybody has gotten it to work on the us998/h931 model?

Ainz_Ooal_Gown said:
You have to fix Device not Certified in order to download anything from the Play-store no matter what gapps package you use.
Click to expand...
Click to collapse
How to do this?
Sent from my LG-H930 using Tapatalk

quangv said:
How to do this?
Sent from my LG-H930 using Tapatalk
Click to expand...
Click to collapse
It's step 4 or 5 in the original guide.

I have updated the OP check it out

No matter which GSi I use, I get system ui crashes occasionally. I'm currently on Havoc 2.0 and System UI hangs here and there and then crashes. What is the most stable GSi?

djpabz23 said:
No matter which GSi I use, I get system ui crashes occasionally. I'm currently on Havoc 2.0 and System UI hangs here and there and then crashes. What is the most stable GSi?
Click to expand...
Click to collapse
Benzo is pretty stable at the moment and so is Pixel Experience Unofficial 9.0

Ainz_Ooal_Gown said:
Benzo is pretty stable at the moment and so is Pixel Experience Unofficial 9.0
Click to expand...
Click to collapse
Benzo is where I get the most freezes and hangs, haha. I'm on ArrowOS right now, will see how it goes.
Edit: Also, do you get an error message saying theres an internal error with your device upon boot?

djpabz23 said:
Benzo is where I get the most freezes and hangs, haha. I'm on ArrowOS right now, will see how it goes.
Edit: Also, do you get an error message saying theres an internal error with your device upon boot?
Click to expand...
Click to collapse
Yes that error is normal even the pixel phones get it from time to time. What else did you flash from the other guide?

Ainz_Ooal_Gown said:
Yes that error is normal even the pixel phones get it from time to time. What else did you flash from the other guide?
Click to expand...
Click to collapse
The only things I flashed afterwards were the Fire GAPPS that you recommended, Magisk, and the Magisk module to fix the unverified device problem. That is it.
Just a quick question, what format is your /system/ partition?

djpabz23 said:
The only things I flashed afterwards were the Fire GAPPS that you recommended, Magisk, and the Magisk module to fix the unverified device problem. That is it.
Just a quick question, what format is your /system/ partition?
Click to expand...
Click to collapse
I also flash Pie-NFC-Fix, dt2w_on_gsi_joan, Post-sGSI_V30_fix_vibrator, Overlays (except for on GSI like Havoc-OS with rounded corners already implemented), System_Accents_P. and only flash the Fire Gapps on GSI roms that don't already include them. Benzo and Pixel Experience pie both include Gapps.

Ainz_Ooal_Gown said:
I also flash Pie-NFC-Fix, dt2w_on_gsi_joan, Post-sGSI_V30_fix_vibrator, Overlays (except for on GSI like Havoc-OS with rounded corners already implemented), System_Accents_P. and only flash the Fire Gapps on GSI roms that don't already include them. Benzo and Pixel Experience pie both include Gapps.
Click to expand...
Click to collapse
I just tried Pixel Experience, and wow... Most stable GSI I have used. No FC's or anything.
Edit: Upon further testing, camera doesn't seem to work.

djpabz23 said:
I just tried Pixel Experience, and wow... Most stable GSI I have used. No FC's or anything.
Edit: Upon further testing, camera doesn't seem to work.
Click to expand...
Click to collapse
Try GCAM from our V30 themes and apps section or Open Cam from the play store

Ainz_Ooal_Gown said:
Try GCAM from our V30 themes and apps section or Open Cam from the play store
Click to expand...
Click to collapse
Tried, no dice. I'll just stick with DotOS for now.

djpabz23 said:
Tried, no dice. I'll just stick with DotOS for now.
Click to expand...
Click to collapse
Camera is hit or miss at the moment...if SGCMarkus can figure out how to boot PIE specifically for our device properly then we can get somewhere on the Camera.

I only got bootloop, never a succesfull boot up. Here are my steps:
Wipe davik, system, data, cache, vendor, internal storage
Flash lineage treble
Back up boot, vendor, vendor img
Wipe davik, system, data, cache, vendor
Flash pixel experience img
Restore boot + vendor + vendor img
Reboot
Bootloop
Someone please tell me what i did wrong!!

Ainz_Ooal_Gown said:
Camera is hit or miss at the moment...if SGMarkus can figure out how to boot PIE specifically for our device properly then we can get somewhere on the Camera.
Click to expand...
Click to collapse
Who said it has to be @SGCMarkus? I already have Pie working fine on 90% of the things. camera works oob.

me2151 said:
Who said it has to be @SGCMarkus? I already have Pie working fine on 90% of the things. camera works oob.
Click to expand...
Click to collapse
Well he's the only developer I know working on Pie for the V30 .-. unless your saying that your gonna take a crack at being a developer?

black metallic said:
I only got bootloop, never a succesfull boot up. Here are my steps:
Wipe davik, system, data, cache, vendor, internal storage
Flash lineage treble
Back up boot, vendor, vendor img
Wipe davik, system, data, cache, vendor
Flash pixel experience img
Restore boot + vendor + vendor img
Reboot
Bootloop
Someone please tell me what i did wrong!!
Click to expand...
Click to collapse
If you don't wipe the vendor in between Lineage and Pie then you don't need to restore it...

Ainz_Ooal_Gown said:
If you don't wipe the vendor in between Lineage and Pie then you don't need to restore it...
Click to expand...
Click to collapse
Yeah, tried that too. Still got bootloop

[GUIDE] How to flash Android 9 Pie (PixelExperience, Havoc OS etc.)

Hello fellow XDA members and flashaholic people! This is a guide about flashing sGSI or GSI (semi-GSI) Android Pie images on VINCE.
This guide is for VINCE only! Please don't try it on WHYRED it may work or it may not.
First you need to treble enabled custom recovery. I suggest OrangeFox V8.1 https://forum.xda-developers.com/redmi-note-5/development/official-orangefox-recovery-project-t3807479
You can either flash it via TWRP or extract zip and flash recovery img by fastboot method.
Second you need treble enabled custom Oreo ROM, I suggest Cardinal-AOSP as it's vendor.img works flawlessly. https://forum.xda-developers.com/redmi-note-5/development/rom-cardinalaosp-t3774232
And third step includes the GSI image. You can find several GSI's here; https://forum.xda-developers.com/project-treble/trebleenabled-device-development
After downloading .zip file from any ROM you wanted extract it to get its system image and move it into the either internal storage or SD card. [SYSTEM IMAGE ONLY NEEDED]
I tried Pixel Experience 9.20 and Havoc OS 9.18 builds both booted without issues.
Please note that you need GApps package for ROM's (Except PixelExperience) you can find them here; https://opengapps.org/ Suggested package is Nano one. But if you want more you can go for bigger packages. I always use Mini version of it.
Steps to get Pie working on our device:
1. Reboot to custom recovery (if you have) flash OrangeFox R8.1 treble-enabled recovery. [If you have already have OrangeFox Recovery skip this step]
2. Touch Wipe and wipe /system /data /cache /dalvik and format /data
3. Flash cardinal-aosp ROM to your device You do not need to install GApps as we are going to use Pie anyway.
4. After flashing reboot to system it will directly go into launcher without setting stuff up. Reboot your device to recovery again.
5. Touch install, touch install image and flash the system image you've extracted. Wait for it to complete.
5.1 If you installed other than Pixel Experience please install proper GApps right after. [IF GAPPS WONT INSTALL BOOT THE DEVICE INTO SYSTEM FIRST AND WHEN BOOT COMPLETED PLEASE REBOOT RECOVERY AND FLASH GAPPS IT WILL WORK] After GApps installed go to wipe and do a factory reset in recovery. Reboot the device into system.
6. After you set up your device there is several optional operations you can do;
6.1 Root: You can use Magisk v17.1 or above to get root access. [Flash via recovery, if Magisk app wont appear in app menu you can install it from apkmirror safely]
6.2 Modules: Magisk modules like V4A, Unified Hosts Adblock etc. works. [Tested].
6.3 Kernel: You can use Genom Kernel or Dark Ages Tercero kernel. [Tested Dark Ages Tercero, works]
PLEASE KEEP IN MIND I DO NOT DEVELOPING ABOVE GSI IMAGES OR HELPING TO DEVELOP. IF YOU HAVE ANY BUGS TO REPORT PLEASE REPORT IN PROPER FORUM POST. I CAN HELP ABOUT INSTALLATION ONLY.
Ah, and there is few screenshots i'll share (Pixel Experience 9.0):

Don't need to flash p lag fix, volte fix and other stuff?

Ritik17 said:
Don't need to flash p lag fix, volte fix and other stuff?
Click to expand...
Click to collapse
Since i did not have any problems about lag or freeze dont need to flash it. Though im not sure about VoLTE but it seems broken for me too. I still wait for official or unofficial Pie ports (which even redmi 2 and 3 got)

bdogan1912 said:
Since i did not have any problems about lag or freeze dont need to flash it. Though im not sure about VoLTE but it seems broken for me too. I still wait for official or unofficial Pie ports (which even redmi 2 and 3 got)
Click to expand...
Click to collapse
Any other bug or issue that you've found in the ROM? Camera problems? Bluetooth or Wifi's MAC changing or reverting to 00:00:00...? Battery drains, memory leaks, crashes? GPS problems? anything?

moralesnery said:
Any other bug or issue that you've found in the ROM? Camera problems? Bluetooth or Wifi's MAC changing or reverting to 00:00:00...? Battery drains, memory leaks, crashes? GPS problems? anything?
Click to expand...
Click to collapse
In few hours of usage i did not encountered very-serious level bugs. Battery was fine and didn't seemed like to draining. Bluetooth and WiFi had no issues for me either. Only VoLTE doesnt works and as may you know thats global issue on it. Did not faced any mem-leaks or running out of memory problems, with freshest install it used up to 1.3 GB mem and with some apps like social ones it went up to 1.6 to 1.9 GB but ROM was overall butter smooth without single lag or freeze. No FCs either, GPS works i guess it was enabled by default on fresh install as usual but since im not using the GPS that much i did not tested it fully though.
As you can guess those are still experimental/beta builds could have issues that i did not encounter. But overall was very fine for me. I'd keep it but it kinda messed "about phone" settings as it goes manufacturer and model both goes by unknown or phh-treble. It's very natural since i installed as GSI image but still bothered me.
Almost forgot; In Havoc OS settings goes direct crash if you touch battery in settings. PE works fine but it has problems with Dark theme beign not applied correctly. Also i did not used or tried substratum or its themes.

Thank you for your instructions. I wanted to install a GSI 9.0 ROM since Pie came out, but other threads with instructions were too complex or convoluted that I thought it was harder.
I would like to make some clarifications on your steps:
* I used the unofficial PixelExperience 9.0 GSI image, as you said. It feels and behaves almost exactly as the official PixelExperience build for our device, but with nicer interface. The image is HERE. Just as a sidenote, the System image comes with DPI = 360, things look a bit too big. To make it look like MIUI or the official PixelExperience build for vince, a dpi of 390 should be set (this can be done from settings > System > Developer Settings > Minimal Width, under the "draw" section).
1. Reboot to custom recovery (if you have) flash OrangeFox R8.1 treble-enabled recovery. [If you have already have OrangeFox Recovery skip this step]
2. Touch Wipe and wipe /system /data /cache /dalvik and format /data
* At this step, I had to make "Format Data", and only then reboot to recovery again, and make the wipes to all other partitions. Without rebooting the wipes weren't possible (it was showing errors while trying to mount partitions). VENDOR PARTITION SHOULD NOT BE WIPED
3. Flash cardinal-aosp ROM to your device You do not need to install GApps as we are going to use Pie anyway.
4. After flashing reboot to system it will directly go into launcher without setting stuff up. Reboot your device to recovery again.
At this point, you must check that the hardware works correctly. Touch, screen, audio, BT, wifi, RIL, LTE or whatever you use. If something doesn't work at this point, it won't work after installing the GSI image.
5. Touch install, touch install image and flash the system image you've extracted. Wait for it to complete.
* In OrangeFox, at this point before flashing the GSI's .img file, the recovery asks for the type of image. For noobs and careful people, "System Image" must be selected before proceeding.
5.1 If you installed other than Pixel Experience please install proper GApps right after. [IF GAPPS WONT INSTALL BOOT THE DEVICE INTO SYSTEM FIRST AND WHEN BOOT COMPLETED PLEASE REBOOT RECOVERY AND FLASH GAPPS IT WILL WORK] After GApps installed go to wipe and do a factory reset in recovery. Reboot the device into system.
6. After you set up your device there is several optional operations you can do;
6.1 Root: You can use Magisk v17.1 or above to get root access. [Flash via recovery, if Magisk app wont appear in app menu you can install it from apkmirror safely]
* When installing Magisk through recovery, the framework will be installed, but the APK won't appear in the app list. It must be downloaded separately from https://github.com/topjohnwu/Magisk/releases/download/manager-v6.0.0/MagiskManager-v6.0.0.apk
The following modules are working without issues in my setup:
* Youtube Vanced
* Google Product Sans font
* MagiskHide Props Config
6.2 Modules: Magisk modules like V4A, Unified Hosts Adblock etc. works. [Tested].
6.3 Kernel: You can use Genom Kernel or Dark Ages Tercero kernel. [Tested Dark Ages Tercero, works]
Cast and mirror screen are broken. After choosing a screen to share the phone's screen to, SystemUI will crash. Apps with cast capabilites won't detect Chromecast devices (the cast button won't appear).
Thank you for your help

moralesnery said:
The following modules are working without issues in my setup:
* Youtube Vanced
* Google Product Sans font
* MagiskHide Props Config
6.2 Modules: Magisk modules like V4A, Unified Hosts Adblock etc. works. [Tested].
6.3 Kernel: You can use Genom Kernel or Dark Ages Tercero kernel. [Tested Dark Ages Tercero, works]
Thank you for your help
Click to expand...
Click to collapse
I don't know what is "MagiskHide Props Config" but is MagiskHide working normally for you?
I'm currently using the Pie "V4 zip" from this thread but MagiskHide isn't working. If it is working normally for you I will try to flash in your way then.
And can I flash 9.0 GSI image over any 8.x roms? Or it must be PE or Havoc?

Can't Show the Image File
After extracting the Hovac OS GSI file (a link that given) can not show Image file it shows file different files in different formats.

GizPrime said:
After extracting the Hovac OS GSI file (a link that given) can not show Image file it shows file different files in different formats.
Click to expand...
Click to collapse
This is the correct link, you don't downloaded gsi file (I did the same thing, currently running Havoc 9 ):
https://sourceforge.net/projects/havoc-os/files/arm64aonly/

sadly i can't flash pie rom because my phone is encrypted. i will try this someday, once i backup my files and do the full format (including internal storage)
i want to try PE pie

Biggest thanks to you as i was in dilemma to try the PE 9.0.
However, the stock camera is so dark so i installed Camera2API, resulting the camera app FC, installed the crashfix Gcam apk i found somewhere in this thread not so long ago to no avail, the camera is still broken. Anyone having the issue ?
TIPS: I tried both Dark Ages and Genom Kernel, the brightness is crazy, i think its the late display driver provided within it: the brightness level is scaled incorrectly, with the 50% on MIUI is 0% in PE, and 50% in PE is equal to 100% of MIUI (the max brightness is at 50% and sliding all over to the right does nothing); clean flashed the whole thing and not using custom-installed kernel at all.

HungNgocPhat said:
I don't know what is "MagiskHide Props Config" but is MagiskHide working normally for you?
I'm currently using the Pie "V4 zip" from this thread but MagiskHide isn't working. If it is working normally for you I will try to flash in your way then.
And can I flash 9.0 GSI image over any 8.x roms? Or it must be PE or Havoc?
Click to expand...
Click to collapse
MagiskHide Props Config" its a module that replaces the ROM's fingerprint with a certified one. This way you get ctsProfile: true and basicIntegrity: true, thus passing SafetyNet. This combined with MagiskHide allows me to use some apps that rely on SafetyNet.
After flashing the Treble-enabling ROM (Cardinal OS) you can install GSI system images based on Oreo or Pie.

Is hotspot working in PIE GSI?

dahrel22 said:
sadly i can't flash pie rom because my phone is encrypted. i will try this someday, once i backup my files and do the full format (including internal storage)
i want to try PE pie
Click to expand...
Click to collapse
If you use orange fox recovery you can wipe encripted partitions and flash custom roms, try it!

Wyneg said:
If you use orange fox recovery you can wipe encripted partitions and flash custom roms, try it!
Click to expand...
Click to collapse
seems like i need to do a format data in recovery. but right now i cant afford to loose all my files in internal storage. once i back up all my file then i will do the format data.
i wish there is some way to decrypt my storage without formatting
btw, i got my storage encrypted because i flashed miui stable rom

it's work but hotspot doesn't work
in cadinal i already check it's work but in gsi have a problem

And.. what If I installed a Treble ROM and I want to go back to stock MIUI, or a non-treble ROM? What should I wipe before going back?

moralesnery said:
And.. what If I installed a Treble ROM and I want to go back to stock MIUI, or a non-treble ROM? What should I wipe before going back?
Click to expand...
Click to collapse
If you do same wipes what you did to flash GSI it's totally ok

expextors said:
it's work but hotspot doesn't work
in cadinal i already check it's work but in gsi have a problem
Click to expand...
Click to collapse
Weird cause hotspot is working fine for me. My kids phone is able to connect without any problems.

soyti2x said:
Weird cause hotspot is working fine for me. My kids phone is able to connect without any problems.
Click to expand...
Click to collapse
i tried on havoc it doesn't work what your gsi you used ? i can't open hotspot because always off when turn on

Updating from OOS_OB12(Oreo) to OOS_OB23(Pie)

Hello Everyone,
I am currently on OOS_OB12 on my 5T. And I have root + Blu_Spark TWRP running. How do I update to Pie without losing data ? I have the treble update, but still on Oreo. I searched a lot and found mixed information, some say I need to go to a specific version first and then to latest., Some say I just dirty flash and flash magisk on top of that. Clean flashing is not an option as I have a lot of data I can't lose, So please help me out here.
TIA

hgaaditya said:
Hello Everyone,
I am currently on OOS_OB12 on my 5T. And I have root + Blu_Spark TWRP running. How do I update to Pie without losing data ? I have the treble update, but still on Oreo. I searched a lot and found mixed information, some say I need to go to a specific version first and then to latest., Some say I just dirty flash and flash magisk on top of that. Clean flashing is not an option as I have a lot of data I can't lose, So please help me out here.
TIA
Click to expand...
Click to collapse
Yeah the treble thing is a bit confusing. I don't remember which one it is for open beta. But the safe way to do it is to install 5.1.3 which installs without problem. Then take an update to 5.1.4. then you can freely update to any pie version without losing data. The problem is that I don't remember the Open Beta equivalent versions for these firmwares.
But like best is that you make a TWRP backup of the data RN before doing anything. OOS is quite picky on what conditions it wants to boot under.
Sent from my OnePlus 5T using XDA Labs

Go to Settings and check for available system update. It will get you the one you need to flash to get Treble. That's how I upgraded from 4.7.4. Downloaded 5.1.3 from Software Upgrade, flashed and booted up, checked update again, received 5.1.4 then 5.1.7 because Pie wasn't out for my country yet.

I checked my 'System Updates ' and it is showing me Open Beta 23 . Does that mean I'm good to upgrade directly to the latest version.?

Update I followed the steps here And everything works as expected. no need to clean flash :
https://forum.xda-developers.com/oneplus-5t/how-to/soon-oxygenos-beta-1-android-o-oneplus-t3726074
[Dirty Flash] For Users with an Unlocked Bootloader and TWRP Recovery coming from H2OS Oreo/Pie, Stable OOS Oreo/Pie, OOS OB Oreo/Pie:
Download the full ROM zip from the downloads section above
Transfer the zip to the root of your device's internal storage
Only needed if you are coming from Oreo: Remove the compatibility.zip from the downloaded full ROM zip with either MiXplorer or Total Commander (not with any other tool!) on your device itself
Reboot to TWRP recovery (make sure you're using siankatabg's TWRP if you're on Oreo or codework's TWRP/blu_spark TWRP if you're on Pie) and take a nandroid backup of your existing ROM
Flash Magisk Uninstaller (recommended)
From the TWRP menu, Wipe > Advanced wipe > Select dalvik-cache and cache > Swipe to wipe
From the TWRP menu, Install > Select full ROM zip (modified one with compatibility.zip removed, in case you're on Oreo or unmodified one, in case you're on Pie) > Swipe to flash
Flash the latest stable Magisk in case you want to root
From the TWRP menu, Wipe > Advanced wipe > Select dalvik-cache and cache > Swipe to wipe
If you were decrypted earlier, flash Disable DM-Verity and ForceEncrypt 2.0 (OP5-5T-Treble).zip from here
Reboot
Closing thread.

[RESOLVED] Updating from OOS_OB12(Oreo) to OOS_OB23(Pie)
Closing thread

Disabling system encryption on 8.1.0?

I was wondering if there existed a 'no-force encrypt' kernel I could flash to the Pixel C on 8.1.0?

Format data and then install magisk.

Monazite said:
Format data and then install magisk.
Click to expand...
Click to collapse
Thanks. I wish it had been that simple .If I do this I think (and Iam not so sure) that wiping the data partition did remove the encryption. I then flashed Magisk. But when I rebooted to TWRP, the system was encrypted again, asking me for a password which I haven't got. Is there not a 'no-force encryption file I am supposed to flash before or after I flash Magisk, to prevent the system from encrypting again?

fgaine said:
Thanks. I wish it had been that simple .If I do this I think (and Iam not so sure) that wiping the data partition did remove the encryption. I then flashed Magisk. But when I rebooted to TWRP, the system was encrypted again, asking me for a password which I haven't got. Is there not a 'no-force encryption file I am supposed to flash before or after I flash Magisk, to prevent the system from encrypting again?
Click to expand...
Click to collapse
Have you checked encrypted status in settings? Magisked boot.img should have disabled encryption if data partition is not encrypted. Or you need flash another kernel?
Sent from my Google Pixel 2 using XDA Labs

fgaine said:
Thanks. I wish it had been that simple .If I do this I think (and Iam not so sure) that wiping the data partition did remove the encryption. I then flashed Magisk. But when I rebooted to TWRP, the system was encrypted again, asking me for a password which I haven't got. Is there not a 'no-force encryption file I am supposed to flash before or after I flash Magisk, to prevent the system from encrypting again?
Click to expand...
Click to collapse
https://forum.xda-developers.com/pi...yflasher-make-install-custom-kernels-t3537487
JUST WANT TO DISABLE VERITY/ENCRYPTION?
You can build lazyflasher by itself, empty, without a kernel Image.fit or modules and flash it!
It's already set up to automatically disable verity and make encryption optional.
Alternatively, there's a branch already set up called no-verity-opt-encrypt. You can find prebuilt official zips at:
https://build.nethunter.com/android-tools/no-verity-opt-encrypt/
Install as last step - after Magisk installation .. but normally Magisk is removing force-encryption too.
Are you sure you did format /data ?
Just wiping is not enough !
As it's not a development topic this thread should be moved to QA section ..
Anyway .. Good luck !

followmsi said:
https://forum.xda-developers.com/pi...yflasher-make-install-custom-kernels-t3537487
JUST WANT TO DISABLE VERITY/ENCRYPTION?
You can build lazyflasher by itself, empty, without a kernel Image.fit or modules and flash it!
It's already set up to automatically disable verity and make encryption optional.
Alternatively, there's a branch already set up called no-verity-opt-encrypt. You can find prebuilt official zips at:
https://build.nethunter.com/android-tools/no-verity-opt-encrypt/
Install as last step - after Magisk installation .. but normally Magisk is removing force-encryption too.
Are you sure you did format /data ?
Just wiping is not enough !
As it's not a development topic this thread should be moved to QA section ..
Anyway .. Good luck !
Click to expand...
Click to collapse
Thanks for the info. I'll try that later on. Don't fancy formatting and having to reinstall everything again for now. Cheers.