yashsingh1/xdaforums huggingface dataset:
[Galaxy Note 3 Android Development] ripee:
Can you please check NTFS and exFAT too?

Encrypted and unencrypted?
[Galaxy Note 3 Android Development] vagenrider:
checked all and everything works perfect..well done again and really hope you solve the aroma issue! :):):o:o
[Galaxy Note 3 Android Development] Imprezzion:
Both work just fine. It encrypted it fine and it recognized the password as well. No issues.

I don't have a SD card in my phone atm as it's in my dashcam so i did save it to internal storage.
[Galaxy Note 3 Android Development] ripee:
Aroma support

I've built TWRP 3.2.1 for a handful of Samsung devices over the past couple of months, and none of those builds supported Open GApps Aroma properly. The developer of Aroma stopped development sometime around the middle of last year, which would explain why versions 3.2 and above wouldn't be compatible with it. See here for a more detailed explanation.

That said, the most I can offer is a custom Aroma package by Creeper36 for the Note 4. It may or may not be compatible with the Note 3, but it's worth a try. If this doesn't work, I personally recommend creating a gapps-config file to customize flashing of the Super or Stock GApps package.

Submitting for official support

Since a handful of you have confirmed that my build works, I will submit it to bigbiff for official support. Let's hope he doesn't mind my nudging his thread out of the way, but if the current official 3.2.1-0 isn't up to snuff, the venerable Note 3 deserves better! :D
[Galaxy Note 3 Android Development] Lobo86:
ResurrectionRemix Oreo 8.1 Official On Redmi Note 3

https://m.youtube.com/watch?v=d0dpn1TMbHE
[Galaxy Note 3 Android Development] lastwarning91:
Thanks for the reply i tried to flash img from twrp 2.8.7.0 but it wont show img files then i downloaded a zip of twrp 3.0 for smn9005 and flashed it from twrp 2 but it resulted in bootloop, here is my complete detail of device, humbly waiting for a fix
[Galaxy Note 3 Android Development] Eleo:
Did you try img/zip files shared here by ripee?

Try to use everything as explained in OP of this thread. Maybe odin 3.0.9 is old... Just trying to troubleshoot to get into depth of the issue
[Galaxy Note 3 Android Development] lastwarning91:
UPDATE 1

i tried with latest odin too, and i read all tutorial and i also flashed TWRP_3.2.1-0_LL_2 found from some user in this thread it works flawless and now i flashed resurrection-remix 7.0 with no error but still it cannot BOOT oreo and pie after flashing

---------- Post added at 07:27 PM ---------- Previous post was at 07:26 PM ----------

can u please link me to ripee zip files

---------- Post added at 07:28 PM ---------- Previous post was at 07:27 PM ----------

can u please link me to ripee zip files
[Galaxy Note 3 Android Development] Eleo:
He shared img and tar other than official. Like here:

https://xdaforums.com/galaxy-note-3/development/recovery-twrp-3-2-1-1-t3746760/post78772464

I don't know if you use any theme in TWRP, but you should have "Images" button (see attachments). If you don't click that you cannot find img files. See TWRP 2.8.7.0 on my note3 hlte. I flashed TWRP 3 img file and rebooted recovery to boot to TWRP 3. I showed the steps.

I hope you can follow them.

P.S. Choose "recovery" option if you are flashing recovery img file. Boot option is only if you are flashing a kernel img file.

P.P.S. I use a twrp3 theme. Your twrp3 may be seen differently.
[Galaxy Note 3 Android Development] ashyx:
I built that recovery for devices incompatible with the twrp versions in this thread. I also have the latest version available.

Unfortunately it seems you have one of the odd ball devices that will not work with anything beyond Android 7.1.
[Galaxy Note 3 Android Development] lastwarning91:
thats a bad news for me :( :( , i think ill have to wait twrp to work in future for my device
[Galaxy Note 3 Android Development] ashyx:
It's likely never going to work. It seems your are stuck with Android 7.1.

Everything else has been tried to get later versions to boot to no avail.

Maybe time to move on?
[Galaxy Note 3 Android Development] andrewilley:
First, I'm running TWRP 2.8.7.0 (because my very nice MagMa_PCE 6.0.1 ROM needs that version), in case that makes a difference.

I've recently been trying to make a somewhat overdue nandroid backup of my Note 3 N9005 (UK), and most partitions (Boot, System, EFS, Modem) seem to backup fine, but my Data partition keeps getting to file 261 of 21981 (approx 984 Mb) and failing with "E:createTarFork() process ended with ERROR=255".

The recovery.log file in the relevant backup folder is zero bytes (this appears to be the case even with the separate good backups for the other partitions) so I can't see where it is going wrong. I also checked for a /tmp/recovery.log, but there isn't one.

If I use ADB to pull the partially completed data.ext4.win000 file (975 MB, 1,022,791,680 bytes) and then rename it as a TAR file, WinRAR shows it as corrupt. The fact that it's quite near to 1Gb seems a bit coincidental, but there's plenty of spare space on the drive (another 12Gb or so). Same issue happens whether I enable compression or not.

e2fsck via ADB says the data partition is clean, and doesn't show any errors even if I do a "-f" to force a check. I'm not sure how to get it (or some other app) to crawl the whole partition file by file though, which I suspect I may need to do.

The device does seem to boot and works OK by the way. I did have some slow-down issues over time and needed to re-flash the same ROM (no wipe), but otherwise it's operating well for a device of its age.

Any thoughts on how I should proceed? Thanks,

Andre
[Galaxy Note 3 Android Development] ashyx:
It's quite likely a corrupt file. Remove the offending file and it will probably work.

Maybe also try a more up to date build of twrp.
[Galaxy Note 3 Android Development] andrewilley:
Yeah, I worked that out. But as it's not saving a recovery.log, it's hard to work out what file is causing the problem. Is there some full complete-filesystem testing app that I can run at root level?

I can't use a more recent TWRP by the way, as the latest releases apparently break the Aroma installer that my ROM uses.

Andre
[Galaxy Note 3 Android Development] ashyx:
Try Advanced>copy log

There should be a log regardless of whether it fails or not. The log is created at start up and is just appended.
[Galaxy Note 3 Android Development] Eleo:
BTW you CAN use latest TWRP. You need 2.8.7.0 ONLY when flashing a zip with aroma installer (a MOD or ROM.zip containing aroma installer). For everything else, you can use newest TWRP.

There is a TWRP flashable zip for twrp2.8.7.0 and newer versions available on twrp.me for hlte (N9005). I myself am using those to switch between 2.8.7.0 and 3.2.3-0 TWRP versions easily directly from recovery mode (rather than using ODIN flashable tar.md5 with my computer).

So you can try newest TWRP and test backup again. When finished you can revert back to 2.8.7.0 via zip flashable from twrp.me. All I am saying is, do not think you have to be on 2.8.7.0 only because you have flashed a aroma installer containing ROM zip.

Good luck.
[Galaxy Note 3 Android Development] andrewilley:
I already tried that, it just copies the zero-byte logfile.

Andre
[Galaxy Note 3 Android Development] JJEgan:
Aroma has not been updated to work with later TWRP.

Might be worth trying Philz Recovery as that works with Aroma.

You can use a later TWRP after installing via Aroma I am.
[Galaxy Note 3 Android Development] ashyx:
You would be better just flashing the recovery.img via twrp rather than messing with zips.
[Galaxy Note 3 Android Development] andrewilley:
I've tried again, and got a logfile this time which pointed to the offending file in /data/app/ . I uninstalled the offending app and ran backup again, and it failed on another app (Snapchat this time). Uninstalled that and tried again and it found an issue a bit later with an adobe reader app file. As there seem to be a few corruption issues (although it's getting further each time) is there an app I can use which will recursively crawl the whole filesystem and identify problems (like chkdsk on a PC) so I can deal with all them all first and then try another backup run - as going in and out of recovery each time is very time-consuming.

I can't see this being a problem with the TWRP version anyway though. I rarely use Recovery, and as long as it installs ROM files and does a proper nandroid, I'm happy with that.

Andre
[Galaxy Note 3 Android Development] Eleo:
I know. But the theme I am using on twrp2.8.7.0 has not incorporated "flash img" button somehow so I use zips
[Galaxy Note 3 Android Development] ripee:
Really? Flashing img has been a thing since 2.8.4...
[Galaxy Note 3 Android Development] Eleo:
I know. Imagine my surprise when I didn't see button. But is not an issue for me. I have done flashing twrp zips for maybe thausand of times. So far no issues. It is present on twrp3.2.3-0 theme but absent from 2.8.7.0 one. Themes are from z31s1g's thread
[Galaxy Note 3 Android Development] Eleo:
I think I had a deja vu:

https://xdaforums.com/galaxy-note-3/development/recovery-twrp-3-2-1-1-t3746760/post79029101

:D
[Galaxy Note 3 Android Development] itsgreat:
Hi,

It seems that twrp 3.2.3-0 cannot decrypt partitions encrypted in Android 9 using the latest haggertk LineageOS 16 build. Quick googling shows that there exists a newer twrp version 3.2.3-1 which might support that.

Do you know whether I can just recompile the latest twrp sources for hlte to get that or it would a big undertaking to get this feature?
[Galaxy Note 3 Android Development] JJEgan:
Have you been to TWRP site ??

Twrp.me
[Galaxy Note 3 Android Development] Eleo:
Never used encryption on custom ROM and with twrp recovery installed. That seems quite unneeded
[Galaxy Note 3 Android Development] andrewilley:
I eventually got my Note 3 TWRP backup sorted out by finding and removing any files which TWRP was not able to copy - about 10 files, mostly base.apk or base.odex inside folders in /data/app, so I removed/uninstalled the apps in question. This allowed the whole backup to run to the end (no errors reported in system, boot, modem, etc) and I thought my issues were sorted, but a few more odd files started showing up as unreadable within a few days, nothing particularly notable that I couldn't restore. I tried e2fsck -cfv, but that showed zero bad blocks. Otherwise though, the phone was working fine for a device of its age.

Today, I glanced at the phone mid-afternoon (after using it fine all day listening to music and reading emails, etc) and it had reverted to the Download screen, reporting "Could not do normal boot, ddi : mmc_read failed."

I ran Odin on my PC and it showed the device as added, so I thought I'll re-upload TWRP so I can at least get into Recovery and see what's going on, but although Odin starts sending the TWRP .tar file normally, it quickly reports "Get PIT for mapping ... There is no PIT partition". The phone screen shows "UDC START" but then "MMC: mmc_read fail".

The USB port and USB cable are the same ones I've been using for the adb pull backups which I was doing to test the error status of all the files in the /data/ partition, so I know they are OK.

Any thoughts on where I go from here to at least get back into TWRP? (ROM is MagMa_PCE_XDA_FB.zip with Phantom kernel, and the phone is a 32GB Samsung Galaxy Note 3 international version)

Andre
[Galaxy Note 3 Android Development] Eleo:
Did you repartition your storage space to increase system size by odin flashable in MagMa NX thread anytime? And also, did you try newer twrp for backup as I advised above?
[Galaxy Note 3 Android Development] andrewilley:
I have not re-partitioned storage space as far as I recall - it was quite a while ago that I started using MagMa ROMs though so I might have done, but as far as I recall I just installed the ROM via the Aroma installer, and have re-installed it periodically to improve general performance sluggishness over time. I do have a copy of an NX_ROM_install_log from 2017 when I was initially setting it up, would that contain anything useful?

The device has been working fine recently, no lag and apart from those few file-system errors it's a great workhorse and a nice ROM.

TWRP 2.8.7.0 was working fine (as I said, apart from those file read errors during nandroid backups, which should not have been related to the recovery version) so I did not try installing 3.1.1-.0. I can't re-install either at the moment (tried both, but the PIT partition issue blocks anything).

Andre
[Galaxy Note 3 Android Development] andrewilley:
What I do have to hand are the following:

Full nandroid backup (copied to my PC) from a week ago.

Full Titanium Backup (on the external SD Card) from about two weeks ago.

adb pulls to my PC of the entire contents of /sdcard/ and /data/app/ from about a week ago.

All of the various ROM installation files, TWRP package, Odin, etc on my PC.

However unless I can determine what PIT I need to try to install, I can't even get as far as Recovery to try to restore anything else. My device is an unlocked/no-carrier UK Galaxy Note 3 N9005 32GB.

Ironically, I was considering getting an S10+ to replace this aging phone, but was intending to wait for the Note 10 before deciding which one to go for, so I really would like to get another six month's life out of this one if I can. I also need to retrieve my old SMS messages from one of the backups somehow, which I'd normally do easily enough if I can get the phone working and restored of course.

Andre
[Galaxy Note 3 Android Development] Eleo:
This is quite unexpected behavior. You can just try any available PIT file on TWRP:

https://xdaforums.com/showthread.php?t=2550823

Or modified PIT file like this:

https://xdaforums.com/galaxy-note-3/development/rom-magma-nx-rom-t3508672/post72374366

Afaik, this will wipe everything on your phone. As far as I recall, the steps are flashing PIT file on ODIN, then stock firmware.
[Galaxy Note 3 Android Development] andrewilley:
Yes, I rather thought it would be a nuclear solution when I Googled the error message.

I hope that if I can get it working at all with a stock ROM and install TWRP, I should then be able to restore my nandroid backup and then copy back everything from my recent /sdcard/ folder backup, and hopefully that should get me back to pretty much square one again, but with the bonus of a fully reformatted file system that might take care of the odd file errors that I was seeing. Of course the memory could be more seriously shot than a reformat can recover, in which case I assume it's effectively bricked?

[Edit: Well that do you know? On a sudden whim I had a look in my /sdcard/ backup for *.pit and found that at some point long ago I must have backed up the PIT anyway, I'll try that file first]

Andre

---------- Post added at 09:35 AM ---------- Previous post was at 08:52 AM ----------

Hmm, no go with any of those PIT files (the two you referred me to, and my own backed up one that I found from my /sdcard/). :(

I ran Odin with AutoReboot, Re-Partition, and F.Reset Time ticked (nothing else set to install at that point, just the PIT file) and it resulted in:

<ID:0/007> Initialzation..

<ID:0/007> Set PIT file..

<ID:0/007> DO NOT TURN OFF TARGET!!

<ID:0/007> FAIL!

<ID:0/007>

<ID:0/007> Re-Partition operation failed.

<OSM> All threads completed. (succeed 0 / failed 1)

When I ran the above process, the phone showed:

UDC START

MMC: mmc_read fail

Anything else I should have set in Odin? Not sure what "Nand Erase All" or "T Flash" are for, but I left them unticked.

Andre
[Galaxy Note 3 Android Development] zlazaar:
I remember repairing a Galaxy S5 (klte) that had the same symptoms using : a 4files repair firmware which include the correponding PIT file + NAND Erase All also ticked.

I used Odin v3.10.7 and after a successful process, flashed TWRP then restored the backed up EFS partition.

hope this gonnna help.
[Galaxy Note 3 Android Development] andrewilley:
Sorry for my ignorance (this is not something I do every day so it's all a bit new) but what is a "4files" repair firmware? [Ignore me, Googled it, makes perfect sense when you read up on it]

Andre
[Galaxy Note 3 Android Development] zlazaar:
Sorry, i'm afraid we are hijacking a developement thread.

I suggest you to creat a new thread or post in an existing one in Help & Troubleshouting section of this forum.
[Galaxy Note 3 Android Development] andrewilley:
True, if the 4files solution does not work I'll open a new thread, as this is getting beyond just the TWRP install/restore issue now.

Andre
[Galaxy Note 3 Android Development] andrewilley:
4files repair installation (PIT, AP, BL, CP and CSC, with Nand Erase All selected) failed too. Please can we continue this conversion over in https://xdaforums.com/galaxy-note-3/help/note-3-stopped-booting-goes-straight-to-t3912883 to avoid clogging up this thread? Many thanks.

Andre
[Galaxy Note 3 Android Development] williamacker77:
SM-900T goes straight to Bootloader mode

Hello , and thank you Ripee , for all your hard work. I am stumped , I went into recovery , to install 3.2.3.0 on my SM-900T , I clicked on the image file , clicked the recovery option , and swiped to flash. It seemed to go through just fine , but when I hit re boot , my phone went into Bootloader mode. The screen said : Could not do normal boot

ODIN MODE

PRODUCT NAME: SM-900T

CURRENT BINARY: Custom

SYSTEM STATUS: Custom

KNOX WARRANTY VOID; 0x1 (4)

QUALCOM SECUREBOOT: ENABLE (CSB)

AP SWREV: S2, T2, A2, A3, P2

SECURE DOWNLOAD : ENABLE

UDC START

Since it was in download mode , first thing I did , was download 3.2.1.0 , that I had already on my PC , this got my phone back on. But whenever I try to boot into recovery , it shows the little blue "recovery mode" at the top left of the screen , but only for 1 second , and then it goes into Bootloader mode , with the same screen that I showed above ??? I have tried many ways to boot into recovery : ODIN , ADB , Developer Options , and the Quickboot app. I am going Nuts , it is like my foundation is shaken , I could always rely on TWRP , whatever problems I got into , Please Please Help.

Oh , Sorry , I am running the Latest Haggert build of Lineage 16.0 , Mar 17 I think.
[Galaxy Note 3 Android Development] Eleo:
What is the file name you downloaded? The twrp img and tar.md5 files.

Did you try to wipe everything. Go back to stock firmware, then try everything (root, twrp, ROM) again?
[Galaxy Note 3 Android Development] williamacker77:
Hello , the file name is : twrp-3.2.3-0.img from twrp.me.

Wow , no I have not tried that , I am no newbie , but I am far from being a developer either. Right now I have a rooted phone , with Lineage 16.0 , and all my favorite stuff , Root Explorer , busy box and the rest .... It scares me that I might not be able to get back to that. I was thinking that it might be the bootloader , I looked at the bootloader download link , but there are no instructions , just files , I have not figured it out yet.
[Galaxy Note 3 Android Development] Don Rich:
Why is it that aroma installer doesn't launch with twrp 3.2.3 hltechn

---------- Post added at 02:42 PM ---------- Previous post was at 02:41 PM ----------

Tried flashing miui on hltechn but aroma never starts with twrp 3.2.3 yet hltech has no twrp 2.8.7 version
[Galaxy Note 3 Android Development] JJEgan:
Aroma is not built for above TWRP 2,8,7

No need to ask its been answered time after time .
[Galaxy Note 3 Android Development] liviuionut22:
https://xdaforums.com/galaxy-note-3/help/flash-philz-recovery-to-sm-n9006-t3600974/post76926706
[Galaxy Note 3 Android Development] svbarbosa:
I had a problem with latest TWRP 3.3.0.

While performing a large nandroid backup (9 GB total) the phone became too hot and the backup failed.

I had to revert to 3.2.3 and the same backup ran fine.
[Galaxy Note 3 Android Development] rayman95:
No issue with normal nandroid (4 Go)....
[Galaxy Note 3 Android Development] stefanct:
I think this might be the actual culprit right there! I had swapped the original display for a replacement (because the buttons were broken) and the stock android (some 4.x) stopped booting and went into a reboot loop. Swapping back the original display made the old system boot again so that was definitely related to the display/digitizer (I can even point out which connector changes the behavior: the one next to the volume buttons).

I wanted to update anyway and thus flashed the latest stock (5.0 lollipop) which booted fine. I then began (for the first time on that phone) to play with custom recovery, i.e. I installed latest twrp via odin - didn't work - tried via heimdall - didn't work - tried pre 3 versions that worked but couldn't flash android 9 images (via adb sideload or directly from sd) because of the device id check. Then I have finally found the relevant posts in this thread and read the rest.

With this suspicion in mind I swapped the digitizer module again to see if a vanilla twrp (twrp-3.3.1-0-hlte.img) and lineage-16.0-20190625-UNOFFICIAL-hlte-Jprimero15.zip (from https://xdaforums.com/galaxy-note-3/development/rom-lineageos-16-0-t3840244) actually works with it. AND IT INDEED DOES with the original display!

So long story short: there is some incompatibility between some kernels and the displays we "unlucky" ones use that is not present in the stock 5.0 image and older twrps but in twrps >2.7.something and 8+ android kernels.

For the record: the exact version of my device (SSN) is N9005GSMH, the replacement display came from aliexpress in fall 2017 and has some minor differences but is definitely for the LTE version and works flawlessly with stock 5.0...
[Galaxy Note 3 Android Development] bigbiff:
OEMs can change the display in the manufacturing cycles. I have seen this many times. It typically means the OEM adding the new display driver to the kernel and releasing the source. I am not sure this happened with Samsung, I guess someone with the phone and look at later kernel versions can check.
[Galaxy Note 3 Android Development] ashyx:
You're probably right. The versions I built a while back worked fine on these obscure devices using the stock kernel.

However it also means something changed in the lineage source code as up to Android 7.1 everything worked fine.
[Galaxy Note 3 Android Development] SheepCN:
No Chinese language

There is no Chinese language,and can't show it ，It shows a white rectangle.
[Galaxy Note 3 Android Development] bigbiff:
The additional languages will need to be added to the boardconfig to include them if the ramdisk is big enough to hold the extra language font files.
[Galaxy Note 3 Android Development] stefanct:
So my next step would have been to compile twrp from source to prepare for further tests with a modified kernel... however I got stuck and wonder how twrp on hlte should actually be built. I have commented with a more detailed explanation on an already closed issue on github that seems very much relevant. I'd be most interested in getting feedback on my way to compile twrp (reproduced here for good measure):

mkdir platform_manifest_twrp_omni
cd platform_manifest_twrp_omni
repo init --depth=1 -u git://github.com/minimal-manifest-twrp/platform_manifest_twrp_omni.git -b twrp-9.0

# Add hlte repo
mkdir -p .repo/local_manifests/
cat << EOF > .repo/local_manifests/hlte.xml
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="TeamWin/android_device_qcom_common" path="device/qcom/common" remote="github" revision="android-7.1" />
<project name="TeamWin/android_device_samsung_hlte" path="device/samsung/hlte" remote="github" revision="android-7.1" />
</manifest>
EOF

# Download everything (takes a long while...)
repo sync -c --force-sync --force-broken --no-tags

# Add undistributed boot.img from stock
cp $stock_archive/boot.img device/samsung/hlte/boot.img

# Remove deprecated flags from BoardConfig.mk (this should be fixed in the hlte repo and I'll send a patch when I am done and know this is the right repo at all :)
# -TARGET_GLOBAL_CFLAGS += -mfpu=neon -mfloat-abi=softfp
# -TARGET_GLOBAL_CPPFLAGS += -mfpu=neon -mfloat-abi=softfp

export ALLOW_MISSING_DEPENDENCIES=true
. build/envsetup.sh
lunch omni_hlte-eng
mka recoveryimage