Database Info

[Q][A]All about Odin3 v1.52

This post is to collect and share everything there is to know about Odin v1.52. Collecting information from your knowledge and experience. Sharing by using the section titles to search particular information.
What do these options do? What do they effect on the device? If you know something or have experience with it, spill the info. If there is a link to another post, use the section title and add the link. I attached a screenshot of it and program.
***Important*****
For this to work right......
To Post. Copy the section title from the OP and give your response. ex.
Odin3 v1.52/Option/Re-Partition
This is ....or what I know about it.............
Then to find the info, search with that section title from the OP in the post to retrieve results
Search post:
Odin3 v1.52/Option/Re-Partition
Here are the sections..............
Odin3 v1.52/Developer
Odin3 v1.52/Uses
Odin3 v1.52/General
Odin3 v1.52/ID:Com
Odin3 v1.52/Option/
Odin3 v1.52/Option/Re-Partition
Odin3 v1.52/Option/Auto Reboot
Odin3 v1.52/Option/F. Reset Time
Odin3 v1.52/Option/Dump
Odin3 v1.52/Option/Dump/AP Ram
Odin3 v1.52/Option/Dump/AP Nand
Odin3 v1.52/Option/Dump/ID
Odin3 v1.52/Option/Phone EFS Clear
Odin3 v1.52/Option/Phone Bootloader Update
Odin3 v1.52/Message
Odin3 v1.52/Control Panel
Odin3 v1.52/Control Panel/Start
Odin3 v1.52/Control Panel/Reset
Odin3 v1.52/Pit
Odin3 v1.52/Files [Download]
Odin3 v1.52/Files [Download]/PDA
Odin3 v1.52/Files [Download]/Phone
Odin3 v1.52/Files [Download]/CSC
Odin3 v1.52/Files [Download]/ETC
Odin3 v1.52/File [Dump]
Odin3 v1.52/File [Dump]/Dump
Good day and God bless!

Odin3 v1.52/Developer
Interesting info about the program and where it came from
Link
http://androidforums.com/samsung-i7500/9078-what-odin.html#post373495
"I'm pretty sure Dejan did not write this tool. Someone can correct me here if I am wrong.
There is a string in 3.95:
"c:\Documents and Settings\seungbum223.kang\My Documents\Visual Studio 2008\Projects\MultiOdin\Release\MultiOdin.pdb"
A quick search turns up a patent application "APPARATUS AND METHOD FOR UPDATING BOOT LOGO IMAGE IN PORTABLE TERMINAL" by "Jeong-Hwan Min and Seung-Bum Kang" for "SAMSUNG ELECTRONICS CO., LTD."
So I'm pretty sure that MultiOdin is from Samsung, which means no source is available. It sure would be nice to reverse engineer what it is doing so we don't need odin anymore."

Odin3 v1.52/Pit
Odin3 v1.52/Pit
9.What is the .pit file? Why are there different versions?
There are now three different versions of the .pit file. 513.pit, 512.pit and 803.pit. 513.pit only works for early firmwares and should not be used anymore. The 512.pit file is used for all Android 2.1 Eclair firmwares and the Android 2.2 Froyo firmwares up to and including the I9000XXJP3 firmware. Several sources now indicate that the 803.pit file solves several problems with the Froyo firmwares released after XXJP3 (i.e. I9000ZSJP2 and I9000XXJPC) compared to the 512.pit file and should be used when flashing those.
What exactly the pit file actually does is somewhat unclear. Initially, it was believed to be responsible for mapping partition sizes but it has recently been suggested that the .pit maps certain files to certain partitions. Since Odin is closed source we cannot be sure at the moment.
http://forum.xda-developers.com/showthread.php?t=723596

Odin3 v1.52/Pit
Odin3 v1.52/Pit
"There is very little technical information on PIT files , so this thread is an attempt to find out some real details about PIT files, and perhaps eventually be able to create our own PIT files (by modifying Samsung ones, probably).
First, what we think we know PIT files do:
- PIT files only affect the 'STL' devices. That is, it affects the OneNAND and not the MoviNAND.
- PIT files appear to control the sizing (and maybe number) of STL devices that appear in Linux.
- PIT files appear to be used by Odin to map filenames inside .tar archives to STL partitions.
STL files are quite small, at under 2KB in size. Most of the file is made up of 0s. I have tried to compare the differences between the 512 513 and 803 PIT files we have available.
All the PIT files start with 76 98 34 12 0D - probably a signature to show it is a PIT file.
[Unimportant]
The 803 PIT file then has 00s all the way to the next common point. The 512 and 513 both have common data till the next common point - but this can't be too important as the 803 just has 00s.
The next common bit seems to read the following:
"oft IBL+PBL Server\90\To boot.bin inn; C:\Program Files\ESTsof
This probably indicates something to Odin. Strange that it has C:\Program Files\ - build path for the PIT file?
Next we have some 0s with common 1s inside them, followed by the word PIT, then more 0s, and then ries.pit. All common from here on with the words 'EFS' and 'efs.rfs'. Probably telling odin to map the efs.rfs file to the 'EFS' token. Tokens probably defined either in the kernel, or in the closed source STL library. More of the same of this, with 'SBL' 'sbl.bin', 'SBL2' 'sbl.bin' -- Both SBL and SBL2 map to the same sbl.bin file?
'PARAM' to 'param.lfs'
'KERNEL' to 'zImage'
'RECOVERY' to 'zImage' (this one is interesting - could we have seperate zImage and recovery? Could save some RAM here!)
[/Unimportant]
And now we'r onto the actual changes between the PIT files. 'FACTORYFS' maps to 'factoryfs.rfs'. However, before the FACTORYFS token, there are some bytes that likely control the partition sizes.
FACTORYFS
803 : A2 04 : 41476
512 : 7A 04 : 31236
513 : CA 04 : 51716
DBDATA
803 : F0 01 : 61441
512 : 18 02 : 6146
513 : C8 01 : 51201
CACHE
803 : 8C
512 : 8C
513 : 8C
MODEM
803 : 32
512 : 32
513 : 32
So there we have it. The only real changes between the PIT files are some seemingly garbage header information in 512/513 that is missing from 803, and FACTORYFS and DBDATA have different numbers -- probably sizes.
So assuming FACTORYFS maps onto /system, we can see that the only differences in the PIT files is moving space back and forwards between /dbdata and /system. The numbers themselves don't mean anything to me - can anybody work it out? "
http://www.galaxyroot.com/tag/pit/

plz help me , my GT-i9000 can active recovery mode and downloading mode but boths Odin3 v1.3 , v1.52 , v1.7 can't recognize my phone when i plug USB cable
my system information :
model number : GT-i9000
firmware ver : 2.2
Baseband Ver : I9000DTJP3
Kernel Ver : [email protected] #7
Build number: FROYO.DTJP5
thanks !!
my usb cable is good (tested)

[Q] Unbricking the unbrickable Nexus S (i9023)

The initial problem
My i9023 got totally bricked after restoring it to factory defaults. As soon as I changed the SIM card and tried to power the phone up, it just wouldn't do anything; the display wouldn't turn on (neither while charging), no vibration, no light on the touch keys, nothing.
The inspirers
I found the posts by AdamOutler about the Unbrickable Mod and the Unbrickable Resurrector, plus a nice thread started by cyberalex88 on how he unbricked his Nexus S.
Current situation
Starting from what it is mentioned on the threads mentioned above, I performed the Unbrickable Mod with the help of a friend last Monday, and now the phone is detected by the Unbrickable Resurrector, but I cannot get it to work again.
The Unbrickable Resurrector interacts with the phone somehow ("S5PC110 detected") and seems to enable the Download Mode, but it is not working as I think it should.
My diagnosis
I think that the partition table of the phone is broken, but there might also be a problem with the resurrection. I've spent a good time finding information, but still I haven't been able to find a way to fix the issue. I do not how to proceed anymore.
Working environment
I've been using a dual boot PC, with Ubuntu 13.04 64bit and Windows 7, trying both Odin 1.83 and Heimdall 1.4.0 (from Ubuntu) to flash the original firmware (I9023_EUR_GRI54_XXKB3) downloaded from samfirmware.
Using The Unbrickable Resurrector
After launching the Unbrickable Resurrector, inserting the battery to the phone and plugin the usb to the Linux machine, the Resurrector detects my phone. From that starting point, I've been able to enable the "Download Mode" (search and home buttons lighted on) in the phone in two different ways:
Selecting Nexus S as Device type
After selecting "Nexus S" and performing the resurrection, the phone enters on what it should be the "Download Mode" (search and home buttons lighted on), but then it is not detected by Heimdall.
Code:
[email protected]:~#heimdall detect
ERROR: Failed to detect compatible download-mode device.
I don't know if it's related with this, but the Resurrector does not show the "Download Mode" photo on top of the window after resurrecting.
This is the log from the resurrection:
Code:
Building command list
#S5PC110 (Nexus S)
#RESURRECTOR SELECTED:HIBL.bin LOCATION:0xD0020000
#SBL: nexus_sbl.bin LOCATION:0x33040000 tool:SMDK
1. Apply UnBrickable Mod
2. Remove then insert Device battery
3. Connect to computer via USB.
4. Click the Download Mode button while holding button combination
5. Download new software with fastboot for Linux.
Begin Resurrection Sequence
Requesting Permission to access device
Please wait.... Uploading..
-------------------------------------------------------------
Hummingbird Interceptor Boot Loader (HIBL) v2.1
Copyright (C) Rebellos 2011
-------------------------------------------------------------
SMDK42XX,S3C64XX USB Download Tool
Version 0.20 (c) 2004,2005,2006 Ben Dooks <[email protected]>
S3C64XX Detected!
=> found device: bus 001, dev 031
=> loaded 24576 bytes from /tmp/TempHeimdallOneClickA2EFF4DC/UnBrickPack/HIBL.bin
=> Downloading 24586 bytes to 0xd0020000
=> Data checksum d8dc
=> usb_bulk_write() returned 24586
Interceptor Injection Complete. Injecting modified SBL
SMDK42XX,S3C64XX USB Download Tool
Version 0.20 (c) 2004,2005,2006 Ben Dooks <[email protected]>
S3C64XX Detected!
=> found device: bus 001, dev 032
=> loaded 1310720 bytes from /tmp/TempHeimdallOneClickA2EFF4DC/UnBrickPack/nexus_sbl.bin
=> Downloading 1310730 bytes to 0x33040000
=> Data checksum 6106
=> usb_bulk_write() returned 1310730
Modified SBL Injection Completed Download Mode Activated
Selecting Galaxy S as Device type
Since the Heimdall message got me worried, I tried to resurrect the phone selecting the other two device types, and it seems that it gets to "Download Mode" (search and home buttons lighted on) as "Galaxy S". As Galaxy S, after the resurrection, and unlike as Nexus S, the window shows the Download Mode photo on the top part and Heimdall detects the phone:
Code:
[email protected]:~#heimdall detect
Device detected
This is the log from the resurrection:
Code:
Building command list
#S5PC110 (Galaxy S)
#RESURRECTOR SELECTED:HIBL.bin LOCATION:0xD0020000
#SBL: Sbl.bin LOCATION:0x40244000 tool:SMDK
1. Apply UnBrickable Mod
2. Remove then insert Device battery
3. Connect to computer via USB.
4. Click the Download Mode button
5. Download new software with Heimdall.
Begin Resurrection Sequence
Requesting Permission to access device
Please wait.... Uploading..
-------------------------------------------------------------
Hummingbird Interceptor Boot Loader (HIBL) v2.1
Copyright (C) Rebellos 2011
-------------------------------------------------------------
SMDK42XX,S3C64XX USB Download Tool
Version 0.20 (c) 2004,2005,2006 Ben Dooks <[email protected]>
S3C64XX Detected!
=> found device: bus 001, dev 033
=> loaded 24576 bytes from /tmp/TempHeimdallOneClick9ECA7A24/UnBrickPack/HIBL.bin
=> Downloading 24586 bytes to 0xd0020000
=> Data checksum d8dc
=> usb_bulk_write() returned 24586
Interceptor Injection Complete. Injecting modified SBL
SMDK42XX,S3C64XX USB Download Tool
Version 0.20 (c) 2004,2005,2006 Ben Dooks <[email protected]>
S3C64XX Detected!
=> found device: bus 001, dev 034
=> loaded 1310720 bytes from /tmp/TempHeimdallOneClick9ECA7A24/UnBrickPack/Sbl.bin
=> Downloading 1310730 bytes to 0x40244000
=> Data checksum f37e
=> usb_bulk_write() returned 1310730
Modified SBL Injection Completed Download Mode Activated
Using Heimdall
Since Heimdall wouldn't detect the phone unless resurrecting as Galaxy S, I proceeded from that resurrection. The first thing I tried was to flash the original rom, but since I got an error message related with the phone's pit file, I focused on getting the pit file from the phone.
This is the output of the "print-pit" argument:
Code:
[email protected]:~#heimdall print-pit
Heimdall v1.4.0
Copyright (c) 2010-2013, Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au/
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/
Initialising connection...
Detecting device...
Claiming interface...
Attempt failed. Detaching driver...
Claiming interface again...
Setting up interface...
Initialising protocol...
Protocol initialisation successful.
Beginning session...
Some devices may take up to 2 minutes to respond.
Please be patient!
Session begun.
Downloading device's PIT file...
ERROR: Failed to receive PIT file size!
ERROR: Failed to download PIT file!
Ending session...
Rebooting device...
Releasing device interface...
Re-attaching kernel driver...
So, Heimdall is not able to get the PIT file from the phone, but it does reboot the device since the search and home buttons are turned off after launching the command. So there is some kind of communication.
Guessing that the partition table of the phone might be corrupted, I found a pit file that it is supposed to be for the device (u1_02_20110310_emmc_EXT4.pit), and launched the following Heimdall command trying to repartition the phone:
Code:
[email protected]:~#heimdall flash --repartition --pit u1_02_20110310_emmc_EXT4.pit --BOOT boot.img --SBL1 bootloader.img --RECOVERY recovery.img --FACTORYFS system.img --DATAFS userdata.img --MODEM modem.img --CACHE dgs.img
Heimdall v1.4.0
Copyright (c) 2010-2013, Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au/
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/
Initialising connection...
Detecting device...
Claiming interface...
Attempt failed. Detaching driver...
Claiming interface again...
Setting up interface...
Initialising protocol...
Protocol initialisation successful.
Beginning session...
Some devices may take up to 2 minutes to respond.
Please be patient!
Session begun.
Uploading PIT
ERROR: Failed to confirm end of PIT file transfer!
ERROR: PIT upload failed!
Ending session...
Rebooting device...
Releasing device interface...
Re-attaching kernel driver...
Using Odin
Since I had no luck with Heimdall, I installed Windows 7 on my Linux machine and rebooted to Windows after the resurrection in both modes of operation (Nexus S and Galaxy S) to try Odin. The result was the same in both cases, the device was not detected and the program only checks if the rom files are correct.
Code:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Bootloader_I9023XXKA3.tar.md5 is valid.
<OSM> PDA_SOJU_GRI54_TMO_EUR_MR1_SIGNED.tar.md5 is valid.
<OSM> MODEM_I9023XXKB3_REV_00_CL912571_SIGNED.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> All threads completed. (succeed 0 / failed 0)
I installed the Samsung USB drivers before using ODIN and plugging in the phone, so I don't think that the fact that the phone is not being detected by Odin has nothing to do with the computer itself.
Call for help
I've tried everything in my hands to try to unbrick the phone with no luck. I don't usually seek for help on the forums, but I see no other choice.
Does anyone have any clue on what to do in order to unbrick the phone?

Have you tried fastboot?

Yes. It does not detect the device.
AdamOutler said:
Have you tried fastboot?
Click to expand...
Click to collapse

unai_goiko said:
Yes. It does not detect the device.
Click to expand...
Click to collapse
Try it again, but hold the key combination.

We don't force the Nexus into Fastboot mode. you could boot it into Odin, Fastboot, or Recovery mode using this tool.

I did try the key combination ( power and volume up), and since it wouldn't work, I also tried others (power and volume down, and power and both volume buttons). Is there any other way to try to get into that mode?
AdamOutler said:
Try it again, but hold the key combination.
Click to expand...
Click to collapse

I'm sitting here with this exact problem. Anymore insight?

Adsmji said:
I'm sitting here with this exact problem. Anymore insight?
Click to expand...
Click to collapse
I had the same problem as the OP. Can enter download mode just fine (thanks to Unbrickable Mod), but fails to print PIT or flash anything. I think the flash is fried, that would explain the problem. The phone however can still be used as a S5PC110 development platform so it's not completely useless.

Adsmji said:
I'm sitting here with this exact problem. Anymore insight?
Click to expand...
Click to collapse
I'm afraid I wasn't able to find a solution and that I gave up. I still have the phone, but i haven't tried to fix it again...

xd.bx said:
I had the same problem as the OP. Can enter download mode just fine (thanks to Unbrickable Mod), but fails to print PIT or flash anything. I think the flash is fried, that would explain the problem. The phone however can still be used as a S5PC110 development platform so it's not completely useless.
Click to expand...
Click to collapse
By the way the other choice (in the drop down menu) which is Nexus S, in theory the proper choice, did not lead to a successful fastboot mode, the phone became totally unresponsive. That's presumably because the fastboot code tries to access the flash and gets stuck at this point. Like the OP I gave up.
The reason for the brick in the first place was that I removed the battery while the phone was booting (fresh ROM just installed). I guess there were some flash writes and the sudden power removal left the flash in a bad state. So don't do this.

[Q] SGS4 I9505 with Google Edition Rom loses mobile network connection

Hi All,
I flashed the otherwise fabulous Jamaal's Google Experience ROM ( http://forum.xda-developers.com/showthread.php?t=2544474 ).
My problem is, when the phone goes in standby, it loses its mobile carrier.
To reconnect I need to go to settings > mobile networks > mobile networks settings > network carriers.
Phone searches available carriers, finds mine among others (I have vodafone). I select it and then it works great... until next standby.
I saw some other people had this same issue (it is posted also on the ROM's thread), but did not find a solution or workaround.
Mu device details:
Samsung Galaxy S4 I9505
AP: I9505XXUAMDE
CP: I9505XXUAMDE
CSC: I9505OXXAMD8
Thanks in advance to all willing to help!
PS: sorry but couldn't post on specific ROM thread cos I'm noob on xda :cyclops:
UPDATE:
As described in this article, possible solution is:
If you are facing mobile network issues, make sure to update your modem to MK9. You will need to flash the modem using ODIN as it is not currently possible to flash a modem using a custom recovery on the Qualcomm variant of the Galaxy S4.
Click to expand...
Click to collapse

Solution
Hi, in case someone had the same problem I post the solution that worked for me.
Now I'm using Google Experience RC1 and all is working great
1. Installed HEIMDALL.
2. Open terminal in the folder with the modem.bin file
3. Boot SGS4 in DOWNLOAD MODE.
4. Connected to my Mac with the USB cable
5. Find out the modem partition name through command: heimdall print-pit : lists all partitions details.
The partition we are interested in is the partition containing the file modem.bin. Note down the partition name (on my device was: MDM).
After the command execution the device will reboot.
6. Repeat 3 and 4
7. Launch command: heimdall flash --[modem partition name from point 5] modem.bin
Wait patiently until it finished. Device will reboot by itself and if you prayed strong enough all will work fine.
For any doubts, here is a very helpful Heimdall command line guide on the GitHub website.

[GUIDE][TW4.4.2][LOCKED BL] Max performance setup

Disclaimer: don't do any of this unless you are familiar with flashing ROMs and debricking. Your device will boot to a "custom" splash screen, can be removed when flashing stock firmware
Model name: GALAXY S III
Country: USA (Verizon)
Version: Android 4.4.2
Product Code: VZW
AP / PDA: I535VRUDNE1
CSC: I535VZWDNE1
MODEM: I535OYUDNE1
Performance/Bare-bones setup
From stock 4.4.2 install
1) TowelRoot
2) BusyBox
3) Unofficial Safestrap Recovery v3.75 (BUG: connecting device to PC via USB cable causes system crash if stock ROM is not selected)
4) Download SUPERLITEROM! v1.0 to internal memory or ext. sdcard.
Reboot into safestrap recovery, Wipe partitions: Data, Cache, Dalvik Cache
5) install SUPERLITEROM! v1.0 to Stock ROM-slot
Reboot into Safestrap recovery, run script: fix permissions (Optional)
Do not install: BusyBox installers, Safestrap, gapps, towelroot (custom ROM already provides these)
When installing apps, be sure to move from SD card to internal memory for faster load speeds.
Optional
Upgrade to SuperSU 2.02 (get Pro)
Default Access: Grant
Show notifications: disabled
Logging: None
Enable su during boot: enabled
trust system user: enabled
Settings -> About Phone
Click several times on Build number to enable Developer Options
Play Store -> Settings
Auto-update apps: Do not auto-update apps
- Root App Delete (testing)
System Apps ->
Disable "Emergency Alerts"
Disable "MDMApp"
Disable "BandService"
Disable "New registration"
Disable "com.samsung.tutorial"
- Google Keyboard
Can Root App Delete "Samsung Keyboard"
**Also can hide icon from app list from advanced settings
- Xposed installer
- Wanam Xposed
- Lucky Patcher | block advertisements
- SD Maid (get Pro) | optimize databases
- Clean Master Phone Boost
**Disable: scan memory, low space notification, junk reminder, scan big files, real-time protection and everything below
Flashlight - comes as widget in SUPERLITEROM
Thanks to:
- Chainfire For SuperSU
- Stericson For BusyBox
- mohammad.afaneh For Safestrap and SUPERLITEROM!
Mirror links for important files: http://echostorms.net/android/

About your device
Downgrading to 4.3 or earlier is not possible without a JTAG
When device is powered off
- Hold Volume Up, Home then hold Power to enter recovery mode (Volume UP + Home + Power)
- Hold Volume Down, Home, then hold Power to enter download mode (Volume DOWN + Home + Power)
Device may be stubborn and can take multiple tries to enter recovery or download mode.
To exit download mode without flashing firmware can be done by removing the battery. In download mode, the device should be recognizable by the computer and be accessed using Odin or Kies.
Odin Flashing
PIT - Partition Information Table
BL / BOOTLOADER - boot loader
AP / PDA - refers to the build version of the firmware
CP / PHONE - refers to the baseband/modem version
CSC - is the consumer software customization and is specific to geographical region and carriers. It contains the software packages specific to that region, carrier branding and also APN settings for data connection, MMS etc for your service provider.
Nand erase all: full eMMC wipe including partitions, use .PIT file when doing this.
Firmware versions
I535VRUDNE1 - KitKat 4.4.2
I535VRUCML1 - Jelly Bean 4.3
I535VRBMF1 - Jelly Bean 4.1.2 (the security policies on the device are improved)
I535VRBMB1 - Jelly Bean 4.1.2
I535VRALF2 - Ice Cream Sandwich 4.0.4
Firmware flash order
HTML:
aboot.mbn
sbl2.mbn (secure bootloader)
sbl3.mbn (secure bootloader)
rpm.mbn (resource/power management)
tz.mbn (trustzone)
boot.img
recovery.img
system.img.ext4
cache.img.ext4
NON-HLOS.bin (modem/baseband)
internal eMMC partitions
HTML:
Model: MMC MAG4FB (sd/mmc)
Disk /dev/block/mmcblk0: 15.8GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 4194kB 67.1MB 62.9MB modem
2 67.1MB 67.2MB 131kB sbl1
3 67.2MB 67.5MB 262kB sbl2
4 67.5MB 68.0MB 524kB sbl3
5 68.0MB 70.1MB 2097kB aboot
6 70.1MB 70.6MB 524kB rpm
7 70.6MB 81.1MB 10.5MB boot
8 81.1MB 81.7MB 524kB tz
9 81.7MB 82.2MB 524kB pad
10 82.2MB 92.7MB 10.5MB param
11 92.7MB 107MB 14.3MB ext4 efs
12 107MB 110MB 3146kB modemst1
13 110MB 113MB 3146kB modemst2
14 113MB 1686MB 1573MB ext4 system
15 1686MB 14.8GB 13.1GB ext4 userdata
16 14.8GB 14.8GB 8389kB ext4 persist
17 14.8GB 15.7GB 881MB ext4 cache
18 15.7GB 15.7GB 10.5MB recovery
19 15.7GB 15.7GB 10.5MB fota
20 15.7GB 15.7GB 6291kB backup
21 15.7GB 15.7GB 3146kB fsg
22 15.7GB 15.7GB 8192B ssd
23 15.7GB 15.8GB 5243kB grow
SysScope and "Nand Erase All"
The "Nand Erase All" option doesn't seem to do a full emmc wipe, as the custom splash screen remained after a repartition.
some links about SysScope
- http://forum.xda-developers.com/showthread.php?t=2324619
- http://forum.xda-developers.com/showthread.php?t=2285894

Charging device using wall charger
1) Plug the wall charger (use brand name SAMSUNG charger) the correct way.
2) Use short cable and avoid USB extension cables.
3) Close all applications and clear RAM.
4) Keep device in a cool area or under a fan.
- Cheap or low budget extension cables or multi socket outlets can cause device to become hot or charge slowly.
- This info also applies if you are plugging in your device to the PC with a USB cable.
- Power saving mode and turning off WiFi and mobile data may help.
- Reducing brightness to lowest will help conserve battery power.
- Lower volume or external speakers with a power source may also help.
Things to avoid
- Updating to stock 4.3 or higher
- BusyBox Pro features will break MMS
- EZ-unlock will hard brick device
- Adblock can infinitely download and use all bandwidth
Device out of memory bug
- Run all scans provided by sd maid pro
- Reboot into safestrap recovery, then clear Dalvik cache and possibly cache.

Couple things.
This guide should be in the general section.
Also you shouldn't link lucky patcher, if you're looking for ad blocking then adaway or adblock are better options. The purpose of lucky patcher isn't to block advertisements and shouldn't really be linked here.

BadUsername said:
Couple things.
This guide should be in the general section.
Also you shouldn't link lucky patcher, if you're looking for ad blocking then adaway or adblock are better options. The purpose of lucky patcher isn't to block advertisements and shouldn't really be linked here.
Click to expand...
Click to collapse
Lol adblock..why not suggest ez unlock too
edit: adblock has bugged out and used up over 3GB in bandwidth in just minutes over 4G, I would suggest to avoid it.
I was just kidding about ez unlock, dont actually try it.

I've pretty much completed my research and updated the thread with more information.
thanks to mohammad.afaneh (SUPERLITEROM!) again for making this possible.

[Direct Download] Latest Bootloaders & Modems

I can't keep my mirror up due to increasing need for more space with all the projects I'm working on, sorry guys.
DOWNLOAD
You can find Odin at:
https://build.nethunter.com/samsung-tools
I am no longer hosting firmware for the Note 3. fw.updato.com provides an alternative, and allows wget/curl. (with --referer="link to the download page"))
Example:
N900W8VLU2DPG1 - MTA clicked on at http://updato.com/firmware-archive-select-model?q=N900W8
Code:
wget "http://fws01.updato.com/GALAXYNOTE3/SM-N900W8/BMC/SM-N900W8_1_20160729160241_v4dg1gvbce.zip" --referer="http://updato.com/firmware-archive-select-model?record=3C39D6E6701111E69B2DFA163EE8F90B"
READ INSTRUCTIONS BELOW, OR IT WON'T STICK AFTER FLASHING!
Each zip file contains a _HOME.tar.md5 containing each flashable partition of your device. You can flash the entire tar.md5 for a complete factory restore, or you can extract individual partitions and re-tar them to make individual flashable partition files. There's a tool for tarring them here:
https://build.nethunter.com/samsung-tools/img2tar.zip
GETTING YOUR FIRMWARE TO STICK
When flashing bootloaders (BL) and modems (CP), you must cold boot your phone for the flash to succeed.
To perform a cold boot into Odin, follow these instructions carefully:
Power down your phone
Unplug any cables from your phone
Pull the back cover off and remove the battery completely
Place the battery back in your phone (there is no need to wait)
Place 1 finger on volume down key, and 1 finger on home key
While holding those keys down, place another finger on the power key
Release the finger from the power key when you feel a vibrate
Release your other fingers once you see the Odin warning screen
You may plug your phone cable back into the phone now, or after the next step
Press volume up key to enter Download mode
SOME ODIN OPTIONS EXPLAINED
Auto Reboot - Once the firmware finishes flashing, the phone will attempt to reboot into your current ROM
Re-Partition - Used to flash a PIT file over the current one. See more information below.
F. Reset Time - Enabled by default. Not entirely sure what it does yet.
Nand Erase All - May have different effects on other devices. On the Note 3, it wipes the just the userdata partition to zeros. (your ROM settings, apps, and internal storage)
Phone Bootloader Update - Doesn't seem necessary to select when flashing bootloaders from cold boot, so unsure of purpose.
Phone EFS Clear - Reformats your EFS partition. This deletes calibration data and some small caches, you will want to flash full stock ROM when using this so it can properly restore itself. It's safe to use, and won't wipe your IMEI.
I advise not touching the other options!
When flashing firmware, you can and should leave the default options selected. Confirm that it is just Auto Reboot and F. Reset Time.
RE-PARTITIONING
Re-partitioning may be necessary in the rare scenario that updating to a newer firmware requires more storage than is available in the current layout.
It is possible to back up your PIT file (partition layout) for flashing in Odin later on or sharing with others that are having trouble flashing firmware that you were able to successfully flash.
PIT files are model specific!
Do not flash a PIT file for N9005 on an N900W8 for example. The partition layout will end up pointing to the wrong locations and you'll end up with a blank IMEI / EFS partition or worse.
If you want to back up your PIT file, you must have a rooted phone or be in TWRP which is an environment already running with root privileges.
Executing these commands will back up your PIT to a file (your-device-name.pit) on your internal storage:
su
dd if=/dev/block/mmcblk0 of="/sdcard/$(getprop ro.product.name).pit" bs=16 skip=1088 count=257
You can open the PIT file in a text editor and make sure it starts with v˜4 to be ensure validity.
Restoring a PIT file is as simple as using the PIT tab in Odin and putting it in the box there, then selecting the Re-Partition checkbox in Options tab. Re-Partitioning will not delete any data, however if your PIT file varies from your previous then partition locations may point to completely different places resulting in a no longer functioning modem or worse, a bricked phone.
WIPING YOUR DATA FOR RESALE
You can use the Nand Erase All option in Odin to make your Userdata partition unrecoverable. When the Userdata partition is nand secure erased, all data on it becomes zeros.
In order for Nand Erase option to work, you need to fill an Odin slot. Flashing your bootloader in the BL slot is usually a safe method.
Most ROMs (kernel boot images actually) can't recover from this and will not boot. In order to fix this you have to boot into a recovery.
In TWRP: Go to Wipe -> Format Data -> type "yes" -> Go
In stock recovery: Use the "factory data reset" option
Both of these perform identical procedures that restore a proper format and ext4 layout to your Userdata partition.
ROMs should now be able to boot.
You can confirm through TWRP that your userdata partition has indeed been secure erased by typing in adb or terminal:
hexdump /dev/block/platform/msm_sdcc.1/by-name/userdata
It should display:
0000000 0000 0000 0000 0000 0000 0000 0000 0000
*
After a few minutes it should complete. The asterisk means that hexdump found that same last row of data (0000...) repeating.
CHANGES
2016-02-26 - Add Nordic SM-N9005XX firmware N9005XXUGPOK2
2016-01-12 - Add SM-N9005XX firmware N9005XXUGBOL3 and N9005XXUGBOJ2 (modem)
2016-01-01 - Add Mexican SM-N900W8UB firmware N900W8UBU2DOL1 and N900W8UBU2DOK1 (modem)
2016-01-01 - Add T-Mobile SM-N900T firmware N900TUVUFOL1
2016-01-01 - Add Exynos SM-N900XX firmware N900XXUEBOL2
2015-12-18 - Add Exynos SM-N900UB firmware N900UBUEBOK1
2015-12-15 - Add Exynos SM-N900XX firmware N900XXUEBOK7 and N900XXUEBOK3 (modem)
2015-12-15 - Add Exynos SM-N900ZS firmware N900ZSUEBOK3 and N900XXUEBOK3 (modem)
2015-12-15 - Add SM-N9005DX firmware N9005DXUGBOK3
2015-12-15 - Add SM-N9005XX firmware N9005XXUGBOK9 and N9005XXUGBOD3 (modem)
2015-12-15 - Add SM-N9005ZS firmware N9005ZSUGOK2
2015-12-15 - Add KT Corporation SM-N900K firmware N900KKKU0GOK3 & N900KKKUGOJ4 (modem) (thanks to Freyelis)
2015-12-11 - Add SK Telecom SM-N900S firmware N900SKSU0GOK3 & N900SKSU0GOJ4 (modem)
2015-12-11 - Add LG Uplus SM-N900L firmware N900LKLU0GOK3
2015-12-02 - Add Sprint SM-N900P firmware N900PVPUEOK2

Why

fingerprinted said:
Why
Click to expand...
Click to collapse
Maybe I just wanna fit in with everybody else!!!!!!!!11
It just seems like a better idea to make all the latest modems and bootloaders for every variant easily available for people who don't want to wipe their custom ROMs or in case of emergencies.
Everything seems to be spread out among multiple threads, and some variants don't even have firmware threads.
Also this post gives me somewhere to send people to when I need it, regardless of what Note 3 variant they have!

Your profile made me chuckle, interests :single females

fingerprinted said:
Your profile made me chuckle, interests :single females
Click to expand...
Click to collapse
Its kinda look cute and honest. Btw,Thanks for a great work.

You are a very organized man, amazing work. Thank you

+1 very neat thread and you can get the files easily. Oh almost forgot to mention that your guide is very detailed.

There are numerous threads regarding Bootloader and Modems, but none as good as this .
Thanks for the effort mate, while this is supposed to be for Note 3, some information inside has a lot of stuff inside worthy of forwarding people to, pretty much a lot of general Samsung stuff explained.
:good:
EDIT: just wanted to add one thing. Sammy tends to confuse us, and we tend to inherit that confusion to other users. I.e, CP and BL are not consistently the same, we have right now K6 as a BL, but the modem seems still to be K1.
We should have a way to identify the real internals through *OUR* naming conventions.

guys
I am facing very low gsm signals after installing a custom rom
I cleaned flashed it wiping al that was needed
Anyway to check if i am using a wrong modem where i am located?

Question
I am having SM-n900k. Can I flash bootloaders from another model? I am sick of korean language in the download mode.

5.1.1 BL and CP?
I using N900W8 (hltcan) on 5.1.1 and im facing some Camera issues, some memers suggested me to update my BL.
This is my BL and CP version; n900w8UBUCNH1
im trying to flash OK6 BL and CP but odin fails every time (FAILED! auth)
(Does OK6 is a newer version? maybe thats the problem)
I've already disabled Device manager, remote controls and reactivation lock.
This:
BL UBU2DOI2
CP UBU2DOE4
are a newer version than UBUCNH1? do they work on 5.1.1?
thanks in advance!

HazeMC said:
I using N900W8 (hltcan) on 5.1.1 and im facing some Camera issues, some memers suggested me to update my BL.
This is my BL and CP version; n900w8UBUCNH1
im trying to flash OK6 BL and CP but odin fails every time (FAILED! auth)
(Does OK6 is a newer version? maybe thats the problem)
I've already disabled Device manager, remote controls and reactivation lock.
This:
BL UBU2DOI2
CP UBU2DOE4
are a newer version than UBUCNH1? do they work on 5.1.1?
thanks in advance!
Click to expand...
Click to collapse
yes those are the ones you should flash if you want to update. for N900W8, CNxx is KitKat (4.4), 2DOxx is Lollipop (5.0)
OK6 is for international/N9005XX models only, which is why it failed auth, and good thing it does or you'd have bricked your phone!
your camera issues are more likely related to incompatible kernel and proprietary .so files (they need to match up)
these are a few possible paths that commands can take to the hardware, sorted by most common to least common AFAIK:
1. android -> translation layer & extra functions libraries (proprietary .so files) -> kernel -> hardware
2. android -> kernel -> hardware
3. android -> translation layer & extra functions libraries (proprietary .so files) -> kernel -> firmware -> hardware
4. android -> kernel -> firmware -> hardware
see the firmware stage of communication. sometimes this firmware is included as part of the kernel, and the respective kernel drivers will flash the firmware for you if it needs updating. sometimes, very rarely, the firmware will be part of the modem or bootloader binaries instead of flashed from kernel. this is a situation where updating bootloader/modem could potentially help.
this is only from reading lots of samsung kernel sources, so some of it is only assumed. i can't know everything.
if anyone wants to share more accurate information than what i can provide, we would all be thankful!

Whats the lastest bootloader and modem for sm-n9005
im using cm13
now i have
CP_N9005XXUGPOF3.tar.md5
BL_N9005XXUGPOF3.tar.md5

sajmon1983 said:
Whats the lastest bootloader and modem for sm-n9005
im using cm13
now i have
CP_N9005XXUGPOF3.tar.md5
BL_N9005XXUGPOF3.tar.md5
Click to expand...
Click to collapse
For N9005XX, OK6 is the latest bootloader, OJ1 is the latest modem. XXUGP series is specific to Nordic regions like Finland, Sweden, etc. only as far as I can tell.
There's probably no difference in bootloader and modem code between the XXUGB and XXUGP series.
In any case, OI2 is the latest bootloader and modem for the N9005XXUGP Nordic firmware. I will add it to the mirror soon. (it's added now)

is there any reason to update to the latest bootloader/modem?
(I use XSP firmware. haven't been able to find or make my own BL or CP files)

jcadduono said:
For N9005XX, OK6 is the latest bootloader, OJ1 is the latest modem. XXUGP series is specific to Nordic regions like Finland, Sweden, etc. only as far as I can tell.
There's probably no difference in bootloader and modem code between the XXUGB and XXUGP series.
In any case, OI2 is the latest bootloader and modem for the N9005XXUGP Nordic firmware. I will add it to the mirror soon. (it's added now)
Click to expand...
Click to collapse
I cant find the link for the differences, but apparently they do actually differ, if i'm not wrong, it has something to do with a different development tree. People have reported issues flashing non-nordic roms after the nordic ones itself, but only when the values change.

jcadduono said:
yes those are the ones you should flash if you want to update. for N900W8, CNxx is KitKat (4.4), 2DOxx is Lollipop (5.0)
OK6 is for international/N9005XX models only, which is why it failed auth, and good thing it does or you'd have bricked your phone!
your camera issues are more likely related to incompatible kernel and proprietary .so files (they need to match up)
these are a few possible paths that commands can take to the hardware, sorted by most common to least common AFAIK:
1. android -> translation layer & extra functions libraries (proprietary .so files) -> kernel -> hardware
2. android -> kernel -> hardware
3. android -> translation layer & extra functions libraries (proprietary .so files) -> kernel -> firmware -> hardware
4. android -> kernel -> firmware -> hardware
see the firmware stage of communication. sometimes this firmware is included as part of the kernel, and the respective kernel drivers will flash the firmware for you if it needs updating. sometimes, very rarely, the firmware will be part of the modem or bootloader binaries instead of flashed from kernel. this is a situation where updating bootloader/modem could potentially help.
this is only from reading lots of samsung kernel sources, so some of it is only assumed. i can't know everything.
if anyone wants to share more accurate information than what i can provide, we would all be thankful!
Click to expand...
Click to collapse
Thanks for a very complete response!
I've realised that the front camera has the same issue recording video, so as far i understand you response, i will try to update the kernel, or try a different rom.
Thanks mate.

I flashed AP_N900W8VLU2DOH1_KERNEL.tar.md5 using Odin, on my N900W8, and when it reboot it get stuck and wont boot into the ROM. What is wrong?

yes ok

jorioux said:
I flashed AP_N900W8VLU2DOH1_KERNEL.tar.md5 using Odin, on my N900W8, and when it reboot it get stuck and wont boot into the ROM. What is wrong?
Click to expand...
Click to collapse
If you are on 5.0 LL you have to use DOI2