Develop Bugs

[G800F][ROM][5.0.2][LRX22G] CyanogenMod 12.0 for G800F [Alpha 23/03/2015]

This is a CyanogenMod 12 ROM for the Exynos3470 based Samsung Galaxy S5 mini (G800F).
DO NOT USE IT FOR G800H/M/... OR YOU WILL BRICK YOUR DEVICE
Although G800F and G800H share the same name they are not related in terms of hardware due to the different SoCs used (Exynos vs. Snapdragon).
Hence please do not ask for support or ROMs for the G800H or G800M here.
Working features
Receiving and making calls
Hardware sensors (Light, Orientation, Compass, Proximity, Acceleration)
Audio
Bluetooth
Wifi
HW accelerated GUI
USB-OTG (Keyboard, Mouse, USB-Audio, Mass-Storage)
Camera (pictures+video: Back+Front)
MTP storage
IR
GPS
NFC
Known-issues:
Capacitive lights are blinking in standby mode
Touchscreen unresponsive for some seconds after resume from standby mode
Non-working features:
Fingerprint scanner (no app for tests found)
Pulse sensor + Step counter (no app for tests found)
SELinux
Disclaimer:
You flash this image at your own responsibility. I am not responsible for any damage that might be caused by flashing this image (bricked device, lost data, ...)
Flashing this kernel image will trigger the KNOX counter, so your warranty will be void.
The image is only for S5 Mini SM-G800F (Exynos)
It might be instable, crash your device, drain your battery, or even might damage your smartphone (e.g. if an USB-OTG device drains too much power)
Backup your data before flashing and check if the original firmware is present (e.g. at SamMobile)
Click to expand...
Click to collapse
Before you start:
Backup your data, like call history, contacts, sms, WhatsApp messages, favourite app settings that are on internal and external sd (by using Titanium Backup or other apps available on PlayStore). At least all internal data will be lost in any case. If you have bad luck you might also loose data from your external sd card.
!!! Development of this ROM is discontinued in favor of the CM 5.1 ROM !!!
This means that known issues will not be fixed. It is not recommended to use this ROM anymore.
The downloads have been removed and fully replaced by the 5.1 version. You can find the new CM 5.1 ROM here
Download:
Odin3-v3.07 (it is contained in CF-Auto-Root)
TWRP 2.8.5.0 recovery image [Updated 23/03/2015] (MediaFire Mirror)
CM12 rom for G800F (MediaFire Mirror)
Google Apps from here (for Google Play, ...). Select the package that suits you best. If you do not need all of the Google services the Micro edition is enough (BasketBuild Mirror for Micro edition).
Install recovery:
Reboot your device into Odin mode: turn off your device, then press Volume-Down + Home + Power button at the same time and release them.
Confirm the following warning message with the Volume-Up button.
Connect your device to your PC via USB
Make sure the device driver's are installed on your PC
Start Odin
In Odin select PDA and select the recovery image (recovery.tar.md5)
Check that only "Auto Reboot" and "F. Reset Time" is set
Click on "Start": the kernel image should be flashed now and the device should reboot afterwards. By flashing the recovery, your warranty will be void.
After the recovery flashing process was successful, power of your device. If not restart into Download mode and flash again or flash the stock rom.
Before you flash:
You need the latest TWRP recovery [Updated 23/03/2015]. Otherwise TWRP might not be able to flash the ROM. This is because TWRP checks now if the device is "supported".
G800M/G800Y are not supported but are not blocked as the ROM might work on these (Exynos3470 based) devices. Only flash the ROM on a G800M/Y if you know what you do. Do not expect help if something went wrong.
Wipe the device to avoid problems with remaining files from the old installation (see instructions below). This also applies if you already installed an older version of CM12.
Flash CM12:
Reboot into recovery mode (Press Volume-Up + Home + Power button)
If you come from a stock rom, this is your opportunity to make a Backup of your phone(Backup, then select Boot, System, Data, then swipe to backup). Note that the recovery might fail to restore the backup when you want to go back to the stock ROM (for me it got stuck after a restore during boot. But the backup was made with a different version of TWRP, so it might work in general) - simply do not expect too much of it at the moment.
If you haven't copied the installation files yet, you can now copy the GApps and CM12 zip to your internal sd or external sd (be careful not to put the files into the data directory of the internal sd card as this will be deleted in the next step). Be sure that MTP is enabled (inside Mounts, click on Enable MTP), then, from your pc, copy the files. If MTP does not work from recovery, try it directly from Android or remove the external sd card from the phone and put it into your PC.
Wipe Dalvik Cache, Cache, System and Data (inside Wipe -> Advanced Wipe). Do not report problems if you did not wipe those partitions as the problems are most probably related to this!
Install the CM12 rom zip-package
Install the GApps zip-package
Reboot the system and enjoy a Lollipop
How to root:
No SuperSu is needed as CM12 already comes with integrated root support. Root access is disabled by default.
You normally do not need root access. If you want to activate root access for apps, do the following:
Open the Settings menu, select "About Phone"
Tap on the "Build number" entry seven times. You should be notified, that the developer settings are now active.
Open the Settings menu, select "Developer options". Enable root access by selecting "Apps" in the "Root-Access" setting.
In case you want to go back to the stock ROM:
lf you do not have the latest ROM for the G800F you can download it from SamMobile
Reboot your phone into Odin mode
Open Odin on your PC and connect your smartphone with your PC via USB
If you have a zip-file unzip it so that you have a .tar.md5 file
In Odin click on the PDA button and select the .tar.md5 file. Then press "Start".
Normally the stock rom fails to boot as the data from CM12 is still on the data partition. So after flashing the stock rom, reboot into recovery mode (it looks a bit different now). First wipe the data partition, then wipe the cache.
Reboot
Changelog
Code:
23-03-2015:
* Fixed non-working mic on incoming call issue
* Fixed non-working menu-button
* Synchronized with latest CM12 sources
This section is for developers:
A script to setup the build environment can be found here:
Code:
https://github.com/tobigun/kminilte-patcher
Sources:
Code:
https://github.com/cm-3470/android_device_samsung_kminilte
https://github.com/cm-3470/android_vendor_samsung_kminilte
https://github.com/cm-3470/android_kernel_samsung_kminilte
https://github.com/cm-3470/android_device_samsung_smdk3470-common
Thanks to Unjustified Dev from Team Regular. As the S5 mini (G800F) and the Galaxy Light are quite similar we worked on this together.
XDA:DevDB Information
[G800F][ROM][5.0.2][LRX22G] CyanogenMod 12.0 for G800F [Alpha 23/03/2015], ROM for the Samsung Galaxy S5 Mini
Contributors
hennymcc, Unjustified Dev
Source Code: https://github.com/cm-3470
ROM OS Version: 5.0.x Lollipop
ROM Kernel: Linux 3.4.x
ROM Firmware Required: TWRP Recovery [version from 2015-03-23]
Based On: CyanogenMod
Version Information
Status: Alpha
Created 2015-03-03
Last Updated 2015-04-15

FAQ
Question:
I'm trying to flash this rom but it says to me: "This package is for kmniltexx, kminiltedv, kminilteub; this device is kminilte. E:Error executing updater binary zip ...."
Answer:
The device names were changed with the newest CM12 build to be able to distinguish between G800F (kmniltexx), G800Y (kminiltedv) and G800M (kminilteub) as all of them are kminilte devices. The new builds of TWRP and CM12 detect the correct device at runtime.
Older TWRP releases (for example that of RVR in another XDA thread) still detect the device as kminilte (instead of kmniltexx,...) and hence are not able to install the new CM 12 releases so please do not install RVR's TWRP if you want to install CM 12. Always use the TWRP image linked in the first post of this thread.

For future use

Thanks for great job. Looking forward to testing it soon!!

I also want to say BIG THANX!
My Phone now makes a backup and than i flash your rom
stiff

I just noticed that the mic is muted on incoming calls. If you want to use the phone for daily use you should not the flash the ROM.

I flashed it already and can confirm, that the mic is off.
But it looks good so far. :good:
stiff

stiffmeister75 said:
I flashed it already and can confirm, that the mic is off.
But it looks good so far. :good:
stiff
Click to expand...
Click to collapse
It works for outgoing calls so I did not notice it before.

Do you know a workaroud?
btw. can you provide a patch with a fix?
or is it necessary to build a new rom?
stiff

sorry my noob question: is this ROM going to be listed in the CM12 nightlies or how will it work? is it an unofficial one yet or... thanks

wabre said:
sorry my noob question: is this ROM going to be listed in the CM12 nightlies or how will it work? is it an unofficial one yet or... thanks
Click to expand...
Click to collapse
It is not official and there won't be nightlies. At the moment there are no plans to get it into the official repo.

stiffmeister75 said:
Do you know a workaroud?
btw. can you provide a patch with a fix?
or is it necessary to build a new rom?
stiff
Click to expand...
Click to collapse
There is some work on this at the moment but no fix yet. Seems as if the audio implementation has to be adjusted a bit. I don't know how much work there is left. As this is a spare time project, this might take some time.
When it works there will be a new ROM for download.

Hey there, been using the rom for a couple hours and I must say, you've done a great job ! The interface is faster than stock touchwiz, and everything runs really smoothly ! I've only encountered two small issues (apart from the incoming call muted mic) :
-when waking up the device, the lockscreen seems to freeze itself (touch doesnt respond), so to fix it, you have to press power button and wake it up again (happened sometimes)
-noticed something strange: while the phone is asleep, the capacitative buttons would blink (they turn on for like 1sec and then turn itself off like a notification light). I'm pretty sure you'll be able to fix it, as it might be kernel related.
-(edit) and I've just realised that the left menu capacitive button doesn't work (but you probably already know this)
other than that, this rom is flawless for an Alpha ! Great job buddy
I was able to score 23 000 pts on Antutu vs 20 000 pts with stock 4.4.2 lol

I have found an issue with the capacitive buttons on the bottom. I was not able to deactivate the lightning and some other settings does not work aswell..
But all in all great alpha, I really enjoyed it ?
Sent from my SM-T530 using XDA Free mobile app

Omg! For my phone!
How cool! I will wait for beta i think...but keep up the good work, i will use it someday
And ill try to help to get ppl to know this thread

basic086 said:
-(edit) and I've just realised that the left menu capacitive button doesn't work (but you probably already know this)
Click to expand...
Click to collapse
Will be fixed with the next build.

i can confirm, that somethimes the capacitive buttons doent work/react.
and the bigger problem is that the micro doent work. (worst problem for me)
and one more problem... the sound on my alarm somethimes got some glitches/sound stops too.
i'll backup the new CM12 and than restore my old backup back... until these errors are fixed.
but, most important, very good work! respect. can i give you a donation ?

E:signature verification failed
what to do?

Hi,
great work!
I also can confirm that the mic for incoming calls does not work and it also doesn't work for either incoming or outgoing calls when using a headset. Haven't used a bluetooth headset yet but will test it later that day.
Many thanks so far for this built and I hope the mic bugs won't be a big deal.
Cheers,
lotherk

bebe.fier said:
E:signature verification failed
what to do?
Click to expand...
Click to collapse
You have a G800F and not a G800H or another variant?
If it is a G800F try to reflash it, maybe somethin went wrong. What is the stock ROM you currently have installed? Is it the newest one - can you give me the version number?

[Guide]Lenovo S5 K520: TWRP, Root and Decrypt data

Hello everyone, after struggling for a few hours I managed to finally disable force encryption in my phone (so that TWRP could backup the data partition).
I'd like to write a quick list of what I did in the form of a guide to unlocking the bootloader, installing TWRP and getting root with Magisk. I'm just a user, not a developer and this guide is brief, it's not a detailed tutorial and does not include trivial steps (like how to install drivers for your OS).
Warnings: Although small, there is always the chance this bricks your phone. I take no responsibilities.
This will factory reset your phone so back up everything before you start.
My phone is Lenovo S5 (K520) Global version (see screenshot) I don't know if this will work for other firmwares.
Prerequisites:
Install Phone, ADB and Fastboot drives. You can get ADB and Fastboot binaries from here:
https://forum.xda-developers.com/showthread.php?t=2588979
Download this archive:
http://www.mediafire.com/?4dcvzw1hdmzfn10
It contains all the files used in this guide.
Alternatively, download all the files used from their sources.
You will need an SD card or a USB flash drive with an OTG adapter.
Copy the following files to it:
A. "Disable_Dm-Verity_ForceEncrypt_12.16.2018.zip"
(Downloaded from http://forum.xda-developers.com/showthread.php?t=3817389 )
B. "Magisk-v18.0.zip"
(Downloaded from http://forum.xda-developers.com/showthread.php?t=3473445 )
C. (optional) "\stock\boot.img"
(Downloaded from the global firmware @ 4pda)
If you chose to use Micro SD card, you can insert it now.
Note: I know there is a way to push these files directly to TWRP from PC through USB instead of using SD Card/Flash drive but I've never tried it.
Lets start:
1. Go to 'Settings>About phone' and tap on "Lenovo version" several times until developer options are enabled.
2. Go to 'Settings>System>Developer options' and enable "OEM unlocking" (Note: for me this option was greyed out and I had to connect to wifi and wait for a minute or two).
Optional: Enable "USB debugging" if you wish to enter fastboot via ADB.
3. Turn off the phone and press and hold 'Volume down'+'Power' buttons until you see "fastboot mode" on the phone screen (alternatively, don't turn off the phone and instead enter fastboot mode via ADB (adb.exe reboot bootloader)).
4. Connect the phone to the PC via USB and open a command prompt in the location that you installed fastboot binary to.
Type (after each command press enter):
Code:
fastboot devices
To verify that the phone is recognized. And if it is type:
Code:
fastboot oem unlock
Now on the phone LCD navigate to "Yes" with volume buttons and press power to select it.
Your phone will factory reset, this will take a few minutes. Let it finish.
5. Put the TWRP image in your fastboot path. I used "recovery-twrp-3.2.3-crn-seoul(v3.2.3-1).img" downloaded from this URL:
https://forum.xda-developers.com/android/development/lenovo-s5-k520-twrps-t3863860
But I included 2 more files that I found (I did not try them).
6. Enter fasboot mode again and type:
Code:
fastboot flash recovery recovery-twrp-3.2.3-crn-seoul(v3.2.3-1).img
(Substitute "recovery-twrp-3.2.3-crn-seoul(v3.2.3-1).img" with the recovery filename of you choice)
7. If successful, disconnect the USB cable and enter Recovery mode, do not turn off or reboot the phone because upon restart the phone will revert to stock recovery (I.E. delete TWRP).
To enter Recovery mode press and hold 'Volume down'+'Power' buttons until you see "fastboot mode" and from there choose "Recovery mode" with the volume buttons and confirm with the power button.
(Alternatively, you can try holding 'Volume up'+'Power' to directly enter Recovery mode but I found it a little finicky)
8. In TWRP, swipe to allow changes. Press cancel when asked for a password to decrypt data.
If you chose to use a USB flash drive with an OTG adapter, connect it and mount it (Mount>usb-otg).
9. Go to Wipe>format data, type "yes" and confirm (if you have any data like installed apps, contacts etc., it will be deleted).
10. Go to Install and install "Disable_Dm-Verity_ForceEncrypt_12.16.2018.zip".
The files will be in (/external_sd/ or /usb-otg/).
11. Install "Magisk-v18.0.zip"
Important note: If you want to keep encryption (if you don't care if TWRP can't access /data/) and just obtain root, skip steps 9 and 10.
12. Reboot to system and wait for a few minutes for the initial setup.
If for some reason boot fails (nothing happens after 10 minutes) and you can still enter TWRP (hold 'Volume up'+'Power'), then you can revert the changes by restoring the stock boot image (TWRP>Install>Install image>boot.img - put a checkmark on "boot").
If this worked for you, please tell us by replying to this thread.

Thanks a lot man. This phone is a beast in quality/price when talking about hardware. Costs a bit more than 100€ and has the same hard than others at 180-200€ at least. Bad thing is software but with TWRP and root everything is possible . Just found what project treble is, amazing possibilities. Can't beliebe nobody replied yet to yor post. Its a great guide and you show all the sources from where your downloads come. As you said in another thread its better this way so people can trust your content more:
C4lculated said:
I also wanted to root but I didn't want to run a bunch of unknown programs (from XN Logos), so I managed to install TWRP and root with magisk. I wrote a guide on how to do it:
https://forum.xda-developers.com/ge...ide-lenovo-s5-k520-twrp-root-decrypt-t3882402
Click to expand...
Click to collapse
I am yet waiting for my Lenovo S5 to arrive but I will give this guide a try. I was about to follow XN logos (stupdroid) guide/software but I prefer yours. Just one question... have you checked whether the TWRP v3.2.3 (latest) from dmilz make proper working backups? Can I trust that a full backup will be loaded correctly after installing any unofficial ROM, to go back to stock if necessary? I made once the mistake of relying a TWRP and later I found out that one was ok for flashing but didn't create working backups. I asked him also the same question, but I guess you also tried yourself to make a backup and restore from it using TWRP.
Next step will be to flash an Android 8.1 or 9 GSI rom (did I already say I'm amazed by GSI/project treble roms? just found about them last days). I will update you about my luck following your guide

does anyone enable lte bands, 4 and 28?

just bought this phone, currently on shipping..
I'll first try with twrp + aosp 9 GSI

Hi man, have you upgrade to gsi
acost91 said:
Thanks a lot man. This phone is a beast in quality/price when talking about hardware. Costs a bit more than 100€ and has the same hard than others at 180-200€ at least. Bad thing is software but with TWRP and root everything is possible . Just found what project treble is, amazing possibilities. Can't beliebe nobody replied yet to yor post. Its a great guide and you show all the sources from where your downloads come. As you said in another thread its better this way so people can trust your content more:
I am yet waiting for my Lenovo S5 to arrive but I will give this guide a try. I was about to follow XN logos (stupdroid) guide/software but I prefer yours. Just one question... have you checked whether the TWRP v3.2.3 (latest) from dmilz make proper working backups? Can I trust that a full backup will be loaded correctly after installing any unofficial ROM, to go back to stock if necessary? I made once the mistake of relying a TWRP and later I found out that one was ok for flashing but didn't create working backups. I asked him also the same question, but I guess you also tried yourself to make a backup and restore from it using TWRP.
Next step will be to flash an Android 8.1 or 9 GSI rom (did I already say I'm amazed by GSI/project treble roms? just found about them last days). I will update you about my luck following your guide
Click to expand...
Click to collapse
Kindly drop the procedure am hitting brick with all the method i used .????????

Stock firmware lenovo k520
I have tried your method on ROM that is based on China and also globally, and TWRP was successfully installed, and I have also tried several Rom GSI, and only AOSP Extended is successful, but with Bluetooth bugs it cannot be turned on, if others want flash files and stock firmware for k520, just let me know, thanks.

Working on S5 Pro too?
Hi! Can it work on S5 Pro too? I really want to root this device and I don't find out a way to get this happening. Thanks!

Does this work for s5 pro l58041?
Thanks

B4ph0 said:
I have tried your method on ROM that is based on China and also globally, and TWRP was successfully installed, and I have also tried several Rom GSI, and only AOSP Extended is successful, but with Bluetooth bugs it cannot be turned on, if others want flash files and stock firmware for k520, just let me know, thanks.
Click to expand...
Click to collapse
Hi! Sorry for offtopic!
Could you please PM me the link on AOSP extended image which you installed. Thank you!

Hello! Did somebody managed to install GCAM to Lenovo S5? I'm trying and I can;t do this, magisk modules are not loading...

so far I've used 2 alternative rom and works fine, aosp & octopus os, especially octopus os

I need some help..
Did anyone had lenovo s5 persist.img..
I lost my persist afer flashing global rom.208st via qfil..
I check the rom has no persist.img

Please visit to https://youtu.be/wbpV59kutJM for tutorial flash and upgrade Lenovo S5 in YouTube

hello guys, i always get into download mode,after press reboot system (twrp), any solution for my problem ?

has anyone achieved unlocking bands in this phone?

Please port miui 11 9.10.30 mi-room pie 9.0 redmi note 4x SD625 to lenovo S5.
https://megaroms.net/miui-11-9-10-30-stable-port-for-redmi-note-4-4x/
https://sourceforge.net/projects/miui-ports.whats-new.p/files/mido/miroom/

After unlocking bootloader, is there anyway to remove the hideous "software can't check for corruption" warning? Thanks.
---------- Post added at 01:44 AM ---------- Previous post was at 01:39 AM ----------
Suryo75 said:
hello guys, i always get into download mode,after press reboot system (twrp), any solution for my problem ?
Click to expand...
Click to collapse
This means no rom is installed in your phone. Either you accidentally wipe system in twrp, or the rom is corrupted.
Download the deodexed stock rom below and flash with twrp. Should fix your problem.
https://drive.google.com/open?id=13tRqo5eSpRiVJwKiA-iSj2GyIF353ATQ

jychung93 said:
After unlocking bootloader, is there anyway to remove the hideous "software can't check for corruption" warning? Thanks.
---------- Post added at 01:44 AM ---------- Previous post was at 01:39 AM ----------
This means no rom is installed in your phone. Either you accidentally wipe system in twrp, or the rom is corrupted.
Download the deodexed stock rom below and flash with twrp. Should fix your problem.
https://drive.google.com/open?id=13tRqo5eSpRiVJwKiA-iSj2GyIF353ATQ
Click to expand...
Click to collapse
thank you i'll try

Could you plz make tutorial about getting back to stock unroot...thx

Twrp gone
Hello sir thank you for this wonderful tutorial,
But I have a problem , after booting to TWRP , then boot to system after that when I try to go back to recovery mode TWRP , twrp is gone , stock recovery back

[TOOL] DualSix - Dual Boot for OnePlus6/6T [25.03.20]

DualSix - Dual Boot for OnePlus 6!
Before You go further, keep in mind that it's mostly recommended for advanced users! And those who can calmly read instructions, preferably twice!
What does this tool do? And what are the benefits? DualSix allows You to boot two ROMs at the same time! You can flash OOS on one slot and AOSP on another or MIUI or GSI etc. How awesome is that? It also gives You as secure virtual mSD Card that will never get encrypted so Your files will be always safe!
How is this Tool different compared to Zackptg5 version for OP7 Pro? Well.. let's be honest.. he's a great Developer and his skills in making scripts and other stuff are a lot better than mine so his version of Dual Boot is definitely better but since he doesn't have OnePlus6 and 7 Pro received great feedback + people wanted me to resurrect DualSix which I made 2 months ago, I decided to finish the project and release it. It will most likely be the last "big project" for this device before 8 Pro.
Now short Q&A:
Q: Can I use on mido, raphael, x00td, vince etc?
A: No! Only use it on OnePlus6 and 6T.
Q: Can I use it with EPR?
A: No. You can't use them on top of each other.
Q: What ROMs does it support?
A: Ports (soon), AOSP ROMs and GSIs.
Known Issues
Storage Settings in ROMs might report incorrect storage size
Currently only 128GB is supported
Shared Storage is sadly only accessible by using any root explorer (/data/media/0/SharedStorage)
This directory is accessible in TWRP as Micro SD Card (keep important files there)
How to Use:
MAKE SURE TO BACKUP EFS, DATA AND PERSIST (if possible) BEFORE USING IT!
MAKE SURE YOU HAVE LATEST OPEN BETA / OOS STABLE IN BOTH SLOTS!
Also make sure You're not currently using EPR!
It is recommended for You to keep most important files in Shared Storage / MicroSD Card.
It won't get corrupted if something goes wrong.
If You mess up and end up without DualSix TWRP. You can also use Emergency DualSix TWRP from Emergency files!
1. Run RUN_BEFORE_DUALSIX.bat/sh in Fastboot Menu.
2. Boot into TWRP of Your choice.
3. Flash dual-six-twrp-3.3.1-x_blu_spark_v9.109_op6.zip
4. Flash Dual Six for Your storage
5. Reboot into recovery
6. Format all new partitions (Data A, Data B, Shared Storage/MicroSD Card)
7. Reboot recovery again, confirm that new TWRP log shows no red error messages
8. Now follow ROM specific guide below
-------- Ports ---------
Because ports are slightly more difficult to patch
Future ports will come with separate DualSix flasher.
REMEMBER. FORCE WIPE ONLY WIPES CURRENT SLOT.
YOUR SECONDARY ROM WILL BE FINE.
--- Once that happens follow ---
1. From fastboot, run flasher.
2. Most flashers auto reboot, if that happens, just boot into TWRP (even if You see boot animation))
3. Now when You're in TWRP, copy Dual Six ROM Patcher to Your MicroSD Card Storage
4. Flash Dual Six ROM Patcher
5. Done! Now reboot into the ROM and once it boots, You can root.
------- AOSP ROMs / GSIs --------
1. Flash AOSP_ROM_NAME.zip
2. Flash dual-six-twrp-3.3.1-x_blu_spark_v9.109_op6/op6T.zip
3. Reboot Recovery
4. Flash Dual Six ROM Patcher
5. Flash GApps (if needed)
6. Reboot and enjoy!
Note: if AOSP ROM / GSI stays on boot animation for longer than 10 minutes, flash a permissiver.zip.
You should apply same guide for both slots.
Download:
DualSix v1.1 - Mar25
If You have any other problems, just ask here on XDA or for the fastest support PM me or ask someone in my group on Telegram
Join my group!
If You want to support this and other projects, buy me a coffee!
https://www.paypal.me/protodevnano
Credits
MounirHero - for 6T support
eng.stk - for his amazing TWRP
CosmicDan - for his sgdisk guide that helped me with EPR and DualSix
My group for motivating me to resurrect this project!
OnePlus for creating this amazing phone!
​
XDA:DevDB Information
DualSix - DUAL BOOT for OnePlus6 & 6T, Tool/Utility for the OnePlus 6
Contributors
ProtoDeVNan0, MounirHero
Source Code: https://github.com/engstk/android_device_oneplus_enchilada
Version Information
Status: Stable
Created 2020-03-24
Last Updated 2020-03-24

What a wonderful thing....!
Thanks Jay! Can't wait to try this out!

Awesome!! Well Done Bro... [emoji16]
Sent from my RMX1971 using Tapatalk

Great job Jay, hoping 64gb comes soon! One of your ports on one slot and GSI on the other would be amazing!

DualSix TWRP not flashing or booting, OnePlus 6T
I cannot get the dualsix twrp to flash to my device. In twrp it says device not compatible and aborts the installation. I also cannot boot the emergency twrp image from the emergency files folder in fastboot mode, when I try it boots back to the rom. I have a OnePlus 6T 128GB model. My guess is that the twrp is only for the OnePlus 6 and that's why it's aborting? But the OP mentions it working on both the 6 and the 6T. I have tried with and without running the "RUN_BEFORE_DUALSIX_WINDOWS.bat" beforehand. Not sure what to try now.
edit: nevermind, the link hadn't updated yet when I first downloaded it earlier so I did have the twrp that was only for OnePlus 6, sorry about that

Nice, will try it when I have time

This is what I thought/hoped the stupid A/B partition nonsense was going to be.
NICE!!

Will this wipes all. Internal storage

Can't wait to try this. Awesome work

Hello everyone, question, just in case if I want to revert back to stock a and b is it just MSM tool? Thanks Dev.

That's terrific ! This sounds promising !
I'll try to get OP6 OOS latest OB and Havoc OS 3.3 alongside

Just updated DualSix to 1.1 which includes external_sd fix which for some reason was missing from previous zip.
Thanks to Lord_Vicky & MounirHero for letting me know.
Edit: Posted a message in my channel where I test ROMs and confirm if they work or not

ProtoDeVNan0 said:
Just updated DualSix to 1.1 which includes external_sd fix which for some reason was missing from previous zip.
Thanks to Lord_Vicky & MounirHero for letting me know.
Click to expand...
Click to collapse
I need access to your g drive to download

david72262 said:
I need access to your g drive to download
Click to expand...
Click to collapse
Oops. Never happened to me before. But fixed it. Enabled file access for everyone. Not sure why mobile uploads have different sharing options

Awesome man. Great going.

What the f*, I though nobody was gonna attempt to do this !
I'll have to try that

oscarmaldonado said:
Hello everyone, question, just in case if I want to revert back to stock a and b is it just MSM tool? Thanks Dev.
Click to expand...
Click to collapse
I was wondering the same thing

Hi...Thank you very much for this mod.
I am willing to do this but i have a few questions regarding it
1st: after we flash this mod...can we go back to the original partition table and if so...could you explain what files to use and in which order.
2nd: if i want to flash OOS on slot a then my current boot slot would have to be active slot b because roms flash to opposite slots right?
3rd: if i have OOS on slot a and a custom rom on slot b...when i have an update for OOS i must be on active slot b and flash the whole OOS full rom zip and flash all the other files like magisk and recovery and patchers or is it a different way?
4th: can we set a password for slot b's rom or will it brick the device like the 7/7Pro' guide section?
5th: does the shared storage have a fixed size or is it dynamic...and if so, if we put photos and media there will the normal apps like gallery and music players be able to access them at all?!
6th: do we have to stay unencrypted?
7th: if we want to flash magisk to slot a....does our active slot has to be slot a or slot b?
8th: if i want to change rom on slot b...then what do i have to wipe to be able to clean install the rom i want?
i know i asked a lot of questions and some may be stupid but i would really like to try this with all the knowledge beforehand so i dont get myself into a perma-brick like the guys over at 7/7Pro's section
Thanks again for this mod and i hope you reply soon .

joepas said:
I was wondering the same thing
Click to expand...
Click to collapse
I tried, I couldn't get it to boot so I was able to revert it back by running DualSix Remover 128GB.zip in the same folder, reformatted everything and reinstalled OOS.

need help
can anybody tell me for certain how bad i just wrecked my phone. So I was on step 4. Flash Dual Six for Your storage, and after it flashed i hit the restart button on accident. My phone was stuck in the op6 3 dot bootloop. Then i might have put the nail in the coffin by fastboot flashing the images out of the 9.0.9-OnePlus6Oxygen_22_OTA_034_all_1909112343_dd26-FASTBOOT.zip. I’m pretty sure im autistic can anyone help me fix my phone?

[Tutorial] How to update Android 10 to Cubot Power (Or any treble-endabled device)

This is a guide how I flashed Android 10 to my Cubot Power.
Preparation:
HINT:
Make a Backup! You will definitely loose all your data on the phone due to several factory resets!
First make sure your Device can use treble and also which one you need with this app:
https://play.google.com/store/apps/details?id=tk.hack5.treblecheck
(according to this post https://forum.xda-developers.com/pr...velopment/aosp-10-0-quack-phh-treble-t3992559)
note down:
Architecture: (Cubot Power: arm64)
System as Root: (Cubot Power: A-only)
then you will need fastboot and adb:
Windows:
https://forum.xda-developers.com/showthread.php?t=2588979
Linux:
Code:
sudo apt-get install android-tools-adb
Code:
sudo apt-get install android-tools-fastboot
Then you need twrp Recovery or something similar. Cubot Power is not supported by the official twrp project, but there is this unofficial version:
https://unofficialtwrp.com/twrp-3-2-3-recovery-cubot-power/
And you will probably need gapps:
https://opengapps.org/
For cubot power you will need "arm64" and "anrdoid 10" of course.
For the variant version I went with "nano" but you can probably choose what you like.
If you have a external sd card you want to copy the gapps, supersu and no-verty-opt-encrypt ZIP onto it.
Now download the android 10 treble image from:
https://github.com/phhusson/treble_experimentations/releases?after=v211
For the Cubot Power i went for the system-quack-arm64-aonly-vanilla.img.xz. But you should select the right one according to the treble app.
I went for vanilla because with gapps it did not seem to work.
Optional:
From this site:
https://romprovider.com/cubot-power-root-twrp/
Download SuperSu (https://download.chainfire.eu/1220/SuperSU/SR5-SuperSU-v2.82-SR5-20171001224502.zip)
and no-verty-op-encrypt (https://romprovider.com/download-no-verity-opt-encrypt-version/)
this prevents bootloops.
In case something goes wrong have your stock rom and sp flash tool ready:
Cubot Power: http://forum.cubot.net/viewtopic.php?f=21&t=2419
Flashing
Make sure your phone is charged probably. Booting might take up to an hour. At least 70% is recommended.
Go to developer settings and enable usb -debugging and disable oem.
now type:
Code:
adb reboot bootloader
the device should now restart and boot into fastboot
now disable oem in fastboot and unlock flashing: (WARNING: this will factory reset your phone)
Code:
fastboot oem unlock
Code:
fastboot flashing unlock
now we want to "install" twrp:
Code:
fastboot flash recovery TWRP_cubot_power-030918.img
--(Optional) check if twrp is working:
Code:
fastboot reboot
and restart with the volume up button
in twrp go to mount and check if you can mount data. If not: https://appuals . com/how-to-fix-twrp-unable-to-mount-storage-internal-storage-0mb/.
Make a Backup. Then wipe "dalvik cache", "cache" and "data"
Then go to install and install no-verty-op-encrypt.
then got to reboot and select bootloader.
--
continue with flashing android 10:
unzip the xz file
Code:
fastboot flash system system-quack-arm64-aonly-vanilla.img
this might take a while.
Then reboot
Code:
fastboot reboot
now your phone should boot into android 10. This can take very long for me it took about 30 minutes. If it takes longer then one hour you can probably start troubleshooting.
Install google apps(playstore)
once it has booted you either can start the login process and enable usb debugging again and reboot into recovery:
Code:
adb reboot recovery
or turn it off and restart into twrp (power button and volume up).
In twrp again check if you can mount data (see the optional step).
Make a Backup. Then wipe "dalvik cache", "cache" and "data"
Install super su and gapps.
Now reboot to system.
Now again the phone will boot a very long time (up to a hour).
Conclusion:
For me it is pretty stable but sometimes the fingerprint sensor does not work or the sim card is not recognized. But a reboot fixes it (sometimes).
But rebooting always takes time. At least 5 minutes sometimes up to 30 minutes. Once the system is booted there are no feel-able performance issues.

Hy there !
My Treble Info says:
Trable & VNDK supports old Version with VNDK version 27.0
System as Root:
Not supported, use A-only-OS
Will this flash to Android 10 work on this Cubot Power ?
The Phone is currently rooted.
regards
Al

Virtu-Al said:
Hy there !
My Treble Info says:
Trable & VNDK supports old Version with VNDK version 27.0
System as Root:
Not supported, use A-only-OS
Will this flash to Android 10 work on this Cubot Power ?
The Phone is currently rooted.
regards
Al
Click to expand...
Click to collapse
Probably it will work, but I can give you no guarantee for that.

Thank you!
Hi Johanno,
Thank you for this great tutorial! I think I already downloaded the treble check tool in March and I also found the github page, but I didn't find any experience on the net related to Cubot Power, so I didn't dare to upgrade.
Did you try later releases?
Should I go with latest release v222 or do you know about any change in v211 that prevents us from upgrading to a later version? ( your link in the tutorial shows only older versions: https://github.com/phhusson/treble_experimentations/releases?after=v211 )
Did you use windows or linux?
Did you experiment with V25 ROM?
https://www.cubot.net/platform/Support/detail/id/192/cid/23.html
Br,
taarzaan

I'm trying the latest release v222. I'm after the last reboot. It's not fast, but I would say it's less than 30 minutes. It should boot in 5 or 10 minutes.
Br,
taarzaan

Results of my experiments
Fingerprint sensor has similar issues like other Cubot devices:
https://github.com/phhusson/treble_experimentations/issues/1273
https://github.com/phhusson/treble_experimentations/issues/1319
I failed to install MS Outlook, Office, Company Intune app and things like that. I tried to unroot the phone, but it didn't help.
Maybe this Magisk thing worse a try next time:
https://github.com/phhusson/treble_experimentations/issues/31
https://github.com/phhusson/treble_experimentations/issues/909
Br,
taarzaan

Virtu-Al said:
Hy there !
My Treble Info says:
Trable & VNDK supports legacy Version with VNDK version 27.0
System as Root:
Not supported, use A-only-OS
regards
Al
Click to expand...
Click to collapse
hi
i just want to understand what is legacy version? and vndk27 ? i googled but few info
my phone say same info here
i ll post the results but if one could explain those 2 things
thank u in advance

taarzaan said:
Fingerprint sensor has similar issues like other Cubot devices:
https://github.com/phhusson/treble_experimentations/issues/1273
https://github.com/phhusson/treble_experimentations/issues/1319
I failed to install MS Outlook, Office, Company Intune app and things like that. I tried to unroot the phone, but it didn't help.
Maybe this Magisk thing worse a try next time:
https://github.com/phhusson/treble_experimentations/issues/31
https://github.com/phhusson/treble_experimentations/issues/909
Br,
taarzaan
Click to expand...
Click to collapse
notes for the next experiment (we should open a proper ticket for phhusson):
"What does "can't be used" mean? Does the pone vibrate? Does screen lights on? If you go in Fingerprint settings, do you see the enrolled fingerprint? Can you enroll a second one? If you press your fingerprint sensor when you're on that screen, what happens?"

I've tried with both v211 and v222 - but I don't seem to get past boot screen.
After using fastboot flash (and I've also tried SP flash tool flash) the phone shows cubot boot screen (with a warning about "orange mode" not being trusted) and can boot into TWRP but when booting system it shows a black screen with white slowly flashing "android" for a long time. More than one hour. I lose faith and re-install stock each time.
Any ideas how to debug and see what's happening?

Any improvements to this? I am having a P20/cubot and had same problems. AOSP v222 does not boot but I tried lineage-17.1-20201215-UNOFFICIAL-treble_arm64_avS.img.xz from https://sourceforge.net/projects/andyyan-gsi/files/lineage-17.x/
Surprise. it works but a bit slowly. Due to large battery I am thinking of cubot power?
I have 2 questions:
1. Can you please try the lineage-17.1 rom?
2. BTW, did AOSP8 work OK in cubot power? (i like oreo more than android 10)
Thanks for your replies.

htorsten2020 said:
1. Can you please try the lineage-17.1 rom?
Click to expand...
Click to collapse
Thanks, sorry, I'll check it only next month. Any other issues besides slowness?
htorsten2020 said:
2. BTW, did AOSP8 work OK in cubot power?
Click to expand...
Click to collapse
I don't know what you mean. Do you mean treble roms? I haven't tried any yet.

taarzaan said:
Thanks, sorry, I'll check it only next month. Any other issues besides slowness?
Click to expand...
Click to collapse
Call/SMS/data stability. A lot of devices that came with oreo (vendor) have lots of issues with signal (mobile SIM) dropping after some hours. Thanks
taarzaan said:
I don't know what you mean. Do you mean treble roms? I haven't tried any yet.
Click to expand...
Click to collapse
Cubot Power ships with Android 8.1 (oreo). So I asked if you tried the old AOSP from phhusson (v32 - this is AOSP8 equivalent treble ROM). I found the AOSP from the same version (oreo as the device) is faster than installing newer ROM.

Hi guys, as you may have noticed I am not very active here ;-)
I actually went back to stock firmware after a few weeks because I couldn't get the phone working again. And since I want to use my smart phone and not tinker on it every few days I gave up. But now I am thinking about using Lineage os.
But first I need to back up everything and that's probably the thing that will hinder me the most.

Hi. I provide you my story with CUBOT power. It took me 2 days. I worked with a device that was never before modified. Guide on this page is very helpful. Johanno thank you very much!
By TWRP install an Orange mode has been triggered (you see small black text on the white screen with CUBOT POWER logo during boot. First I went step-by-step from this guide and I installed AOSP 11.0 v313. But it didnt want to boot because of boot loops. The no-verty-op-encrypt (last version) solved. I did not installed before because I did not want any root (I dont need). The boot time itself is really very long (I did not measure but guess 30 minutes) and after boot 3 buttons at bottom of screen (back/home/change task) were missing. As it was first run of fresh installed Android maybe restarting could help maybe not. I did not try because the boot time is really unacceptable...
Then I downloaded LineageOS 18.1 (lineage-18.1-20220120-UNOFFICIAL-treble_arm64_avS) and tried this one (before install I wiped cache, data, dalvik cache). After install phone started booting - there was some screen about encrypting partitions or so, then animation and there it frozen (I let it run full night without progress). At morning I turned phone off and on and it surpriesd me by just normal boot of working LineageOS 18.1.
Boot time is completely normal (lets say up to 3 minutes) each time I restart.
I tried fingerprint sensor - it works but maybe daily usage is not 100% reliable (Few times during phone unlock it completely ignored fingers). But honestly this sensor is not reliable (from past experiences)
Original LineageOS camera app cannot change some camera settings (I think ISO) because you see only very dark image. But after install F-droid and Simple camera app then it just works without issues.
Another issue i found was the night mode - you will find out that the "low temperature white" color is not stable - it flickers little bit. After some time it started bothering me. I completely solved it by activating developer mode and there I turned on some graphics hardware acceleration (I dont understand why is it turned off by default). Videos playback is working with this with no issues.
This lineageOS has 2 "Music" apps. I did not study the difference but one works and other one crashes.
I did not find any other issue. Gapps works (I installed nano), our local bank apps work (no issues cased by "Orange mode").

kezyr said:
Hi. I provide you my story with CUBOT power. It took me 2 days. I worked with a device that was never before modified. Guide on this page is very helpful. Johanno thank you very much!
By TWRP install an Orange mode has been triggered (you see small black text on the white screen with CUBOT POWER logo during boot. First I went step-by-step from this guide and I installed AOSP 11.0 v313. But it didnt want to boot because of boot loops. The no-verty-op-encrypt (last version) solved. I did not installed before because I did not want any root (I dont need). The boot time itself is really very long (I did not measure but guess 30 minutes) and after boot 3 buttons at bottom of screen (back/home/change task) were missing. As it was first run of fresh installed Android maybe restarting could help maybe not. I did not try because the boot time is really unacceptable...
Then I downloaded LineageOS 18.1 (lineage-18.1-20220120-UNOFFICIAL-treble_arm64_avS) and tried this one (before install I wiped cache, data, dalvik cache). After install phone started booting - there was some screen about encrypting partitions or so, then animation and there it frozen (I let it run full night without progress). At morning I turned phone off and on and it surpriesd me by just normal boot of working LineageOS 18.1.
Boot time is completely normal (lets say up to 3 minutes) each time I restart.
I tried fingerprint sensor - it works but maybe daily usage is not 100% reliable (Few times during phone unlock it completely ignored fingers). But honestly this sensor is not reliable (from past experiences)
Original LineageOS camera app cannot change some camera settings (I think ISO) because you see only very dark image. But after install F-droid and Simple camera app then it just works without issues.
Another issue i found was the night mode - you will find out that the "low temperature white" color is not stable - it flickers little bit. After some time it started bothering me. I completely solved it by activating developer mode and there I turned on some graphics hardware acceleration (I dont understand why is it turned off by default). Videos playback is working with this with no issues.
This lineageOS has 2 "Music" apps. I did not study the difference but one works and other one crashes.
I did not find any other issue. Gapps works (I installed nano), our local bank apps work (no issues cased by "Orange mode").
Click to expand...
Click to collapse
hi, how exactly did you install the lineageos 18.1 with the twrp 3.2.3? thank you in advance for your help

i just get boot loop on every rom i try on cubot power

I had the same problem and gave up

[ROM][A51] HAVOC OS for Samsung Galaxy A51 [GSI]

Hey Guys,
Before you dive in, irrespective of your reading speed read this carefully and slowly for better understanding but if you cannot focus and read it slowly then you better give up music for a few weeks.
About the Device
Before you jump in and get your hands dirty.. you should know that what you will be installing is Generic System Image, It is not specifically made for your device so if you are going to install some other GSI other than this, you might face some issues.
If you are a beginner, you should Go Through Project Treble, just for the sake of knowledge.
Also Galaxy A51 has A/B partition and Supports Project Treble though remember that Treble Devices are not same as A/B devices and Vice Versa.
Things You’ll Need
A Computer (not an iPad)
Internet [requirement around 6 gigs (4.8 gigs optional, for downloading stock Firmware, Highly Recommended)]
Samsung Galaxy A51 (will not work on A50)
Patience and a madcap attitude.
Resources
Download Odin from the link given below and extract it in a folder.
https://odindownload.com/download/Odin3_v3.13.3.zip
Adb and Fastboot Drivers
https://gsmusbdrivers.com/download/adb-fastboot-drivers/#
Samsung Drivers
https://developer.samsung.com/mobile/file/68b2dc40-3833-4a8b-b58e-32f7aca25c00
Havoc OS GSI
Havoc-OS - Browse /arm64-ab at SourceForge.net
Don’t forget to check that there is “arm64” and “ab” written on the name of the file
Other option is with Gapps (it means the rom will come with Google Play services built in
otherwise it is Vanilla Android.
GSI Flasher
(It is used for converting your img file into flashable Zip)
https://drive.google.com/file/d/1J8OlI2CCXpvAJ5FhFlR2b_y58eHQERGs/view?usp=sharing
Extract it you’ll find three folders gsi, META-INF, scripts, keep all of them inside the GSI
Flasher extracted folder.
Twerp Recovery
twrp-a51-3.5.0_10-1_ianmacd.tar | by androidhowto for Utilities (androidfilehost.com)
Do not use any other in this case you might get mounting errors.
Encryption Disabler
Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip | by androidhowto for Utilities (androidfilehost.com)
Its Show time
1. Go to settings and go to about phone, tap build number 7 times and a dialog will appear, you are now a developer.
2. Go to additional setting or search developer options in the settings search bar
3. Once in the developer settings find OEM unlock and turn in on, scroll down and also turn on USB debugging, your phone will ask the permission for accessing the data by your computer.
4. Turn off your device. Get a usb cable and connect it to your computer.
5. While phone is off first press Volume UP and Volume Down together, and then then insert the usb cable into the phone while holding the buttons wait for two seconds. a blue screen will come up telling you about consequences and life choices.
6. Long press the Volume Up Button and a new blue screen will show up asking you for unlocking the bootloader. Press Volume Up to confirm. You device will erase everything and reset itself ( Don’t forget to take backup of your Data).
7. After the setup screen appears skip everything in the setup and enable developers option and enable USB debugging in the developer options.
8. Turn off your device again and Repeat step 5.
9. Press Volume up for entering the download mode
10. Now in your computer, Install Odin and open Odin.exe you’ll find your device as comm: xx
Now click on the AP button and select the twerp you downloaded.
Press start and twerp will be installed in your device. Your device will reboot don’t let it boot to one ui, press all three buttons together and hold, as soon as the screen goes black release only the volume down button. Keep holding the Volume UP and power buttons for 3 seconds and then release, you find yourself in twerp. If you miss it repeat the process again but don’t let it boot to One Ui.
In twerp press wipe => format data =>type yes. Press home button and again go to wipe advanced select Data, Cache and Dalvik and swipe to clear.
Press home again. Go to reboot and select recovery, twerp wil reboot. Once it reboots transfer the encryption disabler to your phone and in twerp press install select the storage, sdcard or internal storage, where you have stored the file, select it and swipe to install.
Now in your computer extract the Havoc os image and rename it as “system.img”.
Extract the GSI flasher, copy system.img and paste it in the gsi folder of the GSI Flasher.
Select gsi, Meta-inf, scripts and compress them into a zip and transfer into the phone.
Now in twerp Press install, select the zip file and swipe to install. Also install Gapps or Magisk if you want (though normal magisk will have problem try install phh_magisk, discussed later).
Reboot and KABLAMO You have installed Havoc OS.
Bugs
A small random issue in Auto Brightness
If you root with magisk and install modules, after you reboot your phone will get into a bootloop. Use Phh_Magisk but I aint sure if it’ll work or not Your call madcap.
NONE OF THE FILES IN THIS TUTORIAL HAVE ANYTHING TO DO WITH ME. If SOMETIHING HAPPENS I AM NOT RESPONSIBLE. ONLY DO IT AT YOUR OWN RISK.
Troubleshooting.
If you find errors in twerp, such as unable to mount vendor or system_root, or data. Then you got to install the stock One Ui Back again, therefore it is highly recommended to keep with yourself the stock firmware. You will need It. And it is 4.78 gigs. You can download it from
Model : SM-A515F - Galaxy A51 — Samfrew.com
To reinstall the stock firmware first extract it and the open odin and repeat steps 8 and 9, once your device is detected in Odin press the respective buttons and select the respective files such as for BL button select the file With BL in the name. Do it for buttons, BL, AP(once you select the file it will take long for it load into odin so do not panic and let it load, it might become unresponsive but use patience and wait.)CP , CSC. Click on start and you’ll have ONE Ui back on your device.
To Lock the bootloader repeat steps 5 and 6.
If you still want more stability and Control You can install a different Kernel NDataX from (@Hendamanu) https://forum.xda-developers.com/m/hendramanu.11224917/

I'd like you to please correct the title and write GSI instead of custom rom as both are different things and the title can be considered misleading.

Yillié said:
I'd like you to please correct the title and write GSI instead of custom rom as both are different things and the title can be considered misleading.
Click to expand...
Click to collapse
Oh, my bad.. changed it.

GrandmaGotGuns said:
Oh, my bad.. changed it.
Click to expand...
Click to collapse
Thanks a lot

Is stable? Does the fingerprint on the screen work?

LichtEstarossx said:
Is stable? Does the fingerprint on the screen work?
Click to expand...
Click to collapse
Its Stable and yes fingerprint works as well. Battery life is also good almost 9 hours of screen on time for my device.

GrandmaGotGuns said:
Its Stable and yes fingerprint works as well. Battery life is also good almost 9 hours of screen on time for my device.
Click to expand...
Click to collapse
I will try to test it although another question arose, the encryption works in the twrp or is it to disable the dm verity?

LichtEstarossx said:
I will try to test it although another question arose, the encryption works in the twrp or is it to disable the dm verity?
Click to expand...
Click to collapse
You need to flash disable dm verity before flashing the gsi.. one ui encrypts the data.

I'll soon update this for Android 11 (R)

I did all the steps correctly (started oneui before), but now it won't start the system, is there any way to fix it?

LichtEstarossx said:
I did all the steps correctly (started oneui before), but now it won't start the system, is there any way to fix it?
Click to expand...
Click to collapse
What android version are you at?

GrandmaGotGuns said:
What android version are you at?
Click to expand...
Click to collapse
I had android 10
one ui 2.5
although it is rare that the gsi does not work

LichtEstarossx said:
I had android 10
one ui 2.5
although it is rare that the gsi does not work
Click to expand...
Click to collapse
If you are using the same gsi mentioned above then it should work. Not all GSIs will run on your device. Did you successfully install twerp?

GrandmaGotGuns said:
If you are using the same gsi mentioned above then it should work. Not all GSIs will run on your device. Did you successfully install twerp?
Click to expand...
Click to collapse
use havoc 3.8 vanilla arm64 ab
and I tried phh aosp but it didn't work

LichtEstarossx said:
use havoc 3.8 vanilla arm64 ab
and I tried phh aosp but it didn't work
Click to expand...
Click to collapse
Model : SM-A515F - Galaxy A51 — Samfrew.com
Model : SM-A515F | Samsung Firmware Database
samfrew.com
Upgrade to android 11, first install one ui 3 from the site above. I'll update it for Android 11 [R].

GrandmaGotGuns said:
Model : SM-A515F - Galaxy A51 — Samfrew.com
Model : SM-A515F | Samsung Firmware Database
samfrew.com
Upgrade to android 11, first install one ui 3 from the site above. I'll update it for Android 11 [R].
Click to expand...
Click to collapse
for now reinstall oneui 2.5, I will try to compile orangefox for android 10, and about the brightness bug in the gsi I know how to correct it, if there is any way to contact you to talk about it, say so

LichtEstarossx said:
for now reinstall oneui 2.5, I will try to compile orangefox for android 10, and about the brightness bug in the gsi I know how to correct it, if there is any way to contact you to talk about it, say so
Click to expand...
Click to collapse
If you are talking about gsi fix then im not sure that it'll work. I tried patching other gsi's for specifically efor xynos but the success rate is 50%. Sure let's talk here

GrandmaGotGuns said:
If you are talking about gsi fix then im not sure that it'll work. I tried patching other gsi's for specifically efor xynos but the success rate is 50%. Sure let's talk here
Click to expand...
Click to collapse
What I say is not a patch, it is one of the phh oberlays for aosp gsi, after I have time I will try to make one, but that overlay would only be for the a51, not for another Samsung
If it is about gsi I am relatively knowledgeable about that, although as far as I know it was not necessary to use this zip to enter gsi, I think the super partition must be modified to install gsi

LichtEstarossx said:
What I say is not a patch, it is one of the phh oberlays for aosp gsi, after I have time I will try to make one, but that overlay would only be for the a51, not for another Samsung
If it is about gsi I am relatively knowledgeable about that, although as far as I know it was not necessary to use this zip to enter gsi, I think the super partition must be modified to install gsi
Click to expand...
Click to collapse
I attach my telegram username in case you need something more specific.
(nicopizza) Add the @

Can someone plz assist........I got the rom installed on issues
Root chkr says I'm rooted but substratum says I'm not Magisk I don't think I have the patch img. for it..... plz can someone hlp