Related
This is a special version of TWRP to be able to decrypt Samsung STOCK ROM's.
Who wants this?
When you use Samsung stock ICS , a stock based ROM or sediROM
AND: When you have enabled full device encryption
AND: When you want to do a nandroid backup OR want to access your data from within TWRP
... then this TWRP version is for you! So maybe no one else then me needs this but as I thought it could be useful for others too I publish it here.
The reason having another TWRP version then the "mainstream" one is that the Team Win Recovery dev's had dropped support for the Samsung proprietary device encryption somewhen since v2.7.
Even TWRP v2.6 does not work without changes as well.
As I use sediROM as my daily driver and I like to have a valid nandroid backup I decided to build a version which can handle Samsung's device decryption.
In short:
I created a TWRP version which is the same then the one bubor made but it is able to decrypt any stock Samsung ICS ROM (or other stock based custom ROM's like sediROM).
Current state:
Please keep in mind that the keyboard within TWRP is not the most responsive one. That said please ensure that you do not press the characters too fast because that can result in "password failed". Type it slow and char by char and it should work absolutely fine.
Backup encrypted /data without entering decryption password ( = full Image of /data) - tested
Backup encrypted /data with entered decryption password - tested
Restore for both above methods - tested
Decrypt /data - tested
Decrypt /sdcard - tested
adb shell - tested
Mounting all available partitions - tested
Installing sediROM (v1.7) - tested (partially working)
--> IMPORTANT HINT: I highly recommend to decrypt within ANDROID before (re)installing another ROM! The reason is when you NOT decrypt (cancel) when starting up TWRP and then install a custom ROM it will make /sdcard inaccessible! If you want to REMOVE all your data and also everything on /sdcard you can also cancel the decryption password in TWRP and then install a custom ROM like sediROM but afterwards when booting up Android /sdcard gets formatted so if that is not what you want decrypt within Android first. This does affect the "modify mode" of sediROM, too - well not all parts of it but I do not want to get into detail. I cannot recommend it - decrypt before modify is the better option believe me. All this will be fixed in sediROM and a bug was already filed.
Using Modify Mode of sediROM (v1.7) after entered decryption password in TWRP - tested (partially working) - I cannot recommend it - decrypt before modify is the better option believe me. All this will be fixed in sediROM and a bug was already filed.
Encrypt a backup file - tested
Restoring an encrypted backup file - tested
Date & Time correct - UTC by default (need 1 successful boot and correct set time in Android) - tested
Known issues:
see available bug reports for this
Download
Go to the "Download" section above.
Installation
sediTWRP will be provided as IMG file and as ODIN package. So you need either "heimdall", "adb" or Odin to flash.
I MAY will provide that sometime as flashable zip, too.
Example for using adb:
boot up TWRP
adb push sediTWRP_v2.6.3.0_sT-v1.0.22-ICS.img /tmp/
adb shell "dd if=/tmp/sediTWRP_v2.6.3.0_sT-v1.0.22-ICS.img of=/dev/block/mmcblk0p8"
adb shell sync
adb reboot recovery
Sources
TWRP sources at Github
Device tree at Github
Thanks
Special thanks @bubor for the source device tree and his help in many questions.
.
XDA:DevDB Information
TWRP with Samsung decryption support, Tool/Utility for the Samsung Captivate Glide
Contributors
xdajog, bubor
Source Code: https://github.com/xdajog/bootable_recovery_twrp_i927
Version Information
Status: Stable
Current Stable Version: v3.0.23
Stable Release Date: 2015-02-10
Current Beta Version: v2.5.8
Beta Release Date: 2015-02-09
Created 2015-01-19
Last Updated 2016-08-17
Known issues & FAQ
Known issues & FAQ
Is it possible to decrypt Cyanogenmod, AOSP based ROM's?
Obviously not. As this TWRP version uses Samsung's crypto libraries this will not work (well you could give it a try but I think the chances are at 0,1% that it would work).
Why is this such an old version?
The reason why I use v2.7 is that I do not need to patch many code here. v2.8 need to be fully patched to get it work so I do not know if I will do it. Maybe...
So what is the exact differences to TWRP by bubor?
In short: They are technical identical but when compiled sediTWRP will use all CRYPTO Flags needed to support Samsung decryption. To get this fully work I patched TWRP code related to decryption and proprietary Samsung crypto libraries have been included.
In detail: Check out the sources at Github (see OP - section "Sources")
Are there any known bugs?
Check out the Bug reports here
.
Changelog
Changelog
Version naming convention is always:
Code:
sediTWRP [[U]sediTWRP-Version[/U]]-[Android version of the proprietary Samsung crypto libs]_v[TWRP-Version]
sediTWRP v3.0.23-ICS_v2.7.1.0
Please keep in mind that the keyboard within TWRP is not the most responsive one. That said please ensure that you do not press the characters too fast because that can result in "password failed". Type it slow and char by char and it should work absolutely fine.
I state this as the first stable version of sediTWRP because all main features are tested and working fine.
That means:
Backup encrypted /data without entering decryption password ( = full Image of /data) - tested
Backup encrypted /data with entered decryption password - tested
Restore for both above methods - tested
Decrypt /data - tested
Decrypt /sdcard - tested
adb shell - tested
Mounting all available partitions - tested
Installing sediROM (v1.7) - tested
--> IMPORTANT HINT: I highly recommend to decrypt within ANDROID before (re)installing another ROM! The reason is when you NOT decrypt (cancel) when starting up TWRP and then install a custom ROM it will make /sdcard inaccessible! If you want to REMOVE all your data and also everything on /sdcard you can also Cancel the decyption password in TWRP and then install a custom ROM like sediROM but afterwards when booting up Android /sdcard gets formatted so if that is not what you want decrypt within Android first. This does NOT affect the "modify mode" of sediROM - this will work when you decrypted within TWRP.
Using Modify Mode of sediROM (v1.7) after entered decryption password in TWRP - tested
Encrypt a backup file - tested
Restoring an encrypted backup file - tested
Date & Time correct - UTC by default (need 1 successful boot and correct set time in Android) - tested
Fixes:
fix(!): decryption of /sdcard was not possible.
The main reason/fix for this was that the code I taken from xdarklight is using aes-cbc-plain:sha1 as crypto parameters for the internal storage (/sdcard)! Well that is wrong. At least in the UCLJ3 Samsung crypto config /sdcard uses the same crypto parameters like for /data. Which means aes-cbc-essiv:sha256 ! I changed the parameter and it works like a charme now! Man that was driving me nuts..
Enhancements:
new: You can now fully decrypt ICS based Samsung stock ROMs with this version of TWRP!
Known issues:
see available bug reports for this
To download go to the "Download" section above.
Previous versions:
sediTWRP v2.5.8-ICS_v2.7.1.0
Fixes:
fix(!): Restore hadn't worked (see bug report)
This was fixed by using CM KK as compiling base (instead of ICS)
fix(!): sediROM installlation hadn't worked (see bug report)
This was fixed by using CM KK as compiling base (instead of ICS)
fix: naming convention (sediTWRP version first)
Known issues:
see available bug reports for this
Enhancements:
new: special recovery kernel compiled from source (sediKERNEL)
It's main purpose is to be as have as less footprint as possible to have more space for the initial ramdisk.
Check out the changeset @ github
To download go to the "Download" section above.
Version naming convention was:
Code:
sediTWRP [[U]sediTWRP-Version[/U]]-[Android Codename]_v[TWRP-Version]
sediTWRP v2.7.1.0_v2.0.11-ICS
same as sT-v1.0.22-ICS but based on TWRP 2.7.1.0
sediTWRP v2.6.3.0_v1.0.22-ICS
added Samsung's Crypto libraries so decrypting /data is possible
some font cosmetics
changed version string to give a meaningful idea for what this TWRP version is for
.
whats the diference of original TWRP by @bubor ?
whats exactly mean encryption & decription. i install, backup, and nandroid backup of my first rom fine. and no problem by v2.6 v2.7 2.8
why used this old version for develop?
----------------------------------------------------------------
please Make a recovery or odin flashable version after more stabler. ( i dont good feeling about adb & termnal Emulators Codes )
organic2 said:
whats the diference of original TWRP by @bubor ?
whats exactly mean encryption & decription. i install, backup, and nandroid backup of my first rom fine. and no problem by v2.6 v2.7 2.8
why used this old version for develop?
----------------------------------------------------------------
please Make a recovery or odin flashable version after more stabler. ( i dont good feeling about adb & termnal Emulators Codes )
Click to expand...
Click to collapse
Open system settings - Security - Device Encryption. This will encrypt your device. Once it is encrypted it will be not possible to backup with twrp anymore.
The reason why I use v2.6 is that I do not need to patch the code here. I currrently develop on v2.7 which will be released soon. V2.8 need to be fully patched to get it work so I do not know if I will do it. Maybe.
-----
Sent from my SGH-I927 using XDA Android mobile app
xdajog said:
Open system settings - Security - Device Encryption. This will encrypt your device. Once it is encrypted it will be not possible to backup with twrp anymore.
The reason why I use v2.6 is that I do not need to patch the code here. I currrently develop on v2.7 which will be released soon. V2.8 need to be fully patched to get it work so I do not know if I will do it. Maybe.
-----
Sent from my SGH-I927 using XDA Android mobile app
Click to expand...
Click to collapse
1)
ahaaa! understand
ok. we dont need the v2.7 & 2.8 . this 2.6 version enough for us. becuse the v2.6 in enough for installing ics & jb roms. dont need 2.7 for stock ics. dont worry. Take it easy. Forget that...
thanks for you work :good:
-------------------------------------------------------
2)
Im fully backup by cwm from my stock GB rom!
i restored it 2 or 3 times fine. and fully worked.
the android v2.3 isnt encrypted? only ics encrypted and cant backup?
organic2 said:
1)
ahaaa! understand
ok. we dont need the v2.7 & 2.8 . this 2.6 version enough for us. becuse the v2.6 in enough for installing ics & jb roms. dont need 2.7 for stock ics. dont worry. Take it easy. Forget that...
thanks for you work :good:
-------------------------------------------------------
2)
Im fully backup by cwm from my stock GB rom!
i restored it 2 or 3 times fine. and fully worked.
the android v2.3 isnt encrypted? only ics encrypted and cant backup?
Click to expand...
Click to collapse
I do not know if 2.3 can be encrypted but even with ICS you need to enable it manually. In Lollipop encryption will be enabled by default but not in gingerbread or Ics.
-----
Sent from my SGH-I927 using XDA Android mobile app
xdajog said:
I do not know if 2.3 can be encrypted but even with ICS you need to enable it manually. In Lollipop encryption will be enabled by default but not in gingerbread or Ics.
-----
Sent from my SGH-I927 using XDA Android mobile app
Click to expand...
Click to collapse
Im Sure. We can backup from GB by CWM normally
You can test it in ICS
Perhaps working too
organic2 said:
Im Sure. We can backup from GB by CWM normally
You can test it in ICS
Perhaps working too
Click to expand...
Click to collapse
You mean encrypted(!) GB? Afaik CWM has no support for encrypted devices. Maybe CWM will simply dump
-----
Sent from my SGH-I927 using XDA Android mobile app
xdajog said:
You mean encrypted(!) GB? Afaik CWM has no support for encrypted devices. Maybe CWM will simply dump
-----
Sent from my SGH-I927 using XDA Android mobile app
Click to expand...
Click to collapse
No no. Fully nandroid backup from my first orginal GB by cwm. And restore anf use it 3 times
organic2 said:
No no. Fully nandroid backup from my first orginal GB by cwm. And restore anf use it 3 times
Click to expand...
Click to collapse
You dont use encypt. Yes, you can backup GB, but you CAN NOT backup encypred GB.
Actually You can backup any encypted partition by dump raw data.
Nobody cares when I removed encrypt support from my twrp builds.
bubor said:
Nobody cares when I removed encrypt support from my twrp builds.
Click to expand...
Click to collapse
well yes until now..
in the meanwhile:
sediTWRP v2.0 has been arrived (check out download section above).
-> based on TWRP v2.7.1 instead of 2.6.3
Decrypting /sdcard is still not possible yet.
I decided instead of merging to TWRP v2.8 the decryption of /sdcard will be my next focus now.
Greetings.
What is exactly difrence of "backup by any encypted data" and "normaly full backup" ?
I used the normall mode and i dont have any problem
Whats difrence of my nandroid backup and your nanroid backup by default original twrp recovery
organic2 said:
What is exactly difrence of "backup by any encypted data" and "normaly full backup" ?
I used the normall mode and i dont have any problem
Whats difrence of my nandroid backup and your nanroid backup by default original twrp recovery
Click to expand...
Click to collapse
You dont encypt, you dont need it. Simple that is.
bubor said:
You dont encypt, you dont need it. Simple that is.
Click to expand...
Click to collapse
It is as @bubor said.
Please take a look again at the OP - especially the section "Who wants this?"
I think (I hoped) it states absolutely clear who need this twrp version and who not..
ok ok
@bubor & @xdajog
ahaa!
ok ok i got it now fully understand your mean
yes absolutly. my roms isnt encrypted. and my nandroid backups is just normaly and not encrypted. becous its disable by default
:good:.
sediTWRP v2.5.8-ICS_v2.7.1.0 released today! (I switched from TESTING to BETA state from now on!)
It is highly recommended to upgrade to this version if you had installed a previous version of sediTWRP!
Fixes:
fix(!): Restore hadn't worked (see bug report)
This was fixed by using CM KK as compiling base (instead of ICS)
fix(!): sediROM installlation hadn't worked (see bug report)
This was fixed by using CM KK as compiling base (instead of ICS)
fix: naming convention (sediTWRP version first)
Known issues:
see available bug reports for this
Enhancements:
new: special recovery kernel compiled from source (sediKERNEL)
It's main purpose is to be as have as less footprint as possible to have more space for the initial ramdisk.
Check out the changeset @ github
To download go to the "Download" section above.
OMG! I can't believe it ... but I got it!
The first fully working version of sediTWRP released ! :victory: :highfive:
Have fun! :laugh: :victory:
sediTWRP v3.0.23-ICS_v2.7.1.0
Please keep in mind that the keyboard within TWRP is not the most responsive one. That said please ensure that you do not press the characters too fast because that can result in "password failed". Type it slow and char by char and it should work absolutely fine.
I state this as the first stable version of sediTWRP because all main features are tested and working fine.
That means:
Backup encrypted /data without entering decryption password ( = full Image of /data) - tested
Backup encrypted /data with entered decryption password - tested
Restore for both above methods - tested
Decrypt /data - tested
Decrypt /sdcard - tested
adb shell - tested
Mounting all available partitions - tested
Installing sediROM (v1.7) - tested
--> IMPORTANT HINT: I highly recommend to decrypt within ANDROID before (re)installing another ROM! The reason is when you NOT decrypt (cancel) when starting up TWRP and then install a custom ROM it will make /sdcard inaccessible! If you want to REMOVE all your data and also everything on /sdcard you can also Cancel the decyption password in TWRP and then install a custom ROM like sediROM but afterwards when booting up Android /sdcard gets formatted so if that is not what you want decrypt within Android first. This does NOT affect the "modify mode" of sediROM - this will work when you decrypted within TWRP.
Using Modify Mode of sediROM (v1.7) after entered decryption password in TWRP - tested
Encrypt a backup file - tested
Restoring an encrypted backup file - tested
Date & Time correct - UTC by default (need 1 successful boot and correct set time in Android) - tested
Fixes:
fix(!): decryption of /sdcard was not possible.
The main reason/fix for this was that the code I taken from xdarklight is using aes-cbc-plain:sha1 as crypto parameters for the internal storage (/sdcard)! Well that is wrong. At least in the UCLJ3 Samsung crypto config /sdcard uses the same crypto parameters like for /data. Which means aes-cbc-essiv:sha256 ! I changed the parameter and it works like a charme now! Man that was driving me nuts..
Enhancements:
new: You can now fully decrypt ICS based Samsung stock ROMs with this version of TWRP!
Known issues:
see available bug reports for this
To download go to the "Download" section above.
@xdajog
thank you i like see you are happy
but, with twrp 2.7 we cant install cm11. inst it?
we need twrp 2.8+ to can install all roms
This is a CyanogenMod 12.1 ROM for the Exynos3470 based Samsung Galaxy S5 mini (G800F/G800M/G800Y). Support for G800M is untested so far.
DO NOT USE IT FOR G800H 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.
Working features
Receiving and making calls
Hardware sensors (Light, Orientation, Compass, Proximity, Acceleration)
Audio
Bluetooth (audio in HFP seems to be distorted with at least some headset devices)
Wifi
HW accelerated GUI
USB-OTG (Keyboard, Mouse, USB-Audio, Mass-Storage)
Camera (pictures+video: Back+Front)
MTP storage
IR
GPS
NFC
Non-working features:
Fingerprint scanner (no app for tests found)
Pulse sensor + Step counter (no app for tests found)
Hall sensor
SELinux
Known issues:
See the Bug Report section of this thread
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)
Some users reported that their touch-screen stopped working permanently after some weeks of usage. For some user's (two at the moment including me) NFC stopped working permanently. Probably this issues are not related to this ROM as also many stock user's complain about hardware issues (random reboots, black screens, unresponsive touchscreen) but you have been warned.
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.
Download:
Odin3-v3.07 (it is contained in CF-Auto-Root)
TWRP 2.8.7.0 recovery image [08/07/2015] (AndroidFileHost Mirror)
CM 12.1 ROM for G800F/M/Y (AndroidFileHost Mirror)
Google Apps (contains Google Play, ...) for Android 5.1.1 from Jajb (Recommended) or the one that suits you best from Consolidated GApps.
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 (see above). Otherwise TWRP might not be able to flash the ROM. This is because TWRP checks now if the device is "supported".
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 CM 12.1.
Flash CyanogenMod:
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 CyanogenMod 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 CM 12.1 ROM zip-package
Install the GApps zip-package
Reboot the system and enjoy a Lollipop
How to root:
No SuperSu is needed as CyanogenMod 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:
15/08/2015:
* Synchronize with newest CM 12.1 sources (contains stagefright patches)
08/07/2015:
* Update to latest CM-12.1 sources (LMY48G)
* Camera app supports saving pictures to external SD-cards
* Partition sizes of system and data slightly reduced to avoid "unable to mount /system" failure during installation on some variants of the G800 (e.g. G800Y)
19/05/2015:
* Update to CyanogenMod 12.1 (Android 5.1.1)
* Merged Kernel-sources from G800FXXU1ANL1
* Re-enabled NFC
* TWRP update
11/04/2015:
* Update to CyanogenMod 12.1 (Android 5.1)
* Update to TWRP 2.8.6.0
* Fixed blinking capacitive touchkey lights
* Fixed unresponsive touchscreen on wake-up
* Added support for Automatic Brightness control
* Added advanced touchscreen settings (Glove and Hovering mode)
* Use open-source Light-HAL, Power-HAL and IR-HAL implementations
* Updated Power-Profiling
23/03/2015:
* Fixed non-working mic on incoming call issue
* Fixed non-working menu-button
* Synchronized with latest CyanogenMod sources
This section is for developers:
A README file with build instructions can be found here:
Code:
https://github.com/cm-3470/patcher_kminilte
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
Developers welcome
At the moment the G800F/M/Y specific port of this ROM is only done by one person (hennymcc). Although Unjustified Dev also works on this ROM he does not own an Galaxy S5 Mini but a Galaxy Light which has a similar base but is different when it comes to camera, nfc and other components (maybe even slightly when it comes to audio and radio).
Help from other developers is always welcome. See the bug/feature section and this thread to see what is missing. Just give some short info (here in this thread or PM) that you want to work on some issue or feature so that work can be synchronized. Maybe there are also other devs that want to work with you on the same issue.
Knowledge in how the kernel works and good programming skills in C, C++ and Java would be nice but not necessary for all problems. At least you should be able to build the ROM and test your changes yourself but you do not need experience in porting ROMs.
Thanks to Unjustified Dev from Team Regular. As the S5 mini (G800F/M/Y) and the Galaxy Light are quite similar we worked on this together.
XDA:DevDB Information
[G800F/M/Y][ROM][5.1.1][LMY48G] CyanogenMod 12.1 for G800F/M/Y [Alpha 15/08/2015], ROM for the Samsung Galaxy S5 Mini
Contributors
hennymcc, Unjustified Dev
Source Code: https://github.com/cm-3470
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.4.x
ROM Firmware Required: TWRP Recovery [version from 15/08/2015]
Based On: CyanogenMod
Version Information
Status: Alpha
Created 2015-04-15
Last Updated 2015-09-22
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.
Reserved
As none of the pre-alpha testers reported any issues with NFC, I assume that the broken NFC of LS97 and me was caused by electrostatic discharge while removing and re-inserting the battery (at least I did this hundreds of times). In addition we already broke our NFC some weeks ago after having used 5.0.2 for some while, so this ROM should be at least as safe as 5.0.2 and there is no direct link between the custom ROM and the broken NFC.
Just as a precaution: to avoid damage of the NFC-chip (which is connected to the antenna in the battery) by electrostatic discharge, use the power button to reboot the smartphone instead of removing the battery.
What a nice first post for this new ROM
Are the links above the same like the ones you posted into the comments in your 5.0.2 thread? Just so i know if something has changed in thos links obove.
CTXz said:
Are the links above the same like the ones you posted into the comments in your 5.0.2 thread? Just so i know if something has changed in thos links obove.
Click to expand...
Click to collapse
Exactly the same.
hennymcc said:
Exactly the same.
Click to expand...
Click to collapse
Ok thanks. Also have you figured out whats up with the screen turning on after locking delay since turning off nfc didn't result changes. Also it doesn't happen always. Only sometimes
CTXz said:
Ok thanks. Also have you figured out whats up with the screen turning on after locking delay since turning off nfc didn't result changes. Also it doesn't happen always. Only sometimes
Click to expand...
Click to collapse
I haven't looked any deeper into this so far.
So how is the Final version going to look like if this is Alpha... Damn [emoji41]
I have a small problem, everytime i touch the screen my capacitive buttons light up. I already tried disabling this in the settings but it doesn't let me do that.
Anyone have soms advice ?
Nielsieboy said:
I have a small problem, everytime i touch the screen my capacitive buttons light up. I already tried disabling this in the settings but it doesn't let me do that.
Anyone have soms advice ?
Click to expand...
Click to collapse
Hey. What i did is just rather turn them off completely.
Settings > Buttons > Backlight > Uncheck Illuminate buttons
Else there is no fix, due cm12.1 universality it doesn't work with the buttons like the stock ROM did.
CTXz said:
Hey. What i did is just rather turn them off completely.
Settings > Buttons > Backlight > Uncheck Illuminate buttons
Else there is no fix, due cm12.1 universality it doesn't work with the buttons like the stock ROM did.
Click to expand...
Click to collapse
Well tried that but The setting just changes back to the default.
Nielsieboy said:
Well tried that but The setting just changes back to the default.
Click to expand...
Click to collapse
Ok thats wierd. Have you wiped all partitions you needed to like said above ( dalvik cache, cache, system, data )
If it gets verry anoying you might give a reflash a try. Also i know this sounds funny but did you atleast try rebooting the device?
---------- Post added at 08:55 PM ---------- Previous post was at 08:50 PM ----------
Also did you give this a shot https://play.google.com/store/apps/details?id=com.deskangel.kblight
There are many more apps on gplay for button backlight. Just search it
i've flashed it yesterday over the old buidl (without full wipe). so i got FC's on several google apps.
after flashing several different gapps for lolipop 5.1 the errors with the FCs are still stere.
then i've made a full clean install with full wipe and installed the pa gapps from the 04-10-2015 and now everything works fine & smooth.
tommorrow ill gonna test the bluetooth cause on the old build there were sond errors....
but for now it looks very good
I've discovered something. If you enable LiveDisplay the device will lag a bit.
And when you think I did a full wipe and reflashed the ROM, just to find out that my problem was related to this little feature...
@henny: can you confirm that this mod will work on your build ?
It sounds very good
Nielsieboy said:
I have a small problem, everytime i touch the screen my capacitive buttons light up. I already tried disabling this in the settings but it doesn't let me do that.
Anyone have soms advice ?
Click to expand...
Click to collapse
it doesnt let you do that? why not? for me it worked...(i hate those lights too)
DerMoeJoe said:
@henny: can you confirm that this mod will work on your build ?
It sounds very good
Click to expand...
Click to collapse
I personally don't see a lot of advantages in it and would not recommend it, especially for this phone, regardless of whether or not it's compatible.
LS97 said:
I personally don't see a lot of advantages in it and would not recommend it, especially for this phone, regardless of whether or not it's compatible.
Click to expand...
Click to collapse
Why not. I use it for daily use and i have to say i have less bugs than my stock rom had.
With that it boosted my phone like hell and there is no more lagg when oppening apps, going to the homescreen, scrolling through apps and no more touchwiz. Plus you got the newest android up to date. That fixed some app issues with my phone ( i no longer got the app not compatible error after lolipop. Oh yeah and no more bubble sounds when pressing on something Thaankk you! There are many other things that i preffer over the stock rom. So i see so much potential in this ROM and would preffer it as much as i can if you got a s5 mini g800f.
CTXz said:
Why not. I use it for daily use and i have to say i have less bugs than my stock rom had.
With that it boosted my phone like hell and there is no more lagg when oppening apps, going to the homescreen, scrolling through apps and no more touchwiz. Plus you got the newest android up to date. That fixed some app issues with my phone ( i no longer got the app not compatible error after lolipop. Oh yeah and no more bubble sounds when pressing on something Thaankk you! There are many other things that i preffer over the stock rom. So i see so much potential in this ROM and would preffer it as much as i can if you got a s5 mini g800f.
Click to expand...
Click to collapse
The only way to find out if it works is to try it. So if you want this feature you can flash that mod and report if it works .
I personally do not need it as I want the phone to turn off when I "power it off".
Note that the mod could cause stability issues. So before reporting bugs here you should reinstall CM 12.1 first with a full wipe and check if the problem is still present.
Edit:
this was supposed to be an answer to DerMoeJoe's question about the QuickBoot mod
This is a LineageOS 14.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
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.
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.
Working features
HW accelerated GUI
Camera (pictures+video: Back+Front) (switching between camera and video-recording might crash the camera-app)
MTP storage
Flash Light
Bluetooth (A2DP, HFP, HID)
IR
Sound
SMS
Initiate and receive calls
Wifi
Mobile Data
USB-OTG (Keyboard, Mouse, USB-Audio, Mass-Storage)
NFC
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)
SD-Card as internal storage (new Android M feature)
GPS
Fingerprint scanner
SELinux
Non-working features:
Known issues:
Camera crashes when switching from camera to video. Use Google camera or Open camera to solve camera issues.
See the Bug Report section of this thread.
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)
Some users reported that their touch-screen stopped working permanently after some weeks of usage. For some user's (two at the moment including me) NFC stopped working permanently. Probably this issues are not related to this ROM as also many stock user's complain about hardware issues (random reboots, black screens, unresponsive touchscreen) but you have been warned.
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.
Download:
Odin3-v3.07 (it is contained in CF-Auto-Root)
TWRP 3.0.0 recovery image [25/03/2016] (AndroidFileHost Mirror)
LineageOS 14.1 ROM for G800F/M/Y
Latest build by hennymcc: Android File Host
There might be a more up-to-date (OTA enabled) build by ayke: https://aykevl.nl/android
There are monthly builds and recent bootloaders and modems by Panzerknakker: https://androidfilehost.com/?w=files&flid=201249
Google Apps (contains Google Play, ...) for Android 7.1. The following is recommended:
Open GApps Project, Platform:ARM, Android:7.1, Variant: whatever you prefer (e.g. "mini" or "nano")
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, power of your device, wait a few seconds and 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.
Before you flash:
You need the latest TWRP recovery (see above). Otherwise TWRP might not be able to flash the ROM. This is because TWRP checks now if the device is "supported".
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 CM 14.1.
Flash ROM:
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 the ROM 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 CM 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:
Changelog:
19/08/2017:
* SELinux policy update
* Update to newest LineageOS sources
02/06/2017:
* Firefox crash&reboot fixed (thanks to Spookcity)
* Enabling the fingerprint reader does not cause bootloops anymore (thanks to Spookcity)
* Ambient display option added (disabled by default)
28/05/2017:
* [COLOR="red"]Note: ROM is stuck in bootloop when fingerprint reader is enabled. ROM removed.[/COLOR]
* Enabled selinux (thanks to mirhciulica for fixing all those selinux denials). If you encounter problems check for "avc: denied" messages in logcat (see: https://source.android.com/security/selinux/validate)
* Fixed Snapchat and SafetyNet problems (Snapchat reported server errors, Safetynet Helper reported a 1970 timestamp): Kernel patch was necessary.
* Updated kernel to 3.4.107
* Applied most of the patches from [URL="https://android.googlesource.com/kernel/common/+/deprecated/android-3.4"]kernel/common/deprecated/android-3.4[/URL]
* Updated LineageOS sources
* FlipFlap added to support smart flip covers: shows a screen with the current time in the window of the smart cover. Note that this relies on the magnetic sensor at the bottom of the phone. So magnets near the sensor can trigger this behavior too.
* Replaced the buggy Gello webbrowser with Jelly - the new LineageOS default browser
* Replaced the buggy Snap camera with the LineageOS default camera app
* Replaced the Samsung battery charger app (lpm) with healthd (looks uglier but at least works with selinux)
20/02/2017:
* Fixed Youtube scaling issue on window resizing
* Compass fixed (thanks to mirhciulica for figuring out what's wrong)
* cpufreq config added
* Charge mode fixed (starts when plugging USB into a powered-off phone)
* USB-Tethering and Wifi SoftAP (Hotspot) fixed
* Camera doesn't crash when switching between camera and video (but might still crash sometimes)
* Fingerprint libs reverted from MM to LP (maybe that fixes the fingerprint issues - please test)
01/02/2017:
* conversion to LineageOS
* updated some libs with stock MM versions
* fixed robotic voice problem
* fixed silence on first call
07/11/2016:
* Initial test build
This section is for developers:
A README file with build instructions can be found here:
Code:
https://github.com/cm-3470/android_device_samsung_kminilte
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
Developers welcome
At the moment the G800F/M/Y specific port of this ROM is only done by two persons (CTXz and hennymcc). Although Unjustified Dev also works on this ROM he does not own an Galaxy S5 Mini but a Galaxy Light which has a similar base but is different when it comes to camera, nfc and other components (maybe even slightly when it comes to audio and radio).
Help from other developers is always welcome. See the bug/feature section and this thread to see what is missing. Just give some short info (here in this thread or PM) that you want to work on some issue or feature so that work can be synchronized. Maybe there are also other devs that want to work with you on the same issue.
Knowledge in how the kernel works and good programming skills in C, C++ and Java would be nice but not necessary for all problems. At least you should be able to build the ROM and test your changes yourself but you do not need experience in porting ROMs.
Thanks to CTXz, Psyafter, spookcity138, ayke and mirhciulica for working on this ROM.
XDA:DevDB Information
[G800F/M/Y][ROM][7.1][NJH47F] LineageOS 14.1 for G800F/M/Y [Beta 19/08/2017], ROM for the Samsung Galaxy S5 Mini
Contributors
hennymcc, Panzerknakker, spookcity138, psyafter, ayke
Source Code: https://github.com/cm-3470
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.4.x
ROM Firmware Required: TWRP Recovery [version >= 15/08/2015]
Based On: LineageOS
Version Information
Status: Beta
Created 2017-02-01
Last Updated 2018-08-18
CostasGr said:
henny, what is ur baseband at the moment?
Click to expand...
Click to collapse
My baseband is G800FOJV1CPK1 at the moment.
Thx!!!
Fingerprint sometimes does not works: No response from the sensor. :crying:
hennymcc said:
My baseband is G800FOJV1CPK1 at the moment.
Click to expand...
Click to collapse
So Marroco Baseband is working in Germany?
Cool .... So ... Stock 6.0.1(Marroco Baseband) will also work in Germany, right?
?
Everything's working perfect right now besides the fingerprint sensor sometimes not getting any input and the "Cast" option for streaming on Smart TV's is broken as well ("Unfortunately, Settings stopped working", when connecting). YouTube still has this weird resizing problem on >=360p...
Thanks anyway for providing free software with regular updates!
EDIT: Are OTA-Updates active in this build or do we have to install them via TWRP-flash?
installing the root didnt work
edit: oh does seem to work, although TWRP says installation failed
edit2: although app says i have no root
wogooo said:
installing the root didnt work
Click to expand...
Click to collapse
Whats your error? What zip flashed? For me it worked at the first time
The problem with the videos is almost solved, it seems a bit slow and it is necessary to play the video, go to the menu and go back
---------- Post added at 09:01 PM ---------- Previous post was at 08:59 PM ----------
Mystixor said:
Everything's working perfect right now besides the fingerprint sensor sometimes not getting any input and the "Cast" option for streaming on Smart TV's is broken as well ("Unfortunately, Settings stopped working", when connecting). YouTube still has this weird resizing problem on >=360p...
Thanks anyway for providing free software with regular updates!
Click to expand...
Click to collapse
If you put the video to 720 and press the home button and you return, the bug disappears for a moment and you can see it normally, once time per video
PS: I use the google translator, I do not speak English
Mrdream94 said:
Whats your error? What zip flashed? For me it worked at the first time
Click to expand...
Click to collapse
You have to download addonsu-arm-signed.zip for 14.1 from the Lineageos Extras download page and install it with TWRP.
Error 7.
operation not supported on transport endpoint
set metadata: some changes failed
Try this zip. For me is working 100%
thanks for the work,great rom, everthing smooth, rooting worked with SR3-SuperSU-v2.79-SR3-20170114223742.zip (can't link it i am new )
only problem for me is the tethering. wifi tethering gives me an error, usb/bluetooth tethering is working but then there is no internet access with my laptop
@hennymcc I saw message here about wierd YouTube video resizing. In galaxy note 3 exynos development section there was same problem in Laos 14.1 ROM and op of that thread fixed it. His name is tincho5588.
Could you look into the Snapchat bug? When loging in it shows: Connection failed.
It only does that on CM14.1 and LineageOS14.
I Tried to log in on my tablet and backup/ restore the APP, didnt work.
Edit: tried everything availible on the Internet. Snapchat wont work
derhunt said:
thanks for the work,great rom, everthing smooth, rooting worked with SR3-SuperSU-v2.79-SR3-20170114223742.zip (can't link it i am new )
only problem for me is the tethering. wifi tethering gives me an error, usb/bluetooth tethering is working but then there is no internet access with my laptop
Click to expand...
Click to collapse
I'm loving my first taste of nougat - the rom is super smooth for me.
Unfortunately I also have a problem with the wifi hotspot. It starts to open the hotspot but a second later says 'error'.
Sent from my SM-G800Y using XDA-Developers Legacy app
Mrdream94 said:
Try this zip. For me is working 100%
Click to expand...
Click to collapse
worked! thx!!
information
anyone has noticed some problems with the battery life?
Ala1101 said:
anyone has noticed some problems with the battery life?
Click to expand...
Click to collapse
Yes, in my case it was the cell phone standby. I had it set to LTE. After switching to 3G battery live is much better because cell phone's energy consumption gets much much lower
Gesendet von meinem SM-G800F mit Tapatalk
No Root Access
There is no option for app root access, only for ADB
Ala1101 said:
anyone has noticed some problems with the battery life?
Click to expand...
Click to collapse
yesterday i've installed lineage, today I had huge battery-drain with 35% Media-Server, now I think it's better
Hello . twrp only for realme Q stable
Link download : <Mod edit>
Link vbmeta support root , rom mod : <Mod edit>
Changelog
Modify the optimization project:
* Delete redundant languages, keep English, add Chinese language, default Chinese.
* Modify the default configuration, for example, the default time zone is East Eight Zone, default screen brightness, default vibration, default 24 hours, default return button on the right, default Chinese and so on.
* Modify the default configuration file path to reduce the possibility of conflicts with other people's compiled versions.
* Adjust and optimize the Chinese text and description, and re-edit all the items one by one to make it more accurate, understandable and humanized. Also added display mtp enable off display, file operation result display, operation page title display, permission description when modifying permissions, etc. UI text display.
* Modify the unlocking interface and adjust the height of the sliding unlocking bar, which can effectively prevent misoperation (the original unlocking bar and the operating unlocking bar are of the same height. When the unlocking is completed, the sliding may be repeated, and the corresponding action is directly operated).
* Open more partition backup and restore, such as modern baseband partition, bootloader, persist, cust and other partitions, easy to backup the underlying files before brushing, can restore the underlying files after brushing.
* Add .bin and .mbn format image files, so you don't need a zip brush package, you can write the underlying file. The original version only supports the brushing of .img format image files. (Be sure to pay attention to the right partition!!!!)
* Solve the problem of interface jam when using the simulation operation (the simulation operation is mainly for testing the theme, and no actual operation).
* Add the manual installation root function in Advanced Options > root system. Add a display root system option on this basis for manual operation.
* Added the ability to unenforce encryption, in advanced options > Unforce Encryption. You can remove the official system to force encryption and cancel the check.
* Change the built-in root mode and add magisk as the default root mode.
* Fixed button and button operations for some interfaces.
* The adb/usb debug mode is enabled by default, which is convenient for operating the phone through the computer command line in rec mode.
* MTP is enabled by default. In the rec state, you can also connect your phone to your computer to facilitate file copying.
* Modify the logo interface, modify the main interface page header, and add the display phone model and team name, author name.
* Fix some logical relationships and modify some interface displays.
* Added clear root function
* Added clear power-on password function
* Added ability to clear battery information
* Increase signature boot function
* Restore official rec function, need official boot and system system to operate successfully
* Increase the option of restarting after the automatic upgrade is completed. In the twrp setting, the default is automatic restart. If you uncheck the box, you can either not restart, and it is convenient to perform some operations after the automatic upgrade to prevent twrp from being overwritten.
* Increased avb2.0 verification function
important:
1. This rec supports data partition automatic decryption, encrypted data can be used normally under rec without formatting.
Please do not arbitrarily brush into the recue of unknown origin, it is likely that the data data can not be decrypted, and the data is completely lost.
The official default is to lock the password to encrypt the data. To enter twrp, you need to enter the lock screen password.
2. This rec supports the official original full-size ozip card brush package.
3. You must unlock the bootloader to brush the third-party rec. Please unlock the BL.
4. Built-in root system / remove root function, through the root system, can not only remove dm check, but also enable the system to obtain root privileges.
5. Built-in remove dm checksum and cancel the forced encryption function. Through certain operations, you can remove the official data forced encryption (the person who knows how to operate naturally).
6. Prevent the functions covered by the official rec (any one can be): root system, signature boot, remove dm check, cancel forced encryption, etc.
7. After the card is officially packaged, it is recommended to turn off the avb2.0 check, otherwise it may cause the boot prompt system damage due to root! ! !
8. If the boot prompt system is damaged due to root, etc., you can use the fastboot line to brush boot.img or brush the verification vbmeta to restore normal! ! !
Sounds good. Will I be able to flash lineage os, opengapps pico and latest magisk with this recovery? I don't want anything else complex.
---------- Post added at 06:13 ---------- Previous post was at 05:59 ----------
Says failed to mount /system_root (invalid agument) error: 7 while trying to flash anything from it.
Rom LG16 support only realme 5pro india...realme Q from china no support
29y6145 said:
Rom LG16 support only realme 5pro india...realme Q from china no support
Click to expand...
Click to collapse
Then why the hell is realme q in the title?
Btw after 10 minutes of showing decrypting ozip file I got an error, invalid argument.
29y6145 said:
Rom LG16 support only realme 5pro india...realme Q from china no support
Click to expand...
Click to collapse
what is the codename for Rm5P india? is it same like global (RMX1971EX)?
rah_asia said:
what is the codename for Rm5P india? is it same like global (RMX1971EX)?
Click to expand...
Click to collapse
Yes.
Contacted developer of this Chinese twrp and even he himself said that we shouldn't try to flash custom rom, magisk.zip or gapps package with it for it can't really flash anything else but stock rom and inbuilt magisk 20.0 that is embedded in twrp itself. So aside from rooting color os or installing stock rom in case of hard brick this twrp pretty much useless for custom rom development, testing, flashing or migrating.
greenys' said:
Contacted developer of this Chinese twrp and even he himself said that we shouldn't try to flash custom rom, magisk.zip or gapps package with it for it can't really flash anything else but stock rom and inbuilt magisk 20.0 that is embedded in twrp itself. So aside from rooting color os or installing stock rom in case of hard brick this twrp pretty much useless for custom rom development, testing, flashing or migrating.
Click to expand...
Click to collapse
So, is problem so difficult to overcome that developers can't build proper twrp?
555frost555 said:
So, is problem so difficult to overcome that developers can't build proper twrp?
Click to expand...
Click to collapse
No. The developers are just lazy and most of time they're not in the mood for it for they mostly own RM5P instead of RMQ. However, @thesprintster compiled a theoretically working twrp for our RMQ devices. We're waiting for him to release so we could test it. On the other hand seemingly even roms need a few lines of change so they'll work on Realme Q. It's a huge pain in the ass but it seems RM5P roms won't work on RMQ even with proper recovery these roms need to be changed, recompiled ?* So yeah. This sucks.
greenys' said:
No. The developers are just lazy and most of time they're not in the mood for it for they mostly own RM5P instead of RMQ. However, @thesprintster compiled a theoretically working twrp for our RMQ devices. We're waiting for him to release so we could test it. On the other hand seemingly even roms need a few lines of change so they'll work on Realme Q. It's a huge pain in the ass but it seems RM5P roms won't work on RMQ even with proper recovery these roms need to be changed, recompiled ?* So yeah. This sucks.
Click to expand...
Click to collapse
God, damn it!
Not for nothing that I bought RM5P
"...even roms need a few lines of change..." - it means that there are differences between RM5P and RMQ. What are they like?
555frost555 said:
God, damn it!
Not for nothing that I bought RM5P
"...even roms need a few lines of change..." - it means that there are differences between RM5P and RMQ. What are they like?
Click to expand...
Click to collapse
Dunno. I've never successfully compiled a working
... thing in the past 10 years even though I followed step by step tutorials so I gave up on compiling Android stuff. All I can do is to bug devs to do the work instead of me but I can do that relentlessly thus it bears fruit more or less often. Ask thesprintster about it. I'm bugging him to make that flashable lineage os soon and after that I'm done for good.
THREAD CLOSED!
@29y6145 Please consult the inbox of your private messages.
WARNING: English isn't my primary language. Sorry for any misunderstanding.
So I've heard of people that wanted to try Ubuntu on their phones(one of them being me). However as of now there isn't a helpful guide for installing it. I'm fixing that.
What works:
-Screen(has some harmless graphical glitches though)
- Mobile data
- Wifi
- Calls
- Camera
- SD card
- You tell me
What doesn't work:
- Messages
- VoLTE
- Wifi Calling
- You tell me
Prerequisites:
- An Android 9.0 Custom ROM that doesn't use the stock /vendor(this one worked great for me, but if you are free to use another one)
- Halium kernel(I'll attach a TWRP script below). You can also try this build by erfanoabdi, however I haven't tested how it works.
- halium-ramdisk
- apparmor-enabler
- GSI Ubports script
- TWRP/OpenFox
1. Wipe data and internal storage(if you're on stock, do it on the Settings app. Otherwise, just do it however you want to as long as it disables the encryption). You shouldn't actually need to do this, since Ubuntu Touch resides only in system partition.
2. Install whatever custom ROM you chose. You don't need to boot it, just reboot to bootloader once you finish installing it. If you do boot into it though you'll need to repeat Step 1.
3. Wipe System(you shouldn't need to but it never hurts )
4. Flash the Halium kernel along with halium-ramdisk.zip and apparmor_enabler.zip.
5. Flash the GSI script.
6. Reboot.
Hopefully you'll boot into Ubuntu after that.
Kernel source used for the kernel in the .zip below
Thanks to:
- Erfanoabdi from Github(idk if he has an XDA account). He's the one that did all the heavy lifting for me.
- The guys at the Halium Telegram.
ultracoolguy said:
WARNING: English isn't my primary language. Sorry for any misunderstanding.
So I've heard of people that wanted to try Ubuntu on their phones(one of them being me). However as of now there isn't a helpful guide for installing it. I'm fixing that.
What works:
- Mobile data
- Wifi
- Calls
- Camera
- SD card
- You tell me
What doesn't work:
- Messages
- VoLTE
- Wifi Calling
- You tell me
Prerequisites:
- An Android 9.0 Custom ROM that doesn't use the stock /vendor(this one worked great for me, but if you are free to use another one)
- Halium kernel(I'll attach a TWRP script below). You can also try this build by erfanoabdi, however I haven't tested how it works.
- halium-ramdisk
- apparmor-enabler
- GSI Ubports script
- TWRP/OpenFox
1. Wipe data and internal storage(if you're on stock, do it on the Settings app. Otherwise, just do it however you want to as long as it disables the encryption).
2. Install whatever custom ROM you chose. You don't need to boot it, just reboot to bootloader once you finish installing it. If you do boot into it though you'll need to repeat Step 1.
3. Wipe System(you shouldn't need to but it never hurts )
4. Flash the Halium kernel along with halium-ramdisk.zip and apparmor_enabler.zip.
5. Flash the GSI script.
6. Reboot.
Hopefully you'll boot into Ubuntu after that.
Kernel source used for the kernel in the .zip below
Thanks to:
- Erfanoabdi from Github(idk if he has an XDA account). He's the one that did all the heavy lifting for me.
- The guys at the Halium Telegram.
Click to expand...
Click to collapse
Thanks a lot for this, installed on my Ocean and it boots, but asks for password. Whats the password.
thanks
Update: password is phablet
Base: Lineage OS by dark98
1, Swipe from right to left (edge drag right to left) to task manager very temperamental
2, removing lockscreen crashes
3, Swipe off (closing opened apps) temperamental) requires holding on the app for like 3 seconds before dragging off to close.
essojay said:
Thanks a lot for this, installed on my Ocean and it boots, but asks for password. Whats the password.
thanks
Update: password is phablet
Base: Lineage OS by dark98
1, Swipe from right to left (edge drag right to left) to task manager very temperamental
2, removing lockscreen crashes
3, Swipe off (closing opened apps) temperamental) requires holding on the app for like 3 seconds before dragging off to close.
Click to expand...
Click to collapse
I can actually confirm all of these. Sadly I can't do much about them. It probably has to do with the GSI implementation itself.
ultracoolguy said:
I can actually confirm all of these. Sadly I can't do much about them. It probably has to do with the GSI implementation itself.
Click to expand...
Click to collapse
thanks for your work once more, Erfan confirm that much it has to do with GSI. Much respect to you guys.. Its a matter of time before this is sorted, thanks once more.
bR
Is there any workaround to get messages to work?
twfs said:
Is there any workaround to get messages to work?
Click to expand...
Click to collapse
Sorry for responding so late. I haven't used Ubuntu Touch in a while so I don't know of any. However, maybe messages work now idk.
none of the links are downloadable from
Hi! I've been trying to install it on my device for 4~5 days. Downloaded everything from https://mirrors.lolinet.com/ and it simply doesn't boot (stuck on unlock warning screen).
Is there any way you can help me?