Related
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
LineageOS for Samsung Galaxy S5 LTE+ / LTE-A
Code:
- Your warrenty is now void.
- You [b]WILL[/b] trip KNOX!
- You have been warned.
- Use at your own risk.
Introduction:
This is the thread for the offical port of LineageOS to
Samsung Galaxy S5 LTE+, SM-G901F, codename kccat6, and
Samsung Galaxy S5 LTE-A, SM-G906S/K/L, codename lentislte.
This port is mostly stable. Still, there's no software without bugs.
This project is based on the port to CyanogenMod by @sktjdgns1189. For details on the history, please have a look at the original thread.
How to install:
For kccat6, use bootloader CQJ1, CQJ2 or later.
For lentislte use bootloader CPL1.
install custom recovery, ideally directly from the TWRP project.
For kccat6: twrp-3.3.0-0-kccat6.img
For lentislte: twrp-3.3.0-0-lentislte.img
Note: TWRP 3.2.1-0 is required starting with Lineage-15.1/Oreo!
Enter recovery mode
Factory reset
Flash below ROM
Optionally flash Gapps. I suggest OpenGapps.
Optionally, if you want SU, install the LineageOS SU addon.
Reboot
Know problems:
Sometimes the SIM doesn't show up after reboot.
Occasional Camera hiccups.
State of kernel security:
CVE tracking list
Download from:
Official nightly builds:
kccat6: https://download.lineageos.org/kccat6
lentislte: https://download.lineageos.org/lentislte
Test builds (only on demand or request):
kccat6: https://cygwin.de/lineageos/kccat6/
lentislte: https://cygwin.de/lineageos/lentislte/
Sources:
LineageOS on GitHub
XDA:DevDB Information
LineageOS for Samsung Galaxy S5 LTE+ / LTE-A, ROM for the Samsung Galaxy S5
Contributors
cvxda, sassmann, xamio, sktjdgns1189
Source Code: https://github.com/LineageOS
ROM OS Version: 9.x Pie
ROM Kernel: Linux 3.10.x
ROM Firmware Required: kccat6: CQJ1/CQJ2, lentislte: CPL1
Based On: Lineage OS
Version Information
Status: Beta
Created 2017-01-08
Last Updated 2019-04-17
Notes:
Thanks to @Stamgastje for the first cut of these notes.
History and older builds (LineageOS)
The Lineage OS project -- a.k.a. Lineage Android Distribution (LAD) -- is a continuation of the CyanogenMod project, which was discontinued in December 2016. Before maintaining Lineage OS 14.1 ROM for this phone, @xamio maintained CyanogenMod ROMs (CM13, CM14.1). You can still find these builds via the link to his site (ionkiwi.nl) above. The original (and oldest) CyanogenMod builds for this phone were created by @sktjdgns1189. His original builds are still available here: http://fsrv1.sayanogen.com/KCCAT6-13/, and this was the original thread on this forum.
Installation
Below some hints that may help you to install these ROMs on your phone.
Clean install, or dirty flashing?
What is the difference?
The difference is whether you clean (format) the entire /data partition (which contains your apps and user data, as well as the dalvik cache), or not, before flashing the new ROM image:
A clean install means: clean the /system, /data (incl. dalvik cache) and /cache partitions, and then install the ROM
Dirty flashing means: clean the /system and /cache partitions, as well as the dalvik cache, but not the entire /data partition, before installing the ROM
With a clean install, you need to manually restore your apps and user data after flashing the new ROM image. With a dirty flash, there is no need to do this -- so this is the faster, but riskier solution. Therefore, it is always recommended to make a backup of your apps (e.g. with Titanium Backup) and user data (internal storage) before flashing any ROM image.
When could you consider a dirty flash?
It is, generally speaking, possible to perform a dirty flash:
When upgrading a ROM to an newer build of the same ROM (but be careful when upgrading between major versions, e.g. from CM13 to CM14.1)
When upgrading from CyanogenMod 14.1 to Lineage OS 14.1 (as Lineage OS is the continuation of CyanogenMod, based on the same sources)
When should you perform a clean install?
In all other cases, so e.g.:
When downgrading a ROM to an older build of the same ROM
When switching between ROMS, e.g. from CyanogenMod to Resurrection Remix (or vice versa). Reason: different ROMs use different code bases that are usually not 100% compatible (exception is upgrading from CyanogenMod 14.1 to Lineage OS 14.1, see above)
(Note: in case you choose to perform a dirty flash over your existing ROM, don't forget to re-flash the GApps package immediately afterwards!)
How to dirty flash an official weekly over an unofficial build (and vice versa)?
When trying to update an unofficial build to an official weekly build, I get an error message in TWRP saying
"Can't install this package on top of incompatible data. Please try another package or run a factory reset". How do I fix that?
At the start of an installation the installer checks the build keys. They differ between unoffical and official builds, and the installer refuses to overwrite builds with different keys. To fix this you have to install the official keys before trying to install the official build:
Run this script called lineage-migration-signed.zip in TWRP.
Then install the official ROM zip.
You only have to do this for the first switch from unoffical to offical build.
There may be reason to dirty flash an unofficial build over an official build, for instance, if you're developing or testing new stuff. The problem is the same, just in the other direction: You have to install the unofficial build keys:
Run this script called lineage-migration-unsigned.zip in TWRP.
Then install the unofficial ROM zip.
Modem and bootloader
Which version do I need?
Builds from Sept. 19 (cm-13.0-20160919-UNOFFICIAL-kccat6xx.zip) and later should use a Marshmallow modem & bootloader (starting with 'C', so e.g. CPE1, CPH3, CPJ1). Older builds require a Lollipop modem & bootloader (starting with 'B', so e.g. BOH4, BOK2).
Generally, it is recommended to use the latest modem that is compatible for your device.
How do I get these images?
The original ROM files containing the modem and bootloader files are available from the Sammobile site. You have to extract bootloader and modem files and flash them to your device using Odin (Windows) or Heimdall (Linux, MacOS, Windows).
Download the firmware file from Sammobile's firmware page for the G901F, G906S, G906K or G906L, depending on your device. The last ones available are CQJ1/CQJ2 for G901F, CPL2 for G906S/K/L. Assuming you download the CQJ1 version for G-901F, the resulting file will be called G901FXXU1CQJ1_G901FDTM1CQJ1_DTM.zip.
Unpack that file. On Windows, right click on the file and choose "Extract all...". On Linux/Mac, simply use the command line:
Code:
$ unzip G901FXXU1CQJ1_G901FDTM1CQJ1_DTM.zip
After unpacking you get a new file G901FXXU1CQJ1_G901FDTM1CQJ1_G901FXXU1CQC1_HOME.tar.md5. This is a standard tar archive and can be opened with any archiver capable of handling the tar format (especially with tar itself). The attached .md5 suffix indicates, that a md5 checksum has been attached to the file.
Extract the file. On Windows you can do this by installing the swiss-army knife of archivers, 7zip. It installs an entry for the right-click context menu. Use it to extract G901FXXU1CQJ1_G901FDTM1CQJ1_G901FXXU1CQC1_HOME.tar.md5. On Linux/Mac, simply use the command line:
Code:
$ tar xf G901FXXU1CQJ1_G901FDTM1CQJ1_G901FXXU1CQC1_HOME.tar.md5
Apart from the different download page and the different file names, the procedure is the same on the G906 variants.
Either way, this extracts the following list of files:
Code:
NON-HLOS.bin cache.img.ext4 recovery.img sdi.mbn
aboot.mbn hidden.img.ext4 rpm.mbn system.img.ext4
boot.img modem.bin sbl1.mbn tz.mbn
The files with suffix .img and .img.ext are the actual system files. You don't want them, unless you want to reinstall stock Samsung Android.
The files NON-HLOS.bin and modem.bin constitute the baseband, all other files with .mbn suffix constitute the bootloader.
How do I flash these images on Windows with Odin?
This is only marginally more complex than by using Heimdall (see below). The difference is that Heimdall can immediately flash the extracted .bin and .mbn files, while Odin needs them packed into a tar file. Fortunately you already have 7zip!
Select all of the aforementioned .bin and .mbn files. Right click to open the context menu. Select 7zip and choose Add to archive... from the sub menu
This opens 7zip's archive dialog. As Archive format choose tar. Append .md5 to the archive filename and press the OK button
Congratulations, you're now the happy owner of an Odin file with only bootloader and baseband images.
Sidenote: You could also create a tar.md5 file, you just have to append the md5 sum to the just created tar file. It's not really tricky, but you'd need an additional md5sum tool which is not available on Windows by default, so we just skip this here.
If you haven't already, download and install Odin.
Boot the phone into download mode: Power off the phone, then press and hold Volume Down + Home + Power buttons. You'll see a severe warning message. Ignore it by pressing Volume-Up. You're now in download mode.
Connect your device to your PC's USB port.
Start Odin.
Select the .tar file you just created.
Enable (only) these options: 'Auto Reboot' and 'F. Reset Time'.
Flash the images.
How do I flash these images on Linux/MacOS/Windows with Heimdall?
If you haven't already, download and install Heimdall. If you have trouble with the most recent version of Heimdall (the official version 1.4.1 has a few annoying bugs) you have to rebuild heimdall from source by yourself. Instructions for rebuilding can be found here and here.
Boot the phone into download mode: Power off the phone, then press and hold Volume Down + Home + Power buttons. You'll see a severe warning message. Ignore it by pressing Volume-Up. You're now in download mode.
Connect your device to your PC's USB port.
Check if Heimdall recognizes your device:
Code:
$ heimdall detect
If it doesn't, you have to do some digging:
On Windows you might have to install Samsung device drivers.
On Linux you might have to create a udev entry for your device. As root, open or create the file /etc/udev/rules.d/51-android.rules and add a line
Code:
SUBSYSTEM=="usb", ATTR{idVendor}=="04e8", MODE="0660", USER="[insert your non-root username here]"
, then reboot the machine.
On Mac... sorry, I have no idea what to do on a Mac in this case.
Flash the bootloader and baseband images:
Code:
$ heimdall flash --APNHLOS NON-HLOS.bin \
--MODEM modem.bin --SBL1 sbl1.mbn --DBI sdi.mbn \
--ABOOT aboot.mbn --RPM rpm.mbn --TZ tz.mbn
This may take a minute or two and then reboot your device automatically. It might reboot into your recovery. That's nothing to worry about. Just reboot from there into system.
Reserved
super!
Just for completeness, hereby a link to a summary of the history of this ROM. I'll stop maintaining that overview post now, with this new thread and the up-to-date overview in the topic start.
Stamgastje said:
super!
Just for completeness, hereby a link to a summary of the history of this ROM. I'll stop maintaining that overview post now, with this new thread and the up-to-date overview in the topic start.
Click to expand...
Click to collapse
I reserved the first two comments to serve as some kind of FAQ. It would be pretty nice if you could have a look over your notes from the old CM thread and rework them slightly for this thread and, if it's not asked too much, the RR thread. If you send them to me in source (i.e. with all format markers), I'd add them to the reserved comments.
Edit: To be clear, there's still some stuff in your notes which isn't in the OP, which might be helpful to newbies and pros alike.
Thanks,
Corinna
cvxda said:
I reserved the first two comments to serve as some kind of FAQ. It would be pretty nice if you could have a look over your notes from the old CM thread and rework them slightly for this thread and, if it's not asked too much, the RR thread. If you send them to me in source (i.e. with all format markers), I'd add them to the reserved comments.
Edit: To be clear, there's still some stuff in your notes which isn't in the OP, which might be helpful to newbies and pros alike.
Thanks,
Corinna
Click to expand...
Click to collapse
Sure, will do so! How can I best send you the source? I can't send you a private message on this forum. AFAIK you should be able to send me a private message, so would be good if you could share me your contact details there (e.g. an e-mail address).
Stamgastje said:
Sure, will do so! How can I best send you the source? I can't send you a private message on this forum. AFAIK you should be able to send me a private message, so would be good if you could share me your contact details there (e.g. an e-mail address).
Click to expand...
Click to collapse
You got a PM.
Thanks,
Corinna
Excellent (separate thread and the rom).
One annoyance still remaining is the backlight not turning on sometimes, have to lock unlock to get it back.
Great work. Pls make for G906x too ?
girtsn said:
Excellent (separate thread and the rom).
One annoyance still remaining is the backlight not turning on sometimes, have to lock unlock to get it back.
Click to expand...
Click to collapse
What backlight?!? This is an AMOLED display. It has no backlight.
Corinna
not sure what is the correct name but usually the phone when unlocked goes quite bright. there are however situations (the issue is not sure how to reproduce) when the display is much more pale, like energy saving or something.
i have adaptive brightness on and display mode of livedisplay on auto
cvxda said:
What backlight?!? This is an AMOLED display. It has no backlight.
Click to expand...
Click to collapse
girtsn said:
not sure what is the correct name but usually the phone when unlocked goes quite bright. there are however situations (the issue is not sure how to reproduce) when the display is much more pale, like energy saving or something.
i have adaptive brightness on and display mode of livedisplay on auto
Click to expand...
Click to collapse
Sometimes, the screen is indeed very dark after wake up (e.g. with power button) and it is fixed by turning the screen off and on again.
I think this is related to the ambient light sensor.
In my opinion it's not a major issue... only a small annoyance at best (if rarely happens).
Stamgastje said:
Sometimes, the screen is indeed very dark after wake up (e.g. with power button) and it is fixed by turning the screen off and on again.
I think this is related to the ambient light sensor.
In my opinion it's not a major issue... only a small annoyance at best (if rarely happens).
Click to expand...
Click to collapse
I see the same problem on klte. IMHO the ambient display brightness algorithm might not be the brightest one
Edit: However, on klte as well as on kccat6 I just have to move the brightness slider to get a more matching brightness.
Corinna
I believe the ROMs can be uploaded to the download section of this thread.
Anyone know how to set the SD card permissions? I can't make any changes to it.
And I'd love to hear when someone has a working Xposed!
Also, settings crashes very often when I try to change my ringtone for example, and I found my phone randomly rebooting twice today.. clean install was done..
Proioxis said:
Anyone know how to set the SD card permissions?
Click to expand...
Click to collapse
I don't understand this. Need more information regarding this? Like cannot see SD card or no write permissions or what?
ruchern said:
I don't understand this. Need more information regarding this? Like cannot see SD card or no write permissions or what?
Click to expand...
Click to collapse
I can't make any changes to the SD card, but I just read it's a known ROM issue.
"File Manager app can't access the SD card, even with root permissions (generic Lineage OS problem)"
Proioxis said:
I can't make any changes to the SD card, but I just read it's a known ROM issue.
"File Manager app can't access the SD card, even with root permissions (generic Lineage OS problem)"
Click to expand...
Click to collapse
I had this problem before but upgrading the ROM worked for me. I couldn't remember what exactly happened.
Are you on LineageOS-20160107 build?
ruchern said:
I had this problem before but upgrading the ROM worked for me. I couldn't remember what exactly happened.
Are you on LineageOS-20160107 build?
Click to expand...
Click to collapse
I'm on the 20170104 build. I'll check the 0107 build.
EDIT: Just checked the SD permissions, still can't change anything.
Proioxis said:
I'm on the 20170104 build. I'll check the 0107 build.
EDIT: Just checked the SD permissions, still can't change anything.
Click to expand...
Click to collapse
Just install and use any other file manager; the one provided with the ROM does not work. I use ES File Explorer and that gives me full access to the SD card.
---------- Post added at 09:28 PM ---------- Previous post was at 09:26 PM ----------
ruchern said:
I had this problem before but upgrading the ROM worked for me. I couldn't remember what exactly happened.
Click to expand...
Click to collapse
I think you're mixing things up. In one of the first CM14.1 builds, the complete SD card was invisible, but that has been fixed long time ago already.
TWRP 3.4.0 for the Samsung Galaxy Fold
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Introduction
It gives me great pleasure to present to you TWRP on the Samsung Galaxy Fold. Your foldable phone just became even more flexible.
This project picks up TWRP where Chris Williamson left off. Chris produced the initial release of TWRP for the Fold, which combined a custom kernel sporting some extra features with a pre-rooted TWRP image.
Chris asked me to take over the development of TWRP for the Fold to allow him to concentrate on kernel development for the device, and I was happy to oblige. My goal is to offer you the most functional build of TWRP that I possibly can, whilst making no assumptions about your desire to root the device or run a custom kernel. For that reason, the kernel I am supplying as part of this project is as close to stock as possible, with only the minimum number of changes required to allow TWRP to function, and with no added features. For the same reason, the images I provide have not been pre-rooted with Magisk.
Rooting Samsung system-as-root devices
How you root your Fold depends on whether you are running Android 9 (Pie) or Android 10. If, however, you have already upgraded your device to Android 10, you can root your device only in the boot partition. For reasons that are not yet clear, the Fold will not boot Android froma custom kernel that is rooted in recovery.
Rooting in the recovery partition
When the device is rooted in recovery, the TWRP image must be patched with Magisk (using the Magisk Manager app) to allow the same kernel to be shared between TWRP and Android. After patching, the user always boots the device from the recovery partition, and uses the device's hardware keys at boot time to select between Magisk-rooted Android and TWRP. A normal system boot from the boot partition brings the system up without root.
Rooting in the boot partition
When the device is rooted in the boot partition, the TWRP image is left untouched. Instead, the boot partition must be rooted with Magisk by flashing the Magisk zip file in TWRP. Rooted Android is booted via a normal system boot and the hardware keys play no special role. There is no option to boot Android unrooted.
Device preparation
Before doing anything else, back up your data now if you have any.
If you are installing TWRP on a brand new device, you must first unlock its bootloader. Select OEM Unlocking from Settings → Developer Options, then reboot to Device Unlock mode to actually unlock the bootloader. This will have the side-effect of resetting the device.
If you are installing TWRP on an unrooted device, it is crucial that you also flash the attached vbmeta.img file at the same time. Simply include this in a tar file with the TWRP image for your device (renamed recovery.img) and flash them together. You must reformat /data after doing this.
If you fail to neutralise the device's vbmeta protection before rebooting, the device's anti-tampering protection will be triggered and you will be unable to boot either Android or TWRP. A full reinstallation of stock firmware will be required and your device may be left in KG State Prenormal, requiring time-consuming extra steps to restore its ability to accept unofficial images again. Do not fail to neutralise vbmeta.
If you have already rooted your device with Magisk, vbmeta has already been disarmed and you may proceed with installing TWRP.
Image preparation
Rooting in the recovery partition
As noted above, the TWRP images supplied here are not pre-patched with Magisk. If you wish to dual-boot TWRP and Android Pie, you must patch the recovery image with Magisk before flashing it. Version 20.2 of Magisk is recommended for this. Versions 20 and 20.1 contain a serious bug that will render the recovery partition unbootable after patching. Please see John Wu's excellent step-by-step instructions for rooting the 2019 generation of Samsung Pie devices with Magisk.
An altogether simpler way of working is to flash the TWRP image on demand, only when required. After finishing your work in TWRP, simply replace TWRP with a Magisk-rooted stock recovery image and reboot to Android. I personally recommend this swapping approach, as it frees both the TWRP maintainer and the user from constantly updating the TWRP image to ensure it contains a kernel that is compatible with the version of the firmware on the device.
Here is a basic sample script that will check whether the current environment is Android or TWRP, flash the appropriate recovery image for the other environment, then reboot to it. You can easily adapt it to fit your needs.
Code:
twrp_img=/sdcard/twrp/twrp-3.3.1.img
stock_img=/sdcard/twrp/recovery-ask2-magisk.img
if [ -f /sbin/magisk ]; then
# We're in Android: Switch to TWRP.
#
infile=$twrp_img
else
# We're in TWRP: Switch to Android.
#
infile=$stock_img
fi
dd if=$infile of=/dev/block/by-name/recovery bs=$(stat -c%s $infile) && reboot recovery
Rooting in the boot partition
No special image preparation is required for installation on Android 10 devices.
TWRP images
TWRP is offered here as an assortment of recovery image files. To use with Odin, first rename the appropriate file recovery.img and then tar it. Ready-made tar files are not supplied here, because it would double the number of files to be maintained, and because it's trivial to generate a tar archive on any modern computing platform, including on the Fold itself.
Post-installation
The Fold, like all 2019 Samsung devices, utilises file-based encryption (FBE) by default. The use of encryption in TWRP on Samsung devices is invariably problematic, however, and encryption is therefore routinely disabled by users wishing to use TWRP. If this is not done, your files will remain unreadable to TWRP.
To remove encryption from your device, please flash the Samsung multi-disabler after installing TWRP, and then reformat /data again. Do not skip this step, even if you have already formatted /data one or more times thus far. If installing TWRP on Android 10, you need at least v2.3 of the multi-disabler.
Compatibility
The images below are known to be compatible with the firmware revisions stated. Results on other revisions will vary.
The F907B images have been personally tested and verified by me on my own Fold 5G prior to release. The F900F images should be of comparable quality.
Download
Android 10
Latest release for F907B (BTH2 firmware)
twrp-winnerx-3.5.0_9-1_ianmacd.img
twrp-winnerx-3.5.0_9-1L_ianmacd.img (landscape)
Latest release for F900F (BTH2 firmware)
twrp-winner-3.5.0_9-1_ianmacd.img
twrp-winner-3.5.0_9-1L_ianmacd.img (landscape)
Android 9
Latest release for F907B (ATA1 firmware)
twrp-winnerx-3.3.1-23_ianmacd.img
twrp-winnerx-3.3.1-23L_ianmacd.img (landscape)
Latest release for F900F (ATA3 firmware)
twrp-winner-3.3.1-23_ianmacd.img
twrp-winner-3.3.1-23L_ianmacd.img (landscape)
Known problems
TWRP is currently displayed only on the device's main (inner) screen.
Haptic feedback is currently unavailable in TWRP.
Frequently Asked Questions
Q. Why do you offer a separate build for each device with landscape orientation?
A. The aspect ratio of the main (inner) screen 4.2:3 is such that TWRP on this device looks good in both portrait and landscape orientation. In portrait mode, the clock and battery meter are shifted to the left to avoid the camera notch. In portrait mode, the entire image is shifted to the right to avoid the notch.
See the gallery of images below, or simply try each version of TWRP on your device, to discover which orientation you prefer.
TWRP source code
TWRP bootable recovery
TWRP device trees
Galaxy Fold a.ka. winner (F900F)
Galaxy Fold 5G a.ka. winnerx (F907B)
Kernel source code
Galaxy Fold a.ka. winner (F900F)
Galaxy Fold 5G a.k.a. winnerx (F907B)
Real-time chat
For support or just to talk about the device amongst friends, please join our small Telegram group dedicated to the Galaxy Fold.
Credits
I am indebted to Chris Williamson (@chrisaw) for laying the foundations for TWRP on the Fold. And thanks in no small part to him and his contagious enthusiasm for the device, I'm now also indebted to Samsung for the purchase price of a Fold 5G.
Thanks to @osm0sis for AIK, a tool without which working with boot images would be far more tedious than it already is.
Thanks to Samsung for engineering this amazing device in the first place.
And last but not least, thanks to my wife, Sarah, for her tolerance of my expenditure on gadgetry.
XDA:DevDB Information
TWRP for the Samsung Galaxy Fold, Tool/Utility for the Samsung Galaxy Fold
Contributors
ianmacd, chrisw
Version Information
Status: Stable
Current Stable Version: 3.4.0-4_ianmacd
Stable Release Date: 2020-10-05
Created 2019-11-20
Last Updated 2021-01-19
Gallery
Unlocked bootloader stage 1
Unlocked ootloader stage 2
Main menu
Making a back-up (in Dutch)
Main menu (landscape)
Instaling an image (landscape)
Changelog
3.5.0_9-1_ianmacd
Update to TWRP 3.5.0.
3.4.0-4_ianmacd
Use latest F907BXXS4BTH2 and F900FXXS4BTH2 kernel source code.
3.4.0-1_ianmacd
TWRP updated to version 3.4.0.
3.3.1-101_ianmacd
Use latest F900FXXU3BTDD and F907BXXU3BTDD kernel source code.
Kernel now built using clang 8.0.11.
3.3.1-100_ianmacd
First release supporting Android 10.
Use latest F900FXXU3BTCD and F907BXXU3BTC9 kernel source code.
3.3.1-23_ianmacd
Use latest F900FXXS3ATA3 and F907BXXS3ATA1 kernel source code.
3.3.1-22_ianmacd (F907B only)
Build kernel from latest F907BXXS2ASL3 source code.
3.3.1-21_ianmacd (F907B only)
Build kernel from latest F907BXXU2ASK9 source code.
3.3.1-20_ianmacd
Use latest F900FXXS2ASKC and F907BXXS2ASK2 kernel source code.
Build without crypto code, as crypto is unsupported.
MInor fstab fix for /data.
Disable sundry irrelevant kernel features for a slightly leaner kernel.
3.3.1-17_ianmacd
First ianmacd release, using F900FXXU1ASJ4 and F907BXXS2ASK2 kernel source code.
That was fast!
Sadly most of us can't afford this 2000$ phone lol
Selling my US version, time to get F900F
Version 3.3.1-20_ianmacd released.
This release upgrades the kernel from the latest Samsung source code. In the case of the F900F, there are significant changes, whereas the F907B's kernel is hardly differs from the previous version.
The builds have also been stripped of superfluous crypto code, and a harmless bug in the fstab has been fixed.
3.3.1-20_ianmacd
Use latest F900FXXS2ASKC and F907BXXS2ASK2 kernel source code.
Build without crypto code, as crypto is unsupported.
MInor fstab fix for /data.
Disable sundry irrelevant kernel features for a slightly leaner kernel.
ianmacd said:
This release upgrades the kernel from the latest Samsung source code. In the case of the F900F, there are significant changes, whereas the F907B's kernel is hardly differs from the previous version.
The builds have also been stripped of superfluous crypto code, and a harmless bug in the fstab has been fixed.
3.3.1-20_ianmacd
Use latest F900FXXS2ASKC and F907BXXS2ASK2 kernel source code.
Build without crypto code, as crypto is unsupported.
MInor fstab fix for /data.
Disable sundry irrelevant kernel features for a slightly leaner kernel.
Click to expand...
Click to collapse
Thank you for all your work !!!
help me plz
hello, I can't flash with Odin because it gives me an error message: blocked from the OEM.
Version 3.3.1-21_ianmacd released for the F907B.
Changelog
3.3.1-21_ianmacd (F907B only)
Kernel built from latest F907BXXS2ASK9 source code.
Hi ianmacd
I know this is off top, but couldn't private message you
On libsecure_storage companion for rooted Samsung devices ver. 2.0 I experienced strong connectivity issues with airpods 2 (on note 9), rolling back to 1.8 got working it ok. Just for your information
DTman22 said:
hello, I can't flash with Odin because it gives me an error message: blocked from the OEM.
Click to expand...
Click to collapse
Same here.. anyone can help ...?
Version 3.3.1-22_ianmacd for the F907B released.
Changelog
3.3.1-22_ianmacd (F907B only)
Build kernel from latest F907BXXS2ASL3 source code.
hi I tried to use the method but something wrong happened, now my f900f stuck on starting android and it won't start up .
how can I go to download mode .?
Note: the VOL_UP + Power bottom it's not doing anything, even if putting the cable into the phone while starting up ..
any solutions .. ?
I'M getting "custom binary blocked by OEM lock "
the OEM unlock in developer option is ON
model F900F
Any solution ?
thmthoom said:
I'M getting "custom binary blocked by OEM lock "
the OEM unlock in developer option is ON
model F900F
Any solution ?
Click to expand...
Click to collapse
All you have done by toggling that option under Developer Options is enable OEM-unlocking of the device. You haven't actually opened the lock yet.
Boot to Download Mode to actually open the lock.
See the OP for more details.
Sent from my SM-N975F using XDA Labs
ianmacd said:
All you have done by toggling that option under Developer Options is enable OEM-unlocking of the device. You haven't actually opened the lock yet.
Boot to Download Mode to actually open the lock.
See the OP for more details.
Sent from my SM-N975F using XDA Labs
Click to expand...
Click to collapse
Thanks for your response brother..
Actually I’m booting to download mode using K 300 tool .. because I cannot boot using VOLUP + POWER bottom .. so my question is :
1- how to open the lock through the download mode , coz I’m not getting any options there.
2- what do u mean by “ see the op for more details “
ianmacd said:
All you have done by toggling that option under Developer Options is enable OEM-unlocking of the device. You haven't actually opened the lock yet.
Boot to Download Mode to actually open the lock.
See the OP for more details.
Sent from my SM-N975F using XDA Labs
Click to expand...
Click to collapse
Brother , for Unlocking Bootloader these are the steps :
Allow bootloader unlocking in Developer options → OEM unlocking ( DONE )
Reboot your device to download mode. Either use adb reboot download, or use the key combo for your device. ( DONE )
Long press volume up to unlock the bootloader. This will wipe your data and automatically reboot. ( the volume up won't work in this step, only I can use Volume down+power to restart the phone )
So what to do in this case if you have any ideas ...
I Followed " John Wu's excellent step-by-step instructions for rooting the 2019 generation of Samsung Pie devices with Magisk. " STEP-BY-STEP these was the resutls :
1- I won't able to use VOL_UP bottom , I skip this step " I think this step caused me a lot of problems "
2- all other steps I'm getting ( boot ) locked OEM or ( vbmeta ) locked OEM
3- I tried to flash recovery alone
4- I tried to flash vbmeta alone
5- I tried to flash both recovery + vbmeta together
The result : FAIL
I think my main problem is unlocking the bootloader using VOL_UP key ..... How to do this while I don't have an option to use VOL_UP key.
even if i'm pressing the VOL_UP key for 1 Minute nothing happens .
you kindness solution will be appreciated
Any chance to have TWRP for F907N?
@ianmacd
First I'd like to say thank you for the work that you've done, and your intro was very well put and super kind to Chris. I know you likely have your hands very full, however I was wondering if you knew of any plans for the F900U or F900U1. I would like to reformat my AT&T phone so that I can get access to unlocking bootloader and hopefully use your TWRP, but I'm not sure if it would work.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hi there,
I prepared an alpha version of LineageOS 17.1/18.1 for Meizu E3 for your taste about it. Now it so more useable as dev-phone for outdoor YouTube viewing. Do play with it your own risk. I am not responsible any liability, nor any technical support too. So please think twice before taking action. AND be safe to backup ALL partitions before and action taken.
You can visit another thread of Meizu E3 unlock bootloader tutorial from your author, to unlock Meizu E3 without any external tool.
Instruction:
(0) to make it align with latest flyme v8000 fw, update system to v8000 is highly recommended. (20200926)
(1) get the phone unlocked bootloader as above mentioned.
(2)download below mentioned fw (boot.img.signed, system.img, vendor.img, recovery.img) in to a folder like "E3_LOS17.1", unzip and get "vendor_image.emmc.win", "system_image.emmc.win" and "boot.img.signed", rename them as boot.img, system.img, recovery.img and vendor.img
(3)hold power+vol_down and do "fastboot.exe boot recovery.img"
(4)in twrp, backup all partition to /sdcard, aka, "/sdcard/system.img", "/sdcard/persist.img"
(5)in host PC backup from phone and upload all above downloaded and unzip rom.img to phone, procedure like open cmd.exe, "mkdir E3", "cd E3/", "adb.exe pull /sdcard .", "adb.exe push E3_LOS17.1 /sdcard"
(6) twrp install, choose install img, select /sdcard/E3_LOS17.1/system.img, system partition, go
(7) twrp install, choose install img, select /sdcard/E3_LOS17.1/vendor.img, vendor partition, go
(8) twrp wipe, choose data partition, go (your data partition got WIPED, all data are LOST)
(9) wait above finish, go back to PC terminal, cmd.exe, issue "adb.exe reboot-bootloader", then "fastboot.exe boot boot.img"
(10) wait for LOS17.1 boots up
optional steps
(2a) you can choose to phh's quack build instead of jasmine_sprout system image as well. download it from phh's github release channel, unpack the zip, use simg->img tool to get regenerated system.ext2.img; check with linux "file" util and get
[email protected]:/mnt/jasmine_vendor# file /mnt/c/d_drive/whyred_temp/los17_20200111_phh_system.img
/mnt/c/d_drive/whyred_temp/los17_20200111_phh_system.img: Linux rev 1.0 ext2 filesystem data, UUID=05050abd-8baa-4dd4-905c-903071f9ac68, volume name "system" (extents) (large files) (huge files)
Click to expand...
Click to collapse
Note:
(1)Please sure to DO backup all the partitions
(2)Please sure DO NOT to flash boot.img to boot partition, every time use fastboot to boot into LOS17.1 thus can easily restore to flyme8 rom
(3)please sure when revert back flyme8, please DO use your own twrp backup to restore all partition is your first choice. Second choise is by flyme8's recovery from recovery partition, or at least the flyme8 recovery downloaded below. DO NOT use TWRP restore the flyme rom directly, and this can avoid many issues; otherwise you are compulsively to reflash flyme once again at least and all your data partition backup become useless; and if you force restore data partition, it wont help, due to internal hw keystore and crypto salt changes. so step (5) "adb.exe pull /sdcard/ ." is essential.
(4)use twrp recovery to restore data partition might not work at all. so once again, backup by using "adb.exe pull /sdcard ." is important. As said, some partition might get changed by bootloader and internal fw, so hw crypto and salt, keystore partition might get changed too after first boot LOS17.1; and you cant backup these partition at twrp screen operation. and even through if you are expert enough, restoring those partitions in adb shell also might not work at all due to same reasoning.
(5)using "adb.exe pull /sdcard ." is important! this is important so as i said 3 times.
(6)backup all partition by "adb shell" if possible. TWRP only list some of usual partition, and some rarely used partition are not listed. Like i suffered from persist partition wiped out and cant restore without a copy. so do a "dd if=/dev/block/bootdevice/by-name/XXX of=/sdcard/XXX" is a good idea.
(7)I had tried my best to make the all mount as "r/o" as possible, but i CANT guarantee all other partition are safe. So best is do as note(6) said.
Release Alpha 13
==================
Latest alpha release on LineageOS 18.1, camera is not working, check below for detail:
Release Alpha 13 · 99degree/android_vendor_meizu_m851q
This release (Alpha 13) is an alpha release that based on brand new Nokia PL2 LineageOS 18.1 release. Detail refer to below: https://lineageos.org/Changelog-25/ This release have an issue about cam...
github.com
Release Beta 2
==================
Latest stable ROM on LineageOS 17.1
Release Beta 2 (20210221) · 99degree/android_vendor_meizu_m851q
This release aimed to get entire system updated to Feb-05 Security bulletin. Changelog: Update to LineageOS Amber 20210214 Known issue: LineageOS clean (wipe data in TWRP) and first time startup wi...
github.com
Older release:
Release note 20210124
==================
Update dts and libmmcamera module. Camera should be alright, actuator is still in progress.
download release 20210126
Release note 20201214
==================
Update to CAF LA.UM.8.2.r2-03400-sdm660.0
Based on LineageOS Nokia PL2 Dragon build 20201208
This is no longer pure CAF due to adreno older fw logic fail.
Selinux enforced now on
Release note 20201011
==================
Update to CAF LA.UM.8.2.r2-02700-sdm660.0
LineageOS Amber 20201011 release, kernel is no longer pure rely on CAF anymore.
It is due to a adreno fw checking logic fail on older fw.
Release note 20200813
==================
Update to CAF LA.UM.8.2.r2-02500-sdm660.0
LineageOS Amber 20200809 release
Release note 20200705
==================
Some sensors are available.
external speaker (TAS2560 SmartAmp) functioning.
Release note 20200701
==================
(1)Special release! Voice-out-loud for social injustice!
(2)Mobile feature enablement
https://github.com/99degree/LineageOS/releases/tag/20200701
Release note 20200613
==================
First version with earphone sound playing. So YouTube is more than possible! This version shifts to official LineageOS.org Yandex Amber build
https://mirrorbits.lineageos.org/full/Amber/20200607/lineage-17.1-20200607-nightly-Amber-signed.zip
Release note 20200303
==================
Workaround the wifi problem, now wifi is working. boot.img.clear is updated.
Release note 20200223
==================
This is a ported version of LineageOS 17.1 based on this thread so you can download the original version of the build over there. In case of preference in phh's treble quack release, it seemed system.img is working well too.
The solo modification in vendor.img included:
(A) fstab.qcom to disable persist partition mount by "r/o", so no longer as "r/w" mode in order to protect it against lost wifi firmware, lost signal, mac address etc.
(B) replace all file lived in /vendor/firmware/* with flyme8's
The modification in system.img:
NIL
Things verified to work:
LCD PANEL
TOUCH PANEL
BLUETOOTH
USB
CHARGING
WIFI
vibration
earphone w/button
mobile feature
speaker and incoming ringing
GNSS
sensors (luminous, proximate, compass, magnet)
selinux-enforced
front camera
back imx362 camera
back imx350 camera(not tested)
Things not working:
those not listed above is considered not working
ROM download:
https://github.com/99degree/android_vendor_meizu_m851q/releases/tag/20210418 for LOS18.1
https://github.com/99degree/android_vendor_meizu_m851q/releases/tag/20210221 for beta 2
release 20210126
release 20201214
https://github.com/99degree/LineageOS/releases/tag/20201011
https://github.com/99degree/LineageOS/releases/tag/20200813 for boot.img and recovery.img
https://github.com/99degree/LineageOS/releases/tag/20200705 system and vendor image
https://github.com/99degree/LineageOS/releases/tag/20200701
https://github.com/99degree/LineageOS/releases/tag/20200613
https://github.com/99degree/LineageOS/releases/tag/20200223
https://github.com/99degree/LineageOS/releases/tag/20200303 for boot.img.clear
Repositories:
https://github.com/99degree/
kernel https://github.com/99degree/android_kernel_meizu_m851q
vendor & release https://github.com/99degree/android_vendor_meizu_m851q
So if you wanted to cook it yourself, please find necessary file with you. All needed files are hosted either in GitHub and LineageOS official Amber/PL2 build),
Please consider to show your support by donation or even YouTube clicks. Last and most importantly, happy ROM flashing and stay away from corona-virus outbreak!
Regards,
99degree
Can you public source code of kernel with device driver? Thank mate
thinhx2 said:
Can you public source code of kernel with device driver? Thank mate
Click to expand...
Click to collapse
Yes, I am on the way to clean up those code. once ready will upload to github and take vlog. Stay tuned.
99degree said:
Yes, I am on the way to clean up those code. once ready will upload to github and take vlog. Stay tuned.
Click to expand...
Click to collapse
Nice sir
99degree said:
...
kernel https://github.com/99degree/android_kernel_meizu_m851q
...
Regards,
99degree
Click to expand...
Click to collapse
How did you manage to port the kernel from code aurora? Any guide or so? I have Santin K1 (almost the same hardware as meizu) Wanna try to port kernel source.
Spencer_D said:
How did you manage to port the kernel from code aurora? Any guide or so? I have Santin K1 (almost the same hardware as meizu) Wanna try to port kernel source.
Click to expand...
Click to collapse
No! Not the way you through. I managed to clone kernel from CAF and search for hardware info. By app "device info hw", google and find some public available driver (basically touch driver and sound driver), add them to CAF tree then analysis the device tree dtb->dts difference. Move them to new dtsi and compile it with kernel as a whole. Then make use of LineageOS Yandex Amber ROM, modify and make it boots into LineageOS, that's it.
So best wish your development on SantinK1.
⚠ This project is no longer maintained. See below. ⚠
You are encouraged to migrate to the official nightly builds (huge thanks to @anishpratheepan and to the LOS team for bringing that up). If you update from an unofficial build, it is highly recommended that you opt-in for build signature check after the flash:
Open Settings
Privacy => Trust
Check "Build signature" at the very bottom
Note that you should be able to update from unofficial to official builds seamlessly, without wiping anything.
-----
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
LineageOS is a free, community built, aftermarket firmware distribution of Android 10, which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Instructions:
Unlock your bootloader
Backup everything, especially the "persist" partition
Make sure you're on a recent version of OxygenOS.
Download the latest build
Run the following commands:
Code:
adb reboot bootloader
fastboot flash recovery recovery.img
fastboot reboot fastboot
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash odm odm.img
fastboot flash product product.img
fastboot flash system system.img
fastboot flash system_ext system_ext.img
fastboot flash vbmeta vbmeta.img
fastboot flash vbmeta_system vbmeta_system.img
fastboot flash vendor vendor.img
fastboot reboot recovery
Wipe all data from recovery.
(Optional) If you need GApps, NikGApps Core are known to work ("Apply update" => "Update from ADB", and then run adb sideload <NikGapps-xxx-arm64-11-yyy.zip>). Note that other variants than Core can crash.
Reboot.
Downloads:
https://drive.google.com/drive/folders/1V17qsn_wMpwPgJHMhCjfYYmZEPGzPvP2
Known issues:
Displays "Charging slowly" when it's actually not
Build signed with public keys for now
Reporting Bugs:
Make sure the bug you want to report isn't already known
DO NOT Report bugs if you're running a custom kernel or you installed Xposed
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
If it is a random reboot, grab /proc/last_kmsg. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues. Any bug not reported in the bug report format below may be ignored.
Code:
What is your--
LineageOS version:
LineageOS Download url:
Gapps version:
Did you--
wipe:
restore with titanium backup:
reboot after having the issue:
Are you using--
a task killer:
a non-stock kernel:
other modifications:
Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
XDA:DevDB Information
[ROM][UNOFFICIAL][instantnoodle][11] LineageOS 18.1, ROM for the OnePlus 8
Contributors
KennyG9, LuK1337
Source Code:
Since February 2021 (based on the official LineageOS device tree):
Device tree: https://github.com/LineageOS/android_device_oneplus_instantnoodle
Kernel: https://github.com/LineageOS/android_kernel_oneplus_sm8250
Proprietary blobs: https://github.com/TheMuppets/proprietary_vendor_oneplus
Before February 2021 (based on LuK1337's work on instantnoodlep with minor adjustments to the device tree):
Device tree: https://gitlab.com/nlr/android_device_oneplus_instantnoodle
Kernel: https://github.com/luk1337/android_kernel_oneplus_sm8250
Proprietary blobs: https://github.com/luk1337/proprietary_vendor_oneplus
ROM OS Version: Android 11
ROM Kernel: Linux 4.x
Version Information
Status: Testing
Created 2021-01-07
Last Updated 2021-02-10
Very cool. Stoked. Can you add link for gapps as I know lineage needs to work properly.
mattie_49 said:
Very cool. Stoked. Can you add link for gapps as I know lineage needs to work properly.
Click to expand...
Click to collapse
I don't have GApps myself and I don't want to flash them on my personal device. I'm fine with adding a link in the original post provided that one or two person can confirm it works and provide instructions. I think NikGApps are the best candidate.
KennyG9 said:
I don't have GApps myself and I don't want to flash them on my personal device. I'm fine with adding a link in the original post provided that one or two person can confirm it works and provide instructions. I think NiksGApps are the best candidate.
Click to expand...
Click to collapse
Fair enough. Thank you for bringing this to the op8 community.
I made an attempt to bundle OpenGApps into the build: https://drive.google.com/file/d/1edechrEwpX5L5SjE6OlsAjRckT-UF69t/view (using https://github.com/opengapps/aosp_build). It bootlooped on my device but I suspect that's because it requires a factory reset which I didn't want to do. Flashing instructions are identical, just make sure you have flashed OOS 11 at some point. If that happens to work for some of you, I'll try to publish both flavors with every release.
KennyG9 said:
I made an attempt to bundle OpenGApps into the build: https://drive.google.com/file/d/1edechrEwpX5L5SjE6OlsAjRckT-UF69t/view (using https://github.com/opengapps/aosp_build). It bootlooped on my device but I suspect that's because it requires a factory reset which I didn't want to do. Flashing instructions are identical, just make sure you have flashed OOS 11 at some point. If that happens to work for some of you, I'll try to publish both flavors with every release.
Click to expand...
Click to collapse
"Flash OOS 11 at some point"
What about upgrading from 17.1 ?
Also - Why no OOS 10 - 18.1?
mobile_sensei said:
"Flash OOS 11 at some point"
What about upgrading from 17.1 ?
Also - Why no OOS 10 - 18.1?
Click to expand...
Click to collapse
LOS builds only contain a few subset of all the partitions that exist on the OP8 (system, boot, product, dtbo, and some others). The OP8 also contains a lot of other proprietary partitions (ABL, AOP, bluetooth, modem, etc…) that only the manufacturer is able to provide updates for. As far as I understand, those blobs must also be updated to be able to run Android 11 without issues. If you don't update them, it'll likely bootloop or refuse to boot and it's not recommended anyways.
I'm not sure upgrading from 17.1 to 18.1 without wiping is even possible, but if you want to give it a shot, I think your best bet is to extract all the proprietary images from a recent OOS build, then flash them and flash LOS 18.1 over that. You may avoid the annoying MSM step, but my bet is that you'll have to wipe anyways if you want to boot, so I strongly advise that your backup all your data and apps before. In deeper details, you need to :
- get a recent and official OOS 11 build from here : https://www.oneplus.com/support/softwareupgrade/details?code=PM1586920535300
- extract the payload.bin from the image using a tool like this one : https://github.com/LineageOS/scripts/blob/master/update-payload-extractor/extract.py
- reboot to bootloader (adb reboot bootloader)
- flash the stock recovery you just extracted (fastboot flash recovery recovery.img)
- reboot into stock fastboot (fastboot reboot fastboot)
- flash all the blobs you just extracted (fastboot flash abl abl.img && fastboot flash aop aop.img && fastboot flash bluetooth bluetooth.img && ………)
- follow LOS 18.1 flashing instructions from the first post
mobile_sensei said:
"Flash OOS 11 at some point"
What about upgrading from 17.1 ?
Also - Why no OOS 10 - 18.1?
Click to expand...
Click to collapse
Yes I agree here.
I and need step by step exact instructions how to flash any rom here.
I am not even gonna try to flash this rom because I know my device is gonna end up at the Qualcomm dump mode.
I can't get anything booted if I flash anything coming from OOS11, don't ask because I have no idea why.
The only way to get my device booting stock rom at this point is to flash stock rom in EDL mode with the msm tool
[OP8][OOS 21AA/BA/DA] Unbrick tool to restore your device to OxygenOS
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been...
forum.xda-developers.com
My device is OnePlus 8 5G - 12GB/256GB Interstellar Glow- Firmware : Firmware: OxygenOS - GE / EN / FR / ES
IN2010
Inspected 2020.06.18
As TWRP isn't working completely is there way to do the equivalent full system backup with all partitions without TWRP perhaps via fastboot? Because I know I'm not gonna be able to flash a rom its gonna be the same story over and over again setting up the same stock rom over again ..it gets old.
Because custom software for OnePlus 8 is not at the stage of flash and forget I think a unified toolkit in a zip is needed.
It can be separate or bundled with each rom release and regularly updated that I can extract and cd into, and run the fastboot commands from to help making flashing roms and debug as accurate as we possibly can starting with all of us using the same exact toolkit to begin with.
Driver used
Developer framework ie fastboot, adb executable
Payload dumper
Readme File
Bat/sh file for automation
perhaps payload/img files
bundled with rom Gapps with dev, flavor and release because this seem to be subject to not booting
This would make sure everyone is 100% following the same exact instructions making debugging much easier, in this case it seem like gapps one piece of the puzzle possibly preventing rom from booting, in my case I'm can't even make it to square one getting stuck at Qualcomm dump mode..
Spoiler
KennyG9 said:
LOS builds only contain a few subset of all the partitions that exist on the OP8 (system, boot, product, dtbo, and some others). The OP8 also contains a lot of other proprietary partitions (ABL, AOP, bluetooth, modem, etc…) that only the manufacturer is able to provide updates for. As far as I understand, those blobs must also be updated to be able to run Android 11 without issues. If you don't update them, it'll likely bootloop or refuse to boot and it's not recommended anyways. I'm not sure upgrading from 17.1 to 18.1 without wiping is even possible, but if you want to give it a shot, I think your best bet is to extract all the proprietary images from a recent OOS build, then flash them and flash LOS 18.1 over that. You may avoid the annoying MSM step, but my bet is that you'll have to wipe anyways if you want to boot, so I strongly advise that your backup all your data and apps before. In deeper details, you need to : - get a recent and official OOS 11 build from here : https://www.oneplus.com/support/softwareupgrade/details?code=PM1586920535300 - extract the payload.bin from the image using a tool like this one : https://github.com/LineageOS/scripts/blob/master/update-payload-extractor/extract.py - reboot to bootloader (adb reboot bootloader) - flash the stock recovery you just extracted (fastboot flash recovery recovery.img) - reboot into stock fastboot (fastboot reboot fastboot) - flash all the blobs you just extracted (fastboot flash abl abl.img && fastboot flash aop aop.img && fastboot flash bluetooth bluetooth.img && ………) - follow LOS 18.1 flashing instructions from the first post
Click to expand...
Click to collapse
Good information, I didn't finish my reply during breakfast and noticed you wrote one more.
The only thing I am not comfortable with is that there are links to tools that I have to download from the internet.
Its one factor subject to being sourced from random google searches.
Like the fastboot binary from xda although old doesn't work on op8, I found out the hard way and I am now downloading this directly from Android developer page.
But a lot of headache could be eliminated trying to figure out where and which binaries should be used, what work and what does not.
Is fastboot/adb bundle too old or driver not installed?
Did all of us follow the exact same installation steps in detail the rom developer did?
I hope you understand.
This device has been the most problematic I've ever dealt with
SUPERUSER said:
Yes I agree here.
I and need step by step exact instructions how to flash any rom here.
I am not even gonna try to flash this rom because I know my device is gonna end up at the Qualcomm dump mode.
I can't get anything booted if I flash anything coming from OOS11, don't ask because I have no idea why.
The only way to get my device booting stock rom at this point is to flash stock rom in EDL mode with the msm tool
[OP8][OOS 21AA/BA/DA] Unbrick tool to restore your device to OxygenOS
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been...
forum.xda-developers.com
My device is OnePlus 8 5G - 12GB/256GB Interstellar Glow- Firmware : Firmware: OxygenOS - GE / EN / FR / ES
IN2010
Inspected 2020.06.18
As TWRP isn't working completely is there way to do the equivalent full system backup with all partitions without TWRP perhaps via fastboot? Because I know I'm not gonna be able to flash a rom its gonna be the same story over and over again setting up the same stock rom over again ..it gets old.
Because custom software for OnePlus 8 is not at the stage of flash and forget I think a unified toolkit in a zip is needed.
It can be separate or bundled with each rom release and regularly updated that I can extract and cd into, and run the fastboot commands from to help making flashing roms and debug as accurate as we possibly can starting with all of us using the same exact toolkit to begin with.
Driver used
Developer framework ie fastboot, adb executable
Payload dumper
Readme File
Bat/sh file for automation
perhaps payload/img files
bundled with rom Gapps with dev, flavor and release because this seem to be subject to not booting
This would make sure everyone is 100% following the same exact instructions making debugging much easier, in this case it seem like gapps one piece of the puzzle possibly preventing rom from booting, in my case I'm can't even make it to square one getting stuck at Qualcomm dump mode..
Good information, I didn't finish my reply during breakfast and noticed you wrote one more.
The only thing I am not comfortable with is that there are links to tools that I have to download from the internet.
Its one factor subject to being sourced from random google searches.
Like the fastboot binary from xda although old doesn't work on op8, I found out the hard way and I am now downloading this directly from Android developer page.
But a lot of headache could be eliminated trying to figure out where and which binaries should be used, what work and what does not.
Is fastboot/adb bundle too old or driver not installed?
Did all of us follow the exact same installation steps in detail the rom developer did?
I hope you understand.
This device has been the most problematic I've ever dealt with
Click to expand...
Click to collapse
I don't have a definitive answer to everything, but here are some remarks:
- Not sure what exactly your problems were and I'm unaware of any way to backup partitions using fastboot unfortunately. As far as I know, it was not possible to restore nandroid backups using mauronofrio's TWRP on Android 10 either. I think the best you can achieve for now is software and data backup (using "adb pull" and "OAndBackup+" or something else). I can also attest that I had way more weird partitioning issues when using TWRP than LOS' fastboot. Since I stopped using TWRP, I never had to use MSM again.
- What you may attempt to reduce the risk of bricking your device is to take advantage of the A/B partitioning. You can flash everything on the unused slot and switch back to the working slot if anything goes wrong. This can be done by running "fastboot getvar current-slot" to get the current slot, then "fastboot --set-active=a" to switch to slot a (or "fastboot --set-active=b" to switch to slot b, depending on which slot was active).
- I second your reluctance on using tools coming from untrusted sources. Please, don't get fastboot/adb from XDA, use the official Android builds. I can't help you regarding the drivers as I use Linux which ships with drivers, but if you use Windows try to get those drivers from either Microsoft, OnePlus or Qualcomm directly. My instructions to avoid flashing Android 11 with MSM makes you use an official image from OnePlus (which you have to trust anyways) + an open-source tool that's made by LOS developers (which you have to trust anyways). At this point, I think the weakest point of trust if you don't want to build LOS yourself is me.
- Regardless of what you attempt, always make sure you have backups of your valuable data, apps and persist partition. Especially given how capricious this device is .
working great so far. any way to re-enable the 90Hz refresh rate?
edit: found it in display options!
LuK1337 said:
OP8 is no longer supported so RIP.
Click to expand...
Click to collapse
New flash method for both 8p and 8t does not allow to use it on instantnoodle, migrated yesterday from there to this build and it's working perfect with NikGapps-core and Magisk, great job @KennyG9
any way to get the OP camera app working? tried several versions available on APKMirror, but all seem to crash. maybe there are some dependencies?
Does OnePlus 8 tmobile version work with dual sim on this rom?
veridiam said:
any way to get the OP camera app working? tried several versions available on APKMirror, but all seem to crash. maybe there are some dependencies?
Click to expand...
Click to collapse
There's a lot of proprietary software/firmware (apart from the camera apk itself) that its not included in LOS. There have been some ports in the past (e.g. OnePlus6 OOS Camera port or oxy-ify) but all of them seem dead, maybe because google camera port working out of the box.
Creating a magisk module should be doable, but you need to start the app, let it crash and add the missing dep N times until you have all of them
@LuK1337 , please accept pull request: https://github.com/luk1337/android_kernel_oneplus_sm8250/pull/1
Running great. I would mention that only nikgapps core works. The rest for me ended in a crash whilst setting up.
passion8059 said:
Running great. I would mention that only nikgapps core works. The rest for me ended in a crash whilst setting up.
Click to expand...
Click to collapse
Thanks, just updated first post to mention that.
KennyG9 said:
Thanks, just updated first post to mention that.
Click to expand...
Click to collapse
Would you be able to look into face unlock? Handy feature for me especially at work.
passion8059 said:
Would you be able to look into face unlock? Handy feature for me especially at work.
Click to expand...
Click to collapse
Face unlock is an OxygenOS feature and I don't think AOSP or LineageOS supports something like that officially as it's quite terrible security-wise. GApps also dropped support for face unlock in Android 10 because of security concerns. So unless I'm missing something it probably won't happen anytime soon unless through some third-party module, sorry. It's not just about porting some blobs, it's a whole new OS feature.
Is WiFi calling and LTE calling working?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Lenovo Tab3 8 Tablet
Models: TB3-850F/M
TWRP 3.6.0_9-0OVERVIEW
The TWRP ports currently available for the Lenovo Tab3 8 are outdated by a number of years and are lacking in official support for more recent Android release versions. TWRP 3.6.0_9-0 was originally compiled using the Android 9 tree, and therefore supports all Android versions up to, and including, Android 9 Pie. This custom recovery build also includes improved manageability of Android supported filesystem standards, better protection against data loss and corruption, added functions, and improved theming support. Likewise, I've made several bug fixes and cleaned up the codebase. To read a more in-depth list on the changeling of TWRP 3.6.0, visit this link the official TeamWin site here: TWRP 3.6.0 Release Notes
REQUIREMENTS
First and foremost, you need an unlocked bootloader. There are a plethora of guides hosted here on XDA that provide detailed instructions for standard bootloader unlocking. If your tablet is not yet unlocked, go ahead and complete that task and return here once finished. Secondly, you will need a Windows PC or laptop with the SDK platform tools installed or, alternatively, the Minimal ADB & Fastboot tools (link provided below). Note that a Linux or Mac machine may also be used; for purposes of this guide, however, I will be focusing solely on a Windows setup. Next, you will need an internet connection to download the files provided in the links below. Lastly, you will need the factory supplied or a quality equivalent USB-A to micro USB data syncing/charging cable.
COMPATIBILITY
This TWRP custom recovery is compatible with both hardware variants (80 & 81) of the TB3-850F model, as well as the TB3-850M 4G-LTE supported model.
DISCLAIMER
Installing a custom recovery on an Android mobile device is an invasive procedure in terms of the modifications made to the stock partition index. Flashing the partitions of your device is a task that encompasses the inherent risk of bricking or otherwise rendering your device inoperable. By proceeding further, you are assuming sole responsibility for the integrity and operability of your tablet. Follow the instructions carefully, employ some patience, and things should go smoothly. I would encourage inexperienced members to read this guide in full prior to starting the instructions.
INSTRUCTIONS:
Download the Minimal ADB & Fastboot tools from the below link and install the program on your Windows PC & laptop. Next, open your Windows File Explorer, open your C: drive, then open Program Files x86. Copy the Minimal ADB & Fastboot folder and paste it to your desktop. (Copying the directory to the desktop isn't required, but does configure the ADB & Fastboot path to a more convenient directory from which to work);
Download TWRP 3.6.0_9-0 from the below link and save the image file in your ADB & Fastboot folder on your computer;
Boot your tablet into fastboot mode as follows: with your tablet booted into the Android OS, ensure ADB Debugging is enabled in the Developer Options menu. Connect the tablet to your PC using a sufficient USB-A to micro USB syncing/charging cable;
Open the ADB & Fastboot folder on your computer. Double click cmd-here.exe to open a command window, and execute the following command:
Code:
adb reboot bootloader
Your tablet may prompt you to authorize the ADB connection;
If properly connected your Tab3 8 will boot into fastboot mode, which will be indicated by the status displayed on the tablet. To verify proper fastboot communication between your computer and tablet, execute this command:
Code:
fastboot devices
If everything is set up properly, the command window will return an alphanumeric string consistent with your tablet S/N;
If your S/N isn't displayed, or if your are given a WAITING... notification, your tablet is not being recognized correctly. Change USB ports, try a different data syncing cable, and/or update your fastboot drivers;
Once a solid connection has been verified, execute the following command to flash TWRP to your tablet:
Code:
fastboot flash recovery twrp.img
(The TWRP file you downloaded below is named twrp.img. The above flashing command assumes that you have left the filename unchanged.);
You may now boot your tablet into TWRP recovery mode by executing:
Code:
fastboot boot twrp.img
Task complete. You should now running TWRP 3.6.0_9-0 on your Lenovo Tab3 8 device.
DOWNLOADS:
• TWRP 3.6.9_9-0 Lenovo Tab3 8
• Minimal ADB & Fastboot Tools v1.4.3
THANKS & MENTIONS:
First and foremost, thanks to TeamWin Recovery Project for providing the base build, and for their many years of hard work and contributions to the custom Android community. Thanks to the XDA members who remain dedicated to the Lenovo Tab3 8 and its continuing development projects. Although I'm slow, I have two more projects in the works for our beloved tablets. Thank you for your patience my friends.BUGS:Please leave a comment detailing any bugs or instabilities you may encounter. I will diligently try to patch and fix any reported bugs.
Hi,
I flashed TWRP v3.4.1-0 from your link but I end up in a boot loop where I fail to mount any of the partitions.
The DL Link for TWRP v3.6.0_9-0 seems to be broken. Do you have an alternate for that?
Note: I'm working on a TB3-850F.
Thanks!
Okay I think dm-veriry is to blame. If you mounted /system after installing TWRP, dm-veriry will be triggered and the device will boot loop.
You need to flash a dm-verity disabler. I'll get you a link .
Any chance you might also have a link to the updated twrp you had linked above? It's a dead link now.
Diznatch52 said:
Any chance you might also have a link to the updated twrp you had linked above? It's a dead link now.
Click to expand...
Click to collapse
Sure. I'll fix the link
Ok link is fixed. Follow these steps.
Warning: This will wipe all data from your device.
Download the no-veriry_opt encrypt file linked below and save it to an external micro SD card. Insert the micro SD in your TB3-850F;
Install TWRP v3.6.0_9-0 and reboot recovery;
Select Wipe, Format Data, and swipe to commence.
Select Install and navigate to the saved location of the no-verity zip you downloaded in Step 1. Select the zip and swipe to commence installation.
Reboot system
no-verity_opt-encrypt_v6.1.zip
If you want root access of the Android OS, install a Magisk systemless root script after Step 4.
Awesome! I'll give it a shot.
Diznatch52 said:
Awesome! I'll give it a shot.
Click to expand...
Click to collapse
Download Magisk v24.3 from this link https://mega.nz/file/4c43FbwS#Qd-pKoupa8LZ-EI9qe5Zsr3L4rSz8NDv2Ojknrd8sCk
Install it after Step 4 if you want root. After you are booted, you can update Magisk to the latest v25.2 using the Direct Install option.
For some reason, after this process, running `adb reboot recovery` brings me to an android crash screen. Any idea why?
To confirm, this procedure did work and you were able to boot into the OS? Once you confirm I'll try to resolve your ADB issue.
Yes.
Diznatch52 said:
Yes.
Click to expand...
Click to collapse
Ok download the official TWRP App, grant it root permission, and flash the TWRP v3.6.0_9-0 to the recovery partition. Reboot your tablet and then try the adb reboot recovery command again.
When you flashed the original TWRP with fastboot, did you immediately boot into recovery and flash TWRP again using the Install>Image option?
As soon as I unbrick this again, I'll give it a shot
Edit: booting into recovery now gives me twrp! Thanks so much!
Now time to see if I have better luck flashing lineageOS
IT WORKED!
Thank you so much!
Anytime friend. Glad it worked out.
Update: December 13, 2022.
I am presently working on bumping TWRP up to v3.7.0_9-0.
The v3.7.0 base build includes Python support for Android Oreo & newer versions.; keymaster API V1 fixes; fixes on copying sepolicy on devices with no /vendor partition; several fixes on custom theme support as well as perfected ROM multiboot functionality. Also, I am updating my implementation of PIGZ compression for data transfer speed improvements and enhanced protection against data corruption. Stability improvements and minor bug fixes also included.
I will keep the OP updated with an ETA.
Diznatch52 said:
IT WORKED!
Thank you so much!
Click to expand...
Click to collapse
I have a build of LineageOS 14.1 that I optimized, fixed some bugs and removed settings entries on SIM cards & mobile networks. Open source libraries have been updated and the security patch level bumped up to June, 2022. GApps have been removed and several performance enhancements have been added. I'm without a working 850F at this time, but I should have a working device soon. I will post the LOS 14.1 build as soon as I can fully test it.
Diznatch52 said:
IT WORKED!
Thank you so much!
Click to expand...
Click to collapse
I have a build of LineageOS 14.1 that I optimized, fixed some bugs and removed settings entries on SIM cards & mobile networks. Open source libraries have been updated and the security patch level bumped up to June, 2022. GApps have been removed and several performance enhancements have been added. I'm without a working 850F at this time, but I should have a working device soon. I will post the LOS 14.1 build as soon as I can fully test it.
Oh, I nearly forgot, would you care to list your stock firmware build number please. Thanks
That would be incredible. I don't know if I still have access to my stock firmware build. I've already got a version of LOS 14.1 (could admittedly be snappier) installed. If you tell me how to find it, happy to send it over.
I just meant on your 850F, go to device settings, about tablet, and let me know your build number. Thx