what do i put into each slot ie; rom in pda, which slot does kernel go in etc?
You use a tar file in PDA, don't extract it so you have the kernel and so on...
Sometimes you will have three tar files,
code - PDA
Modem - phone
csc - csc
These should still be tar files, possibly md5...
The stock roms always seem to come out in 1 file so just put in PDA, make sure repartition is UNticked and flash away...
GOOD NEWS
NO MORE NEED THIS PIT FILE FOR BIG HIDDEN, (for now):
Because have Members that notice have flashed UK Rom's Multi.CSC VFG after flash the Germany DBT Pit file, I tried the same:
After a full wipe I flashed this Pit file attached and link. After I have installed a XXUENB4 VFG TCL Rom that have a hidden file = 86.661 KB.
The install work well without hidden issues, no "FAIL! (Size)". Work well whit a HIDDEN partition whit Block Count = 204.800.
I renamed it because inside PIT partition we have Flash FileName = MSM8974.pit like we can see here:
Identifier: 71 <- Partition Number
Attribute: 5
.............
Partition Name: PIT
Flash FileName: MSM8974.pit
Here the DBT Pit file: https://meocloud.pt/link/4ebb315a-867c-4469-bfdf-c234ca9f4d1e/PIT-File-DBT+VFG-UK-MSM8974.zip/
This Pit file is for Note3's from 32 GB, may be to more also, not tried.
Good work whit this Pit File
==================================================
:good: :good: :good: :good: :good: :good: :good: :good: :good: :good: :good: :good: :good: :good:
==================================================
OLD METHOD CONTINUE HERE LIKE BACKUP:
PIT File whit a biggest HIDDEN partition to flash all Rom's. XEO_OXX.csc, DBT_DBT.csc and UK ROM's_ VFG.csc.
We have on first Kikat to Note3 N9005, the leaked Rom OXXUENA6, the next Pit file: CSC_Signed_HLTE_EUR_OPEN32G_0718.pit.
I analyzed it whit PIT Magic. It have a big HIDDEN partition whit Block Count = 471.070 ( From XEO rom it is = 20.480 <file size=8.441 KB>, from DBT Rom after have flashed the Germany DBT pit file it is = 204.800 <file size=53.125 KB> and from UK_VFG Rom's the file size is 86.661 KB).
If we flash a ROM DBT or UK VFG whit the partition from 20.480 we have this fail in Odin:
.....
system.img.ext4
modem.bin
cache.img.ext4
hidden.img.ext4
FAIL! (Size)
TESTING THIS PIT FILE:
After full wipe data + cache + dalvik and format system on mount and storage on costumer recovery...
I flashed this PIT File alone on Odin 3.09, ticked Re-Partition, and not ticked Auto-Reboot and F. Reset Time.
Power off and new Download Mode to flash a new Rom, first from 20.480. At first reboot it had bootloop on Samsung logo.
New Power off and Download Mode to flash the Customer Recovery kk(0125) from Chenglu. This recovery can't mount the sdcard (I had pull out the ExtSdCard after make to it a backup from the Internal Sdcard). Then, I not had sdcard.
In my opinion the big HIDDEN partition from this pit file was need expand your size using internal storage space, Then, deleted the sdcard partition and your content.
Solution:
On Customer Recovery, Mount and Storage, format /data and /data/media (/sdcard). Not had sdcard but the space was there.
Reboot on recovery and good, now the Rom started well.
And to try, (always after full wipe before) I flashed the DBT NB7, rooted it to see the /efs/imei/mps_code.dat. The DBT was here. Good install.
Flashed also after, the Portugal (Vodafone) NB4 Rom TCL (That not have TCL but ATL from Spain by default, like problem from XEF Rom's) and flashed well. No issues in Odin "hiden.img.ext4 -> FAIL! (Size)" like before. Rooted also and on /mps_code.dat ATL now. Good install also.
After my try's I have decided to not attach here this PIT file.
It have some dangers and change the Knox flag to 0x1, because the need to flash a Customer Recovery (For me no problems, I have my 0x1 from begin).
May be You have that leaked Rom NA6 on Your Pc like me. If not, You can download it from SamMobile, it is always there. (Search, write on white box top right, Leaked Rom N9005 and You see it).
On that leaked are two, only the _0718.pit have a big HIDDEN. The _0805.pit have a small HIDDEN.
THIS IS ONLY ONE IDEA.
If You want try this...
PS: My Note3 work well whit that big HIDDEN partition and I must not have more hidden issues in future Rom's.
Like the pit say this is for Note3 from 32GB only.
In leaked xeo na6 rom there is one pit file
Sent from my SM-N9005 using Tapatalk
newstar said:
In leaked xeo na6 rom there is one pit file
Click to expand...
Click to collapse
Write the name of that, please.
Attach it here.
Thanks
Checking, will report
Sent from what ever device I got my hands on via Tapatalk
Well i got the hidden.img fail message on Odin 3.09...
Anyone can get me that pit file? to fix it?
Edit: Read OP and saw the solution there... going to try and flash the DBT NB7 to see if it does fix it
http://forum.xda-developers.com/showthread.php?t=1916936 May be you should look into this as well.
Flashed XXEUNB4 and it flashed flawlessly
Sent from my SM-N9005 using Tapatalk
joluke said:
Well i got the hidden.img fail message on Odin 3.09...
Anyone can get me that pit file? to fix it?
Edit: Read OP and saw the solution there... going to try and flash the DBT NB7 to see if it does fix it
Click to expand...
Click to collapse
To DBT NB7 + NB4 You have here the Germany Pit.file: http://forum.xda-developers.com/showpost.php?p=50614669&postcount=77 It work well according some Members that flashed it.
Rename the pit file to MSM8974.pit . See next post.
zocster said:
http://forum.xda-developers.com/showthread.php?t=1916936 May be you should look into this as well.
Click to expand...
Click to collapse
This is the Tool that I use to analyze the Pit files, I never created any.
Attached the PIT Magic analyze from CSC_Signed_HLTE_EUR_OPEN32G_0718.pit. Identifier is Partition Number.
You see on HIDDEN partition the Block Count = 471.070. Big enough to all hidden files.
You see also on partition PIT the Flash FileName: MSM8974.pit. Then that name CSC_S... usually work but I prefer rename it always to MSM8974.pit like the partition PIT like, to flash by Odin. Whit this name I'm sure that it work well.
Identifier: 71
Attribute: 5
..........
Partition Name: PIT
Flash FileName: MSM8974.pit
GOOD NEWS
NO MORE NEED THIS BIG PIT FILE, (for now):
See in OP.
ValenteL said:
GOOD NEWS
NO MORE NEED THIS PIT FILE FOR BIG HIDDEN, (for now):
Because have Members that notice have flashed UK Rom's Multi.CSC VFG after flash the Germany DBT Pit file, I tried the same:
After a full wipe I flashed this Pit file attached and link. After I have installed a XXUENB4 VFG TCL Rom that have a hidden file = 86.661 KB.
The install work well without hidden issues, no "FAIL! (Size)". Work well whit a HIDDEN partition whit Block Count = 204.800.
I renamed it because inside PIT partition we have Flash FileName = MSM8974.pit like we can see here:
Identifier: 71 <- Partition Number
Attribute: 5
.............
Partition Name: PIT
Flash FileName: MSM8974.pit
Here the DBT Pit file: https://meocloud.pt/link/4ebb315a-867c-4469-bfdf-c234ca9f4d1e/PIT-File-DBT+VFG-UK-MSM8974.zip/
Good work whit this Pit File
Click to expand...
Click to collapse
Excelent work my friend
Enviado do meu SM-N9005 através de Tapatalk
fRIK
ValenteL said:
GOOD NEWS
NO MORE NEED THIS PIT FILE FOR BIG HIDDEN, (for now):
Because have Members that notice have flashed UK Rom's Multi.CSC VFG after flash the Germany DBT Pit file, I tried the same:
After a full wipe I flashed this Pit file attached and link. After I have installed a XXUENB4 VFG TCL Rom that have a hidden file = 86.661 KB.
The install work well without hidden issues, no "FAIL! (Size)". Work well whit a HIDDEN partition whit Block Count = 204.800.
I renamed it because inside PIT partition we have Flash FileName = MSM8974.pit like we can see here:
Identifier: 71 <- Partition Number
Attribute: 5
.............
Partition Name: PIT
Flash FileName: MSM8974.pit
Here the DBT Pit file: https://meocloud.pt/link/4ebb315a-867c-4469-bfdf-c234ca9f4d1e/PIT-File-DBT+VFG-UK-MSM8974.zip/
Good work whit this Pit File
==================================================
:good: :good: :good: :good: :good: :good: :good: :good: :good: :good: :good: :good: :good: :good:
==================================================
OLD METHOD CONTINUE HERE LIKE BACKUP:
PIT File whit a biggest HIDDEN partition to flash all Rom's. XEO_OXX.csc, DBT_DBT.csc and UK ROM's_ VFG.csc.
We have on first Kikat to Note3 N9005, the leaked Rom OXXUENA6, the next Pit file: CSC_Signed_HLTE_EUR_OPEN32G_0718.pit.
I analyzed it whit PIT Magic. It have a big HIDDEN partition whit Block Count = 471.070 ( From XEO rom it is = 20.480 <file size=8.441 KB>, from DBT Rom after have flashed the Germany DBT pit file it is = 204.800 <file size=53.125 KB> and from UK_VFG Rom's the file size is 86.661 KB).
If we flash a ROM DBT or UK VFG whit the partition from 20.480 we have this fail in Odin:
.....
system.img.ext4
modem.bin
cache.img.ext4
hidden.img.ext4
FAIL! (Size)
TESTING THIS PIT FILE:
After full wipe data + cache + dalvik and format system on mount and storage on costumer recovery...
I flashed this PIT File alone on Odin 3.09, ticked Re-Partition, and not ticked Auto-Reboot and F. Reset Time.
Power off and new Download Mode to flash a new Rom, first from 20.480. At first reboot it had bootloop on Samsung logo.
New Power off and Download Mode to flash the Customer Recovery kk(0125) from Chenglu. This recovery can't mount the sdcard (I had pull out the ExtSdCard after make to it a backup from the Internal Sdcard). Then, I not had sdcard.
In my opinion the big HIDDEN partition from this pit file was need expand your size using internal storage space, Then, deleted the sdcard partition and your content.
Solution:
On Customer Recovery, Mount and Storage, format /data and /data/media (/sdcard). Not had sdcard but the space was there.
Reboot on recovery and good, now the Rom started well.
And to try, (always after full wipe before) I flashed the DBT NB7, rooted it to see the /efs/imei/mps_code.dat. The DBT was here. Good install.
Flashed also after, the Portugal (Vodafone) NB4 Rom TCL (That not have TCL but ATL from Spain by default, like problem from XEF Rom's) and flashed well. No issues in Odin "hiden.img.ext4 -> FAIL! (Size)" like before. Rooted also and on /mps_code.dat ATL now. Good install also.
After my try's I have decided to not attach here this PIT file.
It have some dangers and change the Knox flag to 0x1, because the need to flash a Customer Recovery (For me no problems, I have my 0x1 from begin).
May be You have that leaked Rom NA6 on Your Pc like me. If not, You can download it from SamMobile, it is always there. (Search, write on white box top right, Leaked Rom N9005 and You see it).
On that leaked are two, only the _0718.pit have a big HIDDEN. The _0805.pit have a small HIDDEN.
THIS IS ONLY ONE IDEA.
If You want try this...
PS: My Note3 work well whit that big HIDDEN partition and I must not have more hidden issues in future Rom's.
Like the pit say this is for Note3 from 32GB only.
Click to expand...
Click to collapse
fRIK I cant understand what your saying
I've flashed the UENB4 rom tried the msm8974.pit with the new NB5 rom..
still get the EXT4 error, I've never felt this helpless... I know your doing everything to help but I'm confused..
Fade777 said:
fRIK I cant understand what your saying
I've flashed the UENB4 rom tried the msm8974.pit with the new NB5 rom..
still get the EXT4 error, I've never felt this helpless... I know your doing everything to help but I'm confused..
Click to expand...
Click to collapse
The NB5 Rom is from Taiwen an Hongkong right? And Your Note3 is from 16 GB right?
You know what ValenteL
I'm an idiot.. my note 3 is a UK 32gb
I think I was trying to put a 16gb rom on a 32gb note 3..
Sent from my SM-N9005 using Tapatalk
Fade777 said:
You know what ValenteL
I'm an idiot.. my note 3 is a UK 32gb
I think I was trying to put a 16gb rom on a 32gb note 3..
Click to expand...
Click to collapse
Well, the NB5 Rom's have a Hidden file from 7.865 KB only. It's sure to 16 GB because the smaller to 32 GB is 8.441 GB like on XEO Rom to Poland.
The Pit file from here is only to Germany DBT Rom's, having a hidden file = 53.125 KB and to UK VFG-csc Rom's having a hidden file = 86.661 KB.
You not have need to flash the Pit file. But now You are alright to try DBT and UK VFG Rom's.
Hi I think australian NOTE 3 32g rom has the biggest Hidden.img.. I tried using almost all the PIT file still not luck with flashing the aussie 4.4.2 rom to my UK device..
Still getting the hidden.img.ext4 error..
Now I'm using UK BTU rom.. I would really want to flash australian XSA rom to my note 3.. can anyone help??
below is the post.
http://forum.xda-developers.com/showpost.php?p=56515739&postcount=1280
Reference Thread
Samsung Galaxy S4 I9500 Lollipop Modems and Bootloaders​
Technical background
Actually, we have a dedicated thread that should host updated modems and bootloaders (for both I9500 and I9505). However, the thread was no longer updated since 2014, even the OP is never online since 2014. So, I created this thread to host all Lollipop bootloaders and modems for I9500.
Why do need we update our modem and bootloader?
As you may know, firmwares are updated often, as long as our device still get support from Samsung. Custom ROMs does the same. And often new updates are giving problems with incorrect version of your modem or bootloader (like you installed Lollipop firmware on KitKat bootloader). We need to update our modem and bootloader to ensure the maximum compatibility available and will keep us secure, everywhere (althrough we need an additional protection too).
Installation procedure
Installation via recovery (modem only):
Make sure you've installed the latest version of CWM/PhilZ/TWRP. I'd recommend TWRP.
Make sure you've done an EFS backup (just to be safe).
Reboot to Recovery mode by combination of Power+Home+Vol(+) buttons.
a. For CWM, select Install zip from sdcard.
b. For PhilZ, select Install zip then select Install zip from sdcard0 or sdcard1.
c. For TWRP, select Install.
Navigate to modem zip.
a. For CWM/PhilZ, select "Yes, instal ..."
b. For TWRP, swipe Install button.
Reboot to system.
If after installation of modem your baseband version is Unknown, restore your EFS backup.
Installation via Odin (modem and/or bootloader):
Make sure you've installed the latest version of Samsung USB Drivers on your computer.
Make sure you've done an EFS backup (just to be safe).
Reboot to Download mode by combination of Power+Home+Vol(-) buttons and proceed by pressing Vol(+).
Plug your phone to your computer.
Extract the archive (if compressed).
Open Odin and select modem and/or bootloader .tar or .tar.md5 file(s) into the corresponding location.
Select Start to proceed.
In case if your modem and/or bootloader isn't updated, repeat step 3-6, untick Auto Reboot, and select Start to proceed. Then, do a hard reboot by holding power button for 10 seconds.
If after installation of modem your baseband version is Unknown, restore your EFS backup.
How to contribute
You're welcome to send your contribution. Make sure that version you want to contribute isn't listed on this thread. You need two files: modem.bin and sboot.bin. You could obtain by extracting both files from stock firmware .tar.md5 using 7-Zip on Windows or Archive Manager on Ubuntu (remove .md5 extension first).
Packing into .tar file(s) (modem and/or bootloader):
You need an Ubuntu-installed machine or any distribution based on Ubuntu installed on your machine.
Move both files into your working directory.
Open Terminal and move it into your working directory. Example, if you're working on Desktop folder, enter this command:
Code:
$ cd Desktop
Pack one by one files using these commands:
Code:
$ tar -h ustar -c modem.bin > MODEMVER.tar [COLOR=Green]# Modem[/COLOR]
$ tar -h ustar -c sboot.bin > BOOTLOADERVER.tar [COLOR=Green]# Bootloader[/COLOR]
Replace MODEMVER.tar and/or BOOTLOADERVER.tar with version you're packing. Example, if you're packing I9500UBUHOK1 modem, change MODEMVER.tar to I9500UBUHOK1-MODEM.tar.
Add md5 checksum into .tar file(s) using this command:
Code:
$ md5sum -t PACKAGE.tar >> PACKAGE.tar
Replace PACKAGE.tar with .tar file(s) you've created. If you've more than one .tar file, insert one first and repeat this for another one.
Finally, rename file(s) using this command:
Code:
$ mv PACKAGE.tar PACKAGE.tar.md5
Replace PACKAGE with .tar file(s) you've created (without .tar extension).
Compress it into zip file(s) then attach it here or upload to somewhere else.
If you're a bit lazy to do all these steps above, grab any Odin flashable .tar files, delete everything and replace it with modem.bin or sboot.bin then rename it.
Packing into .zip file (modem only):
Download the attached template below.
Open it with any archiver app.
Put modem.bin inside modem folder.
Rename the .zip file to the version you've included.
Attach it here or upload it somewhere else.
This list is incomplete. Help me to complete this list by contributing.
Note: Sorted by the changelist number.
Latest:
UBUHPB2 (Latin America)
Changelist number: 7068753
Download: Modem Zip - Odin | Bootloader
UBUHOK2 (Latin America)
Modem version: UBUHOK1
Changelist number: 6332925
Download: Modem Zip
XXUHPB3 (Middle East and Africa)
Modem version: XXUHPB1
Changelist number: 6164126
Download: Modem Zip - Odin | Bootloader
XXUHOC6 (South East Asia)
Modem version: DXUHOA1
Changelist number: 3943544
Download: Modem Zip
Thread closed at OP's request.
Hello, i have downloaded the stock rom for Netherlands from Samfirmware.I have extract the zip file,and there came 5 files out.witch files do I have to flash with odin.
AP
BL
CP
CSC
HOME CSC.
Any help is welcome
The first 4 not the HOME CSC
AP
BL
CP
CSC
Oke,thank you.Is it save to flash?
Here is a zip file of the stock tmobile rom. TMB_G935TUVU4APIA
This is the previous rom before the new APK1..
The zip contains 4 files:
1. BL
2. AP
3. CP
4. CSC
This way you can choose what you want to flash.
Here it is >>>>>> TMB_G935TUVU4APIA
Here is just the modem >>>>>>>>APIA MODEM
Make sure when using odin you put the files in the correct slots..
BL = BL (bootloader and/or kernel)
AP = AP ( main software with all stock apps)
CP = CP ( modems)
CSC = CSC ( customer service version, Sales code data, Pit File)
easy. Now remeber that if you flash the BL (bootloader) you might not be able to revert back to a previous version. Use at you own risk. I am not responsible if you mess your phone up or destory the world.
This is here to help out.. I might be new to this S7 EDGE forum, but iam not new to the Samsung Galaxy family of phones and other forums on here..
@galaxyuser88
Great work bud.....[emoji106]