Develop Bugs

[RECOVERY][OFFICIAL] TWRP for Galaxy S9 (Exynos)

Thread moved to https://forum.xda-developers.com/galaxy-s9/samsung-galaxy-s9--s9-cross-device-development/twrp-exynos-t3763464.

Changelog:
Note that this page only includes device-specific changes. For global TWRP changes, go to twrp.me.
Mar 16, 2018 (twrp-3.2.1-1):
Add system_image, vendor_image
Rename display name of /odm to "Carrier Configs"
Mar 15, 2018:
Initial version

Guides:
Be aware that Android Verified Boot requires data (including those in internal storage) to be cleared after you unlocked bootloader and flash custom binaries. ("to protect user data, all state transitions wipe the data partitions and ask the user for confirmation before data is deleted." - https://source.android.com/security/verifiedboot/verified-boot)
It is normal to get prompts like "Integrity verification failed. You have to reset the device to factory settings."
However, this will only happen when there is "state transition" so only when you switch from locked to unlocked or vice versa.
Part 1 - HOW-TO FLASH TWRP:
1. In your ROM, go to Settings -> About device. Tap 7 times on Build number to enable Developer options.
2. Go to Settings -> Developer options and enable OEM Unlock option.
Notice: This is "state transition" mentioned eailier.
3. Download and Install Samsung Mobile Phones Drivers.
- Option 1: Download and Install Smart Switch for PC.
- Option 2: Download and Install standalone driver package.
4. Download and extract Odin (Samsung's Flash Tool) to your computer.
5. Download a .tar image of TWRP.
6. Reboot your device to download mode.
- Hold [VOLUME DOWN] + [BIXBY] + [POWER] for approx. 15 seconds.
- Read the warning carefully.
- If you agree, press [VOLUME UP] to get into Download mode. If you don't agree, STOP.
7. Open Odin and place that TWRP tar file in the [AP] slot.
8. Connect your phone.
9. Hold [VOLUME UP] + [BIXBY] + [POWER] on your phone and then press start on Odin.
10. Wait for the phone to reboot. DO NOT release [VOLUME UP] + [BIXBY] + [POWER] or you may not reboot into TWRP.
Part 2 - HOW-TO INITIALIZE TWRP: (for new phones)
1. If you completed Part 1 successfully, you should be in TWRP now. At this point, you will reach the screen asking you if you want to allow system modifications.
2. Select "Keep /system RO". (Don't swipe right or you may not be able to boot into system if you failed to complete next steps. However, you can swipe right to allow modifications if you are confident that you can complete next steps.)
3. Go to "Wipe" menu of TWRP and you will find "Format Data". Press "Format Data" and type "yes" to continue.
4. Go to "Reboot" menu and Press "Recovery" to reboot TWRP.
5. Download the special dm-verity and force encryption disabler zip on your computer.
6. Transfer the zip to your phone.
- Option 1: MTP: Connect your phone with computer and just copy the zip to internal storage. (similar to how you transfer files when in system.)
- Option 2: ADB: Connect your phone with computer and run command "adb push /path/to/zip /sdcard/".
- Option 3: External SD: Copy the zip to an external SD and then insert the card to your phone.
7. Go to "Install" menu of TWRP and flash the zip.
TWRP is initialized and fully functional at this stage.

jesec said:
Now you can either reboot into system or root, flash custom ROMs via TWRP.
Click to expand...
Click to collapse
In theory you can, but so far no one including myself has been able to root from this.
See this thread https://forum.xda-developers.com/galaxy-s9/development/twrp-samsung-s9-t3763548/
I wiped my data for nothing!

Wow that was fast twrp already.
Nice work Jesec and thank you:thumbup:
Now lets see how long till some dummy asks if it works on the snapdragon lol
sent from my Pixel 2 XL or Note FE

@jesec if this twrp is becoming the official one I suggest you to include some of my features/fixes as for example img flash to specific partitions, OTG fix and more (also people on the s9+ thread reported that usb wasn't working), check my device tree here.
Have a nice day!

Can we flash SuperSU/Magisk instead of the dm-verity disabler? To root as well as for disabling dm-verity at the same time?

Tkkg1994 said:
@jesec if this twrp is becoming the official one I suggest you to include some of my features/fixes as for example img flash to specific partitions, OTG fix and more (also people on the s9+ thread reported that usb wasn't working), check my device tree here.
Have a nice day!
Click to expand...
Click to collapse
Please follow the contribution and code review process of TWRP if you want to contribute.
I will review the changes.

After following the instructions exactly in the OP, I flashed SuperSU v2.82-SR5-20171001224502. My S9 is rooted and everything is working great!
Thanks
(NOTE to North Americans: Don't get your hopes up, although I am in Canada, I have the Exynos version SM-G960F)

flar2 said:
After following the instructions exactly in the OP, I flashed SuperSU v2.82-SR5-20171001224502. My S9 is rooted and everything is working great!
Thanks
(NOTE to North Americans: Don't get your hopes up, although I am in Canada, I have the Exynos version SM-G960F)
Click to expand...
Click to collapse
Will we see a kernel of yours ?
I mean after the news that AOSP GSI images are booting, one of the greatest kernel developer coming to S9 would be like the cherry on the top.

Paradoxxx said:
Will we see a kernel of yours ?
I mean after the news that AOSP GSI images are booting, one of the greatest kernel developer coming to S9 would be like the cherry on the top.
Click to expand...
Click to collapse
Maybe. I got this phone mostly for testing Button Mapper and High Brightness Mode. I couldn't resist trying to build a kernel this morning. It booted after a couple tries, but there was no wifi.

flar2 said:
Maybe. I got this phone mostly for testing Button Mapper and High Brightness Mode. I couldn't resist trying to build a kernel this morning. It booted after a couple tries, but there was no wifi.
Click to expand...
Click to collapse
Sounds like a good start to me
I'm sure Samsung people, and myself would love some kernel magic.
For both Samsung and AOSP flavors

https://www.xda-developers.com/samsung-galaxy-s9-aosp-android-oreo-project-treble/

flar2 said:
Maybe. I got this phone mostly for testing Button Mapper and High Brightness Mode. I couldn't resist trying to build a kernel this morning. It booted after a couple tries, but there was no wifi.
Click to expand...
Click to collapse
It is regarding an unpatched fimc , we had this issue on s8

Fennec_1 said:
It is regarding an unpatched fimc , we had this issue on s8
Click to expand...
Click to collapse
I'm guessing this involves editing a firmware binary?
(Sorry for OT, though it is development related)

flar2 said:
I'm guessing this involves editing a firmware binary?
(Sorry for OT, though it is development related)
Click to expand...
Click to collapse
Yup, im not sure about which fimc-<name>.bin needed to be patched on s9
Although this wont be a problem if you running gsi

Fennec_1 said:
It is regarding an unpatched fimc , we had this issue on s8
Click to expand...
Click to collapse
flar2 said:
I'm guessing this involves editing a firmware binary?
(Sorry for OT, though it is development related)
Click to expand...
Click to collapse
Fennec_1 said:
Yup, im not sure about which fimc-<name>.bin needed to be patched on s9
Although this wont be a problem if you running gsi
Click to expand...
Click to collapse
That was for camera issues, the wifi issue is secure storage related.

mwilky said:
That was for camera issues, the wifi issue is secure storage related.
Click to expand...
Click to collapse
Ah, thanks for correcting me

I've had a few issues with FRP randomly being triggered and not allowing TWRP to boot at all. Still not sure what causes it (might be because I changed my google account password) but I've successfully been able to reflash stock without losing the data partition, so you can re-root without losing anything. Had to remove the USERDATA image from the stock AP tar file to not wipe USERDATA tho.

flar2 said:
Maybe. I got this phone mostly for testing Button Mapper and High Brightness Mode. I couldn't resist trying to build a kernel this morning. It booted after a couple tries, but there was no wifi.
Click to expand...
Click to collapse
Change wifi paths in config

[ROM][UNOFFICIAL][AICP][14.0][dragon] -> 20190213 (DISCONTINUED)

DISCONTINUED
Sorry .. due to limited time I have stopped this ROM.
Pls find the last downloads here ..
https://androidfilehost.com/?w=files&flid=289293
Thanks for understanding ..
Android Ice Cold Project - Pie
aicp_dragon_p-14.0-UNOFFICIAL-20190213.zip
Known issues:
- Encryption seems not work - and has not been tested. -> Pls do not encrypt your data partition yet.
- Keymaster -> If you set Pattern, PIN or Password the Screen unlock may not work correctly.
Workaround for Pattern: On fresh boot you will need to wait a bit longer before you enter credentials.
The waiting time is required on fresh boot only, the following unlocks are working normally.
In case of problems pls use Update.ZIP_TWRP_flashable_pattern_pin_remover_V2.zip to remove pattern/pin or password.
Installation:
1. Boot into TWRP (latest available version)
2. Wipe system, cache, dalvik and data partitions ! ( If you have encrypted /data partition - pls "format" /data via TWRP first ! )
3. Install aicp_dragon_p-14.0-UNOFFICIAL-20190213.zip
4. Install Opengapps (arm64)
5. install Magisk.zip
6. Reboot into system ..
- The ROM does contain it's own vendor.img !
SOURCES:
https://github.com/followmsi/manifests/tree/dragon-aicp-14.0
Enjoy ..

Just playing with the AICP sources for Pie and made a dragon build too ..
Let's test another Android ROM on our lovely dragon device ..
Cheers

followmsi said:
Just playing with the AICP sources for Pie and made a dragon build too ..
Let's test another Android ROM on our lovely dragon device ..
Cheers
Click to expand...
Click to collapse
First boot very fast about 40 seconds but few seconds after end of the setup process, the tablet start to freeze so violently that the device was unusable, nothing respond...
I press the reboot button, the tablet reboot after 30 seconds of freeze.
After reboot everthing seem to work just fine !
Good work, thanks

I'm running into some of the same issues as the other Pie threads:
Lockscreen issues. What worked for me was going into TWRP --> File Manager --> data --> system and deleting the lockscreen file, then booting back up, going into settings -after- initial setup and creating my pin/pattern there.
Encryption - I haven't tried this yet. I'm going to finish my install, make a backup, then see what happens.
Other than that it seems fine.

CharFalco said:
I'm running into some of the same issues as the other Pie threads:
Lockscreen issues. What worked for me was going into TWRP --> File Manager --> data --> system and deleting the lockscreen file, then booting back up, going into settings -after- initial setup and creating my pin/pattern there.
Encryption - I haven't tried this yet. I'm going to finish my install, make a backup, then see what happens.
Other than that it seems fine.
Click to expand...
Click to collapse
Thanks for feedback ..
Like you said .. same problems on all Pie ROMs.
As we use same device/kernel/vendor sources for all ROMs.
For this reason we should have the same/similar problems
Known issues:
- Encryption seems not work - and has not been fully tested. -> Pls do not encrypt your data partition yet.
- Screen Unlock: If you set Pattern or Password the Screen unlock does not work correctly.
(Workaround: On fresh boot you will need to wait a bit longer before you enter credentials.)
(The waiting time is required on fresh boot only, the following unlocks are working normally.)
Updated OP now .. hope the workaround works on AICP too.
Cheers

I feel a bit silly asking such a narrow question, but I couldn't find the answer on the AICP site.
Does AICP provide the ability to add a distinct, separate last app button? That's my favorite feature ever.
(This is not a feature request, like "please add XYZ." I'm just asking if it's already there.)
Thanks

I think this is probably my favorite of all the ROMs you've sent us. Do you have a Patreon or something, followmsi?

February 2019 - the final AICP ROM
aicp_dragon_p-14.0-UNOFFICIAL-20190213.zip
Changes:
- Google security updates -> February 2019
- Google kernel updates -> February 2019
- Latest AICP changes for Pie
The ROM does contain it's own vendor.img !
Enjoy

DISCONTINUED
Sorry .. due to limited time I have stopped this ROM.
Pls find the last downloads here ..
https://androidfilehost.com/?w=files&flid=289293
Thanks for understanding ..

I realise this has been discontinued but after rebooting my Pixel C today it now won't boot up again.
It loads the AICP logo then the animation of the logo almost finishes but leaves a bit of it on screen and just gets stuck in a loop of showing the remaining part of the logo and flashing the lock screen briefly.
I'm not sure what my options are for recovery... I'd rather not have to start over again as it's probably only been a couple of months before I had to start fresh on this device.

[ZE620KL/Android 9][TREBLE] COMPLETE GUIDE: Unlocking, Rooting & Flash GSI + Fixes

[ZE620KL/Android 9][TREBLE] COMPLETE GUIDE: Unlocking, Rooting & Flash GSI + Fixes
Unlocking bootloader to Flashing GSI (Asus Zenfone 5 [ZE620KL] / Android 9.0)
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
About :
The last guide could leads to soft brick, as the instructions were not clear nor the files not supported for Android 9.0.
Here is a complete guide with TWRP 3.3.0 for Android 9.0, clear instructions and multiple fixes for GSI.
It has been tested on stock version v16.0615.1903.92.​
Requirements :
- A stock version V16.0610.XXXX.XX or higher
- A phone on Android 9.0 (not 8.0!)
- A fully working USB cable
- Latest ADB / Fastboot drivers
- Bootloader unlocker (download latest from Asus website or from here)
- TWRP 3.3.0 image
- Android9EncryptionDisablerZE620KL.zip
- Magisk v19.3​
Instructions :
Unlocking Bootloader
1. Backup all your important data.
2. Install the bootloader unlocker APK, and follow the steps. You will loss your warranty here, and it will factory reset your data
3. If there is any issue here, go into your stock recovery (volume down + power button) and factory reset.​
Installing TWRP
4. Shutdown your device & boot in fastboot mode using volume up + power button.
5. Check that the connection between your device and your computer by typing this in your command line :
Code:
fastboot devices
6. Flash TWRP recovery using :
Code:
fastboot flash recovery <twrp_name>.img
7. Now reboot in recovery mode using :
Code:
fastboot oem reboot-recovery
8. In TWRP, select Wipe > Format Data > enter "yes" and confirm
9. Return to the main menu, select Reboot > Recovery
10. Do 8. & 9. and again
11. Using TWRP or ADB, install Android9EncryptionDisablerZE620KL.zip (on TWRP, go into Install > find Android9EncryptionDisablerZE620KL.zip > Install zip)
If everything has gone successfully, you now have a custom recovery.
As for some GSIs, a patched boot partition may cause bootloop, you should try installing Magisk after installing the GSI. If you want to keep your stock ROM, go directly to "Magisk Installation" section.​Installing a GSI
This step may vary depending on the different GSIs distribution. I assume you install Havoc OS v2.7 GSI which actually works on this device.
1. Backup all your important data using TWRP backup.
2. Select the arm64-aonly GSI image you want, and move it on your external SD.
3. Wipe Data, Dalvik, and Cache.
4. Go back in the main menu of TWRP, and reboot to recovery.
5. Remove Magisk if it was previously installed, by using its uninstaller script.
6. Flash the GSI to system partition.
7. Boot and perform a factory reset.​
Installing Magisk
1. Add the Magisk zip archive to your external storage.
2. Boot into TWRP recovery, and install the zip.
3. Enjoy!​
Bug fixes:
Insufficient storage in the system partition to flash GApps : Download your OpenGApps archive on your external SD, and use MagicGApps 2018.9.23 to install GApps.
Auto-Brightness doesn't work: Download framework-res__auto_generated_rro.apk from here.
Using a root explorer or command-line, push the APK to /vendor/overlay.
Then run the following command in a rooted terminal or ADB shell:
Code:
chcon u:object_r:vendor_overlay_file:s0 /vendor/overlay;chcon u:object_r:vendor_overlay_file:s0 /vendor/overlay/framework-res__auto_generated_rro.apk
My camera doesn't work well (green tint on face camera) and/or the app doesn't boot: If Asus Camera doesn't launch on your GSI, you should probably edit your /system/build.prob file.
You need to edit ro.product.model, ro.product.brand, ro.product.name, ro.product.device, ro.product.manufacturer & ro.build.product properties to be:
Code:
ro.product.model=ASUS_X00QD
ro.product.brand=asus
ro.product.name=WW_Phone
ro.product.device=ASUS_X00QD
ro.product.manufacturer=asus
ro.build.product=ZE620KL
You can instead use Google Camera mod (port from Arnova8G2 & modded by 5Z community, thanks to them!), which works well (edit: there is a bug on HavocOS, we can't access settings).​Bonus:
- You can reinstall DTS Headphone:X here.
- For booting your kernel in Permissive mode, check here
Sources:
TWRP 3.3.0 : On GitHub
If you need help or if you want to help on ZE620KL development go here:
https://t.me/Zenfone5Dev
(We will continue to update & help here though.)
Many thanks to all of the Zenfone 5 community (particularly Emincan, Pandolfi and Lmajkej),
Phhusson & Erfan for their works on GSI, and Shakalaca for its work on TWRP 3.3.0!​

On HavocOS v2.8 GSI (13-08-2019):
It works:
- Almost anything
- Adaptive Brightness (after manual fix)
- Notch overlay
- DTS Headphone X (after manual installation)
- NFC
- Face unlock
- Stock camera (after manual fix)
- Magisk
- SDcard access
It doesn't works:
- VoLTE / VoWifi
- Google Camera settings
- External speaker amplifier (NXP amp)
- APT-X / APT-X HD bluetooth
- Low microphone in normal use
- No microphone in calls (only headphone microphone works)

GCam settings
But my google camera keep crashing when I want to go into camera settings

Hi thanks for this tutorial, this is my first time rooting my phone. I'm encountering a problem with my sd card after installing havoc os, everytime i try to move, save or any write functionality i do to my sd card, it always says the android version isn't compatible. I could still see my files from my sd, but everytime it asks permission it always say this

bentley0928 said:
But my google camera keep crashing when I want to go into camera settings
Click to expand...
Click to collapse
Same issue here. I will update the thread when I will find a more working GCam port (perhaps, this GCam port works well on ZenUI)
Jolo110 said:
Hi thanks for this tutorial, this is my first time rooting my phone. I'm encountering a problem with my sd card after installing havoc os, everytime i try to move, save or any write functionality i do to my sd card, it always says the android version isn't compatible. I could still see my files from my sd, but every time it asks permission it always say this
Click to expand...
Click to collapse
It's a known issue, the GSI maintainer @vince31fr is working on it. I don't have it, but I can advice you to use Solid File Manager, which works like a charm on my device.

"- No microphone in calls (only headphone microphone works)"
Funny... I'm on stock latest firmware and I have this issue, so I thought I try something new, and this has that issue. It can't be a coincidence. Something is ****ed up with this device.

Wonder if this will work for the Zenfone 5 Lite (or 5Q)? I wanna root my 5Q so bad haha

Thanks for the great instructions! Steps 1 through 11 worked perfectly for me, then I installed LineageOS (lineage-17.0-20191231-UNOFFICIAL-treble_arm64_avN.img) and it works properly. Then when I go back to TWRP and install Magisk v20.1 it reboots into an endless Lineage bootup logo animation (not boot loop). I can get an adb shell, but now also the external SD card has become invisible. Any suggestions?
UPDATE: I switched over to the patched Magisk version from PHH (https://forum.xda-developers.com/zenfone-5/general/ze620kl-add-support-to-evey-android-9-t3966918) and everything works perfectly now!

Hi!! I thanks for these instructions you gave. I know this post is a bit older. But is the only one I think could help me.
I got an ZE620KL and I'm trying to root this device. I have some experience in unlocking bootloader and rooting devices. But this one... Is giving me a lot of work. Researching in a lot of forums and websites I tried a lot of things with no success. In theory, is just install the official apk provided by ASUS and run the application. But the app doesn't work for a long time as I researched (error accusing network problem). I tried unlock via fastboot commands but I always got stucked by "remote: permission denied" even with latest drivers and ADB Fastboot installed. And yes... I let my device with no one security feature enabled and didn't worked. I tried everything even after wiped data / cache and factory reset and no progress.
In my researches, I realized something about 'oem unlock'. It appears to be the key to solve this. And I guess the tool to work with this is the damn unlock tool from ASUS which don't work! Also, I've heard about workaround with Magisk by flashing a custom recovery to achieve the root. Magisk no longer supports zip files to flash. Only '.img' and '.tar' files. I'd like to find some light here... I don't know what to do. I appreciate any help!

Hello do I need to flash Android9EncryptionDisablerZE620KL.zip if Im gonna flash a non-GSI custom ROM? Or its only for GSI Treble ROM?

[email protected] said:
Hi!! I thanks for these instructions you gave. I know this post is a bit older. But is the only one I think could help me.
I got an ZE620KL and I'm trying to root this device. I have some experience in unlocking bootloader and rooting devices. But this one... Is giving me a lot of work. Researching in a lot of forums and websites I tried a lot of things with no success. In theory, is just install the official apk provided by ASUS and run the application. But the app doesn't work for a long time as I researched (error accusing network problem). I tried unlock via fastboot commands but I always got stucked by "remote: permission denied" even with latest drivers and ADB Fastboot installed. And yes... I let my device with no one security feature enabled and didn't worked. I tried everything even after wiped data / cache and factory reset and no progress.
In my researches, I realized something about 'oem unlock'. It appears to be the key to solve this. And I guess the tool to work with this is the damn unlock tool from ASUS which don't work! Also, I've heard about workaround with Magisk by flashing a custom recovery to achieve the root. Magisk no longer supports zip files to flash. Only '.img' and '.tar' files. I'd like to find some light here... I don't know what to do. I appreciate any help!
Click to expand...
Click to collapse
Im not sure if you still have your phone or you have successfully unlocked bl. but I found an updated version of their tool which works.
*tried unlocking from android 10 not working, it says device model not supported*
Zenfone 5 Unlock BL

cf100clunk said:
Thanks for the great instructions! Steps 1 through 11 worked perfectly for me, then I installed LineageOS (lineage-17.0-20191231-UNOFFICIAL-treble_arm64_avN.img) and it works properly. Then when I go back to TWRP and install Magisk v20.1 it reboots into an endless Lineage bootup logo animation (not boot loop). I can get an adb shell, but now also the external SD card has become invisible. Any suggestions?
UPDATE: I switched over to the patched Magisk version from PHH (https://forum.xda-developers.com/zenfone-5/general/ze620kl-add-support-to-evey-android-9-t3966918) and everything works perfectly now!
Click to expand...
Click to collapse
Do you still have the patched Magisk zip file, the original link in the post seems not working

[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