Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*
*/
Hi,
here you can find my version for the Samsung Galaxy Note 2 LTE on LineageOS 20.
This is a alpha build, also from the LineageOS side, there are typical functions still missing, so don't install it if you want a completely stable and completed ROM and don't report my already listet bugs!
Attention:
Sometimes it needs another reboot to find the sim card.
When you have BitGapps installed, you have to reflash them after every update!
This ROM is only tested with N7105, so maybe you could to give me a feedback if it does or does not work with all the different Note 2 LTE variants.
It theoretically should work for:
SGH-I317
SGH-I317M
SCH-I605
SPH-L900
SGH-T889
SHV-E250S
SHV-E250K
SHV-E250L
SC-02E
GT-N7105/N7105T
SGH-T889V
SHV-E250S/E250K/E250L
SC-02E (SGH-N025)
Here you can see how far everything is working for now.
Spoiler: Whats working
Boot
Audio
Bluetooth
Graphics
Cameras
Sensors
Wifi
GPS
USB
Video playback (HW/SW)
Tethering via USB
RIL
OTA-Updates
Tethering via WIFI and Bluetooth
much more...
Spoiler: Whats not working
Random reboots
NFC
SD-Card can't be formatted as internal storage, this will cause a bootloop
Random losses of sim card
Spoiler: Links
TWRP
ROM direct link
ROM
ROM Mega
Spoiler: Changelog
26.01.2023
13.03.2023
Spoiler: How to improve GPS
You could use a gps.conf from https://app.box.com/s/w57s1v1n3hie7l5lk28i for your location and replace /vendor/etc/gps.conf.
Or you try GPS Server Optimizer app for a faster 3D fix.
For both methods you need root rights.
I would recommend to use microG instead of BitGapps,
here you can find the installation instructions:
Spoiler: microG instructions
Download Magisk 24.1 and flash it via TWRP (yes, flash the APK file), reboot
Open Magisk and update the App (and do a reboot if it's asking)
Enable Zygisk in Magisk
Download and install microG installer in the Magisk manager, reboot
Download and install safetynet-fix in the Magisk manager, reboot
Check with a safetynet checker app and you should pass
Spoiler: If you're facing installation problems.
Samsung seems to use differen't partition tables for these devices,
so far we know a t889, I317 and maybe other devices != n7105 are having a too small HIDDEN (for us vendor) partition.
So if you're facing problems like here
Getting "E2001: Failed to update vendor image." during clean flash.
This means that you have to resize it, check out these two posts:
Manual way
Zip way
Do you like my work?
Than you can simply hit the thanks button and consider to spend me a coffee or a beer,
I'm doing this in my free time and it also costs a lot of money to buy hardware.
donate
Wanna improve your sound configs, control your charging current and more?
Now you can use my app to access all boeffla configurations, there will follow more functions.
Exynos4 Kernel Manager - Apps on Google Play
This app provides Boeffla sound control and other kernel + charging tweaks
play.google.com
Spoiler: How to install it?
Instructions
XDA:DevDB Information
[ROM][13.x][N7105/T0LTE][BETA] LineageOS 20.x, ROM for the Samsung Galaxy Note 2 LTE
Contributors
html6405
Source Code: https://github.com/html6405
ROM OS Version: 13.x T
ROM Kernel: Linux 3.x
ROM Firmware Required: TWRP 3.5.2
Based On: LineageOS
Selinux: permissive, this only makes sense as soon the ROM is stable.
Version Information
Status: Beta
Created 2022-11-09
Last Updated 2023-03-13
Thank you for the your great work!!!I tried this ROM as soon as possible.My device is SC-02E. Here are a few things I found out.
・Magisk 25.2(Latest) is work
・The stylus pen does not work.
I found this reason. It seems that this ROM is for N7100 and not for N7105. until android 12, the model name is also N7105, but this ROM shows N7100.
・When connected to a PC, the USB cable must be disconnected and reinserted once after the USB setting is set to file sharing.
・Video can not save. Photos can be saved.
yonekome said:
・The stylus pen does not work.
I found this reason. It seems that this ROM is for N7100 and not for N7105. until android 12, the model name is also N7105, but this ROM shows N7100.
Click to expand...
Click to collapse
Stylus works fine on my n7105, hmm thats strange, this ROM is built for t0lte and there is no n7100 as model name in the init program, check here:
android_device_samsung_t0lte/init_t0lte.cpp at lineage-19.0 · html6405/android_device_samsung_t0lte
Contribute to html6405/android_device_samsung_t0lte development by creating an account on GitHub.
github.com
Are you sure that you're using the t0lte build?
On my device all functions are given.
And it would be great if you could resize your images a little bit, they are using much space.
And there's another thing, Magisk v25.2 is not compatible with this ROM, only with the N7100 ROM, so there must be something wrong!
I reviewed it again and found that I had installed the N7100 ROM.
I always install the N7100 ROM until the N7105 ROM is uploaded. So it seems I reinstalled what I had installed in the past.
I caused the inconvenience to you.
yonekome said:
I reviewed it again and found that I had installed the N7100 ROM.
I always install the N7100 ROM until the N7105 ROM is uploaded. So it seems I reinstalled what I had installed in the past.
I caused the inconvenience to you.
Click to expand...
Click to collapse
No problem,
but saving videos works on my device, are we taking about video recording with the camera?
yonekome said:
・When connected to a PC, the USB cable must be disconnected and reinserted once after the USB setting is set to file sharing.
Click to expand...
Click to collapse
Yes, this annoying bug still exists :/.
html6405 said:
No problem,
but saving videos works on my device, are we taking about video recording with the camera?
Click to expand...
Click to collapse
After installing the N7105 ROM, I am able to save it.
html6405 said:
Yes, this annoying bug still exists :/.
Click to expand...
Click to collapse
This was also fixed in my environment after reinstalling the ROM.
I get error 1 when trying to install it. My phone was the model SGH-T889 but after rooting and installing a different custom rom it shows its the model GT-N7105. Can installing a rom change the model number?
kerryking1 said:
I get error 1 when trying to install it. My phone was the model SGH-T889 but after rooting and installing a different custom rom it shows its the model GT-N7105. Can installing a rom change the model number?
Click to expand...
Click to collapse
Could you send me the recovery log after the failed installation?
Then I can help you.
Does it automatically save a log?
kerryking1 said:
Does it automatically save a log?
Click to expand...
Click to collapse
No, you have to save it in advanced.
I found it
recovery
Is it uploading the files? Im not seeing them
let me try zip
wrote 306907 blocks; expected 306907
stashed 0 blocks
max alloc needed was 4096
bytes_written_SYSTEM: 1257091072
bytes_stashed_SYSTEM: 0
deleting stash 13c23145f94d68015632f2cd29899c1aaf9ad199
Wrote updated marker to /cache/recovery/13c23145f94d68015632f2cd29899c1aaf9ad199.UPDATED
Patching vendor image unconditionally...Patching vendor image unconditionally...
performing update
blockimg version is 4
maximum stash entries 0
creating stash /cache/recovery/9853a4ae1854a188181291fe94d0b4f37cdfd6e7
1298128896 bytes free on /cache (0 needed)
/cache/recovery/last_command doesn't exist.
erasing 106102 blocks
BLKDISCARD ioctl failed: Invalid argument
failed to execute command [erase 8,560,1492,20777,32256,33282,97792,98819,128000]
new data receiver is still available after executing all commands.
script aborted: E2001: Failed to update vendor image.
E2001: Failed to update vendor image.error: 2001
Updater process ended with ERROR: 1
I:Install took 111 second(s).
Error installing zip file '/sdcard/Download/20.0-20221109-HTML6405-t0lte.zip'
Updating partition details...
Iata backup size is 0MB, free: 5720MB.
I:Unable to mount '/external_sdcard'
I:Actual block device: '', current file system: 'vfat'
I:Unable to mount '/usb-otg'
I:Actual block device: '', current file system: 'vfat'
...done
kerryking1 said:
let me try zip
Click to expand...
Click to collapse
script aborted: E2001: Failed to update vendor image.
Try:
[ROM][UNOFFICIAL][11.0][ N7105/T0LTE ][Samsung Galaxy Note 2 LTE][ LineageOS 18.1 ][BETA][TREBLELIZED]
/* * 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...
forum.xda-developers.com
and report.
It didnt work
im trying again
I think it worked. I missed the step about formatting data.
Awesome its loading. Thank you.
Related
This is a CyanogenMod 12.1 ROM for the Exynos3470 based Samsung Galaxy Tab 4 7.0 LTE (T235/T235Y).
DO NOT USE IT FOR T230(NU)/T231 OR YOU WILL BRICK YOUR DEVICE
Although T235 and T230(NU)/T231 (T230:WiFi / T231:3G) share the "Galaxy Tab 4 7.0" name they are not related in terms of hardware due to the different SoCs used (Samsung Exynos3470 vs. Marvell PXA1088).
Hence please do not ask for support or ROMs for the T230(NU)/T231.
Working features
Receiving and making calls
Hardware sensors (Acceleration)
Audio
Bluetooth
Wifi
HW accelerated GUI
MTP storage
GPS
USB-OTG (Mass-Storage, Keyboard, Mouse working, USB-Audio untested)
Camera (pictures+video: Back+Front)
Non-working features:
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 Tab 4 7.0 SM-T235 and SM-T235Y (Exynos)
It might be instable, crash your device, drain your battery, or even might damage your smartphone
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-v1.85
TWRP 2.8.7.0 recovery image [09/08/2015] (AndroidFileHost Mirror)
CM 12.1 ROM (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 links above). Otherwise TWRP might not be able to flash the ROM.
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 stock ROM 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:
09/08/2015:
*Update kernel to T235XXU1AOD1
*Synchronize with newest CM 12.1 sources (contains stagefright patches)
*Fixed black screen on minimal brightness
12/07/2015:
* Charging animation in standby-mode fixed
11/07/2015:
* Update to newest CyanogenMod sources (LMY48G)
* Left touchkey working now (configured as App-Switch button)
* Camera Preview working (saving a picture might still crash)
30/06/2015:
* Image sizes reduced to fix "unable to mount /system" problems
28/06/2015:
* Initial test-build
This section is for developers:
A README file with build instructions can be found here:
https://github.com/cm-3470/patcher_degaslte
Sources:
Code:
https://github.com/cm-3470/android_device_samsung_degaslte
https://github.com/cm-3470/android_vendor_samsung_degaslte
https://github.com/cm-3470/android_kernel_samsung_degaslte
https://github.com/cm-3470/android_device_samsung_smdk3470-common
Developers welcome
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.
XDA:DevDB Information
[T235][ROM][5.1.1][LMY48G] CyanogenMod 12.1 for T235(Y) [Alpha 09/08/2015], ROM for the Samsung Galaxy Tab 4
Contributors
hennymcc
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 09/08/2015]
Based On: CyanogenMod
Version Information
Status: Alpha
Created 2015-06-29
Last Updated 2015-09-24
i've tried to test the rom but i can't install so far... i've wiped all but it said it can't mount system again...
http://www.mobosdata.com/samsung-galaxy-tab-4-7-0-lte-sm-t235y
According to this the SM-T235Y is based on Marvel cpu vs exynos on the sm-t235
Does anyone really know the differences ? On another page i read the sm-t235y has a snapdragon 400 ...
Hectic confusing samsung numbering + different devices with same model name .
@hennymcc
do you have included selinux_defconfig in your twrp kernel?
androidboot.selinux=disabled at twrps kernel cmd line should be removed
i wiped system and all partitions using your new twrp but when i install the zip file then /system becomes unmountable
/system is formated ext4
should i try to format it f2fs ?
interstellar22 said:
i wiped system and all partitions using your new twrp but when i install the zip file then /system becomes unmountable
/system is formated ext4
should i try to format it f2fs ?
Click to expand...
Click to collapse
any marvell devices will not work with this or any other custom rom.
sub77 said:
any marvell devices will not work with this or any other custom rom.
Click to expand...
Click to collapse
this is an exynos device not marvell
and now for some reason i cant restore the backup i made
i tryed restorng the backup with twrp 2.8.6.0 recovery from this thread and the 2.8.1.0 from the other.
one gives boot animation loop and the other is stuck at boot
hennymcc said:
In case you want to go back to the stock ROM:
lf you do not have the latest stock ROM you can download it from SamMobile
Click to expand...
Click to collapse
Stock Roms on Android File Host (quicker, free-er host site than Sammobile)
@interstellar22 did you try wiping cache after you restored, before you booted?
thisisapoorusernamechoice said:
Stock Roms on Android File Host (quicker, free-er host site than Sammobile)
@interstellar22 did you try wiping cache after you restored, before you booted?
Click to expand...
Click to collapse
i tryed once without wiping cache, but i had cache backed up also
then i tryed to do a factory reset
still stuck at bootlogo
and adb logcat and adb devices shows nothing
sub77 said:
@hennymcc
do you have included selinux_defconfig in your twrp kernel?
androidboot.selinux=disabled at twrps kernel cmd line should be removed
Click to expand...
Click to collapse
The default selinux setting is enforced. As the selinux configuration files are not complete, Android would not boot.
Setting androidboot.selinux=permissive might work, but when I tested this setting on my S5 mini, it was rather unstable for some reason.
interstellar22 said:
http://www.mobosdata.com/samsung-galaxy-tab-4-7-0-lte-sm-t235y
According to this the SM-T235Y is based on Marvel cpu vs exynos on the sm-t235
Does anyone really know the differences ? On another page i read the sm-t235y has a snapdragon 400 ...
Hectic confusing samsung numbering + different devices with same model name .
Click to expand...
Click to collapse
sub77 said:
any marvell devices will not work with this or any other custom rom.
Click to expand...
Click to collapse
interstellar22 said:
this is an exynos device not marvell
Click to expand...
Click to collapse
T235 and T235Y definitely use Exynos 3470 SoCs. Here an extract from the T235Y default.prop:
Code:
ro.product.model=SM-T235Y
ro.product.name=degasltezt
ro.product.device=degaslte
ro.product.board=universal3470
ro.chipname=exynos3470
The default.prop file of the T235 is similar, only that the product name is degasltexx.
Marvell's PXA1088 SoC is used in the T230/NU which is the non-LTE (WiFi-only) variant of the Tab 4 7.0.
Marvell's PXA1088 and Samsung's Exynos3470 are totally different and have nothing in common (except an ARM core), the same applies to Qualcomm's Snapdragon. There are many websites that mention wrong SoC names as Samsung's naming scheme is rather confusing.
The same applies to the S5 Mini: G800F/M/Y -> Exynos3470, G800H -> Qualcomm Snapdragon.
corneo said:
i've tried to test the rom but i can't install so far... i've wiped all but it said it can't mount system again...
Click to expand...
Click to collapse
Code:
Info: format successful
I:mkfs.f2fs -t 1 /dev/block/mmcblk0p18 process ended with RC=0
Done.
Why was the system partition formatted with f2fs? The default file system is ext4.
The TWRP partition table is hardcoded to ext4 so that's probably the reason for these lines:
Code:
E:Unable to mount '/system'
I:Actual block device: '/dev/block/mmcblk0p18', current file system: 'ext4'
Could you reformat it with ext4?
interstellar22 said:
i tryed once without wiping cache, but i had cache backed up also
then i tryed to do a factory reset
still stuck at bootlogo
and adb logcat and adb devices shows nothing
Click to expand...
Click to collapse
Did you flash the stock ROM with Odin?
And afterwards wipe the data partition and then the cache with the _stock_ recovery (as TWRP is not available after flashing the stock ROM)?
interstellar22 said:
i wiped system and all partitions using your new twrp but when i install the zip file then /system becomes unmountable
/system is formated ext4
should i try to format it f2fs ?
Click to expand...
Click to collapse
Short summary:
interstellar22 and corneo tried it so far and both got the error message "/system unmountable"
Strange that corneo was able to generate an error log.
@corneo: did you create the log with adb?
At least according to corneo's log, it seams that after the F2FS format the partition is reformatted with EXT4 afterwards:
Code:
Formatting system using make_ext4fs function.
It also says:
Code:
erasing 588800 blocks
blkdiscard failed: Invalid argument
writing 134395 blocks of new data
lseek64 failed: Invalid argument
I:Legacy property environment disabled.
E:Error executing updater binary in zip '/external_sd/cm-12.1-20150627-UNOFFICIAL-degaslte.zip'
Error flashing zip '/external_sd/cm-12.1-20150627-UNOFFICIAL-degaslte.zip'
Not that sure about what causes this error. Maybe the partition sizes have to be changed.
hennymcc said:
Short summary:
interstellar22 and corneo tried it so far and both got the error message "/system unmountable"
Strange that corneo was able to generate an error log.
@corneo: did you create the log with adb?
At least according to corneo's log, it seams that after the F2FS format the partition is reformatted with EXT4 afterwards:
Code:
Formatting system using make_ext4fs function.
It also says:
Code:
erasing 588800 blocks
blkdiscard failed: Invalid argument
writing 134395 blocks of new data
lseek64 failed: Invalid argument
I:Legacy property environment disabled.
E:Error executing updater binary in zip '/external_sd/cm-12.1-20150627-UNOFFICIAL-degaslte.zip'
Error flashing zip '/external_sd/cm-12.1-20150627-UNOFFICIAL-degaslte.zip'
Not that sure about what causes this error. Maybe the partition sizes have to be changed.
Click to expand...
Click to collapse
i've created the log in recovery and copied it to sd.
now i flashed the tab again with odin and try it again. same issue...
Gesendet von meinem One M8
i managed to get the original firmware back with odin
could it be that the system.new.dat file is corrupted ?
i had formated system with ext4 then did the update and was still getting unable to mount /system afterwards
so most probably the system.new.dat file has some problems or i have no idea why i cant mount /system afterwards
Maybe it is caused by wrong BOARD_...IMAGE_PARTITION_SIZE values in BoardConfig.mk.
Could you please post the contents of /proc/mounts and /proc/partitions:
Code:
cat /proc/mounts
cat /proc/partitions
The above should be performed from the stock ROM. The device must be rooted.
Hmm, the problem might be here:
Code:
Patching system image unconditionally...
blockimg version is 2
erasing 588800 blocks
blkdiscard failed: Invalid argument
writing 134395 blocks of new data
lseek64 failed: Invalid argument
588800 * 4096 = 2411724800 bytes (2,2GB)
This is the value of the BoardConfig.mk taken from the S5 Mini (BOARD_SYSTEMIMAGE_PARTITION_SIZE := 2411724800).
But the system partition is only 2233466880 bytes:
Code:
/system | /dev/block/mmcblk0p18 | Size: 2096MB Used: 1828MB Free: 268MB Backup Size: 1828MB
Code:
I:wipe_path '/system'
Formatting System using make_ext4fs function.
Creating filesystem with parameters:
Size: 2233466880
The system.img itself is only 500MB in size. So I guess reducing the image size should fix the problem.
An updated ROM is available. The image sizes have been reduced. I hope this fixes the problems with the system-partition.
Also use the new TWRP recovery as the partition sizes might be hardcoded in the old one.
good news! new recovery and system image works! very smooth so far, searching for bugs now. the only one i found are the extended settings option. it doesn't work but thats no problem for me. thank you very much!
Gesendet von meinem One M8
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 5.1.x (Lollipop), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are 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 us for messing up your device, we will laugh at you.
*
*/
CyanogenMod 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. You will need to provide your own Google Applications package (gapps). CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit our Gerrit Code Review. Your changelog is whatever was merged into gerrit.
Download Links
Androidfilehost:
Download: https://www.androidfilehost.com/?fid=24391638059057759
Google Apps Minimal Edition:
Download: http://forum.xda-developers.com/android/software/gapps-google-apps-minimal-edition-t2943330
Installation
1.) You must have twrp installed follow this guide here
2.) Download the ROM and Gapps and place them on internal or external storage (depending on your model you may only have internal storage)
3.) In TWRP navigate to "Wipe" and wipe cache, data, and dalvik
4.) In TWRP navigate to "Install" find the location of the downloaded zips and proceed with installation
5.) Once both ROM and Gapps have been successfully flashed reboot system and wait for the device to boot
XDA:DevDB Information
CyanogenMod 12.1 for Alcatel ONETOUCH IDOL 3 5.5, ROM for the Alcatel Onetouch Idol 3
Contributors
Unjustified Dev
Source Code: http://github.com/TeamRegular
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.10.x
Version Information
Status: Stable
Created 2015-10-14
Last Updated 2016-01-28
Status
Working:
Radio (Includes Dual Sim, Data and SMS)
Sound
Camera
BT
Sensors
Wifi
Known Issues:
Please share your bug reports (include a log if possible)
Tap to wake (Works, but disables itself randomly)
Horrendous battery drain
Changelog
20160218
remove unneeded qcom usb script
disable boot freq limit for cluster
20160216
Updated prima driver to LA.BR.1.1.3_rb1.45
Updated kernel to LA.BR.1.1.3_rb1.45
add back various alcatel kernel changes
set usb properties on boot (Fix the usb product model defaulting to Android)
set variant from init and add support for I806 (pivoq)
selinux enforcing (wcnss fixes by pivoq)
add peripheral manager
wcnss: restore stock config
20160128
update storage configuration (fix internal storage access)
don't set tct properties
set taptowake control state to 2
remove window cover support (revisit later)
remove unused zram script
remove tct cmdline garbage
remove unused hdcpService
remove power engine
remove powerup reason
remove unused Tct Daemon
disable secure discard
remove camera wrapper
use half res bootanimation
update WCNSS cfg from firmware bin
Stop the QC-QMI message spam
switch to init.qcom.power and update devfreqs
add script to identify device variants
switch to new cm-12.1 kernel
update adreno blobs
FAQs
Q: Is the device fully reversible on CyanogenMod as well?
A: Unfortunately no, it does allow all rotations but the dialer app currently will not allow you to place calls upside down.
Q: Does Dual Sim work with this ROM?
A: Dual Sim devices are now supported
Q: Why is my device 6045X?
A: The script failed to identify your device the supported model are 6045I, 6045B, 6045K, and 6045Y
Q: How can I get my device supported?
A: Post the model number and stock build.prop
Q: Is the Aero flipcase supported on CyanogenMod?
A:At the current moment it is not supported
Good News! Any plans for supporting 4.7 version aswell?
Is your device tree based on a similar device like yu tomato oder something, could you give me some hints for setting it up?
salzy said:
Good News! Any plans for supporting 4.7 version aswell?
Is your device tree based on a similar device like yu tomato oder something, could you give me some hints for setting it up?
Click to expand...
Click to collapse
No plans at the moment. There's is already someone handling 4.7 variants. Check out the CM port thread for details.
w00t!!!!!
Sent from my 6045I using Tapatalk
Like a kid on Christmas Eve. Waiting for what's to come. Can't wait to see future progress on this. I would give this a shot but WiFi and MMS are like my main two necessities. Thanks to all of those involved on this port for making this happen.
So close but yet so far.. I was so hyped when saw the thread but got down to earth quickly.. Stay focused my man, you're about to make something that's good into the great..
Just wondering if cm have some incompatibles with root apps like greenify, Viper 4 Android? Thank you
Sent from hell
Did you get the kernel to boot building from source or are you still repacking with stock?
Sent from my 6045I using XDA Premium HD app
brian117 said:
Like a kid on Christmas Eve. Waiting for what's to come. Can't wait to see future progress on this. I would give this a shot but WiFi and MMS are like my main two necessities. Thanks to all of those involved on this port for making this happen.
Click to expand...
Click to collapse
It's close. Just seeing how fast @Unjustified Dev has progressed to this point has been impressive.
Great Great Great my idol trembles park in the pits ready to receive new engine.
make sure everyone to get the minimal gapps as 5.1 before download
Whoohoo! so excited haha.
One wonders why use those minimal gapps rather dated instead of gapps latest? On motog 2014 Cyan 12.1 latest release give FC using ones you reported.
While Cyanogen recommends these:deleted
masterdex said:
One wonders why use those minimal gapps rather dated instead of gapps latest? On motog 2014 Cyan 12.1 latest release give FC using ones you reported.
While Cyanogen recommends these:http://forum.xda-developers.com/android/software/tk-gapps-t3116347
Click to expand...
Click to collapse
They worked fine for the testers. I'm sure those gapps would cause issues because they aren't 64 bit compatible.
Unjustified Dev said:
They worked fine for the testers. I'm sure those gapps would cause issues because they aren't 64 bit compatible.
Click to expand...
Click to collapse
Then I immediately delete the link to avoid problems.
My ADB is ready.
will it be regular flash or aroma installer?
masterdex said:
Then I immediately delete the link to avoid problems.
My ADB is ready.
Click to expand...
Click to collapse
CyanogenMod
https://www.androidfilehost.com/?fid=24052804347837558
Bootimg with adb enabled
https://www.androidfilehost.com/?fid=24052804347837588
Flash cm then the boot.img can be done from twrp or fastboot.
To keep it from crashing we need to remove the wlan module
adb remount
adb shell rm -rf /system/lib/modules/wlan.ko
technically you could do that from twrp without ever flashing the boot.img by mounting system after installing cm and using the included twrp file manager
Unjustified Dev said:
CyanogenMod
https://www.androidfilehost.com/?fid=24052804347837558
Bootimg with adb enabled
https://www.androidfilehost.com/?fid=24052804347837588
Flash cm then the boot.img can be done from twrp or fastboot.
To keep it from crashing we need to remove the wlan module
adb remount
adb shell rm -rf /system/lib/modules/wlan.ko
technically you could do that from twrp without ever flashing the boot.img by mounting system after installing cm and using the included twrp file manager
Click to expand...
Click to collapse
Ok I'm downloading.
Then install cm after bootloader and still gapps and after I disable the WiFi with ADB or leave everything as it is?
masterdex said:
Ok I'm downloading.
Then install cm after bootloader and still gapps and after I disable the WiFi with ADB or leave everything as it is?
Click to expand...
Click to collapse
You can flash gapps before and the boot.img isn't needed flash cm and gapps. Once they are done mount system and use the file manager to remove wlan module and that's it reboot and everything should be fine.
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 6.0 (Marshmallow), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are 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 us for messing up your device, we will laugh at you.
*
*/
CyanogenMod 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. You will need to provide your own Google Applications package (gapps). CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit our Gerrit Code Review.
Download Links
CyanogenMod:
Nightly: http://download.cyanogenmod.org/?device=clark&type=nightly
Google apps addon:
OpenGapps: http://opengapps.org/ (you'll want a zip for the ARM64 platform, Android version 6.0)
HEADS UP: Be sure you flash the gapps package with your rom. If you boot your rom, then go back and try to flash gapps after the fact, you're gonna have a bad time.
Misc Links
Unoffical changelog:
Link: http://www.cmxlog.com/13/clark/
Learn to build yourself:
Link: https://wiki.cyanogenmod.org/w/Build_for_clark
The CyanogenMod team would like to thank everyone involved in helping with testing, coding, debugging & documenting! Enjoy!
XDA:DevDB Information
[ROM][OFFICIAL] CyanogenMod 13.0 Nightlies for the Moto X Pure 2015 (clark), ROM for the Moto X Style (Pure)
Contributors
invisiblek, Hashbang173, gmillz, neph81
Source Code: http://github.com/CyanogenMod
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.10.x
Version Information
Status: Nightly
Created 2016-06-03
Last Updated 2016-06-03
I can't flash this build (clean flash). Twrp 3.0.2.0, stuck at "Patching system image unconditionally" forever.
Still able to flash unofficial build normally though.
Device: XT1572 Asia Single Sim.
tanpro260196 said:
I can't flash this build (clean flash). Twrp 3.0.2.0, stuck at "Patching system image unconditionally" forever.
Still able to flash unofficial build normally though.
Device: XT1572 Asia Single Sim.
Click to expand...
Click to collapse
Log? Check dmesg and /tmp/recovery.log
invisiblek said:
Log? Check dmesg and /tmp/recovery.log
Click to expand...
Click to collapse
dmesg:
Code:
Installing zip file '/external_sd/Downloads/cm-13.0-20160603-NIGHTLY-clark.zip'
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
Target: 1464916728
detected filesystem ext4 for /dev/block/bootdevice/by-name/system
Patching system image unconditionally...
That's it, it stop there forever.
Log uploading...
Update: Log link
tanpro260196 said:
dmesg:
Code:
Installing zip file '/external_sd/Downloads/cm-13.0-20160603-NIGHTLY-clark.zip'
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
Target: 1464916728
detected filesystem ext4 for /dev/block/bootdevice/by-name/system
Patching system image unconditionally...
That's it, it stop there forever.
Log uploading...
Update: Log link
Click to expand...
Click to collapse
Wow, so much going on here. Its trying to do a data wipe, failing pretty hard at doing that starting here: https://gist.github.com/invisiblek/f092487c5b5791c4c7e830ef2324e862#file-gistfile1-txt-L531
I see su.img, which leads me to believe you're using that systemless root thing for whatever reason (CM includes root already...not sure what you're trying to achieve here other than complicating things).
I see xposed in there, another strike at attempting to get any official support for something that's broken.
However, it appears to get past all that and is blowing up here: https://gist.github.com/invisiblek/f092487c5b5791c4c7e830ef2324e862#file-gistfile1-txt-L7740
I'm not sure what zip its trying to open there, seems odd to me that it would be trying to open another zip AFTER the install has already taken place.
End result: I don't have a good answer for you. The above snippet is not a dmesg. Not sure if it would provide any more information, but you got a lot of hacks going on here already. My guess is that xposed or that systemless root thing are attempting to re-install themselves after your CM zip is installed and is hanging/failing.
You could wipe /system (use the advanced format option under wipe) as well as /data (but it looks like that fails, so a full format of internal storage would probably be recommended) and try again.
invisiblek said:
Wow, so much going on here. Its trying to do a data wipe, failing pretty hard at doing that starting here: https://gist.github.com/invisiblek/f092487c5b5791c4c7e830ef2324e862#file-gistfile1-txt-L531
I see su.img, which leads me to believe you're using that systemless root thing for whatever reason (CM includes root already...not sure what you're trying to achieve here other than complicating things).
I see xposed in there, another strike at attempting to get any official support for something that's broken.
However, it appears to get past all that and is blowing up here: https://gist.github.com/invisiblek/f092487c5b5791c4c7e830ef2324e862#file-gistfile1-txt-L7740
I'm not sure what zip its trying to open there, seems odd to me that it would be trying to open another zip AFTER the install has already taken place.
End result: I don't have a good answer for you. The above snippet is not a dmesg. Not sure if it would provide any more information, but you got a lot of hacks going on here already. My guess is that xposed or that systemless root thing are attempting to re-install themselves after your CM zip is installed and is hanging/failing.
Click to expand...
Click to collapse
I already performed a full wipe (checked every box except SD card) before flash, it should removed everything right?
Beside, those things are installed on unoffcial builds, not this build.
The other zip file could be the gapps package?
tanpro260196 said:
I already performed a full wipe (checked every box except SD card) before flash, it should removed everything right?
Beside, those things are installed on unoffcial builds, not this build.
The other zip file could be the gapps package?
Click to expand...
Click to collapse
Doubt its the gapps package. One other thing you could try is to change the filesystem of /data to ext4, then back to f2fs, that would wipe it out for sure. Make sure you have a way to get your cm zip back on to the device though afterwards, because it won't be there after you do that.
Something is really hosed with your /data partition when I see it failing to delete (unlink) all those files. That's not good at all...
invisiblek said:
Doubt its the gapps package. One other thing you could try is to change the filesystem of /data to ext4, then back to f2fs, that would wipe it out for sure. Make sure you have a way to get your cm zip back on to the device though afterwards, because it won't be there after you do that.
Something is really hosed with your /data partition when I see it failing to delete (unlink) all those files. That's not good at all...
Click to expand...
Click to collapse
I noticed that only /data is f2fs, the rest is ext4, is it normal?
Could be a hardware defect?
tanpro260196 said:
I noticed that only /data is f2fs, the rest is ext4, is it normal?
Could be a hardware defect?
Click to expand...
Click to collapse
That's normal.
No, pretty unlikely.
invisiblek said:
That's normal.
No, pretty unlikely.
Click to expand...
Click to collapse
One more thing, when I plug the phone to my pc in twrp, it shown "xt1575" instead of "xt1572". Could it be the problem?
tanpro260196 said:
One more thing, when I plug the phone to my pc in twrp, it shown "xt1575" instead of "xt1572". Could it be the problem?
Click to expand...
Click to collapse
No, that's a TWRP thing and its purely cosmetic.
invisiblek said:
No, that's a TWRP thing and its purely cosmetic.
Click to expand...
Click to collapse
Tried your suggestion and failed again.
dmesg is the same.
Log attached. I see some errors in there but I don't understand any of them.
I just installed CM13, booting now... Never unlocked the device, so full stock unmodiffied system 'till now. I flashed CM Recovery but fails to install the .zip it says its for clarck and my device is . (none) so I flashed TWR Recovery and it flashed w/o error at all. First full wipe, including system, then cm.zip and then gapps stock, all fine. Now starting Android for first time optimizations... I'll let you know if something goes wrong.
At last...
Sent from my XT1572 using XDA-Developers mobile app
Clark booted fine no issues accept having issues updating binaries in SuperSU
---------- Post added at 04:31 PM ---------- Previous post was at 04:30 PM ----------
ARUN B said:
At last...
Sent from my XT1572 using XDA-Developers mobile app
Click to expand...
Click to collapse
+1
Haven't flashed anything in weeks, guess I'll finally give cm a shot.
Just noticed cm recovery. Any benefit to flashing this? I'll find out soon enough I suppose.
Weird, I can't flash this rom but I can flash everything else normally (unoffcial cm13, RR, Dirty Unicorn)....
Wow cm recovery is pretty lacking feature wise... Now i have to flash twrp again.
---------- Post added at 09:40 PM ---------- Previous post was at 09:11 PM ----------
Flashed fine here. Loading apps now.
Been running well for me most of the day. Thanks to everyone who has been a part of the ROM.
Hi, can you share battery life?
i9100 LineageOS 11.0 - ABANDONED
LineageOS (as well as CM did until December 2016) still maintains the cm11.0 / 4.4.4 sources to keep pace with 'The Android Security Bulletin' (ASB).
https://source.android.com/security/bulletin/index.html.
Patches for CVE security issues are released at least once a month to the Android Open Source Project (AOSP) repository.
Patches for Android 4.4.4 are not provided by ASB anymore.
This means, security wise Android 4.4.4 is formally dead.
Nevertheless there are a few enthusiasts, still backporting security patches from recent Android versions to 4.4.4.
You should know, such backports are no formal ASB security patches.
Therefore the security patch level of this ROM is named: Unofficial Security Backport "December 2019".
Despite of implementing these security patches by the LineageOS team to its own repository https://github.com/LineageOS, LineageOS does not provide cm11 builds anymore.
Since I personally like 4.4.4. more than later versions, I build it myself unofficially and would like to share it.
The build is made from LineageOS "Branch: cm-11.0" PLUS ASB security patches, even if they are not yet approved by LineageOS.
The main goal of this ROM is to provide up to date builds in terms of ASB security patches, not development.
Instructions:
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
* I'm 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!
*/
First time flashing cm11.0 your device, or coming from another ROM
- download the zip
- install a compatible recovery (TWRP 3.1.0, cwm 6.0.5.1 are ok)
- perform a recovery backup of your current ROM
- flash ROM
- wipe data & cache partitions of your device
- optional: install the Google Apps addon package
Code:
Install lineage-11 on i9100 coming from any ROM (long way)
===============================================
0 Downloads [URL="https://androidfilehost.com/?w=files&flid=298277"]AFH folder with all downloads
[/URL]~~~~~~~~~~~
phone USB drivers
"SAMSUNG_USB_Driver_for_Mobile_Phones.exe"
odin
"Odin3 v3.13.1.exe"
Stock-ROM JB
"I9100XWLST_I9100ODDLSE_I9100DDLS9_HOME.tar.md 5"
Heimdall
"heimdall-suite-1.4.0-win32.zip"
'ROM lineage-11 for i9100'
"lineage-11-20190714-UNOFFICIAL-i9100.zip" or any other lineage-11 ROM
TWRP for i9100
"twrp-3.1.0-0-i9100.img"
NOTE: more recent versions of TWRP won't work in step 3
1 Install Stock-ROM JB
~~~~~~~~~~~~~~~~~~~~~~
Installing Stock-ROM JB shall ensure a clean start.
1.1 PC
install drivers "SAMSUNG_USB_Driver_for_Mobile_Phones.exe"
1.2 Phone
* boot to BootLoader (hold: Vol-Down + Home + Power)
* confirm with Vol-Up
* connect to PC
1.3 PC
execute "Odin3 v3.13.1.exe"
* in 'Log' you must see a device
* select checkbox AP
* select file "I9100XWLST_I9100ODDLSE_I9100DDLS9_HOME.tar.md 5"
* Start
* watch progress until success
1.4 Phone
In the highly probable case of a bootloop on 1st start:
* boot to recovery (hold: Vol-Down + Home + Power)
* execute factory reset
* reboot system
Now Stock-ROM JB should be installed and working.
1.5 Phone
for later usage copy "lineage-11-20190714-UNOFFICIAL-i9100.zip" to Download folder
2 Install Heimdall
~~~~~~~~~~~~~~~~~~
2.2 Phone
* boot to BootLoader (hold: Vol-Down + Home + Power)
* confirm with Vol-Up
* connect to PC
2.2 PC
* extract "heimdall-suite-1.4.0-win32.zip" & navigate to the location of 'heimdall.exe'
Remark: use a folder on the PC's HDD, it didn't work for me when using a USB-Drive
* follow 'Driver Installation Instructions' in README.TXT (switches USB driver with zadig.exe)
* check connection to phone via 'heindall.exe detect'
--> must show 'Device detected'
3 Install TWRP & LOS
~~~~~~~~~~~~~~~~~~~~
3.1 PC
* extract 'ROM lineage-11 for i9100'
* copy 'boot.img' to the folder containing 'heimdall.exe'
* copy "twrp-3.1.0-0-i9100.img" to the folder containing 'heimdall.exe'
* open cmd.exe in the folder containing 'heimdall.exe'
* execute "D:\S2\Heimdall\build\bin>heimdall flash --KERNEL boot.img --RECOVERY twrp-3.1.0-0-i9100.img --no-reboot"
* watch progress until 'Releasing device interface...'
3.2 Phone
* pull out the USB cable
* hold the power button until screen is off (> 8s)
* boot to Recovery (hold: Vol-Up + Home + Power)
* goto Wipe
* goto Advanced wipe --> select Dalvik, Cache, System, Data
* swipe to Wipe
* goto TWRP Install
* navigate to Download folder from 1.5
* select "lineage-11-20190714-UNOFFICIAL-i9100.zip"
Remark: Do not install gapps together with ROM, SUW will crash and ROM is not usable.
* swipe to confirm flash
* reboot System
* configure the just installed ROM
* Optional install gapps:
reboot to recovery
install gapps
reboot system
Download:
<< latest 2019/12/24 >> Unofficial Security Backport "December 2019"
AndroidFileHost
older downloads
Included:
LineageOS per 2019-12-24 status merged at LineageOS
LineageOS per 2019-12-24 status open at LineageOS topics asb-2019.12-cm11
Note
The stock browser is removed from this ROM due to severe security issues, which cannot get fixed.
Get a state of art browser (like firefox) from play store instead.
Known Issues:
xposed not supported
1) A fix is provided by Lenny Bard, see instructions at post here.
2) Fix by lee.wp14. See post https://forum.xda-developers.com/showpost.php?p=79618987&postcount=243.
Download: lineage-11-20190609-UNOFFICIAL-i9100-xposedReady.zip
Be aware, these two fixes might break some security patches.
video in browser fix, thanks to TriboDoP:
https://forum.xda-developers.com/showpost.php?p=70266718&postcount=142
gapps
Paddy's found out, that latest gapps may cause trouble.
Fix: open_gapps-arm-4.4-pico-20161006
Credits:
LineageOS
xpduyson - ASB patches
Tim Schumacher - ASB patches + KRACK patches
mse1969 - ASB patches
Android-Andi - security patches
syphyr - security patches
Hi @grzwolf
That's great!
Thank you very much for building kitkit with latest security patches!
Regards
TriboDP
Sent from my ME173X using XDA-Developers Legacy app
Hi @grzwolf,
It may be an old version of Android, but its a new and updated build... thanks for keeping this cm/los 11 up to date and giving us more options....
Thanks, Lister
Nicee
how is battery life?
Thanks for the good work :good:
Just wanted to note that the bugs here are the same as slimsaber ROM bugs.
Highlights:
1- pixelated YouTube videos.
2- no 480p video quality in YouTube videos
3- no Xposed support.
MigoMujahid said:
Thanks for the good work :good:
Just wanted to note that the bugs here are the same as slimsaber ROM bugs.
Highlights:
1- pixelated YouTube videos.
2- no 480p video quality in YouTube videos
3- no Xposed support.
Click to expand...
Click to collapse
3 - Xposed: you may try this: https://forum.xda-developers.com/xposed/xposed-android-4-4-4-t3249895/post72401950#post72401950
This ROM has brought my S2 back to real usability. I have tried many nougat ROMs with varying results but all were so laggy and unresponsive. This is like a breath of fresh air.
cexcells said:
This ROM has brought my S2 back to real usability. I have tried many nougat ROMs with varying results but all were so laggy and unresponsive. This is like a breath of fresh air.
Click to expand...
Click to collapse
Exactly
Older is always better, because the systems in newer android versions use too much ram, and leave you with less than 25% of free ram(in our case), if you went back to cm10 or cm9, your phone will get smoother, the problem is that those versions are so old now and almost unsupported by apps and games of today, so you are forced to upgrade your phone or upgrade your android.
mhl is working? thank you
edit: sorry, I had thought to read based to 4.1.2
I installed the build with TWRP 3.1.0 and works great!
yes, I have tried many new 7.x roms and the s2 becomes very very very slow and laggy (strange because with an old motorola moto g first edition, android 7.x porting are very fast). nowadays the only use for a s2 is that as mediaplayer (kodi, acetream, live stram player etc.) with mhl cable... pity that one is forced to used stock or stock modified rom...
This ROM is really fast and all.
How did you solve the Camera and Gallery problem?
When opening Gallery it needs external storage.
I have repartitioned my S2 as follows:
System 1.5GB
Data 6GB
Internal Storage 6GB
Thx
DragonZeal said:
This ROM is really fast and all.
How did you solve the Camera and Gallery problem?
When opening Gallery it needs external storage.
I have repartitioned my S2 as follows:
System 1.5GB
Data 6GB
Internal Storage 6GB
Thx
Click to expand...
Click to collapse
That's a wide field, surely not a Gordian knot to solve. I don't do anything but occasional cleanups.
mostly too much camera/gallery garbage: --> settings, apps, all, App info, clear data/cache
sometimes too many leftovers from uninstalled apps: requires CAUTION and a root file explorer
could be a corrupted SDcard, which needs a reformatting/replacement
I will give a try right now!
grzwolf said:
That's a wide field, surely not a Gordian knot to solve. I don't do anything but occasional cleanups.
mostly too much camera/gallery garbage: --> settings, apps, all, App info, clear data/cache
sometimes too many leftovers from uninstalled apps: requires CAUTION and a root file explorer
could be a corrupted SDcard, which needs a reformatting/replacement
Click to expand...
Click to collapse
I'm experiencing this on 2 i9100 with different MicroSD Card.
I don't want to root.
This is a problem that came with KitKat.
If somebody knows a fix please let me know.
You said you only used LineageOS repositories. So you did not include TRIM and Isorec in this ROM? Do we need to install a custom Kernel to have these features?
LeBourrin said:
You said you only used LineageOS repositories. So you did not include TRIM and Isorec in this ROM? Do we need to install a custom Kernel to have these features?
Click to expand...
Click to collapse
Hi
LOS 11 has isorec.
I do not remember if it has trim as i am not on kitkat at the moment.
Sent from my ME173X using XDA-Developers Legacy app
TriboDoP said:
Hi
LOS 11 has isorec.
I do not remember if it has trim as i am not on kitkat at the moment.
Sent from my ME173X using XDA-Developers Legacy app
Click to expand...
Click to collapse
Both implemented, check commits in cm11 branch from March 2016:
https://github.com/LineageOS/android_kernel_samsung_smdk4412/commits/cm-11.0
IsoRec:
https://github.com/LineageOS/android_kernel_samsung_smdk4412/commit/f92a06b7d28586ceac5526d8669dbc44c0df9dab
Trim:
https://github.com/LineageOS/android_kernel_samsung_smdk4412/commit/197f54cdbc99458d07e99d732b72d9e391aa7fc3
Is there a recommended way to play video files on this ROM?
cexcells said:
Is there a recommended way to play video files on this ROM?
Click to expand...
Click to collapse
Why should there be any?
MXplayer or VLC are anyway the only worth alternative I know.
In other news, just a friendly remainder that for as much lineage got up to July patch level, they are still missing the (unavailable) CVE-2017-0671 fix
This build is now official.
Check out https://twrp.me/motorola/motorolamotog9power.html
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Code:
#include <std_disclaimer.h>
/*
*
* We are 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 recovery
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
XDA:DevDB Information
TWRP, Tool/Utility for the Motorola G9 Power
Contributors
mistersmee
Source Code:
Device tree: https://github.com/teamwin/android_device_motorola_cebu
Kernel sources: Prebuilt (for now) [Note: Thanks @fddm, for your patched kernel!]
https://github.com/mistersmee/kernel_motorola_sm6115
TWRP sources: https://github.com/TeamWin/android_bootable_recovery
Telegram group: https://t.me/g9power (English language)
Version Information
Status: Stable
Created 20-05-2021
This is the list of things that need to work, as per TWRP's FAQs.
I will update as I find stuff that works, and as you guys tell me what works.
Code:
Blocking checks
- [X] Correct screen/recovery size
- [-] Working Touch, screen
- [X] Focaltech touchscreen panel (confirmed working)
- [X] Novatek touchscreen panel (confirmed working)
- [X] Chipone touchscreen panel (confirmed working)
- [X] Backup to internal/microSD
- [X] Restore from internal/microSD
- [X] reboot to system
- [X] ADB
Medium checks
- [X] update.zip sideload
- [X] UI colors (red/blue inversions)
- [X] Screen goes off and on
- [X] F2FS/EXT4 Support, exFAT/NTFS where supported
- [X] all important partitions listed in mount/backup lists
- [X] backup/restore to/from external (USB-OTG) storage (not supported by the device)
- [X] backup/restore to/from adb (https://gerrit.omnirom.org/#/c/15943/)
- [X] decrypt /data
- [X] Correct date
Minor checks
- [X] MTP export
- [X] reboot to bootloader
- [X] reboot to recovery
- [X] poweroff
- [X] battery level
- [X] temperature
- [X] encrypted backups
- [X] input devices via USB (USB-OTG) - keyboard, mouse and disks (not supported by the device)
- [X] USB mass storage export
- [X] set brightness
- [X] vibrate
- [X] screenshot
- [X] partition SD card
If it isn't filled, it means it hasn't been checked yet. 'X' denotes that it is working. '!' denotes that it is not working.
Note: As I mentioned in the initial post, I'm using the prebuilt kernel for now, although the kernel sources have been released. For the long-term, using the prebuilt kernel is not ideal. I have been working on the kernel sources, but as of this writing, I have been unable to get them to boot. If any of you have experience working with Android kernels, please let me know, PM me, etc.
The kernel repo I'm working on is here: https://github.com/mistersmee/kernel_motorola_sm4250
PRs are always welcome.
Edit: Nevermind, I got them to boot.
A few notes on the image:
1. Yes, VBMeta shows 0MB in TWRP. It is intentional, nothing is wrong with the build, or your phone.
VBMeta as a partition, is only a few bytes in size, 65536 bytes, which is 65 KB, which is 0.06 MB, to be exact. TWRP displays sizes in MB, and probably rounds those decimals up, hence a size this small registers as 0. However, it is still an important partition, and it is in the stock fstab, so it cannot be left out.
2. The above point applies for "Prodpersist" as well. Although it is not as small as VBMeta, it is still just a few KBs in size, Again, it is in the stock fstab, so it cannot be left out.
Another probable explanation as to why Prodpersist shows up as 0MB, is that it is actually related to the /product partition. Due to the way Android 10, and dynamic partitions work, basically, the /system, /product, and /vendor have been subsumed under one big "super", which is incidentally read-only. Those individual partitions can only be mounted if the super partition as a whole is mounted, and TWRP does not mount that partition while booting, hence why it probably shows up as 0MB.
In any case, Prodpersist is actually not *that* important, so it doesn't *really* matter anyways.
3. As I said in the last paragraph above, Android 10 changed the way the /system partition works. Because of this, most modifications that in earlier Android versions we could do in TWRP, think flashable zips that change your boot animation, or anything that modified the system partition, will not work.
The only way to do those kinds of mods is through Magisk.
4. Yes, the image is 64MB in size. But, the stock recovery image is also 64MB.
The reason as to why it is 64MB, is because AVB support is enabled. AVB is, of course, Android Verified Boot, which allows GSI support, which should theoretically mean support for flashing GSI images in this TWRP build.
Without AVB support, the image is around 20MB, which is the more "normal" size of TWRP images of the past.
I'm a little late but. Thank you very much
Unfocusedobsessiv said:
I'm a little late but. Thank you very much
Click to expand...
Click to collapse
You're welcome!
Also as a general note to everybody:
If you updated to Android 11 and find that TWRP is not working for you i.e. it doesn't boot, nothing is wrong with your phone/you didn't mess anything up.
The build isn't working due to the Android 11 update, but I'm currently working on it.
still waiting for twrp for android 11
bhavesh.kale.73 said:
still waiting for twrp for android 11
Click to expand...
Click to collapse
No ETA except to say I'm working on it. It depends on external factors, i.e Motorola releasing the updated kernel sources which they haven't done as of this writing.
Hello everyone. I've never had any luck restoring twrp backups of stock on encrypted A/B phones. Does anyone know if that's possible nowadays? I'm still on 10 too because of a Real Racing 3 bug that prevents it from loading in 11.
And a big thank you to you, @mistersmee . Your twrp is the reason I chose this phone.
arkansawdave74 said:
Hello everyone. I've never had any luck restoring twrp backups of stock on encrypted A/B phones. Does anyone know if that's possible nowadays? I'm still on 10 too because of a Real Racing 3 bug that prevents it from loading in 11.
And a big thank you to you, @mistersmee . Your twrp is the reason I chose this phone.
Click to expand...
Click to collapse
You're welcome! And yeah, I had no problem backing up and restoring /data on cebu, so not sure what's going wrong for you.
mistersmee said:
You're welcome! And yeah, I had no problem backing up and restoring /data on cebu, so not sure what's going wrong for you.
Click to expand...
Click to collapse
Actually, I haven't tried in a couple years...Not since the G7 Power (Ocean). We had a terrible time trying to restore stock backups on that phone. I haven't even looked at the partition list in the backup section of your TWRP, but I'm about to. What partitions besides /data did you backup and restore successfully, if you don't mind my asking.
arkansawdave74 said:
Actually, I haven't tried in a couple years...Not since the G7 Power (Ocean). We had a terrible time trying to restore stock backups on that phone. I haven't even looked at the partition list in the backup section of your TWRP, but I'm about to. What partitions besides /data did you backup and restore successfully, if you don't mind my asking.
Click to expand...
Click to collapse
Just about every partition that is available to backup/restore. Though frankly, backing up any partition other than /data is a waste of time and space, we don't actively modify them, and they are available in the stock firmware file if you manage to mess them up anyway.
Oh my gosh why didn't I think of that before.
The Moto G7 Power was the first a / B phone any of any of us had had back then. We tried and tried and tried many different ways to restore a backup but we never thought of that, which is surprising, but we were trying to make a complete backup that you could restore all from TWRP like in the old days. System, Boot, and data.
Anyway, I went to flash Resurrection Remix Q GSI and made it back up of stock first just /data. Restored just fine after the GSI failed to boot. You really made my Android experience so much better.
Thank You.
Hey guys. Just wanted to mention that I'm trying Android 11 Official GSI Customs coming off a stock 10 and TWRP still boots fine while running the 11s.
arkansawdave74 said:
Hey guys. Just wanted to mention that I'm trying Android 11 Official GSI Customs coming off a stock 10 and TWRP still boots fine while running the 11s.
Click to expand...
Click to collapse
That's great to hear.
New release
TWRP 3.6.0_11
This build supports the Android 11 stock ROM. Unknown if it is backwards compatible with stock Android 10. Until confirmed that it is backwards compatible, people running 10 for whatever reason should stick to the 3.5.2 image, or update to 11 and run 3.6.0.
Everything is confirmed working. Download links are on the TWRP website, as always.
mistersmee said:
Is your new build official as well?
New release
TWRP 3.6.0_11
This build supports the Android 11 stock ROM. Unknown if it is backwards compatible with stock Android 10. Until confirmed that it is backwards compatible, people running 10 for whatever reason should stick to the 3.5.2 image, or update to 11 and run 3.6.0.
Everything is confirmed working. Download links are on the TWRP website, as always.
Click to expand...
Click to collapse
Is your new build official as well?
EDIT. Nevermind. I missed the last line.
arkansawdave74 said:
Is your new build official as well?
Click to expand...
Click to collapse
Yes, it is official.
Booting twrp-3.6.0_11-0-cebu.img boots ok TWRP but touch freezed, any idea?
sirjuncos said:
Booting twrp-3.6.0_11-0-cebu.img boots ok TWRP but touch freezed, any idea?
Click to expand...
Click to collapse
Try this image: https://build.twrp.me/twrp-3.6.0_11-0-cebu.img