yashsingh1/xdaforums huggingface dataset:
[Galaxy Note 10.1 (2014 Edition) Original Android D] ollimi1:
Hey bschatzow!

Make sure you set google assistent as default assistent in settings>apps>gear symbol>assist+voice input. There are also some apps in playstore which enables/installes google assistent.

And I know there is an how-to somewhere in the thread but don't ask me where, Lol! :good:

---------- Post added at 09:47 ---------- Previous post was at 09:32 ----------

Hey k-semler,

you are on a LL bootloader, but official LOS is still based for KK bootloader for some reasons. So if you want to use it you need to flash KK LOS kernel uploaded by [MENTION=4810273]ZakooZ[/MENTION] or Prime V7 KK by [MENTION=5006338]Hitman[/MENTION].

Download links for KK+LL kernels are a few pages back, Prime has it's own thread.

Probably the next official build is anyway based on LL bootloader so no need to go back for just only one build.

Q: "is there something that I can do"?

A: "Yes, read at least the last few pages next time. There is a detailed how-to posted by the OP with further informations and instructions"
[Galaxy Note 10.1 (2014 Edition) Original Android D] k-semler:
Thanks. I'll wait until the next official build then. I've only had the tablet for 2 days now, and it was given to me because it was "broken". (wouldn't power on, wouldn't charge, black screen). I fixed it, so now I have a tablet. It's like factory new right now, but the ROM that I flashed is based on 5.1, so it's a little dated. I'd like to have Nougat on it.
[Galaxy Note 10.1 (2014 Edition) Original Android D] bschatzow:
My device is English and in the US. Where is the gapps-config.txt file? I looked at the latest download (pico) and I do not see the file.
[Galaxy Note 10.1 (2014 Edition) Original Android D] jaholm:
Hi,

I installed 20170302 with supersu 2.79 SR3 and opengapps nano 20170303 after formatting system and data.

My external sd-card (128G, formatted with exfat) was detected and I can see how much GB was free.

But the I cannot accces the external sd-card via standard file manager. Document provider did not work. So I cannot access my Titanium backup via document provider. Access via total commander works.

I checked the sd-card with fsck.exfat on my Linux system. Filesystem is ok.

So, I'm back on 20170113.

Anyone else with this problem, or any hints?

---------- Post added at 02:26 PM ---------- Previous post was at 02:25 PM ----------

PS: KK bootloader
[Galaxy Note 10.1 (2014 Edition) Original Android D] ZakooZ:
That's related to the kernel being SELinux enforcing; Please post dmesg (kernel log, "adb shell dmesg") immediately after it fails, as the problem has never happened in my end but I'm aware of it

Also don't install supersu, install the official lineage root in the first post
[Galaxy Note 10.1 (2014 Edition) Original Android D] jaholm:
You are right!

Access for 'search' is denied for comm=Binder on dev=mmcblk1p1

This block is repeated ever and ever:

[ 606.943425] [B2: logd.auditd: 2369] type=1400 audit(1488725320.983:3866): avc: denied { search } for pid=6824 comm="Binder:4393_5" name="/" dev="mmcblk1p1" ino=1 scontext=u:r:priv_app:s0:c512,c768 tcontext=u:object_r:exfat:s0 tclass=dir permissive=0
[ 606.943965] [B2: logd.auditd: 2369] type=1300 audit(1488725320.983:3866): arch=40000028 syscall=334 per=800008 success=no exit=-13 a0=ffffff9c a1=b4379be0 a2=0 a3=0 items=1 ppid=2499 ppcomm=main pid=6824 auid=4294967295 uid=10008 gid=10008 euid=10008 suid=10008 fsuid=10008 egid=10008 sgid=10008 fsgid=10008 tty=(none) ses=4294967295 comm="Binder:4393_5" exe="/system/bin/app_process32" subj=u:r:priv_app:s0:c512,c768 key=(null)
[ 606.944469] [B2: logd.auditd: 2369] type=1307 audit(1488725320.983:3866): cwd="/"
[ 606.944984] [B2: logd.auditd: 2369] type=1302 audit(1488725320.983:3866): item=0 name="/mnt/media_rw/6ED1-12FC/DCIM/Camera/20150210_101500.jpg"
[ 606.946487] [B2: logd.auditd: 2369] type=1320 audit(1488725320.983:3866):
[Galaxy Note 10.1 (2014 Edition) Original Android D] ZakooZ:
With help from [MENTION=3594812]ShevT[/MENTION] this issue will most likely be solved by next build
[Galaxy Note 10.1 (2014 Edition) Original Android D] ericfabreu:
You have to create it manually. Just put the attached file in the same folder your gapps package is in and try flashing it again.

If for some reason this doesn't work, reflash the 20170302 build to undo any changes you've done to the build.prop file and flash gapps again (with the gapps-config.txt file in the same folder)
[Galaxy Note 10.1 (2014 Edition) Original Android D] bschatzow:
I could not get the 3/2 file to install. Working on the 2/11 Rom. I will refresh the gapps with the config file. Tried the new gaps and the config file. Still not working for me.
[Galaxy Note 10.1 (2014 Edition) Original Android D] bschatzow:
I was using the nightly, not the official.
[Galaxy Note 10.1 (2014 Edition) Original Android D] mosimchah:
We don't have nightly lineage builds, what are you talking about?
[Galaxy Note 10.1 (2014 Edition) Original Android D] ericfabreu:
The pico package does not seem to install the Google (search) app as a system app and I don't think that the assistant will work without it being a system app. Try flashing the nano package instead of pico (make sure that the gapps-config.txt file is still in the same directory as the nano package when you flash it)

Also, why did the 3/2 file fail to install? If you're on the Lollipop bootloader, you'll need to flash the Lollipop kernel after flashing the ROM. If you're still on the KitKat one, just flashing the ROM should work. The 2/11 ROM isn't an official Lineage OS ROM (the first one was 2/22), though, so you'll need to do a clean flash like ZakooZ said in order for it to work
[Galaxy Note 10.1 (2014 Edition) Original Android D] bschatzow:
I thought (incorrectly, I guess) it wasn't official until it was built for LL not kk. I'll wait until the new build comes out for ll and install it as well as a new boot loader.
[Galaxy Note 10.1 (2014 Edition) Original Android D] ericfabreu:
If you're on the KK bootloader, you don't actually have to do anything. Just clean flash the new rom and everything should be working fine. When the LL rom comes out, you can just flash the LL bootloader ZakooZ posted a few pages ago. If you're on the LL bootloader, you just have to clean flash the rom and flash the LL kernel that he also posted a few days ago.

I don't know if the bootloader region makes a difference, but if you want to make sure you have the latest LL bootloader for your region, you can download Samsung SmartSwitch and use the emergency firmware recovery option to download and flash the latest stock rom
[Galaxy Note 10.1 (2014 Edition) Original Android D] bschatzow:
Will I have to do another clean flash or will you be able to do a dirty flash with the ll boot loader?
[Galaxy Note 10.1 (2014 Edition) Original Android D] ericfabreu:
Flashing a new bootloader does not require a clean flash. You only need a clean flash if this is the first time you're flashing one of the official Lineage ROMs
[Galaxy Note 10.1 (2014 Edition) Original Android D] bschatzow:
I am using the February nightly, again I thought it was unofficial until ll was supported. If I flash the ll you posted a few pages ago and the official Rom will I be able to dirty flash after the new Rom that supports ll is released?

---------- Post added at 02:35 PM ---------- Previous post was at 02:33 PM ----------

It didn't install as I was doing a dirty install. Just found out that I could not do this. Can't install an official release on top of an unofficial release.

---------- Post added at 03:11 PM ---------- Previous post was at 02:35 PM ----------

I have re-read the last several pages of posts and I am confused on what is necessary to do to go from the 2/11 unofficial version to the 3/3 office version. I have kk boot loader and 3.4.113 kernel. I understand I need to do a clean install, but don't know if the kernel and boot loader need to be updated also. Thanks in advance.
[Galaxy Note 10.1 (2014 Edition) Original Android D] ericfabreu:
If you're the KK bootloader, you just need to do a clean install. You won't need to update the kernel or bootloader for now. You'll only need to flash the LL kernel now if you want to use the LL bootloader with the current (03/02) rom. If that's the case, you'll need to flash the bootloader, then clean flash the rom, and flash the LL kernel on top of it.

However, when the LL rom is released, you'll need to flash the LL bootloader. This will *not* require a clean install. You only need a clean install now because you're updating to an official Lineage rom for the first time.
[Galaxy Note 10.1 (2014 Edition) Original Android D] bschatzow:
I installed the file linked from the first post and I don't have root access after my new clean install. I did not see that I had to enable root in development options. .Does supersu not work?
[Galaxy Note 10.1 (2014 Edition) Original Android D] jerrys0828:
Flash the root add-on linked in the first post and it the root option will appear in developer settings.
[Galaxy Note 10.1 (2014 Edition) Original Android D] Urich24:
Hi where can I find the kit Kat bootloader please
[Galaxy Note 10.1 (2014 Edition) Original Android D] mosimchah:
You don't need the KitKat one, just flash the lollipop kernel and you're good to go (linked a few pages back), very soon you won't be able to flash lineage while on the KitKat bootloader...
[Galaxy Note 10.1 (2014 Edition) Original Android D] Anonymous9926:
hi, develper.

Im using stock firm Lollipop 5.1.1.

When is the ROM loaded with the LL bootloader uploaded?
[Galaxy Note 10.1 (2014 Edition) Original Android D] mosimchah:
This Thursday most likely
[Galaxy Note 10.1 (2014 Edition) Original Android D] hitman1376:
The upcoming build is going to be for the Lollipop Bootloader ( btw , you can ask any TE5420 member relating to the project like These Dear users [MENTION=4810273]ZakooZ[/MENTION] and [MENTION=6227169]mosimchah[/MENTION] who can help you best ... ) and AFAIK , Users are going to be offered a Bootloader zipfile to flash through Odin before using the ROM ... I hope it helped ;)

With Best Wishes

Hitman1376​

PS. Sorry , My mistake ... I thought you were the guy I had left my reply for :D ...
[Galaxy Note 10.1 (2014 Edition) Original Android D] bschatzow:
"Originally Posted by bschatzow

I have re-read the last several pages of posts and I am confused on what is necessary to do to go from the 2/11 unofficial version to the 3/3 office version. I have kk boot loader and 3.4.113 kernel. I understand I need to do a clean install, but don't know if the kernel and boot loader need to be updated also. Thanks in advance." I did the update and all seems to be working well (including assistent)
[Galaxy Note 10.1 (2014 Edition) Original Android D] etmflde:
Installed the lineage-14.1-20170302-nightly-n1awifi-signed.zip on LL bootloader and the first thing I noticed is that some applications are not able to see the content of my 128GB SD card (valid also for SD card browser in the settings - it display a red hourglass and a message that the content of the SD card cannot be displayed right now). ES File Explorer can read and access the content of the external SD card. Any idea how to fix this? My Backup Pro gives a hint about "Unhide SD card" but I could not find this option anywhere.
[Galaxy Note 10.1 (2014 Edition) Original Android D] ZakooZ:
Read the last pages
[Galaxy Note 10.1 (2014 Edition) Original Android D] etmflde:
Read it, and it seems the issue is not related to the bootloader version (I have LL, the guy that originally reported it, was on KK). I will wait for the next release.

Other issues: Facebook and Facebook Messenger keep restarting and I cannot open any of the two.

Opera gives me the following message: "To run Opera you need more space. Try removing some apps or clearing app data" and then it crashes. Not need to mention that I still have plenty of space and memory available.

I will try to uninstall them and reinstall them again.
[Galaxy Note 10.1 (2014 Edition) Original Android D] rayik:
On LL bootloader. Working well with LL kernel posted few pages back.

Before wiping system used Titanium Backup Pro to backup apps and data. Titanium restored all apps and data with no problems.

Hardware buttons area used. Note on screen buttons are not present and can't find option to enable. Hardware menu button not working in Titanium. Work around was in button options set home button long press to open / close menu.

Looking forward to installing official LL based ROM.
[Galaxy Note 10.1 (2014 Edition) Original Android D] mosimchah:
You already did, lol
[Galaxy Note 10.1 (2014 Edition) Original Android D] Bad Mod:
Does that mean it is also possible to have snote? Will that be fixable by the rom or the kernel? I know there is no plan or promises to fix that but it is nice to know we could have it someday. Anyway, I found MyScript and I enjoy it even more than snote and I'm ready for LL build.
[Galaxy Note 10.1 (2014 Edition) Original Android D] rayik:
My bad. Meant to say looking forward to official LL based rom.
[Galaxy Note 10.1 (2014 Edition) Original Android D] Stogie87:
With latest nightly update double tap on home button feature is not working anymore.
[Galaxy Note 10.1 (2014 Edition) Original Android D] ArmadiloDS:
Im on the latest build and its awesome! I get about 10 days Batterylife!!! Until now I had no bugs.

The only thing I miss is Screen Mirroring. It would be nice if it get into "Not-working"-list.
[Galaxy Note 10.1 (2014 Edition) Original Android D] etmflde:
Do you mean the one from today (March 9th)?
[Galaxy Note 10.1 (2014 Edition) Original Android D] Stogie87:
Right, i remember with unofficial builds Screen Mirroring was definitely working, but i forget to test it with official builds.

On my device screen mirroring is also not working.

---------- Post added at 12:21 PM ---------- Previous post was at 12:19 PM ----------

Yes.
[Galaxy Note 10.1 (2014 Edition) Original Android D] etmflde:
Did you test also if the access to external SD is working now properly?
[Galaxy Note 10.1 (2014 Edition) Original Android D] Stogie87:
I never had problems with access to external sd card.^^
[Galaxy Note 10.1 (2014 Edition) Original Android D] ollimi1:
Is the build from today based on LL bootloader as mentioned earlier or still KK bootloader?
[Galaxy Note 10.1 (2014 Edition) Original Android D] ZakooZ:
LL! I'll update the first post when I get home
[Galaxy Note 10.1 (2014 Edition) Original Android D] Anonymous9926:
I use stock 5.1.1 lollipop.

Today I install twrp recovery / lineage-14.1-20170309-nightly-n1awifi-signed / open_gapps-arm-7.1-pico-20170309

I am having difficulty installing now.

setup wizard is stopping...

so i cant proceed to the next step.

I also try to install open_gapps-arm-7.1-nano-20170309 but i cant....

also try to install lineage-14.1-20170302-nightly-n1awifi-signed

That's working but, i can't proceed recovery mode and can't upgrade lastest ver. 20170309
[Galaxy Note 10.1 (2014 Edition) Original Android D] amitabh15:
So it's safe to flash it over the previous nightly? I had downgraded to KK a long time ago when I was using the unofficial ROMs. So I'm presuming I'm still on KK bootloader. Is it safe to flash the update? Will the 9Mar update automatically update the bootloader or is the ROM compatible with both KK & LLC bootloaders?
[Galaxy Note 10.1 (2014 Edition) Original Android D] mosimchah:
It won't boot on the KitKat bootloader, you would have to flash a KitKat kernel, and soon the ROM won't even flash on the KitKat bootloader
[Galaxy Note 10.1 (2014 Edition) Original Android D] ollimi1:
Hey Anonymous9926,

You can try to remove "setup wizard" from system/apps in TWRP recovery file manager, just not forget to mount system right before. And make sure you have latest twrp from shevT 7.1.1 thread installed.
[Galaxy Note 10.1 (2014 Edition) Original Android D] THERAZORKILLE:
Where can we get the LL bootloader to flash with Odin? One of my P600s already has the LL bootloader, so no problem there, but my daily driver was rooted long before the official LL ROM was released.
[Galaxy Note 10.1 (2014 Edition) Original Android D] yl1504:
Same problem on my side would love to know what is the quickest and easiest way to get the LL bootloader up and running?
[Galaxy Note 10.1 (2014 Edition) Original Android D] mosimchah:
It was posted a few pages back
[Galaxy Note 10.1 (2014 Edition) Original Android D] Anonymous9926:
I cant find twrp file manager system/app 'setup wizard'

I cant see anymore
[Galaxy Note 10.1 (2014 Edition) Original Android D] mosimchah:
It's in priv_app and removing the setup wizard is not a good idea...
[Galaxy Note 10.1 (2014 Edition) Original Android D] Anonymous9926:
What should I do??

Install 20170302 ver. is working but I cant update 20170309 ver.

it say "device could not restart to recovery mode" - nevertheless installed twrp lastest ver.....;;;

and I install 20170309 ver is not working for me. I cant proceed beacause setup wizard is stopping
[Galaxy Note 10.1 (2014 Edition) Original Android D] mosimchah:
Just use the older version, you don't need to update
[Galaxy Note 10.1 (2014 Edition) Original Android D] ZakooZ:
Please follow this procedure to get the logcat of the SetupWizard crash:

1. https://drive.google.com/file/d/0B_qzEVl3qv8MMFoyOUJjd1ZrMnM/view?usp=sharing

Flash that boot.img in TWRP (in the install menu select Install Image, select this boot.img, select the 'boot' partition, flash)

2. Boot 20170309 and use it until the SetupWizard crashes

3. Follow https://xdaforums.com/showthread.php?t=1726238 to get the logcat, and post it here

You can also dirty flash 20170309 over 20170302
[Galaxy Note 10.1 (2014 Edition) Original Android D] ZakooZ:
How to update to Lollipop bootloader (required for 20170309 and later builds)

Updating the bootloader is very quick and doesn't wipe data or repartition the device.

If the last Samsung ROM you had was 5.1 Touchwiz, you already have lollipop bootloader and don't need to follow these steps.

1. Download the bootloader-only Odin package: BL_P600XXUDPL1_LL.tar.md5

This has the latest lollipop bootloader (December 2016)

https://www.androidfilehost.com/?fid=817550096634751968

2. Download Odin 3.11

You can skip this if you already have a working Odin

https://www.androidfilehost.com/?fid=673368273298937183

3. Shutdown your tablet and start it up by holding Power+Home+Volume Down to enter Download Mode. Volume Down is the one right next to the power button.

Really shut it down and use this key combination, if you use Advanced Restart the bootloader won't change.

4. Make sure the screen of your tablet has a green android symbol with a "Downloading..." text

5. Open Odin3_v3.11.1.exe and follow the instructions in this image:

If anything is missing, you WON'T flash bootloader succesfully.

6. Click Start. Your tablet will automatically reboot back into your ROM.

7. To verify you have the new bootloader, you can run in terminal emulator "getprop ro.bootloader". It should say P600XXUDPL1.
[Galaxy Note 10.1 (2014 Edition) Original Android D] Cool34000:
Rebooted in download mode, flashed the new bootloader BL_P600XXUDPL1_LL.tar.md5. All seems good:

<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Added!!
<ID:0/004> Odin engine v(ID:3.1101)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> sboot.bin
<ID:0/004> NAND Write Start!!
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Removed!!
<ID:0/004> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)

But still with P600XXUCNH3 bootloader... What's wrong?
[Galaxy Note 10.1 (2014 Edition) Original Android D] Orion116:
How are you rebooting to download mode? Use the manual key combo and it will work.
[Galaxy Note 10.1 (2014 Edition) Original Android D] Cool34000:
I rebooted directly in download mode from restart menu (I have enabled the advanced reboot in dev options)

I tryed with the key combo and it's working... Weird, but thanks!

---------- Post added at 09:52 PM ---------- Previous post was at 09:44 PM ----------

Sorry, I missed the important part:
[Galaxy Note 10.1 (2014 Edition) Original Android D] jerrys0828:
After flashing the BL and installing the ROM, I can't get through device setup. It crashes briefly at the "Anything Else?" screen, then hangs on "Just a Sec" or "Completing setup" before returning to "Anything Else?".

I wiped everything except internal storage and SD card, and tried with 03.09 and 03.04 OpenGapps Nano.

Edit: I had reset into Download mode as instructed (proper shutdown, not using advanced power menu button.)

Edit 2: Dirty flash method in post #1257 worked!
[Galaxy Note 10.1 (2014 Edition) Original Android D] Genebaby:
He did kind of say not to use the download menu, lol.

I will do this later and check out the new build. Thanks guys.
[Galaxy Note 10.1 (2014 Edition) Original Android D] enotar:
Al ok at first here Thank you. But SELinux is enforcing on this one?
[Galaxy Note 10.1 (2014 Edition) Original Android D] mosimchah:
Yes
[Galaxy Note 10.1 (2014 Edition) Original Android D] Cool34000:
Don't blame me... Every update feels like xmas to me! I was so excited that I just saw the BL and flashed as I usually do :angel:
[Galaxy Note 10.1 (2014 Edition) Original Android D] ZakooZ:
You didn't miss it - I edited it in afterwards :)
[Galaxy Note 10.1 (2014 Edition) Original Android D] ZakooZ:
I'll be investigating the issue... I probably already fixed it - problem with OTA update permissions... A fix not included in the current build...

In the meantime you can flash 20170302 + kernel-n1awifi-cm-141-LL-bootloader.zip , complete the setupwizard, then dirty flash 20170309 on top.
[Galaxy Note 10.1 (2014 Edition) Original Android D] Revan335:
Forced Closed by Setup Wizard finishing!

Please fixit!

Many thanks for your work!

I'm testing your Post above!
[Galaxy Note 10.1 (2014 Edition) Original Android D] Anonymous9926:
I can't OTG update...

Whats the problem? T.T

I installed TWRP recovervy lastest ver.
[Galaxy Note 10.1 (2014 Edition) Original Android D] rayik:
On boot I'm getting: "kernel is not seandroid enforcing". Not sure how to correct this.

20170309 with LL bootloader
[Galaxy Note 10.1 (2014 Edition) Original Android D] mosimchah:
Don't worry about it, it's not anything bad
[Galaxy Note 10.1 (2014 Edition) Original Android D] rayik:
Thanks.

If it means anything, this was a dirty flash over 20170302. (Had clean flashed that on LL bootloader and then flashed LL kernel)
[Galaxy Note 10.1 (2014 Edition) Original Android D] mosimchah:
There is nothing that you can flash in TWRP to change the bootloader, you have to use Odin
[Galaxy Note 10.1 (2014 Edition) Original Android D] ViRuS-MaN:
the last release crash my tablet
[Galaxy Note 10.1 (2014 Edition) Original Android D] etmflde:
I could not do the update using option to update LOS from the settings (after the download finished, got the message that the tablet cannot be reboot in recovery. I was also not able to find the folder where it have downloaded the zip file so I went to LOS page and downloaded manually the latest release and then did the manual upgrade via TWRP. It went fine and now I can access the external SD card (thank you!) and most of the stuff seems OK with two exceptions: Flipboard and Opera browser continue to crash while using them. So far I did not check the S-Pen and many other apps so I still have things to do.

Couple of questions:

- I have not loaded a newer version of GApps since a while now (have always used the nano version and had no issues). Do I need to do that now and then or the apps included in GApps are also updated through normal App Store updates?

- Have anybody tried to encrypt the tablet and the content of the external SD card? Will TWRP still see the external SD after that and be able to install further updates? I need that in order to install AirWatch Agent and some other related apps.