Database Develop

[ROM] [OFFICIAL] LineageOS for the Shield Portable

{
"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 6.0.1 (Marshmallow), 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 :
Download the latest build and gapps
Reboot to recovery
Flash the latest build and gapps
Reboot
Downloads :
Builds : https://download.lineageos.org/roth
Root addon : https://download.lineageos.org/extras
Google Apps : http://opengapps.org/
Reporting Bugs
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 /sys/fs/pstore/console_ramoops. (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:
Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
XDA:DevDB Information
LineageOS for the Shield Portable, ROM for the Nvidia Shield
Contributors
Steel01
Source Code: https://github.com/LineageOS
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.4.x
Version Information
Status: Nightly
Current Stable Version: 13.0
Created 2017-02-25
Last Updated 2017-02-25

Wow nice work! Thanks for porting Lineage OS to Nvidia Shield Portable. So before I want to do download and install it... Does everything work? The Nvidia controller, Power button, etc?

edtide25 said:
Wow nice work! Thanks for porting Lineage OS to Nvidia Shield Portable. So before I want to do download and install it... Does everything work? The Nvidia controller, Power button, etc?
Click to expand...
Click to collapse
All the hardware works, yes. Some of the software features aren't ported like touch mapping for the gamepad, wireless controller support, gamestream, etc. But for the normal use cases I have of retroarch, a handful of controller enabled native games, and kodi, everything works beautifully. So, depends on your use cases.

Is this full android or ATV like the one you built for me?

This is a normal build. Probably won't do atv for officials unless the userbase really asks for it. Need to fix gapps before that would even be considered, though. Only 32 installs atm, and half of them are probably me testing.
So, haven't had a bootloop on the new build myself. Anyone having any troubles at all? Seeming really solid to me finally.

When using snes9x ex the performance is way down in comparison to nvidia update 110. The screen refresh rate as reported in the emulator is 48.85hz. If that's correct its far too low.
In addition there appears to be another bug where ui animations stutter and loop back a few frames on themselves. Not sure if this is related to the apparent refresh rate issue.
I would also like to chime in on the possibility of an atv build. Without the right stick mouse functionality of the stock firmware the tv interface makes a whole lot more sense.
Thanks for the build and the work you've put in on this and fixing nvidia messes over the years.

That's great to know!!
Once they manage to port the touchmapper and some other software from this device to it, I'm pretty sure to stick with it forever.
I'm using lineage at my MotoG3 and i'm lovng git!!

Thanks for this. I just installed it. I had been running your 12.1 CM ROM the last week. I decided to try it out after had enough of the buggy stock ROM. I would install apps, and they would (seemingly) randomly disappear. I would install them over and over again. Anyways, your custom builds of CM/Lineage have been working beautifully.
The only thing that I'm really missing is the gamepad touch mapper. I know you've said that you don't use it, but it seriously hurts not having it, because you can so quickly and easily make most touchpad only games work so quickly and easily.

Ziontist said:
The only thing that I'm really missing is the gamepad touch mapper. I know you've said that you don't use it, but it seriously hurts not having it, because you can so quickly and easily make most touchpad only games work so quickly and easily.
Click to expand...
Click to collapse
The problem is that Nvidia's touch mapper is mostly in the stock framework. That's code I don't have access to and even if I was interested in trying, I don't have near the time needed to try and recreate it. And tincore is still an option. I know it's a major pain to set up, but it does work.

Steel01 said:
The problem is that Nvidia's touch mapper is mostly in the stock framework. That's code I don't have access to and even if I was interested in trying, I don't have near the time needed to try and recreate it. And tincore is still an option. I know it's a major pain to set up, but it does work.
Click to expand...
Click to collapse
Gotcha. What a shame. I guess Tincore Mapper it is. It seems like something that probably is really awesome, once you invest the time into learning it. There's probably way more in depth options and things you can do with it, than Nvidia's mapper (but I'll still miss the ease and convenience lol).

Hello,
Are there any plans to get Noughat on board of Nvidia Shield Portable?
thank you

Well, good news. I actually got the portable to boot N / 14.1. Bad news. It's a jerky mess. I took the advice of one of the other Tegra 4 devs and stuffed the blobs from the Jide Ultratablet in there. Flipped a couple flags, and voila, it boots. No sound, no touch, and quite jerky. But at least I finally found a graphics stack that works. I can work with that, find out which specific pieces I need to pull of the graphics stack and leave the other Roth stuff in place. Should be able to make it usable. No guarentees on when, but I'll keep working on it.

Is it somehow possible in this rom tu use nvidia's shield hub app to use gamestream and geforce now? When you install and run the app those options dissapear from the app. I know I can use moonlight to stream, just curious why it doesn't work on this rom, maybe the app detects that it's not an official firmware and disables it or some libraries missing?

Try installing nvidia games from google play.

Yeah tincore mapper is a pita the stock nvidia mapper is way easier.

For the these two platform, which do I download? Cause last time I tried to update, the device was bricked and somehow magically started up today and went back to thinkering with my shield lol
i'm currently on android 6.0.1 with CyanogenMod Version 13.0 Nightly build
Root addon : https://download.lineageos.org/extras
Google Apps : http://opengapps.org/

What's different between this and CM13?

Lineage is the continuation of CM. No one is working on CM anymore.
@danny_boi: Unfortunately flashing from CM to Lineage official builds will require a wipe due to a change in signing keys. Then you want the 13.0 arm su zip and one of the arm 6.0 opengapps packages. I personally use micro, which I also believe is the largest that will fit on this devices small system partition.

painkiller_93 said:
Is it somehow possible in this rom tu use nvidia's shield hub app to use gamestream and geforce now? When you install and run the app those options dissapear from the app. I know I can use moonlight to stream, just curious why it doesn't work on this rom, maybe the app detects that it's not an official firmware and disables it or some libraries missing?
Click to expand...
Click to collapse
fr500 said:
Try installing nvidia games from google play.
Click to expand...
Click to collapse
Hello about to flash this rom and wanted to findout if the shield hub works as this is not mentioned when I searched. Does installing nvidia games from Google play work please?

marvi0 said:
Hello about to flash this rom and wanted to findout if the shield hub works as this is not mentioned when I searched. Does installing nvidia games from Google play work please?
Click to expand...
Click to collapse
You can install the app from the play store but it won't show you the options to use gamestream or geforce now. If you want to use gamestream you can install moonlight app.

[OFFICIAL] [WEEKLIES] Lineage OS 15.1

{
"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"
}
Moto Z2 Force
Code:
- Your warrenty is now void.
- You have been warned.
- Use at your own risk.
Introduction:
This is the official Lineage OS thread for the Motorola Moto Z2 Force, codename nash.
We support both the Sprint, International, and T-Mobile variants, as their bootloaders are unlockable, while we can 't support the Verizon and AT&T variants, as their bootloaders are permanently locked.
How to install:
Necessary Base Firmware: 8.0.0 (OCSX27.1.2, May 2018) (for TMO, or equivalent security patches for other variants)
Boot the newest TWRP .img from the Official TWRP Project Site.
In TWRP, click "Wipe", "Format Data", then type "yes" as prompted.
ADB sideload the newest weekly
(Optionally) You can flash the newest TWRP Installer also found at the Official TWRP Project Site if you wish to maintain TWRP, though the pre-installed Lineage Recovery instance will do everything you need it to in most cases. We don't recommend or support the use of the TWRP installer, as it is overwritten on every update (will need ot be re-installed every update), and has no addon.d-v2 persistence.
Click "Reboot, then choose "Recovery", this will boot you to either Lineage Recovery or TWRP depending on your choice to install TWRP or not. It is necessary to reboot between ROM flash and GApps/Addon flash due to verity/slot-swap logic.
(Optionally) Flash GApps - MindTheGApps arm64 are recommended, OpenGApps are compatible with A/B as of 09102018, but I still only reccoemend and support MindTheGApps.
(Optionally) Flash SU - you'll need to turn it on from in developer settings after first boot Lineage OS SU Addon. - Magisk works fine, though is not supported.
Reboot
Known Problems:
Audio Mods don't work (this includes headphone jacks on mods) -- We can't fix this, don't use custom ROM's if you care about these.
Official Lineage OS builds will not ever allow Moto's Battery Mod "Efficiency Mode" to work -- though these can be made to work unofficially, join our discord if you're interested in this feature.
Wi-Fi Calling won't work until either the International or T-Mobile variant gets 8.1 blobs.
Ultrasonic Proximity Sensor doesn't work -- likely won't ever. It is used my Motorola's Active Display, but by nothing in Lineage.
Compass doesn't work -- no clue why.
Stock Display Color Profiles (the ones in Settings, "Display", "Colors") -- The ones in Settings, "Display", "LiveDisplay" work.
The default LiveDisplay "Natural" setting in Settings, "Display", "LiveDisplay", will occasionally dispaly color corruption, to deal with this, just swap to the "SRGB" profile, and swap back to "Natural", or leave it on "SRGB if you don't mind, then you won't experience those infrequent issues.
Notes:
Official Lineage OS builds will not pass CTS/SafetyNet -- due to the AVB flag's "red" status.
Official Lineage OS builds ship with full treble compatibility, with VNDK runtime enforcement! This means that unlike most "ported treble" you'll see, ours is just as it would be from the OEM, and can run any GSI (yes, even Pie!) without need for hacks or additional flashable zips. We relabeled /oem as /vendor (as /oem isn't used in custom ROM's anyway). To use a GSI, flash official Lineage, then flash your GSI, it's that simple! Flashing a factory image will likely write over /oem and remove the mock vendor image. Please don't report GSI bugs here, report them instead to the GSI's maker.
Download:
LineageOS Updater
XDA:DevDB Information
[OFFICIAL] [WEEKLIES] [TREBLE] Lineage OS 15.1, ROM for the Moto Z2 Force
Contributors
npjohnson, invisiblek, erfanoabdi
Source Code: https://github.com/LineageOS
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 4.x
ROM Firmware Required: 8.0.0 (OCSX*)
Based On: LineageOS
Version Information
Status: Stable
Created 2018-07-15
Last Updated 2019-03-18

first (always wanted to do that)
thanks for this, nice work everyone!!!

Nice, I was wondering when we were going to get an official thread. I'll be waiting for the 17th to install the weekly.

I have the international version (-05) and have installed plenty of these version (since unofficial release from both invisiblek site and ods.ninja site) as well as the official weeklies (all versions already released) and everything works (based on the description here and known issues), so I'd say it's safe to say intl version had been tested and known to be working as well.
Let me know if you need additional/specific tests that I can do here.
Thanks the official post!
Also, how about volte support? Is it supposed to work?

felipevsw said:
I have the international version (-05) and have installed plenty of these version (since unofficial release from both invisiblek site and ods.ninja site) as well as the official weeklies (all versions already released) and everything works (based on the description here and known issues), so I'd say it's safe to say intl version had been tested and known to be working as well.
Let me know if you need additional/specific tests that I can do here.
Thanks the official post!
Also, how about volte support? Is it supposed to work?
Click to expand...
Click to collapse
If it isn't in the bugs list, its expected to work, it works on TMO and SPR. And I'll flag the international as compatible, thanks.

Since it isn't in known issues, I assume VoIP compression was fixed?
Edit: known workaround is use Bluetooth for video/VoIP calls. I don't know if USB audio would work or not.

Uzephi said:
Since it isn't in known issues, I assume VoIP compression was fixed?
Edit: known workaround is use Bluetooth for video/VoIP calls. I don't know if USB audio would work or not.
Click to expand...
Click to collapse
Added to OP as an issue.

??? for listing known accurate issues ???
I was pissed after installing Invictrix rom only to find out sound mods don't work.

I'm having an issue with video calls on Whatsapp and Duo. The other person can't hear me and I can't hear the other person.
Some other issues:
- Ok google not working with screen off (but it's fine to me)
- Overview is messy sometimes when using multi-window (doesn't show previews of multi-windowed apps)
- Even when installing Moto Camera the app does not show secondary camera functions (Portrait, B/W, etc)
For my daily usage the audio on video calls is the most serious issue that drives me back to stock. I hope they fix it soon.

fixed, can remove this.

DTHayakawa said:
I'm having an issue with video calls on Whatsapp and Duo. The other person can't hear me and I can't hear the other person.
Some other issues:
- Ok google not working with screen off (but it's fine to me)
- Overview is messy sometimes when using multi-window (doesn't show previews of multi-windowed apps)
- Even when installing Moto Camera the app does not show secondary camera functions (Portrait, B/W, etc)
For my daily usage the audio on video calls is the most serious issue that drives me back to stock. I hope they fix it soon.
Click to expand...
Click to collapse
Anything that uses VoIP compression is broken. Most video calling or internet calling apps in general use it.

DTHayakawa said:
I'm having an issue with video calls on Whatsapp and Duo. The other person can't hear me and I can't hear the other person.
Some other issues:
- Ok google not working with screen off (but it's fine to me)
- Overview is messy sometimes when using multi-window (doesn't show previews of multi-windowed apps)
- Even when installing Moto Camera the app does not show secondary camera functions (Portrait, B/W, etc)
For my daily usage the audio on video calls is the most serious issue that drives me back to stock. I hope they fix it soon.
Click to expand...
Click to collapse
1. Added to known bugs.
2. I don't experience this (and if it is present, its platform wide, and not our problem specifically).
3. I can't really easily support a prebuilt app all that easily. The B&W cam us supported in the default Snap camera.

Also, OTA will be broken until we figure out why signing server's aren't signing our payload zips right.
To work around this, you can update weekly by sideloading the nightly, rebooting to recovery (important), re-sideloading any mods you use (GApps, AddonSU, etc.).

fixed, can remove post now.

Uzephi said:
Anything that uses VoIP compression is broken. Most video calling or internet calling apps in general use it.
Click to expand...
Click to collapse
So I assume this would apply to hangouts and hangouts dialer?

npjohnson said:
Also, OTA will be broken until we figure out why signing server's aren't signing our payload zips right.
To work around this, you can update weekly by sideloading the nightly, rebooting to recovery (important), re-sideloading any mods you use (GApps, AddonSU, etc.).
Click to expand...
Click to collapse
Resolved.

Unable to install Lineage su addon (using TWRP 3.2.2-2)
_BEGIN_
Installing su addon...
set_metadata: Error on lstat of "/system/etc/init/superuser.rc": too many symlinks encountered
Updater process ended with ERROR: 7
_END_
Thoughts?

MattKilla said:
Unable to install Lineage su addon (using TWRP 3.2.2-2)
_BEGIN_
Installing su addon...
set_metadata: Error on lstat of "/system/etc/init/superuser.rc": too many symlinks encountered
Updater process ended with ERROR: 7
_END_
Thoughts?
Click to expand...
Click to collapse
I was literally plugging in to try this ROM until I read this. Have you tried Magisk yet?

Magisk Works
3's&7's said:
I was literally plugging in to try this ROM until I read this. Have you tried Magisk yet?
Click to expand...
Click to collapse
I have ran into this same issue when flashing build > lineage-15.1-20180721-nightly-nash-signed.zip
I can confirm that it happens with both TWRP 3.2.2-2 & TWRP 3.2.1-1
I flashed Magisk 16.4 and it works flawlessly no issues.
I am very happy with this ROM it works great for me. Thank You Devs! :good:

MattKilla said:
Unable to install Lineage su addon (using TWRP 3.2.2-2)
_BEGIN_
Installing su addon...
set_metadata: Error on lstat of "/system/etc/init/superuser.rc": too many symlinks encountered
Updater process ended with ERROR: 7
_END_
Thoughts?
Click to expand...
Click to collapse
was TWRP installed or did you just boot to it?

[ROM] [P] [PORTED] [AXON 7] Android P beta developers preview

{
"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"
}
A few days ago we could see a YouTube video of an Axon 7 running Android P. Since that preview was not available, I decided to assemble one myself using the Vendor and boot partitions from the latest Treble ROM by NFound, the complete Pixel XL system image and a few hours removing Pixel specific items, adding a working camera, trying to stabilize it so it could boot without FC, connect to internet, having working Google Apps and being able to experience Android P with the limitations of the available resources. It made me feel so glad to see Android P in my device that I decided to share this feeling with everyone. So, now you will be able to flash and experience my Android P proof-of-concept in your own Axon 7!!!
:laugh: Working:
- It boots!!!
- Wifi
- Camera
- Google apps
- Magisk root
Not Working:
- SIM detection (No phone or mobile communications)
- Sound
- Bluetooth
- Sensors
- GPS
- Stability issues.
As you can see it is not, by any means, a daily driver. It is a proof of concept of what we will see in the future. The best of all is that it can only improve!!! Do not expect any maintenance, NFound is working in a proper Android P development so take this just as a sneak peek of what Android P roms would bring to your device in a few weeks/months. This is a single release I just assembled to see a preview of Android P in our own phones, having a better idea of the UI changes, take some screenshots, benchmarks, app compatibility and some camera shots too. It is up to you.
REQUIREMENTS:
You need:
An unlocked Axon 7
A Windows computer
The USB cable.
DOWNLOAD:
Axon7_Android_9_Oki20180728_FULL_EDL.7z
INSTALLATION:
WARNING, THIS GUIDE WILL WIPE ALL THE DATA IN YOUR DEVICE.
This procedure will delete and overwrite your device. All the data and internal storage information may be lost so do a backup of your data partition and your internal storage before running these instructions.
!!! Whatever you do, it is at your own risk !!!​
Just follow these instructions and, in a few steps, you will have Android P (sort of) in your Axon 7:
Un7zip the EDL package to a folder in your computer.
Install MiFlash in your PC. It includes the Qualcomm Snapdragon SoC drivers, nonetheless you can always install the latest drivers.
Enter EDL mode using one of the following options:
by pressing VolUp+VolDn+Power until the power led flashes briefly
Installing a terminal app and typing reboot edl at the app prompt.
connecting your phone to your PC and typing adb reboot edl at your computer's command prompt.
If you haven't done yet, it's time to connect your phone to your computer.
Open MiFlash in your computer.
Click Browse button and select the folder you created with the EDL firmware files.
Click Refresh button and your device will appear listed as virtual COM port.
Click Flash button and wait for a few minutes until it finishes. Note the bottom options are not applicable.
Press VolUp+Power until the phone vibrates to enter into recovery, then release both buttons. Go to Advanced > Terminal and type: reboot disemmcwp
Wait a few seconds until the boot animation begins and press again VolUp+Power until the phone vibrates to enter again into recovery. Go to Advanced > Terminal and now type: reboot "dm-verity enforcing"
Wait a few seconds until the boot animation begins and press again VolUp+Power until the phone vibrates to enter again into recovery for a 3rd time. To ensure everything is clean you should format the DATA partition, including internal storage. Go to settings and ensure "Use rm -rf instead of formatting" option is not selected. Then go to Wipe > Advanced Wipe, select Data partition and tap on Repair_or_Change_File_System button and then on Change_File_System button. Select F2FS and confirm action. Do the same to apply F2FS to the Cache Partition. Now from the main menu > Wipe select and clean cache and dalvik.
Your system is now ready, reboot to system to enjoy the Android P developers preview.
To return your axon 7 to the standard B12 Treblerized structure compatible with Treble and not Treble ROMs just repeat the previous steps but flashing Axon7_OREO_B12_TREBLE-Ready_Oki20180728_FULL_EDL.7z. This will leave a basic bootable AEX ROM with Magisk and TWRP 3.2.2 so you could flash or restore your previous ROM and backup.
CREDITS/SOURCES:
Google for releasing the Android P developers preview for the Pixel XL, and updated Google services from APK mirror
@NFound for his Oreo AEX 5.7 ROM image (I took the Oreo device files to add Axon 7 support to Android P).
@Spillunke for the nice splash image.
@djkuz for his Axon 7 EDL Tool that helped to extract all this and put it in a single EDL file.
Cheers!!!!!

Why did you make a separate branch Android P so early? Eh, every time because of such as you I have lost the desire to continue to work. I wanted to put out a full-fledged working version, but now I'll see if I can do this...
In the this Archive Axon7_OREO_B12_TREBLE-Ready_Oki20180728_FULL_EDL.7z
Neither contain one and your work, you just took and added your name here. In this case, I leave it to YOU to fix the current bugs, and I'll look at it as a spectator :good: #popcorn_and_tv
PS in the channel on YouTube been write: Currently, and repair minor bugs, so the link to download will be later. The work is being done
Moderator Edit:
Take personal issues/disagreements with another member to PM, not in Public here
XDA is about collaboration and contribution, not conflict
If you feel that you have a genuine grievance, you are duty bound to report your concerns to the Moderator Team.
Thanks!

If I have time, I can test out some things, Oki. Is it sound that's not working or is it just sound through the speakers? I remember a while back we had a problem running encrypted and sound through the speakers, but sound through the headphone jack worked.

Was the first thread not closed? I'm a little bit comfused? Why a new post?

BaamAlex said:
Was the first thread not closed? I'm a little bit comfused? Why a new post?
Click to expand...
Click to collapse
Moderators closed the thread due to some controversy. Now its open again. This is not a new post, since there are no other threads for Android P.

BaamAlex said:
Was the first thread not closed? I'm a little bit comfused? Why a new post?
Click to expand...
Click to collapse
Well yesterday there was a misunderstanding. NFound released a few days ago a YouTube Video of an Android P running in his phone. A project he has started and he is working on at this moment.
I liked the idea. Since he also released a Treble version of a couple of Oreo ROMs (Havoc and AEX) I took the Pixel XL Android P preview firmware image and added the vendor partition and the treble enabled kernel from the Oreo ROM. This combination required the removal of a lot of items from the Pixel XL system and adding some files and patches to the boot and vendor partitions to be able to boot and stabilize this Frankenstein ROM. I finally wrapped it in a single flashable EDL package for easy installation.
Since NFound was working on an Android P release and suddenly my assembly came up, he thought I was releasing his work, but actually I took only publicly released Oreo AEX rom files from him without any kind of copyright protection, available for download to everyone. Of course I gave credit to him for the portions I used (about 9% of this assembly are files extracted from his Oreo roms, and most of them are LOS15.1 files). He was claiming that this was a branch of his Android P work, but actually it is not, and It never was. I am not into developing roms at this time. I did more than 10 years ago, but family takes a lot of my personal time. The moderator closed the thread since there was claim about stolen work but I clarified the situation.
I really felt very bad, since I just published this assembly just for sharing with you all the good feelings I experienced when I saw Android P working in my device. An act of goodness that turned into a nightmare for me. By doing so, suddenly I found myself under suspect, being challenged by NFound, and judged by everyone for a crime that I never commited!!! A very bizarre and stressful situation.
I do not have anything against NFound and I strongly believe we are lucky to have him in the Axon 7 scene. I know I will never have an apology from those who judged me wrong and gave thanks to such aggressive posts against me, It was an experience I do not want to experience anymore.
I have been a member in XDA forums for more than 12 years, I saw Android first steps, building Test roms for the HTC Diamond, just to see an immature OS in a very small screen still with the pencil. But, at some time yesterday, I was tempted to leaving this forums for a few months. I thought I had contributed enough.
Nonetheless, I would like to leave all that behind and return to a normal situation were we were before. I really enjoy playing with this amazing device, enjoying the new releases from NFound and Kranoner and helping others to make the Axon 7 scene greater and better. You do not have to decide which side are you in, NFound and me are in the same team, the Axon 7 scene team, along with Kranoner, OrdenKrieger, djkuz, DrakenFX, raystef66, all the contributors in the past such as tenfar, jcadduono or Unjustified Dev, all that are still to come, and of course you too. Let's show the world why we consider the Axon 7 one of the best phones ever built.
No bad feelings anymore.
Peace

TPMJB said:
If I have time, I can test out some things, Oki. Is it sound that's not working or is it just sound through the speakers? I remember a while back we had a problem running encrypted and sound through the speakers, but sound through the headphone jack worked.
Click to expand...
Click to collapse
WHOA!!!! There is a lot of things not working in this assembly such as sound, all sound, and the rest of the items described in the OP. It is a Frankenstein assembly that is not going to be improved in the future. i am not going to dedicate any time on it since NFound will release a proper Android P build as soon as he could. It is there and I shared it so everyone could see Android P booting in their devices, maybe taking a screenshot or two, some pictures, or some benchmarks if you want.
Just enjoy Android P for a while only if you want to see it running in your phone.

Oki said:
WHOA!!!! There is a lot of things not working in this assembly such as sound, all sound, and the rest of the items described in the OP. It is a Frankenstein assembly that is not going to be improved in the future. i am not going to dedicate any time on it since NFound will release a proper Android P build as soon as he could. It is there and I shared it so everyone could see Android P booting in their devices, maybe taking a screenshot or two, some pictures, or some benchmarks if you want.
Just enjoy Android P for a while only if you want to see it running in your phone.
Click to expand...
Click to collapse
Ehhh I'll pass then.
Also I'll pass on whatever drama is going on now too.

TPMJB said:
Ehhh I'll pass then.
Also I'll pass on whatever drama is going on now too.
Click to expand...
Click to collapse
I just wanted to save your time by adjusting your expectations to the actual situation of this rom.
Drama? What drama? I don't remember any drama.

Oki said:
I just wanted to save your time by adjusting your expectations to the actual situation of this rom.
Drama? What drama? I don't remember any drama.
Click to expand...
Click to collapse
The king has invited you to lake Laogai.
Thank you for your time in this community, it's very exciting hearing about any DP implementation in the Axon 7, never thought that would ever come!

oh no! I remember you this guy,your post help me a lot in xda,I`sure you are a kindly man in life,why just leave for some reason not your fault?nfound is too Self-inflation for his work

zouyiqiang said:
oh no! I remember you this guy,your post help me a lot in xda,I`sure you are a kindly man in life,why just leave for some reason not your fault?nfound is too Self-inflation for his work
Click to expand...
Click to collapse
Hi, I really appreciate your attention. Nonetheless We are all a community, a team. There are no sides here at all. @NFound is a very brilliant boy and I am sure we all agree that he deserves the credit and respect for making this possible. Development is a chain and all the links are important. Without NFound work on treblerize those Oreo ROMs I wouldn't be able to use part of his rom files in adapting a Pixel XL rom image to our hardware. The same way he couldn't have released all the B12 roms without OrdenKrieger's work. At the end everyone adds his 2 cents to work done by others in the past.
It would be nice if there were more developers working in the B12 device tree and the treble ROM. Donations are something that is promoting serious development at XDA but at the same time is reducing the amount of open source code and teamwork. There are well prepared developers in the Axon 7 scene such as @Kranoner, @messi2050 or @freeza among others I do not mention here but are as prepared as them. Some of these developers are willing to help on solving bugs and problems in current implementations, or even properly treblerizing the LineageOS 15.1 implementation for the Axon7. However the developers with those current B12 device trees, created by them after countless hours of dedication, are keeping that code closed. I can only think they just want to keep it closed since they are getting a lot of donations for their work. In this sense, it is hurting the proper development teamwork. I understand that for a teenager gathering $100-$200 in donations, for developing a ROM or kernel, is a fortune. I know this very well, I also was a teenager trying to win some money to maintain my car, my computer and my electronics lab (no cell phones at that time), but that was decades ago and this is just a hobby for me now.
I do not want the Axon7 scene die because of this, but it doesn't depend on me. It only depends on the willingness of the current Axon7 ROM and kernel developers to let others contribute on, or fork, their work to continue them in other direction, the same way others shared their sources in the past such as @jcadduono or @Unjustified Dev did. We all remember their contributions here. There were many ROM developers and a lot of options in the past thanks to them. At the end, we all develop on top of other's work. That is what open source is all about. In twelve years in these forums I've seen some amazing devices die just because unavailability of up to date, device tree, kernel and vendor sources. I've also seen other devices that persisted in time just because the open source and cooperation spirit was there, contributing for a common cause. I don't want to see the Axon7 stagnating too for this same reason. The amount of bugs and the time it takes to fix them is inversely proportional to the amount of developers working in the device tree, kernel and vendor blobs. This ROM in the OP is the living proof that Android P is possible in your device, extending the life of the Axon7 at least another full year. Let's make it happen.

you are right Oki,it`s right nfound is a good development,but hi closed nearly all of his source code even thought some of it is from other`s work,it is really a pity that axon7`s third party rom is less than other device although it`s a amazing device,nfound Almost always igonre all other`s bug report in his topic,so i don`t think he is a Excellent developers,and his cynicism is really …… for these reason,I go back stock 7.1 rom today and wait for zte`s official oreo update,maybe next month in china。
just now,i faced a problem,I rembered My axon7 has not Virtual navigation key when i bought and use stock rom for a long time,and then i used third party rom for server month,now i flashed stock rom by axon7-edl-tool , Virtual navigation key is appear and can`t hide perpetual，my device has Entity navigation key,I konw to modify the build.prop file to hide,but I don`t want to root and Get ready for lock bootloader,why? could any one help me?

[CLOSED] [ROM][CUSTOM][O][SM-J530F] /e/ OS for Samsung J5 2017 (j5y17lte)

{
"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"
}
brought to you by the
Code:
/*
* I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed (like it did for me...).
* Please do some research if you have any concerns about features included in the products you find here 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.
* Your warranty will be void if you tamper with any part of your device / software.
* Same statement for XDA.
*/
About /e/
/e/ is an a mobile ecosystem (ROM + onlines services) that:
is open source
is pro-privacy
is compatible with most existing Android applications
cares about usability
is as far as possible freed from shackles by Google and OEMs
already exists!
It’s the alternative to the Apple/Google duopoly on the smartphone.
... so again and just to be clear: /e/ is not just a ROM, it is more a complete privacy ecosystem and consists of:
an installable mobile operating system for smartphones, which is forked from Android and strongly “ungoogled”
a set of sorted and improved default open source applications
various online services that are linked to the mobile operating system, such as: a meta search engine for the web, drive (with synchronization), mail, calendar, notes, tasks.
Features
Based on the stable Lineage OS
microG fully pre-installed with Signature Spoofing in restricted mode!
All features described on the /e/ page: What is e
All features and fixes of our LOS 15.1 builds.
My builds come with full OTA update support
... you know that thing which informs you that a new update is there and where you just click to download + install
Difference from pure /e/ or: why are the builds CUSTOM?
The /e/ app store has been removed completely (read FAQ #0 why I did this drastic change)
AuroraStore has been added (pls always use "anonymous" unless you need paid apps to avoid bans)
F-Droid has been added (The OpenSource alternative store. First search for any apps here!)
Dozens of F-Droid repositories are pre-installed (activate them with just a finger tip! That's needed to ensure you only get what you want)
The above changes are the reasons why my builds are of the type "CUSTOM" and not "UNOFFICIAL".
This is according to the rules defined by /e/.
Known issues:
Keep in mind that this is brand new stuff so it may (still) contain unknown issues!
So back up regularly and frequently!
When your current STOCK firmware or the latest you had flashed is PIE (Android 9) RIL will not work in this ROM. I am trying to fix that currently but while it works when your STOCK firmware/bootloader stack is on Oreo or earlier it stops working when you ever upgraded to pie
If you find a bug not listed let me know and SHARE LOGS! -> READ FAQ#1 for how to provide proper logs.
Requirements
Latest TWRP or SHRP build.
Latest TWRP build based on Oreo sources (build by myself) can be found here: click
Do a full Nandroid backup before doing anything!
Installation
Full clean install as described here (FAQ #2) is highly recommended. DO NOT REPORT ISSUES when you have skipped that step!
Flash /e/
Optional (if you want root): Flash Magisk
Flashing OpenGapps ????? NO No no! you don't want that on a google-free phone! /e/ contains everything you need to live without Google! So flashing OpenGapps on /e/ is like using a bit more secure LOS but that's not the point of /e/. Either try without or go with LOS (imho).
Boot it (will take a bit on first boot!!! be patient!)
Enjoy the most easy way to have a privacy focused and google-free phone!
Download
Get your builds from my leech server (new installs or re-installs)
http://leech.binbash.rocks:8008/e-os/oreo/
If you have /e/ installed already and just want to update to a newer release:
Android settings -> Updater (yes my builds have OTA support!)
Note:
Builds are updated as soon as possible. There is no build cycle.
Information pertaining to your device is displayed accordingly.
The current build is the latest for your device.
Changelogs
search results from this thread: click
Support
Of course in this thread but also by Telegram. I have created a generic group for all stuff around Android : here
and another one if you want to keep up2date whenever I build something (TWRP, SHRP, LOS, /e/, ...): here
Credits
nailyk
LineageOS (the base of /e/)
The /e/ foundation and all related devs making this experience possible!
The Exynos7870 Team
and more..
Sources
build manifest
XDA:DevDB Information
j5y17lte_eos-oreo_custom, ROM for the Samsung Galaxy J5
Contributors
steadfasterX, nailyk, ananjaser1211,DarkLord1731,Exynos7870 Team (github)
Source Code: https://gitlab.e.foundation/e
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.x
ROM Firmware Required: NOUGAT/OREO only - if you have stock PIE installed RIL won't work!
Based On: Lineage OS
Version Information
Status: Beta
Created 2020-08-05
Last Updated 2020-09-09

-
Frequently Asked Questions (FAQ)
Q #0: Why is the /e/ App store not included??? It is GREAT!
Mainly due to security and privacy concerns. Wth? I thought /e/ is secure and privacy focused? Yes it is but.. read on:
First of all the App store itself has no security or privacy issues. It is opensource and I see no issues with the app itself!
... the most important point for a smartphone is the availability of apps. I mean having a secure device which respects your privacy is great but it will have no chance to win when you cannot get easily apps on it.
... and the most dangerous part for a smartphone is installing apps because here is where Malware can easily step in! So whatever you do never install APK files from a website directly unless you can be 100% safe it is trustworthy.
It is all about trust again and when you look in the sources of the /e/ Apps store you find it connects to: cleanapk.org.
/e/ makes that not a secret though as you can read here.
So who is behind that cleanapk.org? Why is /e/ trusting them? While reading through the /e/ forums I found that this page hosts (as far as we know) apps mirrored from apkpure + fdroid.
.. and it's completely unclear who hosts that site and where is behind it. On the other site /e/ (Gael, the founder as well) states clearly they are not in any relation to that site. "They just using their api".
here some facts:
you cannot get the owner by a whois request
They have a info page here which just roughly describes where the apps are coming from and how
There is no detailed privacy statement or even an info if they keep your data GDPR compliant or not
No way for devs to get their apps removed or updated
The /e/ foundation clearly states they have no relationship to that repository of apps but some things are interesting aren't they:
IP's of /e/ and cleanapk are at least nearby
During an ongoing discussion about exactly that topic something took my attention: the welcome notification on api.cleanapk.org was exactly at that time: https://archive.is/U1E0y (I mean.... )
/e/ itself was audited several times by a site named "infosec-handbook" and of course even they find that app store at least "mysterious"
During that mentioned discussion and after pointing Gael to that - the welcome message suddenly changed to what it is today..
The full topic where even Gael is talking (not that friendly) is: here
TL;DR:
/e/ is providing apps (the most used way to get infected by malware) by an API which is at least questionable.
I do not say /e/ is doing questionable things and as said before the /e/ ROM is 100% trustworthy (otherwise I would not do any builds for it) but that cleanapk.org site is truly another story.
An interesting quote of Gael can make one read between the lines (I marked the interesting ones bold and cursive):
Some users have reported that they are using Aurora, [...] (context: we will never integrate this) because it’s infriging the play store terms of services.
For this, we have to use indirect mechanisms, that don’t infrige the play store TOS, and therefore, we are using a service that is not officially part of the /e/ project, and which is called cleanapk.org
On the long run, we other plans with partners, to offer something more transparent, but it’s too soon to talk about this.
Click to expand...
Click to collapse
Of course /e/ needs to ensure that what they are doing is 100% legal and offering an app repository like cleanapk.org is not.
My personal assumption is that /e/ is offering that repo - indirectly so not officially by the e.foundation itself.
A relation between is for sure nothing they want to have public as this would cause legal questions.
So the last question is:
Q: Why do I consider AuroraStore "better" then using cleanapk.org and so removed the /e/ apps store and adding AuroraStore instead?
A: Because I definitively know where the apps are coming from when using Aurora instead of /e/. Not just the app itself is OSS (like the /e/ one) the apps are coming directly from the play store instead of an unknown source.
Q #01: I want to report an issue. What is the proper way to do so?
I'm glad that you are asking: before doing so check the KNOWN ISSUES topic in the OP and ofc the other FAQ's listed here!
if you have an audio issue follow FAQ #6 instead.
If your issue is not listed there click here to proceed:
If your issue is not listed there follow the directions here briefly and I may can fix it:
logcat GUIDE
Ensure you have done a full CLEAN install before doing so (refer to FAQ #2 for what that means).
Warning: NO SUPPORT when:
- magisk is installed (known to cause issues sometimes - regardless of the ROM or version)
- Xposed is installed (known to cause issues sometimes - regardless of the ROM or version)
If you have installed any of these UNINSTALL or better do a FULL CLEAN install (see FAQ #2) before doing anything else. Often enough these above causes several issues like battery draining, problems on booting and much more. Even when they may work properly you should re-produce your issue without them first and follow the above to grab the log.
Magisk is a great piece of software and besides that it is Open Source which SuperSu never was.
I just saying I do not "support" issues when you have Magisk installed. Why? It is (like Xposed) extendable with modules (made by whoever) and those can cause billions of issues.
Other then that magisk was sometimes the reason for battery drain etc. Magisk modifies the boot "process" and sits very deep in the system (which is needed to make it work ofc) but that has the potential to make a system/ROM unstable or result in strange behaviors.
so in order to support a specific issue I have to be sure the ROM is in a "clean" state, no magisk, no xposed.
Pro-Tip: a very first test is to set magisk on core functions only to see if an extension causes your issue or not.
Q #02: I want to install clean, how? What is a clean install? What is the recommended way to flash a new ROM version?
A clean install ensures that there are no leftovers from any previous install. One can say that there are 2 phases of a clean flash:
1) regular
2) full - when you (still) encounter issues
Usually the regular one is fully ok when flashing a new ROM version but if you encounter strange issues nobody else is reporting or if a release post is recommending it you should do a full clean install instead.
A regular clean install can be done like this:
WIPE -> Advanced -> select: System + Cache
Flash the ROM
reflash root addon/magisk if you want root
A full clean install needs 2 steps more then the regular:
follow the steps for regular clean
go back in WIPE -> touch the "FORMAT data" button and type "yes" to format the internal storage (you will LOOSE ALL YOUR DATA - obviously)
REBOOT -> Recovery
Flash the ROM
reflash root addon/magisk if you want root
It is absolutely recommended to create a backup before and COPYING IT to your PC(!) before doing the above.
Q #03: Are there any plans or a chance of official /e/ builds?
TL;DR answer is: who knows...
Background:
/e/ points to LineageOS requirements which need to be met first. LineageOS has "some" requirements before they accept it to do official builds: device-support-requirements.
No I personally do not have any plans in going official atm. That might change though.
If someone else wants to go that way and needs help, I am here. But I cannot spend my whole free time on that.
Q #04: Will this ROM support / pass SafetyNet?
When you install Magisk you can hide and so yes you might be able to pass SafetyNet. Which can change every day though because even when that might work atm you should note the following:
Magisk has its own protections to ensure you pass safetynet but this is something which will change one day and there is no known method yet to workaround that.
Q #5: Is there an /e/ specific FAQ?
Sure:
FAQ: click
Forum: click
HOWTOs: click (a great resource for all your first questions)
Q #6: issues with audio (e.g. echo's, silence on one or the other site, ..)? Read here how to provide a specific log for that:
Do the following steps:
1) Ensure you have adb set up on your PC, and have adb debugging and adb root enabled in developer options on your phone
2) Then perform the following (all one command)
On Linux:
adb root ; adb shell "stop audioserver; logcat -c -b all; start audioserver" && sleep 10 && adb logcat -b all |egrep -vi "(dialer|telecom|ril|gsm|touch|brightn|dct|QC-time-services|SST|sensors|AlarmMan|Lights|perfp)"
Click to expand...
Click to collapse
On windows:
adb root ; adb shell "stop audioserver; logcat -c -b all; start audioserver && sleep 10 && logcat -b all |egrep -vi '(dialer|telecom|ril|gsm|touch|brightn|dct|QC-time-services|SST|sensors|AlarmMan|Lights|perfp)' "
Click to expand...
Click to collapse
3) Then re-produce your audio issue and cancel the logcat from step 2 before hanging up!
4) Share the logcat output from the console screen using paste.omnirom.org
Q #7: I'm scared about that microG , I don't want to expose my phone so is this /e/ version a security risk?
First of all you need a lot of trust installing ANY custom ROM. A developer can do nasty things right? Besides that yes microG allowing to let apps act like as they are another app, also known as signature spoofing. This CAN be a good and a bad thing. Read on why my builds are different:
In general the microG patch is an all or nothing. A ROM which supports microG (i.e. signature spoofing) have that feature enabled, always.
The difference in my /e/ builds is that I am using the "restricted" option of signature spoofing so as long as you trust me you are as safe as without microG.
.-

Reserved

Encryption of storage works?

jw96 said:
Encryption of storage works?
Click to expand...
Click to collapse
Haven't tested yet
Sent from my OnePlus 7T Pro using XDA Labs

I just installed it on my J5 2017 (SM-J530F). I did a full clean install (No magisk or xposed installed), but sadly my sim card is not detected.

Morceaux said:
I just installed it on my J5 2017 (SM-J530F). I did a full clean install (No magisk or xposed installed), but sadly my sim card is not detected.
Click to expand...
Click to collapse
yes one reason for that (I encountered that rn) might be the bootloader version.
What was the last stock ROM version you flashed? exact version if possible but at least if it was nougat, oreo, pie
or even better show a screen of "baseband version" in Android settings
.-

steadfasterX said:
yes one reason for that (I encountered that rn) might be the bootloader version.
What was the last stock ROM version you flashed? exact version if possible but at least if it was nougat, oreo, pie
or even better show a screen of "baseband version" in Android settings
.-
Click to expand...
Click to collapse
My baseband Version is "Unknow" rn, and I didn't check on my last ROM.
I used the stock ROM and was in pie version (I don't have the exact version rn, if you really want it I'll check tonight.
Do you want more informations ?

Morceaux said:
My baseband Version is "Unknow" rn, and I didn't check on my last ROM.
I used the stock ROM and was in pie version (I don't have the exact version rn, if you really want it I'll check tonight.
Do you want more informations ?
Click to expand...
Click to collapse
exactly what happened to me. I have upgraded the STOCK bootloader and modem to pie and RIL stops working. Was trying to figure out the reason for that but no luck yet.
so for sure the prev. STOCK version is an issue here. My last Samsung is a while ago so I dont know if one can downgrade without an issue or if I would brick it..
EDIT:
woa.. I cannot downgrade.. "check fail" in ODIN pointing to lower ARB levels.. damn.
so it seems that I have to find out the root cause for newer (i.e pie) bootloader stack
.-

steadfasterX said:
exactly what happened to me. I have upgraded the STOCK bootloader and modem to pie and RIL stops working. Was trying to figure out the reason for that but no luck yet.
so for sure the prev. STOCK version is an issue here. My last Samsung is a while ago so I dont know if one can downgrade without an issue or if I would brick it..
EDIT:
woa.. I cannot downgrade.. "check fail" in ODIN pointing to lower ARB levels.. damn.
so it seems that I have to find out the root cause for newer (i.e pie) bootloader stack
.-
Click to expand...
Click to collapse
I tried the same things last night, and I had the same problems (just so you know, If maybe it can help)

Morceaux said:
I tried the same things last night, and I had the same problems (just so you know, If maybe it can help)
Click to expand...
Click to collapse
thx. yes it definitively depends on the bootloader stack if it works or not. I have updated the OP with that information ("firmware required").
technical site info: I was able to flash the OREO radio (modem.bin) and cp_debug (modem_debug.bin) partitions without a problem but this alone does not make it work again.
Like for LG the 2nd stage bootloader likely initializes the hardware and the software (i.e. e.g. RIL) must know where and how these are loaded in memory etc. That's why just replacing the radio partitions will not fix it. RIL (and that is not just replacing a file) must fit to that as well..
The good news are: I am able to boot the radio now - PIN popup comes up and baseband is now correctly displayed (I am on the latest stock pie ROM available..)
but as you can see in the status bar still no cell service so still something missing..
IMEI is still 0 as well so it might has to do with the EFS.. which would explain it
but at least some progress.. At least it is clear now why some ppl reported on our LOS thread that SIM does not work for them while it worked for others.
.-

steadfasterX said:
thx. yes it definitively depends on the bootloader stack if it works or not. I have updated the OP with that information ("firmware required").
technical site info: I was able to flash the OREO radio (modem.bin) and cp_debug (modem_debug.bin) partitions without a problem but this alone does not make it work again.
Like for LG the 2nd stage bootloader likely initializes the hardware and the software (i.e. e.g. RIL) must know where and how these are loaded in memory etc. That's why just replacing the radio partitions will not fix it. RIL (and that is not just replacing a file) must fit to that as well..
The good news are: I am able to boot the radio now - PIN popup comes up and baseband is now correctly displayed (I am on the latest stock pie ROM available..)
but as you can see in the status bar still no cell service so still something missing..
View attachment 5078627
IMEI is still 0 as well so it might has to do with the EFS.. which would explain it
but at least some progress.. At least it is clear now why some ppl reported on our LOS thread that SIM does not work for them while it worked for others.
.-
Click to expand...
Click to collapse
Do you have a link to the last stock rom ? I think I don't have the right one, because I couldn't flash it, or maybe I did something wrong
(Nevermind, I found the right one)

Morceaux said:
Do you have a link to the last stock rom ? I think I don't have the right one, because I couldn't flash it, or maybe I did something wrong
(Nevermind, I found the right one)
Click to expand...
Click to collapse
https://sfirmware.com/samsung-sm-j530f/

goodjob

steadfasterX said:
The good news are: I am able to boot the radio now - PIN popup comes up and baseband is now correctly displayed (I am on the latest stock pie ROM available..)
but as you can see in the status bar still no cell service so still something missing..
View attachment 5078627
IMEI is still 0 as well so it might has to do with the EFS.. which would explain it
but at least some progress.. At least it is clear now why some ppl reported on our LOS thread that SIM does not work for them while it worked for others.
.-
Click to expand...
Click to collapse
Hi,
do you think there is a chance to get this running for phones which are already on PIE? (I think this is the majority of all phones.....)
kind regards
Jagged

jaggedN said:
Hi,
do you think there is a chance to get this running for phones which are already on PIE? (I think this is the majority of all phones.....)
kind regards
Jagged
Click to expand...
Click to collapse
Oof .. Well i don't have much time atm but i need that phone as my navigation device for my motor bike. so i need to fix it
Sent from my OnePlus 7T Pro using XDA Labs

New eOS v1-oreo build *20200909* has finished!
Changes:
- kernel: commits
- Device tree: commits
- Common Device tree: commits
Download: see OP
Known issue with the OTA Update!
Unfortunately it will work with the next update first. There was a missing entry in the fstab causing the install to fail. You can still use the Updater to download the package though!
1. Open Settings —> System
2. Expand Advanced & select Updater
3. Refresh if not listed already
4. Download
5. Reboot to TWRP
6. browse to /data/lineageos_updates/ and select the zip from here
BREAKING NEWS
I've decided to create a Telegram group for all stuff around Android : here
and another one if you want to keep up2date whenever I build something (TWRP, SHRP, LOS, /e/, ...): here
The second one will also show sha256sums of every build for those who need it.
.-

No more OREO builds!
The reason is that almost everyone has flashed stock PIE in the meanwhile and I switched to Android 10 already. A10 works great so far and so backporting whatever is needed is not worth it.
Check it out: j5y17lte - Android 10 / Q
Thread closed.
.-

[11][OFFICIAL] CarbonROM | cr-9.0 [fajita]

{
"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"
}
CarbonROM is an aftermarket firmware based on the Android Open Source Project. We are dedicated to fast, stable, and feature-filled ROMs, honesty and communication with our users, and openness with our code. We like frequent builds, with the very latest and greatest hardware support and fixes. We strive to not only provide you with the best ROM we can build, but also to give back to the Android community and our fellow developers. For us, this is about creating something we can be proud of and hope you will enjoy.
Please feel free to look, build, and use our code at CarbonROM's GitHub...
What is R?
Our release of Android 11, titled CR-9.0.
It provides you with the features you need while keeping the focus on delivering an elegant, smooth, and well polished experience. R delivers a set of unique features, like a system-wide font engine that also allows for applying fonts on user apps while supporting user fonts through custom APKs generated on fonts.carbonrom.org. We are confident you'll love it, and there's many more things to discover
Disclaimer:
While we make every effort to test these builds as much as possible, we are not responsible for anything that may happen to your device, family, pets, or perception of reality. We ask that you do your part to know your device and know how to recover from problems before you flash! As always, make sure to do backups.
Support:
We spend an astonishing amount of time developing this software. We can't spend much time on XDA as a result, so if you need support, please try the following:
1) Search. Search, search, search. Yes, you. I don't care how unique or important your question is, it's very likely someone has addressed it already. Especially if you're even close to new at this.
2) Ask a question in your device forum. Someone will no doubt try to help you. Warning: this help may come in the form of telling you it's a dumb question that has been asked before. See step 1 - such are the perils of asking questions when you haven't done the research yourself. Android is about helping yourself.
3) Join our Discord server or Telegram group! There, you can connect with other Carbon users and our developers, and you can get quicker responses to your bug reports. The invite link is right below.
Install Instructions:
You should start off with the latest Android 11 OxygenOS stable build on both slots and then proceed to flash Carbon.
The easiest way to do that is by installing the latest Version and then copy it by flashing the copy-partitions script made by LineageOS in the recovery. (See install Instructions for the recovery)
The recommended way to install is using the CarbonRecovery linked below.
Download the ROM and optionally GApps, reboot to recovery by flashing the boot.img using
Code:
fastboot flash boot fajita-YYYYMMDD-HHMM-boot.img
followed by booting to recovery through the bootloader.
Sideload the ROM. (Apply Update -> Apply from ADB -> Connect to PC ->
Code:
adb sideload CARBON-CR-9.0-R-WEEKLY-fajita-YYYYMMDD-HHMM.zip
Reboot recovery (to switch between slots)
Flash GApps/MicroG through sideload like above (optional)
Factory reset -> Format data/factory reset (Make sure to have a backup of your data)
Done
Followup builds can be updated through the builtin CarbonDelta Updater or by dirtyflashing.
Download
Download CarbonRecovery
Homepage
Join the CarbonROM Discord server
Meet us on Telegram
GitHub
Kernel source
Remember, every penny you send to us goes right back into the rom. It's used for hardware, server costs, etc - all the things that help us make Carbon better with every release. Your support means the world to us! If you've enjoyed Carbon, please consider a donation toward this goal. Thank you, and we hope you continue to enjoy Carbon!
​

FINALLY! YES! WOOHOO!

I just want to confirm based on the top post, that for the 6T we are indeed using the A10 base since that is still the "Latest Stable Build"?
Void4ever

void4ever said:
I just want to confirm based on the top post, that for the 6T we are indeed using the A10 base since that is still the "Latest Stable Build"?
Void4ever
Click to expand...
Click to collapse
Indeed, the current required base is the latest Android 10 stable.

Thx @Myself5 I appreciate the info. Hopefully I don't run into the same Android Auto issues I did with 8.0. However to be 100% fair I ran into those issues with multiple other roms as well. Something to do how OxygenOS handles the detection of USB vs ASOP I assume on the 1+ hardware. Literally the only thing thats kept me from running custom roms.

Found and fixed the issue with video playback in Apps. New builds coming within the next 2 hours.
void4ever said:
Thx @Myself5 I appreciate the info. Hopefully I don't run into the same Android Auto issues I did with 8.0. However to be 100% fair I ran into those issues with multiple other roms as well. Something to do how OxygenOS handles the detection of USB vs ASOP I assume on the 1+ hardware. Literally the only thing thats kept me from running custom roms.
Click to expand...
Click to collapse
I havn't had issues with Android Auto in the VW Discover Pro on any devices so far. Unfortunately the only car I can test it with, and the Emulator is working fine as well. If it's still broken for you I'd greatly appreciate if you can provide logs of the issue and I'll try to take a look

Myself5 said:
Found and fixed the issue with video playback in Apps. New builds coming within the next 2 hours.
I havn't had issues with Android Auto in the VW Discover Pro on any devices so far. Unfortunately the only car I can test it with, and the Emulator is working fine as well. If it's still broken for you I'd greatly appreciate if you can provide logs of the issue and I'll try to take a look
Click to expand...
Click to collapse
I would be happy to provide logs if/when i run into an issue.
I can give some background right now, which may not be very useful since we don't know if 9.0 is going to have the same issue. I don't recall if it was you @Myself5 or the dev from Paranoid, but we had a short discussion about this a while ago. If I recall one of you suggested it might be the modules you were using from the ASOP libs maybe? I'd have to go search through the old threads.
The only car I have to test with is my 2019 Traverse. AA works perfect everytime with stock Oxygen, and the only other ROM I ever ran into that seemed to work fine was AOSIP, however the rom itself was unstable on my hardware and I had to remove it due to my alarm not going off cuz the phone would crash overnight. So perhaps there's something in the way they implemented USB detection.
The last rom I tested (I forget which) I noticed that the phone wasn't even popping up the USB notification (where you can select File Transfer, USB tethering, MIDI, PTP, No data transfer) when connecting to the car.
Anyways this is far more info than we need until I can test it. Hopefully this weekend if not sooner.

Bit rusty running custom Rom
I was able to install perfectly fine, running perfectly just a bit iffy on Rooting afterward.
Can we install Magisk through CarbonRecovery? Do we need to keep the Carbon Recovery as the defacto Recovery for this Rom? Can I go back TWRP?

Mckillagorilla said:
Bit rusty running custom Rom
I was able to install perfectly fine, running perfectly just a bit iffy on Rooting afterward.
Can we install Magisk through CarbonRecovery? Do we need to keep the Carbon Recovery as the defacto Recovery for this Rom? Can I go back TWRP?
Click to expand...
Click to collapse
Yes you can install Magisk through Carbon Recovery. TWRP should be just fine, especially as the Recovery isn't used for updates etc as that is all done through Seamless updates in CarbonDelta on the system itself.

When i installed the rom i had to install the gapps after i was done with the phone setup. Otherwise the Android Setup would crash as soon as android booted.
The screen would then go cracy (blinking button icons) and I couldn't do anything.
I also can't update using the ota update.
Just tells me "Update could not be installed".
Other than that it works great
Edit: I didn't see the message about the video playing fix in some apps.
Updated from to latest version and now all videos work

Myself5 said:
Found and fixed the issue with video playback in Apps. New builds coming within the next 2 hours.
I havn't had issues with Android Auto in the VW Discover Pro on any devices so far. Unfortunately the only car I can test it with, and the Emulator is working fine as well. If it's still broken for you I'd greatly appreciate if you can provide logs of the issue and I'll try to take a look
Click to expand...
Click to collapse
Thank you for this great rom .
I had a problem with Android Auto, It's solved but I report if someone faces the same issue.
With Nikgapps basic on cr-9.0, Android Auto was not working: the phone was detected by the car (Peugeot 2008 from 2018), but when I initiated the connection the phone hangs and freeze, nothing happens on the car and I often had to reboot the phone.
It was an error related to usb permission in the logs.
It was solved using the stock package of Nikgapps (the problem is reported on other other devices as well). I was using the basic package of nikgapps on carbonrom cr-8.0 without problem, I don't know what changed that made the stock package needed.
I did not try for other gapps providers, but at first glance, this problem doesn't seems related to the rom itself but more to the gapps package.

My facebook and insta videos r not playing.. can't able to see them .. how to fix it

Prabhuraj 0 said:
My facebook and insta videos r not playing.. can't able to see them .. how to fix it
Click to expand...
Click to collapse
By updating to the latest build as mentioned a few posts above yours.
On that note:
I've found and fixed an issue where the device would not be reported as an A/B device properly which resulted in the integrated updater being broken. It will be fixed in wednesdays build (along with August ASBs) but you will need to manually update (through recovery) to that build.

So I haven't had a chance to install because I had to be OnCall for my job this week, no messing with my phone...... BUT that may have been a blessing?
I see the Stable A11 was released today for the 6 and 6T. Are there plans to rebase Carbon 9.0 to this?
Void4ever

Solid ROM! I haven't used Carbon since the Epic 4g phone. I'm running latest without Gapps, and I have to ask is there a better camera available outside of the play store? I know its a long shot but thought I'd try.

Google Camera, just google up gcam ports

only reason fr nt using Carbon is there is no
face unlock

Why is there no new download link from 25/8 for fajita. I can see the update on my phone but I want to flash the update.zip file from recovery.
Thanks

Wishmasterflo said:
Why is there no new download link from 25/8 for fajita. I can see the update on my phone but I want to flash the update.zip file from recovery.
Thanks
Click to expand...
Click to collapse
The last version also took a while (~4-7 days, not sure) until it was available on the website

I see it now. Probably didn't wait long enough!
Also @Myself5 is this by chance based on A11 now, or still A10?