[RECOVERY][OFFICIAL] TWRP 3.5.2_9-0 [tblte][trlte][trlteduos] - Galaxy Note 4 Android Development (Snapdragon)

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
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:
* [B][U]Your warranty is now void.[/U][/B]
* 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.13.3
Heimdall
- Glass Echidna
TWRP for Samsung Galaxy Note 4 (Qualcomm)
How to flash a bootloader and/or modem​1. If your tablet is turned on normally, turn on Advanced reboot in Developer options and select "Download" from the Restart menu,
2. In Odin, import either the bootloader.tar or bootloader_modem.tar file, depending on your variant, with the "AP" button.
How to flash TWRP with Odin​1. If your tablet 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, and Home buttons simultaneously. When the blue screen appears, release all 3 buttons and press Volume Up.
2. In Odin, import the appropriate twrp.tar file for your variant with the "AP" and press the "Start" button.
3. Pull the battery as soon as your phone vibrates.
4. You can then boot directly into TWRP by pressing the Power, Volume Up, and Home buttons simultaneously. Release all three buttons as soon as you see the boot screen ("Samsung Galaxy Note 4").
How to flash TWRP within a previous version of TWRP​1. If your tablet 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, Volume Up, and Home buttons simultaneously. Release all 3 buttons when the boot screen appears ("Samsung Galaxy Note 4").
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.
Changelog
- See post #2.
Bugs
E:recv error on uevent
- This warning appears during the process of making a nandroid backup. I assure you that it's perfectly innocence: your backup should complete successfully and it should restore successfully without any reference to this warning. This is a known bug that affects other Exynos devices as well, such as the Samsung Galaxy S7 Edge (hero2lte).
- Technical explanation from bigbiff himself: "I think it must be a bug, probably shouldn't print the log out if we aren't using ueventd to pull in partition information on a target device. I am not sure what devices we are supporting using ueventd however. Looks like it only runs from the process_fstab function. It's harmless, but I wonder if it should be put in an ifdef guard."
Credits
- Inspiration in motivating me to learn how to build TWRP: _mone
- Kernel work and device trees for related devices: cvxda
- micky387 and every other open source developer and user who contributes directly or indirectly to the TWRP community in the development of and in providing feedback for the tblte, trlte, and trlteduos.
Sources
- apq8084 kernel repository
- tblte repository
- trlte repository
- trlteduos repository
- TWRP repository
XDA:DevDB Information
TWRP 3.5.2_9-0, ROM for the Samsung Galaxy Note 4
Contributors
ripee, _mone, cvxda, micky387
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
Version Information
Status: Stable
Current Stable Version: 3.5.2_9-0
Stable Release Date: 2021-04-06
Created 2019-05-24
Last Updated 2022-12-09

---

Reserved

---

Reserved

---

Hello,
First of all, thank you for you continuous work and courage to keep our devices up to date, by you I mean the whole awesome team !
Updated of TWRP 3.3.1-0 was successfully done within TWRP 3.3.0-0 - flash image - recovery.
Update of Bootloader_Modem file was a bit longer :
- with the provided Odin3 v3.13.1 - the ID:COM was going crazy connecting/disconnected no matter what USB port (2.0 and 3.0) I was using and I was using OEM cable.
<ID:0/005> Added!!
<ID:0/005> Removed!!
<ID:0/005> Added!!
<ID:0/005> Removed!!
...
Updating Samsung Mobile Phone Driver didn't help (but just in case, link = https://forum.xda-developers.com/showpost.php?p=78823944&postcount=623 )
Even after a restart of Windows 10 OS.
Luckily I had kept a zip of Odin3_v3.10.7 close by me (this was the version I used for my previous BL/CP update) and using this version was fine, my n910f is correctly on DRI2_DQL1.
<ID:0/005> Added!!
<ID:0/005> Odin engine v(ID:3.1100)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> aboot.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> modem.bin
<ID:0/005> NON-HLOS.bin
<ID:0/005> rpm.mbn
<ID:0/005> sbl1.mbn
<ID:0/005> sdi.mbn
<ID:0/005> tz.mbn
<ID:0/005> RQT_CLOSE !!
<ID:0/005> RES OK !!
<ID:0/005> Removed!!
<ID:0/005> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
I'll report if anything good or bad is noticed within the next few days.
Thank you again,

---

Updated to 3.3.1-0 and for some reason it refuses to remember the correct date and time. Every time I boot in it defaults to something like 1971-01-20 with a completely wrong time for my time zone. Some other basic setting like reversed navbar would not stick every time.
Reverted to 3.2.3-0 and everything's back to normal. Any ideas? I though maybe my phone was somehow causing it but once I reverted the problem disappeared.

---

Apex Predator said:
Updated to 3.3.1-0 and for some reason it refuses to remember the correct date and time. Every time I boot in it defaults to something like 1971-01-20 with a completely wrong time for my time zone. Some other basic setting like reversed navbar would not stick every time.
Reverted to 3.2.3-0 and everything's back to normal. Any ideas? I though maybe my phone was somehow causing it but once I reverted the problem disappeared.
Click to expand...
Click to collapse
@ripee
Has the issue been resolved yet ?
It only happens to me when I do a full complete wipe for a clean flash.
It doesn't seem to affect a roms integrity when restoring a backup.
Once a rom has been run for a length of time the TWRP clock updates ok.
All these backups are less than 3 days old.
All are the latest builds of each respective rom.
The oldest backup is Xenon

---

mangojack01 said:
@ripee
Has the issue been resolved yet ?
It only happens to me when I do a full complete wipe for a clean flash.
It doesn't seem to affect a roms integrity when restoring a backup.
Once a rom has been run for a length of time the TWRP clock updates ok.
All these backups are less than 3 days old.
All are the latest builds of each respective rom.
The oldest backup is Xenon
Click to expand...
Click to collapse
The easiest way to resolve this is to wipe your phone, flash stock, then start again with twrp and your rom. TWRP gets its time and date from the system clock, which is set by the rom, which is set by your mobile company.
I had the same thing happen on my wifi-only tablet, and reflashing stock is the only thing that worked. No idea why this happened in the first place, perhaps some twrp or rom update went screwy, and some file or folder permission isn't allowing it to be set properly.

---

I'm still using 3.2.3 so this might be irrelevant info, or just wrong info, but it looks like that .twrps file on the internal sdcard is where the settings are stored. I had never updated my time in twrp so it had been on mountain time (-7) and the file at /storage/emulated/0/TWRP/.twrps reflected that but I just changed to it to my correct time, eastern standard (-5) (it's still daylight savings so its EDT instead EST for the moment). Now that hidden file has been updated with EST and EDT references.
I guess if you're formatting the internal sdcard there's no way to protect it, but perhaps users could copy it and then replace it after a full wipe assuming TWRP is not being updated. If updating TWRP it might just be safer to redo the settings or, like I apparently have, just not pay it any attention.
Since there's a variety of file explorer apps out there I thought I would add that some file managers may use the symlink path of /sdcard/TWRP/.twrps or mnt/sdcard/TWRP/.twrps but for those that are curious the actual path is /storage/emulated/0/TWRP/.twrps

---

kevintm78 said:
I'm still using 3.2.3 so this might be irrelevant info, or just wrong info, but it looks like that .twrps file on the internal sdcard is where the settings are stored. I had never updated my time in twrp so it had been on mountain time (-7) and the file at /storage/emulated/0/TWRP/.twrps reflected that but I just changed to it to my correct time, eastern standard (-5) (it's still daylight savings so its EDT instead EST for the moment). Now that hidden file has been updated with EST and EDT references.
I guess if you're formatting the internal sdcard there's no way to protect it, but perhaps users could copy it and then replace it after a full wipe assuming TWRP is not being updated. If updating TWRP it might just be safer to redo the settings or, like I apparently have, just not pay it any attention.
Since there's a variety of file explorer apps out there I thought I would add that some file managers may use the symlink path of /sdcard/TWRP/.twrps or mnt/sdcard/TWRP/.twrps but for those that are curious the actual path is /storage/emulated/0/TWRP/.twrps
Click to expand...
Click to collapse
I agree, it's more of an annoyance than anything else, especially to a grumpy, slightly aspie, 69yo pedant.
I run trwp v 3.3.1
I've tried cut n paste .twrp after formating internal sd many times in many ways via twrp file manager.
eg, wipe everything internal, reboot recovery, setup recovery, replace/ overwrite or edit new .twrp file, reboot recovery, but without success.
cest la vie
Thanks for your feedback, I'm sure others also may find it enlightening.

---

Hi, Ripee
I got two 910V I bought it off one has bad efs partition and one has bad speaker/mic I was thinking to copy bad speaker/mic efs partition to another one, but copying over efs partition didn't do anything. I thought it will copy over IMEI stuff to this second phone?

---

zfk110 said:
Hi, Ripee
I got two 910V I bought it off one has bad efs partition and one has bad speaker/mic I was thinking to copy bad speaker/mic efs partition to another one, but copying over efs partition didn't do anything. I thought it will copy over IMEI stuff to this second phone?
Click to expand...
Click to collapse
You have an interesting challenge. .
Have you tried a restore sd card ?
Check the emmc brickbug if you can.
I believe the hack to get root for the Verizon note 4 writes to the efs partition to clone it into a developer edition. Which every with a hacked Verizon phone like mine has the exact same IMEI 1000000000000 or something like that

---

Hi
how to flash N910FXXU1DRI2_N910FXXU1DQL1.tar (bootloader_modem.tar) with Heimdall ? I understand I have to untar and flash files separately, but there are not only two files in this .tar, there are 7 files !
Can you guide me please ?
Thanks

---

louisJJ said:
Hi
how to flash N910FXXU1DRI2_N910FXXU1DQL1.tar (bootloader_modem.tar) with Heimdall ? I understand I have to untar and flash files separately, but there are not only two files in this .tar, there are 7 files !
Can you guide me please ?
Thanks
Click to expand...
Click to collapse
Incase you haven't solved it yet.
This worked for me on manjaro-linux with heimdall installed as well as on debian-sid with heimdall-flash.
As root:
Code:
heimdall detect
To make sure your device is detected
Code:
heimdall flash --APNHLOS /tmp/e/NON-HLOS.bin --ABOOT /tmp/e/aboot.mbn --MODEM /tmp/e/modem.bin --RPM /tmp/e/rpm.mbn --SBL1 /tmp/e/sbl1.mbn --DBI /tmp/e/sdi.mbn --TZ /tmp/e/tz.mbn --no-reboot
Where for example /tmp/e/ is your path to files to flash.
When process finished successfully pull battery and reboot to recovery.

---

Thanks a lot!

---

Hi,
I am having troubles with the modem that is listed in this thread...N910FXXU1DQL1....I have poor reception.
Can someone point me to a full list of modems I can test ? I am installing LineageOS 16 from this tuto.
Thanks

---

louisJJ said:
Hi,
I am having troubles with the modem that is listed in this thread...N910FXXU1DQL1....I have poor reception.
Can someone point me to a full list of modems I can test ? I am installing LineageOS 16 from this tuto.
Thanks
Click to expand...
Click to collapse
Just adding this here in case anyone else is looking for it
N910FXXU1DRI2_N910FXXU1DRI1.tar.md5

---

Caution: backups made with older versions than v3.4.0 seem to be not compatible. I wanted to restore a backup I made with v3.2.1 with v3.4.0 but the system couldn't boot. Verified this two times. Had to go back to v3.21 to perform a successful restore.

---

It's better using TWRP 3.3.1 for all flashing operations.

---

I think we have the same odin
PasSlert said:
Hello,
First of all, thank you for you continuous work and courage to keep our devices up to date, by you I mean the whole awesome team !
Updated of TWRP 3.3.1-0 was successfully done within TWRP 3.3.0-0 - flash image - recovery.
Update of Bootloader_Modem file was a bit longer :
- with the provided Odin3 v3.13.1 - the ID:COM was going crazy connecting/disconnected no matter what USB port (2.0 and 3.0) I was using and I was using OEM cable.
<ID:0/005> Added!!
<ID:0/005> Removed!!
<ID:0/005> Added!!
<ID:0/005> Removed!!
...
Updating Samsung Mobile Phone Driver didn't help (but just in case, link = https://forum.xda-developers.com/showpost.php?p=78823944&postcount=623 )
Even after a restart of Windows 10 OS.
Luckily I had kept a zip of Odin3_v3.10.7 close by me (this was the version I used for my previous BL/CP update) and using this version was fine, my n910f is correctly on DRI2_DQL1.
<ID:0/005> Added!!
<ID:0/005> Odin engine v(ID:3.1100)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> aboot.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> modem.bin
<ID:0/005> NON-HLOS.bin
<ID:0/005> rpm.mbn
<ID:0/005> sbl1.mbn
<ID:0/005> sdi.mbn
<ID:0/005> tz.mbn
<ID:0/005> RQT_CLOSE !!
<ID:0/005> RES OK !!
<ID:0/005> Removed!!
<ID:0/005> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
I'll report if anything good or bad is noticed within the next few days.
Thank you again i think we have the same version of odin, how did you downgrade it,or you have 2 version of odin installed on you computer which you can switch to any version you want to use
Click to expand...
Click to collapse

---

Odin doesn't have to be installed.
Just to doubleclick any of the different .exe starts the appropriate version.