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?
Related
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review.
Code:
#include
/*
* 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.
*
* Submitting bug reports on nightly builds is the leading
* cause of male impotence.
*/
WHAT WORKS
Boot
WiFi
Hotspot
Audio
RIL
Bluetooth
Sensors
FM
Camera
SDCard
GPS
KNOWN ISSUES
Video recording
VoLTE [Don't expect it to be working anytime soon]
SELinux Enforcing
!!! BUG REPORTS WITHOUT LOGS WILL BE IGNORED !!!
Android: adb logcat
Radio: adb logcat -b radio
Kernel: adb shell dmesg
Full Bugreport: Developer Menu -> Bugreport
HOW TO INSTALL LINEAGEOS
- Download the LineageOS zip(s). (see Downloads)
- Download the TWRP Image. (see Downloads)
- Copy the LineageOS zip to internal sdcard.
- Unlock bootloader and install TWRP from downloads.
- Boot into TWRP.
- Perform a backup of your current ROM. (Optional)
- IMPORTANT: Do a Factory Reset. (Wipe data & cache)
- Flash LineageOS.
- Optional: Install the Google Apps addon package. (see Downloads)
- Reboot
DOWNLOADS
LineageOS:
https://www.androidfilehost.com/?w=files&flid=203899
TWRP:
https://www.androidfilehost.com/?w=files&flid=203904
Google Apps:
OpenGApps (recommended: arm, 7.1.1, nano)
SOURCECODE
Device tree: https://github.com/ashwinr64/android_device_motorola_taido
Kernel: https://github.com/ashwinr64/android_kernel_motorola_mt6735
Vendor: https://github.com/ashwinr64/android_vendor_motorola_taido
HOW TO CONTRIBUTE
Use our code review system to send patches: https://review.lineageos.org
SUPPORT ME
Do you like my work? Consider donating me some beer!
XDA:DevDB Information
LineageOS for taido, ROM for the Moto E3
Contributors
ashwin007
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.x
Version Information
Status: Testing
Created 2017-08-03
Last Updated 2017-08-03
Changelogs
-> Build 1 [04-08-2017]
* Initial Public Release
* Merged upstream 3.18.63 kernel.
* Switched to XZ kernel compression and enabled -O2 flag.
* Widevine has been fixed, so DRM contents are playable.
-> Build 2 [16-08-2017]
* Synced with Lineage
* Merged upstream 3.18.65 kernel
* Hotspot fixed
* Added support for F2FS
Thanks a lot!
And the development starts again
Dear @ashwin007,
I'm so glad [emoji1] to see that you are working on taido.
I appreciate your brilliant work.
All the best
A fresh install of this ROM shows 14 GB used up by the system partition and negligible space in the data partition. Any solutions?
Not installing.
Code 7 error
bubba1601 said:
Not installing.
Code 7 error
Click to expand...
Click to collapse
use TWRP given by Ashwin, also check weather u did factory reset....
also follow the instructions....
spykarzzz said:
use TWRP given by Ashwin, also check weather u did factory reset....
also follow the instructions....
Click to expand...
Click to collapse
My Friend, I've been flashing Roms on various devices for more than three years.......
So I have done a factory reset, as I'm using another lineage OS version on my E3.
I followed all instructions.
So the TWRP version I'm using must be the issue, its the Dr framazone version 3.0.0.2, I can't flash the new twrp image in the twrp I'm using.
I'll have to try in fast boot mode through the PC.
U need deckers TWRP to flash dis particular Rom....Try this only!!!
One request, can you please add double tap 2 wake feature in the kernel?
spykarzzz said:
U need deckers TWRP to flash dis particular Rom....Try this only!!!
Click to expand...
Click to collapse
Yes, I know and understand that.
As I said in my previous comment, I cannot flash the newer twrp image through the version of twrp I'm using.
I've have now managed to flash the twrp image via fast boot and have this ROM up and running.
Unfortunately I've ran into many problems not seen in the other lineage OS ROM that I've been using for the last week.
1. Guest user was activated after initial set up, meaning I could not change any settings.
2. I cannot access my external SD card.
So important files to me are inaccessible?
3. No photographs taken using the camera are being saved, they just disappear from the gallery into thin air.
4. My service provider doesn't list in networks or the signal indicator (O2 UK) instead my device shows "23410"
Its at this point I confess to running this rom on my XT1700 and NOT a XT1706 (My device is in fact a European spec standard Motorola E3, but running E3 power firmware and renamed in system to a E3 power XT1706 - this was flashed by Motorola themselves during a repair as they claimed I had to pay for XT1700 firmwares, so E3 Power firmware was flashed by them.
Although I appreciate Ashwins efforts and i appreciate this is a testing version, I cannot use this ROM as I'm now also in trouble with my employer for not having photographic evidence of my work today (My E3 is used as my work device, and taking photos of my finished work is a requirement of my employment)
I have to now move to another ROM for this reason until these issues can be fixed and photos taken with the camera will be saved and stay saved.
Sorry.
Is there any issue with this rom
Pls let me know friends
I am waiting for a stable rom
Camera is working or not
Or any kind of bugs pls tell me
aman4512 said:
A fresh install of this ROM shows 14 GB used up by the system partition and negligible space in the data partition. Any solutions?
Click to expand...
Click to collapse
Bro do this....
U have to go to fastboot mode....
Then enter fastboot format userdata....
Then fastboot flash recovery.img
Then dont go to recovery let ur phone start....
Then enable usb debug & oem unlock in phone after rebooting...
Again switch of ur phone...
Now goto fastboot mode....
Type fastboot flash recovery .img
Now go to recovery and flash the rom file
It ll work 100%
solkarsalman said:
Bro do this....
U have to go to fastboot mode....
Then enter fastboot format userdata....
Then fastboot flash recovery.img
Then dont go to recovery let ur phone start....
Then enable usb debug & oem unlock in phone after rebooting...
Again switch of ur phone...
Now goto fastboot mode....
Type fastboot flash recovery .img
Now go to recovery and flash the rom file
It ll work 100%
Click to expand...
Click to collapse
Thanks, but I had solved the problem. The thing is my phone wasn't booting at all after flashing TWRP. Tried many version. It was some issue with the phone's boot.img (some Lenovo phone has a similar issue, K4 power I think). I flashed a stock ROM and after flashing TWRP, I flashed SuperSU, since it patches boot.img. That worked, after which I wiped /system, /data, /cache and flashed Lineage.
bjyadav4 said:
Is there any issue with this rom
Pls let me know friends
I am waiting for a stable rom
Camera is working or not
Or any kind of bugs pls tell me
Click to expand...
Click to collapse
Read the comments above you own
Don't install it, I had major issues.
Read previous comments before posting.
bubba1601 said:
Yes, I know and understand that.
As I said in my previous comment, I cannot flash the newer twrp image through the version of twrp I'm using.
I've have now managed to flash the twrp image via fast boot and have this ROM up and running.
Unfortunately I've ran into many problems not seen in the other lineage OS ROM that I've been using for the last week.
1. Guest user was activated after initial set up, meaning I could not change any settings.
2. I cannot access my external SD card.
So important files to me are inaccessible?
3. No photographs taken using the camera are being saved, they just disappear from the gallery into thin air.
4. My service provider doesn't list in networks or the signal indicator (O2 UK) instead my device shows "23410"
Its at this point I confess to running this rom on my XT1700 and NOT a XT1706 (My device is in fact a European spec standard Motorola E3, but running E3 power firmware and renamed in system to a E3 power XT1706 - this was flashed by Motorola themselves during a repair as they claimed I had to pay for XT1700 firmwares, so E3 Power firmware was flashed by them.
Although I appreciate Ashwins efforts and i appreciate this is a testing version, I cannot use this ROM as I'm now also in trouble with my employer for not having photographic evidence of my work today (My E3 is used as my work device, and taking photos of my finished work is a requirement of my employment)
I have to now move to another ROM for this reason until these issues can be fixed and photos taken with the camera will be saved and stay saved.
Sorry.
Click to expand...
Click to collapse
I didn't face any of the above issues on my Moto E3 Power. Camera is working fine and photos are also saving.
SD card is also accessible.
---------- Post added at 07:34 AM ---------- Previous post was at 07:30 AM ----------
bjyadav4 said:
Is there any issue with this rom
Pls let me know friends
I am waiting for a stable rom
Camera is working or not
Or any kind of bugs pls tell me
Click to expand...
Click to collapse
Camera is working properly.
If you do this
Thanks, but I had solved the problem. The thing is my phone wasn't booting at all after flashing TWRP. Tried many version. It was some issue with the phone's boot.img (some Lenovo phone has a similar issue, K4 power I think). I flashed a stock ROM and after flashing TWRP, I flashed SuperSU, since it patches boot.img. That worked, after which I wiped /system, /data, /cache and flashed Lineage.
Click to expand...
Click to collapse
then storage problem will also be solved.
aman4512 said:
A fresh install of this ROM shows 14 GB used up by the system partition and negligible space in the data partition. Any solutions?
Click to expand...
Click to collapse
Is this the actual screenshot? Because the developer has mentioned that LTE is not working but the screenshot shows LTE in the notification bar.
ranjithgn said:
Is this the actual screenshot? Because the developer has mentioned that LTE is not working but the screenshot shows LTE in the notification bar.
Click to expand...
Click to collapse
LTE works, VoLTE doesn't.
precedentbrute said:
I didn't face any of the above issues on my Moto E3 Power. Camera is working fine and photos are also saving.
SD card is also accessible.
---------- Post added at 07:34 AM ---------- Previous post was at 07:30 AM ----------
Camera is working properly.
If you do this
then storage problem will also be solved.
Click to expand...
Click to collapse
Thank you for your feedback, although I can't share your optimism or your confidence.
I've now reflashed this rom three times.
I cannot access external storage.
Photos disappear from the gallery, and now all my Google apps keep force closing - I'm using the recommendation of Google apps, open gapps nano arm.
Remember just because it's all good for you doesn't necessarily mean it's good for others, as I've seen so many times in these forums.
Regards.
This is a LineageOS 15.1 ROM for the Exynos3470 based Samsung Galaxy S5 mini (G800F/G800M/G800Y).
DO NOT USE IT FOR G800H OR YOU WILL BRICK YOUR DEVICE
Please do not ask for support or ROMs for the G800H. G800F and G800H have nothing in common.
Working features
HW accelerated GUI
Initiate and receive calls
Camera (only photos)
Flash Light
Sound
Fingerprint scanner
Hardware sensors (Orientation, Compass, Proximity, Acceleration, Hall sensor, Step counter)
Light sensor (needed for auto-brightness)
Pulse sensor (preliminary and very inaccurate. Works with Apps like Kardiograph)
Wifi
GPS
Bluetooth (A2DP, HFP, HID)
Mobile Data
SMS
MTP storage
USB-OTG (Keyboard, Mouse, USB-Audio)
IR
NFC
Video reproduction is still sometimes a bit buggy on browser (Youtube works fine)
Untested features:
SD-Card as internal storage
Known issues:
USB-OTG (Mass-Storage): detected but the file-system is not usable and will be corrupted afterwards (--> do not connect your USB-stick at the moment)
SELinux not enforcing
Video recording is still buggy/not working (crashes)
Fingerprint scanner can only records 3 fingers and sometimes it could be unresponsive
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.
Applications that use KNOX (e.g. "Private Mode") might not work anymore when returning to the stock ROM, as the device is regarded as compromised. Do not flash this ROM if you need those applications.
The image is only for Exynos3470 based S5 Mini variants SM-G800F/M/Y.
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)
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.
Important note: It is possible that flashing this ROM can cause efs partition issues. Therefore it is strongly recommended to make a backup of your efs partition before flashing this ROM. This can be done via TWRP.
Download:
Odin3-v3.07 (it is contained in CF-Auto-Root)
TWRP 3.1.1-0 (.tar.md5 file)
Latest TWRP (.img/.tar file)
LineageOS 15.0 ROM for G800F/M/Y: Android File Host
LineageOS 15.1 Monthly/Weekly updates (@Andrea224): Google Drive
Open GApps (select the variant you prefer, e.g. mini)
Install recovery:
Reboot your device into Download 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" (in newer versions: "AP") and select the recovery image (recovery.tar.md5)
Check that only "F. Reset Time" is set. "Auto Reboot" should be disabled to avoid a reboot into stock ROM.
Click on "Start": the recovery image should be flashed now. By flashing the recovery, your warranty will be void.
After the recovery flashing process was successful, reboot into recovery mode (see instructions below).
Important: make sure not to boot into stock ROM, otherwise the stock ROM might remove the custom recovery again. If this happens, flash the recovery image again.
Flash ROM:
Reboot into recovery mode (Press Volume-Up + Home + Power button)
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.
Copy GApps and LineageOS ROM zip to your device's internal or external SD card
Connect your device via USB to a PC. You should see the device in the Windows File Explorer now.
If you do not see the device in File Explorer, make sure that MTP is enabled (inside Mounts, click on Enable MTP).
If MTP does not work from recovery, try to copy via MTP by booting your old Android ROM or just remove the external SD card and copy to it directly.
Select one of the two drives (internal or external SD) and copy the files to it.
Do not put the files into the data directory of the internal sd card, otherwise they will be wiped in the next step.
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 LineageOS ROM zip package
Install the GApps zip package
How to root:
LineageOS does not have root support integrated by default. You have to download addonsu-arm-signed.zip for 14.1 from the Lineageos Extras download page and install it with TWRP.
After that root access is still disabled by default. 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 CM 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:
24/10/2017:
* Wake on Home button press
* Model string fixed ("G800F" instead of "G800")
* GPS fixed
* Bluetooth fixed
* Update to newest LineageOS sources
* Note: Android 8.0 requires a new TWRP recovery (build from 22/10/2017). otherwise you will not be able to flash the image ("E3004: This package is for device: kminiltexx,kminiltedv,kminilteub,kminilte; this device is .")
10/10/2017:
* telephone calls working
* Camera works (recording videos might still not work)
* LineageOS sources updated
24/09/2017:
* Initial test build
Source:
https://github.com/cm-3470/android_device_samsung_kminilte (Check README.md for build instructions)
Help from other developers is always welcome. Just ask in this thread or PM if you want to help.
Thanks to spookcity138, ayke, mirhciulica, Psyafter and CTXz for working on this ROM.
XDA:DevDB Information
[G800F/M/Y][ROM][8.1.0][OPM2] LineageOS 15.1 for G800F/M/Y [Alpha], ROM for the Samsung Galaxy S5 Mini
Contributors
hennymcc, ayke, Andrea224, spookcity138, mirhciulica, CTXz
Source Code: https://github.com/cm-3470
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.4.x
ROM Firmware Required: TWRP Recovery [version >= 22/10/2015]
Based On: LineageOS
Version Information
Status: Alpha
Created 2017-09-24
Last Updated 2018-07-05
Wow thanks for your amazing work!
I am experiencing random reboots when I lock my device.
oh nice, im testing right now
tibor8 said:
I am experiencing random reboots when I lock my device.
Click to expand...
Click to collapse
Thanks for the info. I was able to reproduce it now. Will be fixed in next build.
RIL will be fixed too.
phone when it locks up in a reset, it does not turn on a constant download, and the wi-fi is on and off after every 5 seconds. Also, there's no way to turn off the backlight of the buttons. Also, I noticed that the connection only lights up H on the seven I'm on H +
wasya78 said:
phone when it locks up in a reset, it does not turn on a constant download, and the wi-fi is on and off after every 5 seconds. Also, there's no way to turn off the backlight of the buttons. Also, I noticed that the connection only lights up H on the seven I'm on H +
Click to expand...
Click to collapse
That means you see the SIM-card now?
yes sim card is seen
---------- Post added at 09:20 AM ---------- Previous post was at 09:17 AM ----------
still noticed that the android 8.0 does not work camera
amazing
wasya78 said:
yes sim card is seen
Click to expand...
Click to collapse
Hallelujah, I'm gonna go get drunk *vodka*
ty best news since your lineage 14 release +++
Hello, is it possible to deactivate this new Slide Menu on Home Screen? To have the old Catapult menu Button back? Or will it be possible in future releases?
There is root inbuild again?
Thanks for development!!
MikeT. said:
There is root inbuild again?
Thanks for development!!
Click to expand...
Click to collapse
No
Sorry my mistake, its the rootmanagment for addonsu in develooer options, now i see it.
Thanks for fast reply
Great! Thanks. Looking forward to next build.
Will these non-working features be updated soon? Because I am using version 14.1 at the moment, and I can't even start the camera... I hope you will either update the previous version or get the camera working in version 15 so I can use that version.
just wanna stop by and tell you that you're awesome, keep up the amazing work!
Jelsie said:
Will these non-working features be updated soon? Because I am using version 14.1 at the moment, and I can't even start the camera... I hope you will either update the previous version or get the camera working in version 15 so I can use that version.
Click to expand...
Click to collapse
At least camera and calls work now. I was abroad for a week so I could not work on it or release a new build.
Maybe there will be a new build next week.
I uploaded a new build with RIL and camera fixed. See opening post for more details.
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
Test twrp build for this mediatek device (SM-C7100). Post logs etc so I can help solve issues when I am available to do so.
TWRP download: https://www.androidfilehost.com/?fid=673956719939834043
SM-C7100_C7100ZHU1ARB1.zip: https://www.androidfilehost.com/?fid=673956719939834050
Kernel download: https://www.androidfilehost.com/?fid=746010030569970527 April, 23rd, 2018
Sources
Kernel source: https://github.com/travismills82/android_kernel_samsung_mt6757
TWRP device tree: https://github.com/travismills82/twrp_android_device_samsung_jadeltechn
Kernel Features
Knox Disabled
DM-Verity Disabled
Tima Disabled
More TCP congestion control algorithms
Remove verifiedbootstate flag from /proc/cmdline (for safety net)
Conservative gov enabled
Always enforce selinux disabled
Fsync on/off Toggle
Ninendo Wiimote support
+ More not listed check git changes for a full list
Regards,
Travis82
Hi it didn't work... I think this is for J7 plus only and please Help after flashing the custom recovery my boot logo of C8 is gone.... Please help
I have tried to install using odin and it says on the phone a chinese message,which i translated with google, that read your phone needs to be unlocked to install a custom operating system, even though i enabled oem unlock and usb debugging. I used viper4android on my old phone and its annoying that im not able to install it on my new one.
Please help me when you get time:good:
the twrp cannot mount data partition unless format it first. and my device is sm c7100.
I can't install twrp in the first place.
How did you guys install it.
I managed to install twrp with odin after unlocking bootloader with crom service and disabling frp lock but when i try to boot into it there's nothing. It just boots into android. Tried installing it again. I tried adb reboot recovery but that booted to the official samsung recoveryb even though i installed twrp. How to fix this??
How to use the TWRP with Android Oreo?
Gautam488 said:
I managed to install twrp with odin after unlocking bootloader with crom service and disabling frp lock but when i try to boot into it there's nothing. It just boots into android. Tried installing it again. I tried adb reboot recovery but that booted to the official samsung recoveryb even though i installed twrp. How to fix this??
Click to expand...
Click to collapse
Brother how do you manged to unlock bootloader...? Please share with us
google play gives an error, the installation screen is not constantly installing
Hi everyone,
For those who have tried, could you please confirm whether the files are working or not.
Since there is no steps and instructions, can someone post the the procedure/code used for flashing kernel and TWRP?
Thanks
I finally tested everything out. Please feel free to take the command for reference.
Disclaimer:
1. Warranty would be voided and I am not responsible for any:
- Bricked device
- Data loss. So PLEASE BACKUP and you will definitely lose all your data during the rooting process.
2. I am not the one who build the files such as Kernel and TWRP img
Donation:
- BUT I am the one spending the time to test the files out. So, if you are happy with my work, please donate. I am happy for whatever (I mean the amount) support you give me.
- Bitcoin address: bc1qzvv3wrfj0furpzhdfxvzp07gy7whan907045gn
Aim:
1. Since Samsung Galaxy C8 has only 64GB of internal storage, 1000% sure it is not enough for using in 2021 onwards -> We need data and obb to SD card
2. MediaTek Hellio P20 is not powerful enough for using in 2021 onwards -> Need some CPU tweak
-> So, IT CAN’T BE USED WITHOUT ROOT
3. Makes Android great again
Summary:
- Both TWRP and Kernel, posted by Travis82 are definitely working for Samsung Galaxy C8 since I have tested them out and using them but they are only for Android 7.1.1 and not for stock Android 8.1.
- The files are NOT tested with Custom Rom.
- The reason why I said the Kernel is also for Android 7.1.1 because you need TWRP for flashing.
Procedure (For Android 8.1 user) NOT RECOMMENDED:
- First of all, Android 8.1 is SERIOUSLY NOT RECOMMENED for Samsung Galaxy C8 as nothing much you can do even though you are rooted. (i.e. XInternalSD causes bootloop)
- As mentioned above, both TWRP and Kernel posted by Travis82 are not compactable with Android 8.1
- For Android 8.1 user, it is recommended to downgrade to Android 7.1.1 with Odin.
- If you still want to use Android 8.1 and root, follow the guide in the link below using Magisk. Just follow the section for Samsung is good enough:
https://www.xda-developers.com/root/amp/
Procedure (For Android 7.1.1 user) RECOMMENDED:
Unlock bootloader + Enable developer mode -> USB debug + Prepare a SD card and put both Kernel and Magisk zip to the SD card
Applying TWRP recovery
Compress the recovery image to a .tar archive using 7-Zip
Install 7-zip
Right-click on recovery.img
“7-zip”
“Add to archive”
Select “tar” for “Archive format”
Flashing the recovery tar archive in Odin
Download, install and open Odin (I use Odin3 v3.13)
Unclick/Deselect “Auto Reboot” and “F. Reset Time” under “Options”
Enter Download mode
Power off, Power button + Volume Down + Home button, connect your PC
Flash the recovery tar archive in AP slot
When done flashing, unplug the device and enter recovery mode.
Power button + Volume Up + Home button, when the screen goes blank quickly, Power button + Volume Down + Home button.
If you can’t boot to recovery in this way, use ADB. “adb reboot recovery”
Applying new Kernel and Magisk
If storage can’t be mounted in TWRP (i.e. 0MB), consider changing the SD card or see this post: https://forum.xda-developers.com/t/...rnal-storage-0mb-in-twrp-permanently.3830897/ To be honest, there are lots of ways to fix this problem. Find the one best fit for you.
Flash Kernel zip in TWRP as usual
Flash Magisk zip in TWRP as usual
Reboot and wait, it takes quite a long time to boot
NOT DONE yet. You will probably face a serious problems in this stage:
Wifi passwords and Bluetooth connections can’t be saved
To solve this problem -> Install “Libsecure_Storage” in Magisk
DONE
Want Xposed? -> Search for the one for Android 7.1.1
Want app data to SD card? -> ExSDCard Access Enabler (Magisk) + XInternalSD (Xposed)
Want app obb to SD card? -> ExSDCard Access Enabler (Magisk) + Obb on SD (Xposed)
Want ram (swap), CPU tweak? -> App2SD
Want to reward me for my hard work? -> Donate
Bitcoin address: bc1qzvv3wrfj0furpzhdfxvzp07gy7whan907045gn
If you found anything on top of these things, please share.
toto4c19 said:
I finally tested everything out. Please feel free to take the command for reference.
Disclaimer:
1. Warranty would be voided and I am not responsible for any:
- Bricked device
- Data loss. So PLEASE BACKUP and you will definitely lose all your data during the rooting process.
2. I am not the one who build the files such as Kernel and TWRP img
Donation:
- BUT I am the one spending the time to test the files out. So, if you are happy with my work, please donate. I am happy for whatever (I mean the amount) support you give me.
- Bitcoin address: bc1qzvv3wrfj0furpzhdfxvzp07gy7whan907045gn
Aim:
1. Since Samsung Galaxy C8 has only 64GB of internal storage, 1000% sure it is not enough for using in 2021 onwards -> We need data and obb to SD card
2. MediaTek Hellio P20 is not powerful enough for using in 2021 onwards -> Need some CPU tweak
-> So, IT CAN’T BE USED WITHOUT ROOT
3. Makes Android great again
Summary:
- Both TWRP and Kernel, posted by Travis82 are definitely working for Samsung Galaxy C8 since I have tested them out and using them but they are only for Android 7.1.1 and not for stock Android 8.1.
- The files are NOT tested with Custom Rom.
- The reason why I said the Kernel is also for Android 7.1.1 because you need TWRP for flashing.
Procedure (For Android 8.1 user) NOT RECOMMENDED:
- First of all, Android 8.1 is SERIOUSLY NOT RECOMMENED for Samsung Galaxy C8 as nothing much you can do even though you are rooted. (i.e. XInternalSD causes bootloop)
- As mentioned above, both TWRP and Kernel posted by Travis82 are not compactable with Android 8.1
- For Android 8.1 user, it is recommended to downgrade to Android 7.1.1 with Odin.
- If you still want to use Android 8.1 and root, follow the guide in the link below using Magisk. Just follow the section for Samsung is good enough:
https://www.xda-developers.com/root/amp/
Procedure (For Android 7.1.1 user) RECOMMENDED:
Unlock bootloader + Enable developer mode -> USB debug + Prepare a SD card and put both Kernel and Magisk zip to the SD card
Applying TWRP recovery
Compress the recovery image to a .tar archive using 7-Zip
Install 7-zip
Right-click on recovery.img
“7-zip”
“Add to archive”
Select “tar” for “Archive format”
Flashing the recovery tar archive in Odin
Download, install and open Odin (I use Odin3 v3.13)
Unclick/Deselect “Auto Reboot” and “F. Reset Time” under “Options”
Enter Download mode
Power off, Power button + Volume Down + Home button, connect your PC
Flash the recovery tar archive in AP slot
When done flashing, unplug the device and enter recovery mode.
Power button + Volume Up + Home button, when the screen goes blank quickly, Power button + Volume Down + Home button.
If you can’t boot to recovery in this way, use ADB. “adb reboot recovery”
Applying new Kernel and Magisk
If storage can’t be mounted in TWRP (i.e. 0MB), consider changing the SD card or see this post: https://forum.xda-developers.com/t/...rnal-storage-0mb-in-twrp-permanently.3830897/ To be honest, there are lots of ways to fix this problem. Find the one best fit for you.
Flash Kernel zip in TWRP as usual
Flash Magisk zip in TWRP as usual
Reboot and wait, it takes quite a long time to boot
NOT DONE yet. You will probably face a serious problems in this stage:
Wifi passwords and Bluetooth connections can’t be saved
To solve this problem -> Install “Libsecure_Storage” in Magisk
DONE
Want Xposed? -> Search for the one for Android 7.1.1
Want app data to SD card? -> ExSDCard Access Enabler (Magisk) + XInternalSD (Xposed)
Want app obb to SD card? -> ExSDCard Access Enabler (Magisk) + Obb on SD (Xposed)
Want ram (swap), CPU tweak? -> App2SD
Want to reward me for my hard work? -> Donate
Bitcoin address: bc1qzvv3wrfj0furpzhdfxvzp07gy7whan907045gn
If you found anything on top of these things, please share.
Click to expand...
Click to collapse
Libsecure storage cannot be downloaded from anywhere could you please provide me link for the module
toto4c19 said:
For Android 8.1 user, it is recommended to downgrade to Android 7.1.1 with Odin.
Hello, thx for all your hard work.
Click to expand...
Click to collapse
My C8 is 8.1 tried resetting back to factory, still 8.1
Noted your comment re ODIN, but I use Linux, Odin seems Win only.
Have successful rooted and installed Lineage on an old Note 3, but I didn't have to downgrade that!
Can you give me please, some guidance how I can return this wretched thing back to 7.1?
Actually, I am suspecting return is the wrong word as it may have come with 8.1 installed.
I'm a bit lost at this point.
Cheers
p
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