yashsingh1/xdaforums huggingface dataset:
[Galaxy Note 10.1 (2014 Edition) Original Android D] RXT00:
I got it from here: https://apkpure.com/deathly-adiutor/com.exynos5420.deathlyadiutor.ads
[Galaxy Note 10.1 (2014 Edition) Original Android D] RXT00:
I've attached screenshots of some of my settings, and it's been smooth in my experience. I adjusted the thermal throttling to reduce heat, but if you game heavily you might need to increase the temp a bit.
[Galaxy Note 10.1 (2014 Edition) Original Android D] technosapien:
Hi,

I stumbled on this step before realizing I had the stock 5.1.1 OTA update - the bootloader is already the one you need if you did this OTA update.

May not be your case, but it worked for me to proceed without having to flash the lollipop bootloader.

---------- Post added at 04:29 PM ---------- Previous post was at 03:58 PM ----------

Hey I had the same issues. From the information I gleaned poking around the web for answers, it's a catch-22... because you didn't complete the Setup Wizard, the home button won't work and the developer mode can't be activated, and prob. some other little things won't work right.

I did not need to flash the Lollipop bootloader though, since I had the 5.1.1 OTA update, but after some finagling, I was able to get it going with:

Odin 3.10.6 -->> Latest official TWRP ( https://twrp.me/samsung/samsunggalaxynote1012014exynos.html )

From within TWRP, flashed the 5/5 Vanilla TeamExynos5420 image (I tried the 5/9 Deathly image and that's the one I kept having SetupWizard issues with, so tried Vanilla in hopes it'd work)

Without rebooting also flashed the ARM 7.1 Gapps Nano from OPENGapps website and the 14.1 arm root addon

Rebooted, Setup Wizard ran successfully, good to go.
[Galaxy Note 10.1 (2014 Edition) Original Android D] coxackie:
Vanilla vs Deadly

Hi there, does anyone know what is the advantage of Exynos Deathly version as opposed to Exynos vanilla? At least for me vanilla feels more responsive and drains less battery, although I would guess otherwise from previous posts...
[Galaxy Note 10.1 (2014 Edition) Original Android D] PowerPorridge:
Installed the newest Deathly version of the rom. Getting the Setup wizard crashing problem and cant finish the setup. Tried several workaround, but none was working. Any solution that worked for you?
[Galaxy Note 10.1 (2014 Edition) Original Android D] ziouzitsou:
Hello,

Is there CAF version of this ROM or other based on android 7+ ?
[Galaxy Note 10.1 (2014 Edition) Original Android D] toker562:
Anyone has good working links. The ones on the post are broken. Thanks
[Galaxy Note 10.1 (2014 Edition) Original Android D] meekspace:
http://download.exynos5420.com/LineageOS-14.1/n1awifi/
[Galaxy Note 10.1 (2014 Edition) Original Android D] toker562:
Thanks bro I got the rom but gapps doesn't work. Seems the website is down or something
[Galaxy Note 10.1 (2014 Edition) Original Android D] meekspace:
How can I install the 5.1 stock keyboard?
[Galaxy Note 10.1 (2014 Edition) Original Android D] blazzer12:
Well, did you find a solution?

---------

You can try this:

How to Fix Setup Wizard has Stopped on Android
[Galaxy Note 10.1 (2014 Edition) Original Android D] meekspace:
I found with a clean sd card, flashing stock lollipop first, then doing the lineage setup worked for me.
[Galaxy Note 10.1 (2014 Edition) Original Android D] maserati2011:
I'm facing the same issue with the latest deathly builds.
[Galaxy Note 10.1 (2014 Edition) Original Android D] meekspace:
I think there was something leftover from previous installations left on the SD card. After formatting it, installation was a breeze.
[Galaxy Note 10.1 (2014 Edition) Original Android D] bselesnew:
This Might Help

Follow the steps outlined in post #2293 . It will help you fix your boot loader then reinstall TWRP then retry with this rom. I was having the error code 7 then found this. I installed everything after that no issues. Hope it works out for you. Sorry for replying to a year plus old comment, hope it finds its way to you.
[Galaxy Note 10.1 (2014 Edition) Original Android D] wadken1:
[insert deity name of choice]!! That is an old post and the one your reference is even older - 4 years ago now. In fact the bootloader fix is something we all had to do to transition to LOS at the time - I never expected to have to do it again but I'll give it a go when I have more time - it's been so long since I messed around with this device that I don't even think I have a working Odin set-up.

Anyhow, thanks for the tip - I'll post my progress here if & when.

Cheers
[Galaxy Note 10.1 (2014 Edition) Original Android D] juppi:
Lineage Setup Wizard is buggy. Reboot to TWRP, run file manager, delete /system/priv-app/LineageSetupWizard directory. Then boot normally and now you should be able to finish your setup.
[Galaxy Note 10.1 (2014 Edition) Original Android D] meekspace:
Video decoder or demuxer had an error with the content

I have just come from a fresh install of stock 5.1 and installed 20201020 official and was met the following error ten seconds after starting the news on SBS.com.au

Video decoder or demuxer had an error with the content. (PLAYBACK_VIDEO_DECODING_ERROR)

Happens with chrome and Firefox but not on my phone

Any ideas
[Galaxy Note 10.1 (2014 Edition) Original Android D] meekspace:
I reflashed ROM, it didn't fix it.

Last night it worked in chrome in desktop mode, tonight it didn't.

Could you try https://www.sbs.com.au/ondemand/program/sbs-world-news and see of you can replicate the error when you play the news?

Well I went to SBS and they cane back with this:

At present, we haven't been able to replicate your error on our end. As far as we can see the SBS World News Bulletins play out fine and there are no error messages like the one you've mentioned. We also haven't received any comments from a customers regarding this issue.

Can you please try carrying out the following steps to see if they resolve this issue:

1. Sign Out of your SBS on Demand account

2. Clear your Browser's Cache (Google Chrome - see here: https://support.google.com/accounts/answer/32050?co=GENIE.Platform=Desktop&hl=en)

3. Sign back into SBS On Demand to see if the Issue persists?

It didn't work. Funny thing is the advertising works just fine.
[Galaxy Note 10.1 (2014 Edition) Original Android D] FALCREB:
Hi. My microphone volume is very low. Why could it be ?
[Galaxy Note 10.1 (2014 Edition) Original Android D] meekspace:
It has something to do with the mixer paths. I have made some adjustments, still needs improving, but its better than before. Make a backup of your current media_paths file first in case you need to change back. Rename it mixer_paths.XML.bak

You will find the file in system/etc
[Galaxy Note 10.1 (2014 Edition) Original Android D] FALCREB:
It doenst work :(
[Galaxy Note 10.1 (2014 Edition) Original Android D] meekspace:
That is my mistake. The file is for another 7.1 rom I'm using. I don't have anything for this rom. Sorry
[Galaxy Note 10.1 (2014 Edition) Original Android D] meekspace:
OK, I have misplaced my copy of lineage-14.1-20170127-UNOFFICIAL-n1awifi.zip

I have googled but can't find a copy to download.

Can anyone help please?

SOLVED

So much for Google, I found a copy here

https://xdaforums.com/t/p600-n1awifi-rom-7-1-official-lineageos-14-1-weekly.3457898/post-79487764
[Galaxy Note 10.1 (2014 Edition) Original Android D] meekspace:
Has anyone worked out how to do a clean install of the unofficial rom?

I get past the setup wizard error.

SOLVED

Using Odin I installed kitkat, then lollipop and twrp. Then flashed unofficial lineage and gapps. When it got to the setup wizard failed, rebooted into recovery, mount system. Then using file manager, went to system, priv-app and deleted lineage setup wizard. Rebooted and finished setup, All good!!!

Now, I just need to figure out how to get Disney+ and Netflix to show up in play store...

NOT SOLVED

Couldn't find a way to get Disney and Netflix from the play store. So wiped device, flashed official, set up with apps being installed by Google which included Disney and Netflix. Then dirty flashed unofficial ROM.

Currently running very hot - high 70's Celsius
[Galaxy Note 10.1 (2014 Edition) Original Android D] Cannonball_CO:
Hi all, been running the last Official Lineage 14.1 for SM-P600 for about two years.

A week ago go the bug to see if I could get something more recent, more security patches. Installed Vanilla from the exynos5420.com site. Went smooth, added open_gapps and addonsu.

This week I got a bug, why not try Deathly? There's that link describing how to deal with the crashing setup wizard, why not? The fixes at that link kind of work... but if you get through it all the system is left in an incomplete state. Once you're actually at a launcher, the buttons don't work, you can't enable developer options, and as far as I can tell, installs from the app store are stalled as well. If you make it to the second method of the setup wizard fix (fixing permissions), you can set all permissions, but that didn't help me. Maybe I messed up somewhere here... lemme know?

So, I thought, why not try more at the command line? There's suggestions on what permissions need setting. Well, it does not appear one cannot fix permissions in adb shell from TWRP. OK, maybe I can get a script to run at boot?

None of this got the job done. I surrender. Going back to Vanilla. If anyone defeats this, please let me know.

Best

Kendall
[Galaxy Note 10.1 (2014 Edition) Original Android D] Hostilian:
Anyone actually got the deathly working well?

Was going to update mine (to the latest and greatest possible) before giving it to my mum (I have had the latest LineageOS build from a year or two back installed).

I got a Galaxy Tab S7 last year - and the stylus is awesome in comparison to my old 2014 Note. :)
[Galaxy Note 10.1 (2014 Edition) Original Android D] meekspace:
The deathly kennel is the latest, because it's not maintained anymore. It has full functionality only with the unofficial version
[Galaxy Note 10.1 (2014 Edition) Original Android D] Hostilian:
OK, installed..... eventually. Wasn't without its problems!

I got the crashing setup app - just after entering login details.

Removing the Lineage Setup wizard file in Priv-App brought me to a different setup Wizard, where I was stuck only being able to set up the tablet by importing data from another device (I wanted to set up a fresh device).

The only way to get around this was to select NOT to use a network for setup (in the Wifi network options). It then allowed me onto the desktop!

So far so good!
[Galaxy Note 10.1 (2014 Edition) Original Android D] Cannonball_CO:
Off topic but hell yeah, my Tab S6 is a champ; tempted to get the Tab S7+. I keep the Note 10.1 around for personal use.
[Galaxy Note 10.1 (2014 Edition) Original Android D] Hostilian:
Should say.. The versions I used on my Note 2014.

Updated TWRP (from within my existing version) to - twrp-3.5.0_9-0-lt03wifiue.img

Lineage version used - lineage-14.1-20210129-UNOFFICIAL-n1awifi

GAPPS version - open_gapps-arm-7.1-stock-20210202.zip

Note.. If you don't use Stock (Gapps), you don't get any keyboard, so can't type in the dialog screens in the setup wizard..

Root - addonsu-14.1-arm-signed.zip

Boot to TWRP, updated TWRP, factory reset, then Lineageos install (don't reboot), then GApps, then Root, then reboot to system (after clearing caches).

Worked fine. Eventually, as previously described. :)
[Galaxy Note 10.1 (2014 Edition) Original Android D] tejljr:
I did that and it screwed up my home button and didn’t let me use quick settings
[Galaxy Note 10.1 (2014 Edition) Original Android D] Hostilian:
Both work for me. Did you try using the same versions I did?

Mentioned on the next post.
[Galaxy Note 10.1 (2014 Edition) Original Android D] tejljr:
It worked, however, the SafetyNet is broken. The SELinux status is Permissive, which I suspect to be the culprit. Which means no Disney+ or Netflix for now
[Galaxy Note 10.1 (2014 Edition) Original Android D] Cannonball_CO:
Sounds similar to my experience. When I get a weekend and feel machoistic (🤣) perhaps I'll try Hostilian's

exact

approach... when I attempted last I restored data from a previous install.

Also, quick question: is there a changelog for 14.1 out there? I have been looking here and because no changes have appeared since mid-Dec there seems to be no point in updating to the next weekly build... unless there's another log I should be viewing?
[Galaxy Note 10.1 (2014 Edition) Original Android D] tejljr:
I used his exact approach and it worked. But I don’t use that ROM because of the SafetyNet, I use another build created by a developer known as Mackay, where his rom has the Deathly Kernel and the SafetyNet works properly
[Galaxy Note 10.1 (2014 Edition) Original Android D] tejljr:
Ok guys, I think I figured it out. So what I did was, I took the boot.img file from the Mackay ROM from 2017 (which has the Deathly Kernel and working SafetyNet).

Installed the latest unofficial LineageOS 14.1 zip file in TWRP, flashed the boot.img that I pulled from the other rom, installed Gapps (7.1 Stock on Opengapps), Magisk, then cleared Cache and Dalvik.

When you get to the welcome screen, you still run into the crashing Setup Wizard. So I rebooted back into TWRP, mounted the System, deleted the LineageSetupWizard folder in system/priv-app, then reboot. Gave me a new setup wizard that worked properly.

SELinux is enforcing, SafetyNet check says Success in Magisk, and Deathly Adiutor is pre-installed as well.
[Galaxy Note 10.1 (2014 Edition) Original Android D] Andrex27:
Hello everyone.

I've just installed the vanilla version of the LOS on my p600.

Everything seems working fine, but I can't find the recent apps button.

Can someone tell me what button should open recent apps?

Thanks in advice.
[Galaxy Note 10.1 (2014 Edition) Original Android D] atomickaiserklein:
Hi,

I am a newbie in this forum.

I am searching for a stable stock-rom, based on android 7 for my SM-P600 and I guess to find it here but the download-link above doesn't work. Is there anyone who can help me to get this Rom?. When I mentioned "stable" I mean that all necessary featurres like camera, Wlan and so on should work. Thanks in advance and you developers are doing a great job!

Regards,

Christian
[Galaxy Note 10.1 (2014 Edition) Original Android D] tejljr:
lineage-14.1-20170503-MACKAY-n1awifi.zip | by kasperhettinga for GALAXY Tab PRO 10.1

Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.

androidfilehost.com

This is the ROM I’m using as a daily driver. LineageOS 14.1 (Android 7.1.2). Everything in here works properly. SafetyNet passes, so you shouldn’t have any issue there. Also comes with the Deathly Kernel for CPU and thermal controls.
[Galaxy Note 10.1 (2014 Edition) Original Android D] tejljr:
The menu button should act as the Recent apps key by default. You could change what that button does in Settings > Buttons.
[Galaxy Note 10.1 (2014 Edition) Original Android D] bitblaster:
Just to let you know how I finally worked around the buggy setup procedure:

TWRP version: twrp-3.5.0_9-0-lt03wifiue.img

Lineage version: lineage-14.1-20210409-UNOFFICIAL-n1awifi.zip

GAPPS version: open_gapps-arm-7.1-nano-20210410.zip

Root extra (from Lineage extra repository): - addonsu-14.1-arm-signed.zip

Install sequence:

Boot to TWRP

Wipe dalvik, data, cache, system, internal storage (probably this not needed)

mount USB storage while in TWRP and copy the 3 zip files to internal storage

Install LineageOS

Install Root

Install GApps

Advanced->File Manager: delete the folder /system/priv-app/LineageSetupWizard

Reboot system

After a while the full Google setup wizard appears

(optional) If it hangs checking for updates just press the back button and, in the network selection screen, choose to ignore the network
[Galaxy Note 10.1 (2014 Edition) Original Android D] rajivshastri:
Any idea why development of Vanilla seems to have stopped? There's no update for more than 2 weeks now even as Deathly has been updated once...
[Galaxy Note 10.1 (2014 Edition) Original Android D] megarain555:
Just realized that dash charging isn't working for me. Anyone else experiencing this issue?
[Galaxy Note 10.1 (2014 Edition) Original Android D] datecasp:
I actually am running my own build from LineageOS github repo for n1awifi and it runs clear and smooth.

Security patch is from March 5 2021 and everything looks work properly (set-up camera, wifi...). I didn't installed gapps (didn't need them for the use of this device) so I can't check SafetyNet...

I know it's a bit headache to build your own but in my opinion it deserves the work.
[Galaxy Note 10.1 (2014 Edition) Original Android D] Ramidalf:
Could you please provide instructions to build it?
[Galaxy Note 10.1 (2014 Edition) Original Android D] datecasp:
Hi @Ramidalf

You will find the most of the instructions here https://wiki.lineageos.org/devices/n1awifi/build

Also you'll have to create a local_manifests.xml and add the proprietary blobs from here https://github.com/TheMuppets/proprietary_vendor_samsung/tree/cm-14.1/n1awifi (attached my local_manifests.xml)

Problably you'll have a bunch of errors firsts times, but googleing you could find more help (I can't rememeber more webs) and successfully build your own ROM
[Galaxy Note 10.1 (2014 Edition) Original Android D] supergrobi94:
Hello @datecasp

so I've tried building my first LineageOS for n1awifi with the linked instructions. After many errors I was able to fix so far, I'm now stuck with this error:

make: *** No rule to make target '/home/lineage/android/system/out/target/common/obj/APPS/Bluetooth_intermediates/with-local/classes.dex', needed by '/home/lineage/android/system/out/target/common/obj/APPS/Bluetooth_intermediates/classes.dex'. Stop.

Haven't found a solution yet, but did you get the same error and have a solution maybe?
[Galaxy Note 10.1 (2014 Edition) Original Android D] datecasp:
I can't remember all the errors I had...

Could you post more lines of the log? Maybe before of that line should be anything that give you a clue about the problem.

Did it say anything about 'ninja'? If so, you can build without ninja (read this https://hacksandgeeks.com/single-post/2017/04/02/How-to-Build-Custom-Lineage-OS-ROM)

Also check your Python version and Java version (open Terminal and type "python --version" and "java --version"), as I remember you need Java 8 and Python 2.7.18 for this source

How many gb's did you put in Jack configuration? I believe I finally alloc 8gb instead the 4gb that instructions says.
[Galaxy Note 10.1 (2014 Edition) Original Android D] datecasp:
Sorry but I can't help here...

Are you building from the top of the tree? Croot betwen breakfast and brunch

I found this you could try I see what happens https://xdaforums.com/t/tutorial-aosp_build-how-to-fix-no-rule-to-make-target-error.3223434/

I checked my bashrc and I finally configure jack to 10GB

Hope it helps you!

Tell me what happens please!
[Galaxy Note 10.1 (2014 Edition) Original Android D] supergrobi94:
Yeah, breakfast n1awifi > croot > brunch n1awifi. Changed jack to 10GB, too. The fix from the thread didn't work for me.

I will try to look to fix the Bluetooth_intermediates error somehow, but for now Thank you very much for the support!
[Galaxy Note 10.1 (2014 Edition) Original Android D] datecasp:
If I get any possible solution I will tell you.

Good luck!!
[Galaxy Note 10.1 (2014 Edition) Original Android D] datecasp:
@supergrobi94 one maybe stupid question (I found myself in this error today)... Are you trying to build the correct branches?

Both repo init and local_manifests projects
[Galaxy Note 10.1 (2014 Edition) Original Android D] supergrobi94:
Yeah, I think so. Since I still can't solve the error, I will start from scratch again, maybe something went wrong while downloading the files the first time.

Update: Even after beginning again from start (from Ubuntu 20.04.2.0 to 21.04 and downloading all files again), still stuck in No rule to make target Bluetooth_intermediates error.
[Galaxy Note 10.1 (2014 Edition) Original Android D] Cannonball_CO:
Hey @datecasp thanks for assembling this. Quick question this is CPU independent, yeah? I only have an RP4/8GB with 128GB of SDcard so I'm gonna do compilation there. I know gcc can do cross-compilation so being on aarch64 isn't critical but shouldn't hurt either?!?
[Galaxy Note 10.1 (2014 Edition) Original Android D] datecasp:
Hi @Cannonball_CO

I'm not sure if I get your question, no English native...

It's recommended at least 16gb RAM for building. Enable ccache and get a cup of tea.

Also for building the CPU is important, in last builds my 8 core is working full the most of the time.

And I'm not sure about build in a SDcard... Can you mount it to your system? I know you can use a external drive but an SDcard is first time I hear about

Has this sense with your question?
[Galaxy Note 10.1 (2014 Edition) Original Android D] Cannonball_CO:
Hey @datecasp no worries. I am compiling on an ARM machine, specifically a Raspberry Pi 4 with 8GB RAM - and for a Raspberry Pi the only disk it's got is an SD Card :-).

I'm at 'repo sync' right now so no idea if this will actually go, but I'll report back if it works. I don't have an AMD64 Linux system anymore (only Win10 🤮😭) LOL
[Galaxy Note 10.1 (2014 Edition) Original Android D] datecasp:
Hi @Cannonball_CO

Just give some tries to the Raspberri and see what happens. Maybe success maybe not, but learning for sure!

In win10 you can use WSL and Ubuntu for Windows

Hope you success in your build!
[Galaxy Note 10.1 (2014 Edition) Original Android D] Cannonball_CO:
Nope, gotta setup a dual boot, x86_64 linux system...

make: *** No rule to make target 'build/core/clang/HOST_arm64.mk'. Stop.

I learned a lot about the process though. Thanks again for the links, @datecasp!

OR... you've helped me again, with your idea!

https://xdaforums.com/t/guide-how-to-build-lineageos-on-windows-10-wsl-2-0.3750175/
[Galaxy Note 10.1 (2014 Edition) Original Android D] datecasp:
I have seen in a telegram group that you can't build on arm...

So chance for WSL or to make a dual boot in your machine (I have this setup and works fine)
[Galaxy Note 10.1 (2014 Edition) Original Android D] datecasp:
OMG!

Maybe something about building in WSL... Nothing of that happened to me in native Ubuntu 20.04. I had problems with Jack, with ninja, with the python version (old build in new OS)... Everything "easily" fixable

Congrats for your success @Cannonball_CO
[Galaxy Note 10.1 (2014 Edition) Original Android D] etofi:
Can you please upload your version?
[Windows 10 Mobile] yochu20:
As soon as I was able to get powershell moved over and tested, my first thought was to see if WinRM (Windows Remote Management or PSSessions) was functional. I was greeted with the cryptic message that "WinRM command line is not available on this system". rpcss and http are required services for WinRM startup, so I have created startup entries for both. Sadly rpcss wants lanmanserver and lanmanworkstation started, and I am unable to start either due to permissions, but these services appear to have startup entries already. Anyone else working on this and interested in swapping notes?
[X Style (Pure) Q&A, Help & Troubleshooting] Mohannad-K:
Dears

Can you guide me to the best ROM for Moto X XT1575?

Thanks
[X Style (Pure) Q&A, Help & Troubleshooting] gulshanstrider:
In my opinion AOSP ROMs are better than CM based. I have tried almost every ROM for Moto X Style / Pure

There are only 2 which I liked most.

1) BrokenOS (Substratum Theme engine)

2) Dirty Unicorns (CM theme engine )

Happy Flashing ;)
[X Style (Pure) Q&A, Help & Troubleshooting] Cdub1976:
Another vote for du. Best ROM I've tried. I'm more of a cmte kind of guy though. Didn't really like substratum.
[X Style (Pure) Q&A, Help & Troubleshooting] pato2015:
whats the meaning of aosp?
[X Style (Pure) Q&A, Help & Troubleshooting] Mohannad-K:
Thanks

What about Pure Nexus?

And i want ask if Moto Action especially chop twice for flashlight working with any Rom cuz iam using this feature in my work
[X Style (Pure) Q&A, Help & Troubleshooting] Edvin73:
Stock, rooted. Anytime.