I have the latest full stock base for the Galaxy Tab Pro 12.2 Wifi (SM-T900) and want to make a bootloader package that can be flashed in ODIN.
Inside of the full stock tar file is:
boot.img
recovery. img
system. img
cache.img
hidden.img
sboot.bin
Which is the bootloader, and what do I need to do to the file, if anything, so that it can be flashed individually in ODIN? Also, should there be a modem file? Alternatively, is it possible to create a zip of these things (bootloader, modem) that's flashable in TWRP?
Thanks in advance for any help.
trav06 said:
I have the latest full stock base for the Galaxy Tab Pro 12.2 Wifi (SM-T900) and want to make a bootloader package that can be flashed in ODIN.
Inside of the full stock tar file is:
boot.img
recovery. img
system. img
cache.img
hidden.img
sboot.bin
Which is the bootloader, and what do I need to do to the file, if anything, so that it can be flashed individually in ODIN? Also, should there be a modem file? Alternatively, is it possible to create a zip of these things (bootloader, modem) that's flashable in TWRP?
Thanks in advance for any help.
Click to expand...
Click to collapse
I'm not quite sure which one is bootloader. Sometimes you can't flash each one individual ly with odin(ex like creating an odin tar that just has system). Modem files are only on lte devices. Most times you don't need them for custom roms. Anyway, you can extract each IMG and create and tar the IMG up. There are a few commands and guides to tar something and add md5 to them.
As for a flash able zip yes and no. Bootloader can't be flashed in twrp most times since I have never seen anything like that. You usually have to flash bootloader with odin. Modems don't need to be flashed since twrp doesn't mess with it most times. But you can create an flash able zip of kernel, recovery and I'm unsure of system.img(may need to extract or adjust updater scipt. Though I dont fully know).
Usually the twrp flashable in ArchiKitchen so it can help with the updater scipt stuffs. Just don't add any options such as root and busybox to it. I've never seen a flashable bootloader in twrp so it's highly unlikely of it being possible.
Hope this helps!
trav06 said:
I have the latest full stock base for the Galaxy Tab Pro 12.2 Wifi (SM-T900) and want to make a bootloader package that can be flashed in ODIN.
Inside of the full stock tar file is:
boot.img
recovery. img
system. img
cache.img
hidden.img
sboot.bin
Which is the bootloader, and what do I need to do to the file, if anything, so that it can be flashed individually in ODIN? Also, should there be a modem file? Alternatively, is it possible to create a zip of these things (bootloader, modem) that's flashable in TWRP?
Thanks in advance for any help.
Click to expand...
Click to collapse
Hi
The bootloader tar package for flashing in ODIN:
1) boot.img
2) sboot.bin
Use 'Total Commander' (google it) to make tar package (bootloader).
Any luck with the port?
shayind4
Stock & Rooted Android 4.4.2 packages for the AT&T i317 Note 2 (firmware version UCUCNJ2) in Odin and recovery flashable formats. Plus Rooted/Deodexed version of same, with restoration of SELinux file context security info, (eliminates issues when returning from custom kernels).
These are options flashable from custom recovery (CWM, TWRP) or via Odin. They are built from the August 2015 stock OTA for the AT&T I317.
** They do not include bootloader or tz files (you have the option to flash these later if desired) **
** IF YOU ARE ALREADY ON THE MK6, NE5, NJ1, or NJ2 BOOTLOADER (OR ABOVE) FLASHING ANY OF THESE PACKAGES WILL TRIP THE KNOX FLAG **
These packages are intended only for the AT&T version of the Note 2 and include the modem for this phone. Flashing on any other North American Note 2 will result in a soft brick and require a re-flash of the modem specific to your phone. Flashing on any other phone will likely require a complete reflash of your phone's stock firmware to recover - do not attempt. The other standard disclaimers apply - while these packages have been tested and work on the AT&T i317, you assume all risk in flashing.
All stock firmware packages include the system firmware, kernel, and modem from UCUCNJ2. The rooted versions include Linus Yang's build of busybox. The rooted Odin package includes a a slightly customized kernel (I added init.d support for some cleanup scripts that were needed). The full packages do not include recovery, bootloader or tz (you install the last two separately via Odin if needed).
The stock packages do not include root access - you will need to flash SuperSU separately if you use these packages.
Install instructions:
For Odin packages a format of /system from custom recovery is strongly recommended prior to flashing. (The CWM/TWRP packages will do this for you). If you are coming from another stock-based i317 firmware data/factory wipe should not be necessary. If coming from any other firmware (or if after flashing you get stuck at the Samsung or AT&T boot logo) data/factory wipe is recommended from recovery. Make any needed app and SD card backups beforehand.
**NOTE** Odin ZIP packages should be unzipped ONCE. The extracted MD5 file should be placed in the PDA slot in the Odin app. Do not change any other options. If the phone shows up on top as COMn and the MD5 checks out OK in the status window, you are good to click Start. **
1 - Download the package(s) you plan to install.
2 - Copy any CWM/TWRP packages and SuperSU (if needed) to your phone (external SD card recommended if you need to do a factory reset)
3 - Install a current custom recovery - I've been using Philz CWM v6.48.4, but current TWRP or standard CWM should also be fine
4 - Boot recovery, perform needed wipes (see first section under install)
5 - Flash package (Odin or CWM/TWRP)
6 - (Stock packages) Boot phone once, click past any setup screens, let settle for a few minutes
7 - (Stock packages) Boot recovery, flash SuperSU
8 - Boot phone, (click past setup screens), run SuperSU, disable Knox - SuperSU will hang - wait a minute, restart phone
9 - After restart, run SuperSU again, disable Knox again, this time it will take
10 - profit
Packages (hosted on Android Filehost)
AT&T UCUCNJ2 i317 Stock CWM/TWRP Note 2 --- AFH
AT&T UCUCNJ2 i317 Stock ODIN Note 2 --- AFH
AT&T UCUCNJ2 i317 Rooted CWM/TWRP Note 2 --- AFH
AT&T UCUCNJ2 i317 Rooted ODIN Note 2 --- AFH
AT&T UCUCNJ2 i317 *Deodexed* *Rooted* CWM/TWRP Note 2 --- AFH
If you *are not* running 4.3 (MK6), 4.4.2 (NE5, NJ1, NJ2) or newer bootloader:
After flashing one of the firmware packages above flash the bootloader package below in Odin to get wifi working (sorry, no option available for CWM/TWRP). I've included the Odin executable just after if needed.
Bootloader needs to be flashed only once. See post #2 here for information on how to check what version of bootloader you have installed.
** Warning - do not attempt to flash MJ4 bootloaders if you already have the MK6, NE5, or NJ1 bootloaders - this will soft brick your phone - see post #2 in my MK6 thread for more **
AT&T i317 ODIN 4.3 UCUBMJ4 (Leak) Bootloader & TZ (AT&T Note 2 ONLY) --- AFH
If you *are* running 4.3 (MK6) or 4.4.2 (NE5, NJ1, or NJ2) bootloader:
]After flashing one of the full packages, you may need to flash the NJ2 tz.img and optionally the param.bin (from the MJ4 leak). The param.bin is sometimes needed if you are on one of these bootloaders and have previously reverted to 4.1 firmware. The zips below contain Odin packages for NJ2 TZ with and without PARAM. If after flashing the stock package and you are on one of these bootloaders, try flashing the tz only package first (in Odin), then the tz+param package to see if this gets your phone to boot. You may also need to boot recovery and do a factory reset.
I've also included a final option which adds the NJ2 bootloader if you want to upgrade and lock your phone into this version. If you are on MK6 or NE5 (or lower) bootloader you can optionally flash the bootloader package. You will not be able to revert to an earlier bootloader version once you do this. Do not attempt if you are already on the NJ2 bootloader - you will soft brick your phone and need to flash something else in Odin to clear the brick. (I recommend something small, like a recovery, or one of the TZ only packages here if they match what you have on your phone). If you flash the bootloader package you can safely flash the file containing the param.bin afterward if need be.
AT&T i317 ODIN 4.4.2 UCUCNJ2 TZ.IMG (AT&T Note 2 ONLY) --- AFH
AT&T i317 ODIN 4.4.2 UCUCNJ2 TZ.IMG & UCUBMJ4 (Leak) PARAM.BIN (AT&T Note 2 ONLY) --- AFH
AT&T i317 ODIN 4.4.2 UCUCNJ2 SBOOT.BIN, UCUCNJ2 TZ.IMG (AT&T Note 2 ONLY) --- AFH
Need Odin ? --> Odin 3.07 --- AFH
Here are separate links to the ucucnj1 modem, stock kernel & stock recovery (modem and kernel are included in the main packages above, no need to reflash these a part of base install).
CWM/TWRP AT&T i317 UCUCNJ2 Stock *Modem* Note 2 --- AFH
CWM/TWRP AT&T i317 UCUCNJ2 Stock *Kernel* Note 2 --- AFH (Caution - SELinux Enforcing)
CWM/TWRP AT&T i317 UCUCNJ2 Stock *Recovery* Note 2 --- AFH
CWM/TWRP UCUCNJ2 Stock *Kernel* Custom - init.d & bootanimation support --- AFH
Here are links to custom recoveries specific to the I317 (AT&T Note 2):
PhilZ Advanced CWM Edition
TWRP Recovery
• Thanks to Chainfire for SuperSu - we wouldn't have root access on 4.3 and above without his work (consider donating to him or buying his pro version)
• Thanks to Linus Yang for the busybox build
After 6 months of procrastination and RL distractions, here are the stock packages for the UCUCNJ2 release! For additional details check post #2 in my NJ1 and NE5 stock threads (links in my sig)
.**...**.***..*..**.*..*.**...**.**.*.**.**..*.*
.***.*...***..**..*......**....*.**.***..**..*..
..*......***.*...***.*.*.**.**.*.**...*..**.**..
.**..*.*.***.***.**..*.*.**..*.*.**..*...***..**
..*......**..***.**.****..*......**.*....**..*.*
.***..*..**..*.*
Zen... thanks for your continued love and support for the AT&T Galaxy Note 2. I've been running the rooted NJ1/MJ4 firmware for over a year... never a problem... rock solid. Also, I like staying on KK 4.4.2 as mods seem to be easier (i.e., editing/swapping out pngs etc). Anyway, quick questions for you:
(1) Is there a Deodexed Rooted NJ2 "ODIN" package... or just the Recovery flashable package?
(2) most likely will stay on MJ4 BL, but curious... after all this time, is there any advantage(s) to upgrading to the NJ2 BL (i.e., does Android Pay play well with older BLs, etc). Understand once I upgraded, KNOX will trip and there's no going back.. just wondering is any advantage. (or conversely, potential for opening Pandora's box for more issues by changing BLs)
Thanks again pal for the continued support and stellar work.
If there's demand I can make an Odin of the deodexed firmware. That said, the recovery option is cleaner - it wipes system for you.. Odin does not.
Not sure about Android Pay - I don't use it. I know on MM it looks for an unaltered system partition. That's definitely not the case when deodexed.
As for bootloader, the only downside I've seen is inability to revert to earlier bootloaders. The Knox flag shouldn't matter anymore as I don't think any Note 2's are under warranty. Personal choice.. I'm on NJ2 on one phone and MJ4 on the other, fwiw. No real difference. Only thing I've seen is that with NJ2 bootloader you can turn off the phone, plug in a charger, and it stays off while charging.
Zen...
Thank you !!
I was looking at flashing NJ1 and doing OTA....but I lost a device EMMC a few days ago doing exactly that. ... (bad encryption issues)...
This is perfect. ..no more OTA...g
Hi Zen, why does I317-ODIN-UCUCNJ2_BL_TZ.zip contain two tar files?
"AT&T i317 ODIN 4.4.2 UCUCNJ2 SBOOT.BIN, UCUCNJ2 TZ.IMG (AT&T Note 2 ONLY)"
contains:
I317_UCUCNJ2_BL_TZ.tar / I317UCUCNJ2-TZ-PARAM.tar
I was only expecting to find the first one.
A - It's good to have options?
B - Thing is a terrible dyslexia?
C - I forgot to delete the other tar file before zipping?
The tar files are named correctly ... Use the one that matches what you are looking to install
I seem to be having issues. I rarely post as most things go super smooth but I cannot get this one to stop boot looping on me. Through Odin, I flashed the rooted version. It went into bootloop as soon as I unplugged the usb cable. I then flashed the tz without param. still looped. then flashed tz with param and a wipe in TWRP. Still looping. I am coming from the NJ1 file, though admittedly when I turned this phone on this morning It was in a boot loop which was odd as I never once had an issue. Any thoughts?
Was your previous rom/firmware 100% NJ1 (kernel, modem, system)? If something custom you may need to revert back, make backups (TiBu), factory reset, reflash this stock package, and restore non-system apps/data.
As a first step you could try flashing the custom version of the NJ2 kernel from recovery (see OP). It includes some repairs of the data partition to recover from running kernels that completely disable SELinux. You could also try wiping the system partition first before flashing the whole package... Odin does not do this, the cwm/twrp version will.
That said, if your phone was bootlooping before you made any changes it may have other issues.
Prior version was 100% NJ1 including bootloader all done through odin via your prior thread. I flashed this update via odin, it says pass every time I do not get to the att screen. I'm suspecting something happened as it worked pretty flawless up until I went to turn in on yesterday morning. I tried flashing everything again today, even the NJ2 bootloader, and it got to the att screen then just turned off and that was it. Luckily, and sadly, I was using it only as a media player.
Try flashing a custom recovery - I use the last version of Philz - 6.48. Boot that recovery. Do a factory reset. Format system. Wipe cache and dalvik. Using ADB copy the CWM package you want to phone (/data/media/0). Flash that package from recovery.
If you are not comfortable with ADB, replace the last two steps with flashing the Odin tar.md5 file you used before (try extracting it from the zip again just in case).
Im using the latest twrp 3, and i tried this yesterday. I couldn't get passed the boot animation. I flashed the nj2 bootloader. I tried the deodexed+rooted version. Then I tried dna4 and with that i couldn't get to the boot animation. Just kept powering on to recovery.
If you are coming from a ROM with a non-stock kernel you will have to do one of two things:
1 - flash the "custom" stock kernel zip package in the OP (this fixes most issues with the data partition after having run with SELinux disabled kernels). You can go back to the stock kernel afterwards if this works.
2 - If #1 doesn't work, clean wipe factory reset from recovery (this will wipe data partition - make backup and copy off phone first)
Otherwise, if your phone is other than an ATT Note 2 you can try flashing the modem for your phone last. Might work. This firmware is intended only for the ATT spec phone. See OP for details.
Sent from my Nexus 6P using particles and waves
E
8xnx. M
3G connectivity is near **** out of the US on this modem. It keeps dropping of mobile internet connectivity. Is it because I am out of the US?
I'm using note 2 stock rom version 4.1.2 baseband DXDLK7 but I flashed DXDLK5 to fix problem about SOS Call only , the problem is when I flash stock rom 4.3 or 4.4.2 I got SOS only problem again and I stuck in 4.1.2 forever . I flashed modem MJ9 but still not work , and all modem download link in this forum died since hotfile server down . All new custom rom such as lolipop and marshmallow require baseband modem XXUFND3 but i can't go to that modem because SOS Call problem . So how can I fix this problem ? Thanks
Make EFS backup and then:
Download firmware from sammobile for your device i.e. N7100.
Install 7zip to extract it and copy SBOOT. and modem, then use 7zip again and pack (*.tar) those files separately, so you will have sboot.tar and modem.tar
sboot is the bootloader and modem is...modem.
Use Odin to flash modem and bootloader in download mode, then use also Odin to flash TWRP.
Then go to recovery mode and install your ROM using instructions in ROM thread (1st post).
You have to know that stock ROMs are identified by letters and numbers, the newest is probably OE1, I used bootloader and modem from French ROM.
yaro666 said:
Make EFS backup and then:
Download firmware from sammobile for your device i.e. N7100.
Install 7zip to extract it and copy SBOOT. and modem, then use 7zip again and pack (*.tar) those files separately, so you will have sboot.tar and modem.tar
sboot is the bootloader and modem is...modem.
Use Odin to flash modem and bootloader in download mode, then use also Odin to flash TWRP.
Then go to recovery mode and install your ROM using instructions in ROM thread (1st post).
You have to know that stock ROMs are identified by letters and numbers, the newest is probably OE1, I used bootloader and modem from French ROM.
Click to expand...
Click to collapse
Thanks , i'll give it a test later , hope it's work
hmmm i can't see sboot file in the .tar rom file , only boot file
Hi all,
I'm looking to install my very first updated stock rom for a Galaxy Tab 3 7.0 (SM-T210) before to jump and go beyond and test a custom one.
So I found and downloaded latest 4.4.2 kitkat firmware update here:
http://www.droidviews.com/update-galaxy-tab-3-7-0-sm-t210-android-4-4-2-kitkat/ (United Kingdom: BTU-T210XXBNI1-20141021162349.zip)
Unzipping the zip archive, I have:
SS_DL.dll
T210XXBNI1_T210BTUBNI1_T210XXBNI1_HOME.tar.md5
Untar:
boot.img, cache.img, hidden.img, loke_2nd.bin, loke_pxa988.bin, NVM.img, param.lfs, PBL.bin, radio.img, recovery.img, system.img
Based on what I understood, I have to use ODIN or Heimdall software with the device in download mode but have no idea how to deal with these files.
Your help would be greatly appreciated.
Thanks!
How do people get the stock firmware img rom files from Samsung (Not the updates, but the stock firmware) - which is used for ODIN?
Over in the Note 4 forums, we are trying to build an ODIN flashable img, but need to get the Samsung firmware.
Is this from Samsung, or do you need root to extract it from the phone itself?
Thanks!