yashsingh1/xdaforums huggingface dataset:
[Galaxy Note 10.1 (2014 Edition) Android Developmen] DeanoD:
Any Tips For Long Overdue Full Wipe Install of RR?

Just looking for some tips here. I've gotten lazy with my daily driver unit, and it is showing the usual signs that I need a clean install. That usually means longer screen lags, and often odd homescreen and mail app behaviour. Like my mail app randomly opening a new mail window. But the biggest tell that I get is keyboard input going whacko - random added characters, foreign language symbols, etc. Like having a haunted keyboard.

A full format and wipe usually solves everything. Except that this time, I'm also dealing with SU and Magisk fighting each other. So, I gotta fix that also.

I hope that I'm not going to be the last user "in this room", but it has been an interesting trip. ;-DeanoD
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Lord Sithek:
Youa are not alone in this room, I'm using this great room on my smp600, but without any issues you are going through ;)

---------- Post added at 07:11 PM ---------- Previous post was at 06:36 PM ----------

Youa are not alone in this room, I'm using this great room on my smp600, but without any issues you are going through ;)
[Galaxy Note 10.1 (2014 Edition) Android Developmen] keru32:
Hi, thank you for support this old device. Which version should i install? The last one?

Regards.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] RXT00:
Just to clarify, are you using Supersu? If so you should only be using Magisk alone now, since they do the same thing and Magisk is still being updated.

Yes, the recent builds are stable for me.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] keru32:
Anyone can suggest any particular kernel? Or the one inside the rom is the best one with this build? Thanks
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Lord Sithek:
There is one kernel called Prime for this device, but it has no more support and I belive this one inside is the freshest
[Galaxy Note 10.1 (2014 Edition) Android Developmen] RXT00:
For more features, you can use the latest deathly kernel from the unofficial lineage builds; that's what I'm using right now and it runs really well with the latest RR builds. In fact I've never even had a random reboot.

You probably should only use it if you like to tweak the kernel settings with deathly auditor; if you don't tweak so much, the stock luis kernel is good.

Attached is the kernel I'm using right now that I extracted recently.

To install: boot to TWRP > install > change from zip flash to img flash > select the deathly.img attached > flash to boot partition

If you had magisk installed, reflash it to patch the new kernel.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Lord Sithek:
Thanks for sharing, I just flashed this and looks like very smooth experience :D Out of curiosity: from which Lineage build exactly did you extract this kernel?
[Galaxy Note 10.1 (2014 Edition) Android Developmen] keru32:
Which kind of twerking are you talking about?

Thanks
[Galaxy Note 10.1 (2014 Edition) Android Developmen] RXT00:
Deathly kernel has options like additional cpu and i/o governors, charging speed settings, etc.

I got it from here. I think build 20190914. If you want to extract, just download and open the zip and you'll see a boot.img inside. That's all you need to flash. Also, if you look at their github you'll see there's some recent kernel updates.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] DeanoD:
"recovery is not seandroid enforcing" msg in twrp opening

Just looking for a show of hands here. Who in this group is still getting this message in recovery? And if you do, get this message in recovery, are yiu ALSO dealing with the looping boot screens?

There is a website FonePaw that contends that this warning comes up due to "an incompatible" ROM has been installed on your Samsung device. They offer a fix, but it only works with specific devices to repair this error. They say there is a direct corellation with this message and boot loops. I also note that my Note which is still stuck wirh RR from last November build of RR. So, how did or do we get rid of the "not seandroid enforing error" in Recovery to go away. That MIGHT fix the bootloops. ;-DeanoD
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Lord Sithek:
Yes, I see this message every time I boot into TWRP, but I don't have any problem to boot into the system.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Lord Sithek:
I must admit it's very good kernel. Scrolling smoothness increased noticably :victory: Thank you!
[Galaxy Note 10.1 (2014 Edition) Android Developmen] RXT00:
Sounds like you're having a bunch of problems, maybe you should start from scratch. Here's what I did when I was having issues:

(If you don't have Odin use the link in step 2)

Follow this guide. (should reset your bootloader back to 4.4.2, this fixes issues for a lot of people)

Now re-upgrade your bootloader back to 5.1.1 (required for RR)

Flash TWRP; I recommend ShevT's version (for SM-P600 and SM-P601) it's been the most reliable one for me.

I assume you've installed it before but in case you forgot: Download the latest img.tar file (ShevT link above), choose the correct box in Odin (AP/PDA). Untick the Auto-reboot box. Start. After it says success, boot to TWRP manually using Power and Volume UP.

Now that you're in TWRP. Wipe System, Data, Cache, Dalvik-Cache.

Flash Latest RR

Flash OpenGapps Pico

Flash Magisk 20.1 (I've recently updated to v20 and things are working fine)

Now reboot to system

Good luck!

If any of the links are down, let me know, I'll try to re-upload. If this doesn't work, then it has to be some hardware difference.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] DeanoD:
My point here is that I have two SM-P600 units running current RR builds and neither of them display that warning in Recovery. But, the third unit, which is "stuck" on a Nov '18 build. It loops when a current build is flashed. And, it DOES display the error in Recovery. Coincidence? ;-DeanoD
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Lord Sithek:
:confused::silly::eek:
[Galaxy Note 10.1 (2014 Edition) Android Developmen] keru32:
Thanks for the kernel.

Which tricks do you suggest with Deathly Auditor? Or should I install the APK and then leave it stock?

Thanks again.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] RXT00:
I attached screenshots of some of my settings. Stock is pretty smooth, but mine is tweaked for a little more battery life and less heating up.

If you use Magisk, I recommend universal gms doze module for less standby drain.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] veekay:
Are the custom settings for the rom stored in a specific place? I'd like to move only my settings to a new setup (the personalization options).
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Bracher:
I have a question since the last update my WLan connection (Fritz!box) is no longer stable it shuts down round about after 30 seconds, this creates some problems when downloading or synchronising, has anybody noticed that as well?

Nevertheless it's a great ROM thanks a lot for all this work!!!
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Primokorn:
There's a while I didn't touch a Samsung device... The device of my friend has this bootloader: P600XXSDRI1

Is it OK or do I have to upgrade it first? If required where can I fint it? Thanks.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] JuankyKong:
Same

It looks like I am facing the same issue with this recent update, which BL did you use sorry ?
[Galaxy Note 10.1 (2014 Edition) Android Developmen] JuankyKong:
I do seem to have the same issue at this time with my P600 I did try LL 7.2 for a BL and still hangs on loading screen am I missing something?
[Galaxy Note 10.1 (2014 Edition) Android Developmen] DeanoD:
You, my friend, are experiencing the same elusive bug. I've done full wipes and restores, etc. And I'm at least back on this RR ROM. Just not the current build. For whatever reason, this bug comes up when you switch between using more than one ROM version on a SM-P600 unit. And as to WHY it happens, your guess is as good as anybone else's. Keep tryingin any case.

Sorrry for the delayed posting, I've had a "few" health issues. But I'm determined to find an answer. Good luck. ;-DeanoD
[Galaxy Note 10.1 (2014 Edition) Android Developmen] JuankyKong:
Hello, Thank you kindly for your help, and I seriously hope you health only gets better from now on.

I to be honest had no idea nothing about Custom Roms for android until I got this tablet, that being said for the last few days I have read and read info about it, and got myself some downloads attempting to install different ROMS, and different Bootloaders, I also found out how to go about changing this with the help of ODIN, and I do have the latest TWRP, my one question: As downloads are getting harder to find, would you happen to have a KK BL download that works with this device? or perhaps a few files that you know should work? my one doubt now, is that I may not have the correct files. thanks for your help!
[Galaxy Note 10.1 (2014 Edition) Android Developmen] wadken1:
I've been stuck with an old version LOS for a good while now so thought I'd give RR a try. I've downloaded both the available builds from this link by two different methods and have tried to flash them via the latest official TWRP. Both builds give me a "Digest failed to match on....." and "Digest verification error" messages.

This sounds like it's probably a problem with the build itself rather the TWRP - can you tell if have you flashed these files yourself ? i.e do you know they work OR perhaps you normally just update via OTA.

I did notice that both the build files are labelled as OTA so I also wonder if they are complete recovery flashable roms.

Cheers for any help
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Lord Sithek:
So yesterday I flashed latest build from TWRP without any problem. Actually, I've never had any major problem with flashing RR or Lineage, but as I see in this thread, some users have.

OTA feature will direct you to download link, but you have to flash it manually from TWRP anyway.

By the way, I don't know if you are aware that those builds are generated automatically every two days. So no new feature included for a long time, maybe some minor kernel changes...
[Galaxy Note 10.1 (2014 Edition) Android Developmen] RXT00:
I haven't experienced any errors flashing except for corrupted downloads, and tbh I haven't tested the latest builds since they keep changing without any major updates. How's your internet connection? It may be a matter of just re-downloading. I can try to upload the current build I'm on, but my upload is really slow so it could take a while. Also, I'd suggest you follow the whole post you quoted since it may eliminate other issues and I only use the TWRP version in that post (unofficial).

Also [MENTION=10275041]JuankyKong[/MENTION] I'd suggest you try it too as a last resort: https://xdaforums.com/showpost.php?p=80509287&postcount=440
[Galaxy Note 10.1 (2014 Edition) Android Developmen] wadken1:
Thanks to you and [MENTION=9630286]Lord Sithek[/MENTION] for your replies. I did a little checking into md5sum and found that indeed the "digest" error is a result of file corruption resulting in a mismatch between the chesksum value that TWRP calculates for the rom.zip and the one posted in the md5sum file. It turns out that both my downloads, despite multiple attempts and different routes, were both corrupted. I managed to get a good download lat night and flashed it along with all the other relevant files. Everything flashed without error but, just like current LOS builds, it got stuck on the boot screen - just endlessly displaying the boot animation (left it overnight to be certain it wasn't just being slow).

So, when I get a chance, I'm going to have to try your method in post #440.

Cheers for now
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Lord Sithek:
Good luck buddy :) Soon I'm leaving this boat, because new Galaxy Tab S5e just arrived to me. But it was nice 5-years experience :svetius:
[Galaxy Note 10.1 (2014 Edition) Android Developmen] stevvie:
Just a heads up, tried updating from RR-N-v5.8.5-20190529-n1awifi-Luis.zip to RR-N-v5.8.5-20191202-n1awifi-Luis.zip with the latest gaps just like normal in TWRP and was greeted with 'downloading do not turn off target'. I even tried a full wipe and just the RR-N-v5.8.5-20191202-n1awifi-Luis.zip and OpenGaps but SAME thing. The only way to get rid of it thankfully was to restore a backup of my boot partition.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] akramarshad:
Same thing happened to me and I wiped everything including internal ROM and restored from some previous backup,If it did not work I was planning to to use Odin to go back to official Lollypop.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] stevvie:
If it happens again just restore ONLY the boot img backup
[Galaxy Note 10.1 (2014 Edition) Android Developmen] supergrobi94:
Same happened to me after trying updating from version 20191118 to 20191220 with getting stucked in download mode. Following solution worked for me:

-Extracted boot.img from version 20191118 zip and flashed via TWRP

-Device worked again, but no root. So i flashed latest Magisk and now it's working fine. ツ
[Galaxy Note 10.1 (2014 Edition) Android Developmen] dusan.s:
Hey people, I'm kinda stuck during a flash so I could use some help.

I decided to dust off my p600, after it being idle for a couple of years. It had an early temasek cm13 build on it with a lot of stuff not working properly so I thought I'd try a new rom.

I flashed the newest TWRP (3.3.1-0).

Deleted data, cache, dalvik cache and system.

Tried flashing the rom zip file with zip signature verification - FAILED.

Tried flashing without the verification - went through with no problems logged ("script succeeded: result was [1.000000]").

Looking at the files, the sdcard folder contains only one folder "TWRP". It looks like nothing was actually installed. Internal storage shows 25.8/26.0 GB free.

While booting, after the initial "Samsung Galaxy..." white letters upon booting-up, the device will go idle. The display will be black but turned on, indefinitely.

I've tried redoing the steps to no avail. I've checked the file's MD5 hash. I've used the 20200102 build. After that I've used an older build with the same result.

Any tips on how to proceed?
[Galaxy Note 10.1 (2014 Edition) Android Developmen] qietan:
Hi there,

I have exact the same problem like dusan.s . Is there anybody who might help?
[Galaxy Note 10.1 (2014 Edition) Android Developmen] DeanoD:
....AND you are saying that this trick got you around the "boot screen loop of death"? Once you got the boot image installed and running, were you then able to install newer builds afterward? As in regular TWRP flashing?

From what I've seen on my tab which is still stuck with an older RR build, there was SOMETHING left from running an older Lineage build. Some kind of tenacious artifact causes the looping. But, I an ef well gonna try your fix! Thank you for this post and please let me know if you can now keep installing newer builds after your fix. ;-DeanD
[Galaxy Note 10.1 (2014 Edition) Android Developmen] qietan:
I have found the error. Even if you install TWRP, the correct Bootloader is missing.

https://xdaforums.com/showpost.php?p=71355516&postcount=1247

Just update the bootloader and it will work. I found the information in another thread, maybe install info could be updated here
[Galaxy Note 10.1 (2014 Edition) Android Developmen] dusan.s:
Yup, that did it. Thanks a lot!
[Galaxy Note 10.1 (2014 Edition) Android Developmen] DeanoD:
Think I Am Screwed (as in bricked badly)

Hi, I'm still trying to update my spare smp600, and I think it is gone. A couple of new things have come up. First, I get an error message like "persist / bad command" in recovery. I Googled it and there is persist.img file that COULD be used as a fix, but I don't have it. My other prob is that while I can get INTO recovery, my input controls are so tetchy that it won't let me select files to flash. Any tips, here? Only thing that comes to mind is to setup files on the sd card with only one .zip file per folder... Thanks. ;-DeanoD
[Galaxy Note 10.1 (2014 Edition) Android Developmen] pingwingugu5:
Hi. Where did you get the updated bootloader for SM-P600? The ZakooZ guide gives a link to BL_P600XXUDPL1_LL.tar.md5 on androidfilehost but I am getting only "Mirror not found" there. So it looks like the file is gone now :(
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Bracher:
Hi to everbody, I have a problem which is out of topic, sorry - but I have no idea where else I can put it: my P-600 does suddenly no longer recognise any SPen, I tried several... The display is seems ok, I can draw with my fingers but no longer with SPen. I searched in the net for tips, got even back to format all my data and made a clean install but nothing helped. I'm using this ROM now a long time, had never problems, but out of a sudden this.

For me it's a big problem as I used the SPen with LectureNotes a lot. Has anybody had similar problems do you think it's a hardware problem (unfortunately the replacement of the display is quite expensive and I don't know if this might really help.

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

Sorry for coming back ones more: if it is not a hardware Problem but linked to the latest nightlies - has anybody a RR ROM from December - because in December my SPen worked fine still on the first two January nightlies I had as well no problem. But I unfortunately deleted them!

PLEASE DISREGARD THIS POST IT'SOLVED

I realised to late, that on the download side now the nightly of December is placed - and with this nightly my P-600 recognises ones more SPens!!!!
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Smuji:
hey, i made a mistake. i wiped eveything: dalvik, cache,data,internal and system..... now it doesn't start anymore und i can't get a connection to my pc for flashing TWRP or ROM.... i have an older version of TWRP and i can go into the menu of it.

what can i do? :(:(:confused::confused:
[Galaxy Note 10.1 (2014 Edition) Android Developmen] uktavxda:
Encryption Support

First of all, a big thank you for the custom rom. Its the only one I tried that is works out of the box hassle free on my P600.

I am trying to get the P600 to encrypt because of work requirements. Do you know what would be required to support this? Currently if I choose to encrypt through settings it merely reboots and does nothing.

Thanks
[Galaxy Note 10.1 (2014 Edition) Android Developmen] meekspace:
Thanks to all the developers and those who are maintaining this thread with their support.

It's nice to have this tablet back up and running, resurrected!!!

Takes a while to charge though.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] meekspace:
So where is the deathly.img on that github? I was trying to get the latest.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] narenrajaram:
Hey guys, I installed this ROM yesterday with the above steps followed. I'm stuck in the splash screen that says "Get Resurrected" forever. Frustrated trying several steps over and over again. Any help would be greatly appreciated. Thank you.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] meekspace:
It could take 10 minutes to reboot....
[Galaxy Note 10.1 (2014 Edition) Android Developmen] lecorbusier:
Give it 30 to be on the safe side.

Normally it would take 10min after dirty flashing an update on my S5, to recompile all ART Binaries (System, Gapps, user apps). And considerably less for a clean install with only rom and GAPPS. But **** can happen, probably phone crashes and reboots several times and will still make it in the end.

I was once unable to update/install Lineage dirty or clean on my S5, but still able to restore a TWRP backup. So i quit and could install the official RR at the first attempt, which became sort of instable one year ago. I then immediately could flash Lineage, again.

So try installing a different rom, if only to make the phone install RR at the next attempt.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] meekspace:
Is this ROM still being worked on? I have picked up on a few minor issues. If so, I'm happy to share the info ?
[Galaxy Note 10.1 (2014 Edition) Android Developmen] narenrajaram:
Everytime I tried a different method, I let it boot for 15 minutes atleast but nothing helped, unfortunately.

I followed the steps in the thread mentioned by the OP. I also tried the flashing prime kernel v8 for lollipop after flashing the rom nothing helped.

Any other suggestion please? Thank you.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] meekspace:
When I had this problem, I went back to the beginning.

Flash stock rom 5.1.1 with Odin and then setup tablet

Flash twrp with Odin and restart into recovery

Wipe system data cache

Flash rr rom, gapps and magisk.

I found that having the power cord unplugged helps in trying to force reboot into recovery

Also have a clean formatted SD card. I suspect there was something left over in the card that messed with things
[Galaxy Note 10.1 (2014 Edition) Android Developmen] RXT00:
The github link is just the changelog. Go to the first link https://download.exynos5420.com/LineageOS-14.1-Deathly/n1awifi/ and download the latest rom there. It's the boot.img inside the rom zip.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] meekspace:
According to this thread

https://xdaforums.com/galaxy-note-1...p601-lineage-nougat-galaxy-note-10-1-t3546012

only lineage OS is still active.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] diggedy:
Does anyone know where the latest download for this is? The link in the first post takes me to a changelog
[Galaxy Note 10.1 (2014 Edition) Android Developmen] clicker4721:
Download evaporated

Oh, man! I just started using this rom less than a week ago. I messed up and got stuck in a boot loop. I come back and the download is gone!

Man, this was the best my tablet had ever run. I hope the download comes back!

EDIT: The source is still on github. I can imagine that it'd be wonderful to be able to get to the rom on Mega. I am totally willing to build it for myself, if somebody could point me in the right direction. I do development at work but I don't know anything about developing for Android.

EDIT: IT'S BACK UP!! I hope Luis enjoys his new bone! :)
[Galaxy Note 10.1 (2014 Edition) Android Developmen] djlongmoney:
help please

can someone please help me with the install for this i cannot get past the error 7 when flashing using twrp. i have the most uptodate version of twrp for the smp600 but i think there might be something im either missing or didnt do correctly and im just trying to update a tablet i really enjoy
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Wozzyb:
I have a problem with installs after the september 2019 ota. I tried the november and december versions a few months back and tried todays nightly with the same result. What happens is that everything installs normal but when it boots up and gets to the launcher screen it is completly black so i cannot see anything but when I hold down the power button the menu appears and allows me to shut down, reboot etc. I reinstall the september ota and everything is back to normal and working. Anyone had a experience like this?
[Galaxy Note 10.1 (2014 Edition) Android Developmen] DeanoD:
OK. I got the new Tab. Bit faster than this.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Roger_K:
I just gotta say, this worked flawlessly. Thanks to the author and the team for the best build ever!