yashsingh1/xdaforums huggingface dataset:
[Galaxy Note 10.1 Android Development] html6405:
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.

Code:

*

Your warranty is now void.

* I am not responsible for bricked devices, dead SD cards,

* thermonuclear war, or your getting fired because the alarm app failed. Please

* do some research if you have any concerns about features included in this ROM

* 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.

Odin

- Odin3 v3.10.5

Heimdall

- Glass Echidna

TWRP for Samsung Galaxy Note 10.1

How to flash TWRP with Odin

1. If your phone is turned on normally, turn on Advanced reboot in Developer options and select "Download" from the Restart menu. Alternatively, power it off and press the Power, Volume Down simultaneously. When the warning screen appears, release all buttons and press Volume Up.

2. In Odin, import the appropriate twrp.tar file for your variant with the "AP".

3. Disable auto reboot in Odin and press start.

4. You can then boot directly into TWRP by pressing the Power and Volume Up simultaneously. Release all buttons as soon as you see the boot screen ("Samsung Galaxy Note 10.1").

How to flash TWRP within a previous version of TWRP

1. If your phone is turned on normally, turn on Advanced reboot in Developer options and select "Recovery" from the Restart menu. Alternatively, power it off and press the Power and Volume UP simultaneously. Release all buttons when the boot screen appears ("Samsung Galaxy Note 10.1").

2. In TWRP, tap "Install" then "Install Image".

3. Navigate in the folder structure to the location of the appropriate twrp.img file for your variant and tap it.

4. Select the "Recovery" radio button.

5. Move the slider to the right to flash the TWRP image.

6. Tap "Reboot System" or, alternatively, tap the back arrow 3 times to return to the main menu, then tap "Reboot" and "Recovery" to reboot into the TWRP image you have just flashed.

Bugs

- You tell me!

Credits

TWRP Team and all people who worked / are working on the exynos 4 devices.

Sources

- n8000 repository

- n8010 repository

- n8020 repository

- TWRP repository

Do you like my work?

Than you can simply hit the thanks button and consider to spend me a coffee or a beer,

I'm doing this in my spare time and every donation keeps me motivated.

donate

XDA: DevDB Information

TWRP 3.6.0_9-X, ROM for the Samsung Galaxy Note 10.1

Contributors

@html6405

ROM OS Version: 7.x Nougat

ROM Kernel: Linux 3.0.x

Version Information

Status: Stable

Current Stable Version: 3.5.2_9-1

Stable Release Date: 2021-02-14

Created 2021-02-14

Last Updated 2021-10-12
[Galaxy Note 10.1 Android Development] CurbThePain:
Hey after updating to this recovery I noticed when I went to wipe my /data partition it would end up wiping my internal storage even though I did not select the internal storage. Just wanted to let you know about this bug I encountered.
[Galaxy Note 10.1 Android Development] html6405:
What have you exactly done? If you choose wipe /data, then it should also wipe your internal memory (this is mounted in data/media).

But if you made a factory reset, then the internal memory shouldn't be deleted.
[Galaxy Note 10.1 Android Development] CurbThePain:
Well previously using TWRP 3.3.1 I would do the advanced wipe and only select the /data partition not the internal storage. Then it would say "wiping /data without wiping internal storage". But if I did the same thing in TWRP 3.5.0 it would say "wiping /data and internal storage". I stopped using the basic factory reset many years ago because it always wiped my internal storage. But I will give it a shot and let you know if that works for formatting just the /data partition.
[Galaxy Note 10.1 Android Development] html6405:
This was a faulty behaviour, because the factory reset should wipe only /data withoult /data/media.
[Galaxy Note 10.1 Android Development] Deleted member 9635294:
Off topic, but it seems like emojis need to be disabled in the 1st post.
[Galaxy Note 10.1 Android Development] html6405:
TWRP 3.5.1_9-0 is now ready to download :love:, if you should find any bugs, let me know.​
[Galaxy Note 10.1 Android Development] noobody168:
got an error

"Size of image is larger than target device"

device N8013 twrp version 3.4.0-0

running Slim 7
[Galaxy Note 10.1 Android Development] html6405:
Thanks for testing it,

I will check on this later, maybe something went wrong in the conversion,

I will fix this and we will receive a new build.
[Galaxy Note 10.1 Android Development] html6405:
All image sizes are fixed,

new builds are up!
[Galaxy Note 10.1 Android Development] SteelK:
Alas, the image size is too large, not flash, n8000 :( (2021-03-22 09:05:36 build)
[Galaxy Note 10.1 Android Development] noobody168:
Works fine with with revised version now, thank you very much
[Galaxy Note 10.1 Android Development] html6405:
Are you sure? I've tested it, I will check on this later.
[Galaxy Note 10.1 Android Development] SteelK:
Yes, I'm sure I tried the latest version from TWRP site for N8000

View attachment 5258777
[Galaxy Note 10.1 Android Development] html6405:
Now I've tested the files again from both servers, and it is working in my case.

The file size is lower then our border size.View attachment 5258803
[Galaxy Note 10.1 Android Development] SteelK:
Is there any option to find out the size of the recovery partition?

Im used https://dl.twrp.me/n8000/twrp-3.5.1_9-0-n8000.img.html

How is this possible ...

The image from the tar archive was installed, but the image from the img link was not.

md5 are the same.
[Galaxy Note 10.1 Android Development] html6405:
I have no idea, actually if the md5 is the same, it must work.

Yes, but they are equal for all of us.
[Galaxy Note 10.1 Android Development] xtoad:
I seem to have lost access to my microSD in recovery..? I updated from the microSD and on reboot the card was corruptred in LOS18...I was able to fix and recover on my computer and am able to see it again in Android, but still won't mount in recovery. Any ideas?
[Galaxy Note 10.1 Android Development] html6405:
Which file system are you using?

I had to sort out some things, TWRP needs much more space now.
[Galaxy Note 10.1 Android Development] xtoad:
I believe it is ext4. Or whatever the default is. I have not changed it on my own.
[Galaxy Note 10.1 Android Development] html6405:
ext4 is for example your internal memory. Exfat is most the common file system for sd cards and usb sticks, but this is still enabled.

I've removed the old fat filesystems for the moment, maybe we can safe some space elsewhere.
[Galaxy Note 10.1 Android Development] xtoad:
Thanks. I'll reformat in exFat and check again.

EDIT: All good now formatted with exFat. Thank yor for your work. I had a brain fart about the file system question and thought you meant the filesystem of the recovery partition. The SD card was formatted in FAT.
[Galaxy Note 10.1 Android Development] blainus:
FYI: i had same issue with sd card missing on the latest version...

reverted back to the previous version and the sd card popped up again

cheers
[Galaxy Note 10.1 Android Development] html6405:
If you are using fat32 for example, then yes, there is no place at the moment for this filesystem.
[Galaxy Note 10.1 Android Development] html6405:
TWRP 3.5.2_9-0 builds are up, I've readded some file systems.
[Galaxy Note 10.1 Android Development] Anghirrim:
Hey, first of all, thanks for keeping the device up to date!

Some of my friends asked me to "do something" on his old GT-N8010 yesterday night.

I am just amazed to see the incredible community around this 9 years old device, and how good it is. It runs so well under LOS 16.0!! Crazy, in more than 10 years on XDA, there are really only a few devices that got so much love from devs...

That being said,it seems that the bug of formatting /data instead of just wiping /data without /data/media is still present.

I have ran a simple "swipe to factory reset", and everything in /data/media got deleted. I don't remember if it was done only due to the "factory reset", or by selecting wipe data in "Advanced". BUt nevertheless, both should wipe data, preserving /data/media. But it behaves as if we really clicked on "Format data", that requires a "yes" to really perform.
[Galaxy Note 10.1 Android Development] html6405:
Really?

I will retry this by my own today, if this should be really present, I will hand of this to TWRP.
[Galaxy Note 10.1 Android Development] Anghirrim:
Tell me if you need me to test any further to at least identify the faulty option.
[Galaxy Note 10.1 Android Development] html6405:
No thx, I just have to "swipe to factory reset" and if my data got deleted, the we have to find the bug,

but this behaviour was never present for me, I'm factory resetting many times for my tests.
[Galaxy Note 10.1 Android Development] Anghirrim:
OK. I'll be giving it back to my friends today. So won't be able to test after. Anyway, I'll warn them about it so that they always back up their important data before doing anything if they ever boot under TWRP one day.
[Galaxy Note 10.1 Android Development] html6405:
It's working like it should, nothing got deleted from my personal data, this was always working for me,

and I really have to wipe many times.
[Galaxy Note 10.1 Android Development] Anghirrim:
Indeed.... I don't know what I did wrong, or if it was because of the first flash of TWRP, etc...

Anyway, tried again and you're right. Both options work as intended.

Sorry for the trouble.
[Galaxy Note 10.1 Android Development] html6405:
Update 16.06.2021:

Brought support for GSI flash & reused old HIDDEN partition as vendor.

Brought support for encrypted /data partition.
[Galaxy Note 10.1 Android Development] _Wiktor_:
Two issues.

1. I can't understand why I see only option to "apply update from external storage" (sdcard) but hasn't any option to flash from internal memory (sdcard0).

E:failed to mount /sdacard (No such file or directory)

It seems like without microSD card I can't do anything becouse:

2. No matter which ROM I tried sideload via adb (Version 30.0.4) I get this output on command line:

adb sideload C:\Users\Administrator\Downloads\lineage-16.0-20211007-HTML6405-n8000.zip
adb: sideload connection failed: closed
adb: trying pre-KitKat sideload method...
sending: 'C:\Users\Administrator\Downloads\lineage-16.0-20211007-HTML6405-n8000.zip' 100%

and on N8000 screen:

Verifiyng update package...

E:failed to verify whole-file signature
E:failed to verify whole-file signature
E:signature varification failed

Installation aborted.

So, I stuck.
[Galaxy Note 10.1 Android Development] html6405:
As it look's like, data/media can't be mounted, so you have to do a factory reset and check if /data is formated as ext4.
[Galaxy Note 10.1 Android Development] _Wiktor_:
Well, OK, I just did factory reset . Now, I can't find any working linux shell command to show type of partition. I tried:

file, blkid, parted, tune2fs, lsblk, cfdisk - everything is "not found", except one command: df which outputs results:

shell@android:/ $ df
Filesystem Size Used Free Blksize
/dev 909M 84.0K 909M 4096
/mnt/asec 909M 0.00K 909M 4096
/mnt/obb 909M 0.00K 909M 4096
/system 1.35G 1.24G 103M 4096
/efs 19.7M 8.54M 11.1M 4096
/cache 787M 13.4M 773M 4096
/data 11.8G 312M 11.4G 4096
/storage/sdcard0 11.7G 312M 11.4G 4096

but:

shell@android:/ $ df -T
Filesystem Size Used Free Blksize
-T: No such file or directory

So, which shell command should I use on Jelly Bean 4.1.2 to show how /data id formated?
[Galaxy Note 10.1 Android Development] Alexfs:
hi friend i had the same

hi friend i had the same problem. the sd has to be formatted to exFat.
[Galaxy Note 10.1 Android Development] html6405:
It's enough to choose wipe, advanced wipe, change or repair filesystem and then you will see the used filesystem.
[Galaxy Note 10.1 Android Development] _Wiktor_:
I see no such option
[Galaxy Note 10.1 Android Development] html6405:
You don't have TWRP installed, this is the stock recovery...

Did you flashed TWRP in the download mode at all?
[Galaxy Note 10.1 Android Development] _Wiktor_:
😮 I flashed twrp-3.5.2_9-1-n8000.img.tar and later twrp-3.5.0_9-0-n8000.img.tar via Odin in download mode and it shows green "PASS" message. I thought everything goes well! 😮
[Galaxy Note 10.1 Android Development] html6405:
If it's not possible to overwrite the stock recovery, than it could be, that your eMMC is locked and needs to get replaced.
[Galaxy Note 10.1 Android Development] _Wiktor_:
Am I doing something wrong? :(
[Galaxy Note 10.1 Android Development] html6405:
No, did you disable the auto reboot checkbox?
[Galaxy Note 10.1 Android Development] _Wiktor_:
Yes, I did...

But device always stuck for infinite time, progres bar seems like 100%:
[Galaxy Note 10.1 Android Development] html6405:
This is ok,

then you have to boot directly into the recovery, disconnect the usb cable and press the button combination.
[Galaxy Note 10.1 Android Development] _Wiktor_:
OMG. It worked, TWRP installed, finally. So, my mistake was I reboot device not directly to recovery after flashing in download mode. It seems like OS during booting geting back old system recovery, as warning states on www page .

Should I delete all my posts here, as they are irrelevant?
[Galaxy Note 10.1 Android Development] html6405:
Exactly, the stock ROM overwrites a custom recovery at every boot.

Hmm no, just let them there, maybe someone else is running into this issue.
[Galaxy Note 10.1 Android Development] html6405:
Update 10.12.2021:

Removed bash to bring TWRP 3.6.0_9 up
[Galaxy Note 10.1 Android Development] stingbandel:
So it's safe to install 3.6.0.9 now on n8000? Not like last time which deleted all my internal storage? Thanks
[Galaxy Note 10.1 Android Development] html6405:
Sure!
[Galaxy Note 10.1 Android Development] stingbandel:
Ok will do it later. Thanks
[Galaxy Note 10.1 Android Development] SteelK:
I have encountered a strange problem. The latest versions of TWRP (3.6.*) do not work restore backups. Restoration happens, but the tablet does not start, stays on the logo. Backed up with LOS 16 before upgrading to LOS 19.1. Attempted to restore from TWRP 3.5.0 9.0 was successful, everything started. Has anyone encountered this?
[Galaxy Note 10.1 Android Development] JJEgan:
TWRP does not always restore older TWRP version backups .

TRY

restore boot then reboot and restore the rest .
[Galaxy Note 10.1 Android Development] SteelK:
That's the problem. I created a backup on 3.6.1, but it was not able to recover properly. As well as on 3.6.2.
[Galaxy Note 10.1 Android Development] JJEgan:
Wipe then try recover System only .
[Android Q&A, Help & Troubleshooting] zohaibahmedpk:
I recently flashed my device with the latest firmware (Binary: 8) downloaded from sammobiles. The binary it had before flash was 6.

Now it is boot looping and would not boot up normally. It goes into recovery but it shows some errors. Please look into the attached images (both download mode and recovery mode) displaying and corresponding the exact problem.

View attachment 5221727View attachment 5221729

OEM is OFF

FRP is OFF

Till now, I have diagnosed the problem to be DRK ERROR (dm-verity verification failed.)

This file: "J530F Binary U8 Android 9 Pie FIX DRK - dm-verity Failed Frp Off Oem Off (J530FXXS8CTK1).rar" may solve the problem but can't find this anywhere for free.

Please help!
[Android Q&A, Help & Troubleshooting] zohaibahmedpk:
@hainguyenthao helped on discord step by step for installing a custom ROM for normal booting of the device. As the custom ROM was buggy (/e/ ROM), I flashed stock ROM using Odin, with TWRP+no verity script+root(magisk), and got my device working and boot up to the system. Thanks for your time @hainguyenthao. :) ;)
[Android Q&A, Help & Troubleshooting] Mitoww:
bro pls tell me how to fix this, i got the same sh*tty problem over here :( i would be so much thankful
[Android Q&A, Help & Troubleshooting] zohaibahmedpk:
message me on discord: ZohaibPK#6207
[Android Q&A, Help & Troubleshooting] Mitoww:
i already got it solved, thanks though :)