Database Develop

[Q] Can't boot - E:Can't mount /dev/block/stl10

I was running JPH on my i9000m when it lost signal, froze up, and wouldnt boot past the i9000 splash screen. So I flashed JH2 on it, It then came up with the error: "E:Can't/b mount /devlock/stl10". It will get past the galaxy s boot up video but will hang into black. Its just like my 1st i9000 that didnt have 3-button recovery at the time, I had it replaced. But this one had 3-button recovery out of the box. I am surprised I cannot fix it ATM. I flashed different froyo builds on it and they came up with: "E: can't mount /dev/block/mmcblk0p1". I have read that this has something to do with the filesystem of the phone being corrupt or something of that effect? Which makes sense, Since I did have a lagfix on it when It keeled over.
I hope someone can point me in the right direction
PS: I spent hours researching but I couldn't find anything that worked. I rarely post for help...buuuut, I'm kinda at a loss :S
PPS: I will be playing Dead Rising 2 early as I wait for responses

your phone is most likely toast, search around for similar problem, no one has been able to wipe or reset the internal sd card when this happens...its very frustrating, im on my second galaxy S because of this problem. the sooner you take it back the sooner you will have a new phone.

Flash jpc with 512 pit and reparation ticked.
Than you can go back to jph by flashing again without pit and without reparation.
Sent from my GT-I9000 using XDA App

omrij said:
Flash jpc with 512 pit and reparation ticked.
Than you can go back to jph by flashing again without pit and without reparation.
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
I'd love to hear if this actually works, i'm guessing it won't....I was told to try all kinds of different things including this....nothing worked. good luck.

omrij said:
Flash jpc with 512 pit and reparation ticked.
Than you can go back to jph by flashing again without pit and without reparation.
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
Ya-no.
This will not work with this error code. Although, It has worked in the past with other errors.
I have a feeling I'm gonna have to get ANOTHER replacement....It probably won't be a DOA instant switch like last time though..augh....Loner-Phone, Here I come! :'(

I wonder...
Does Clockwork Recovery have a button combo? Much like regular recovery?

Jordiharrison said:
I was running JPH on my i9000m when it lost signal, froze up, and wouldnt boot past the i9000 splash screen. So I flashed JH2 on it, It then came up with the error: "E:Can't/b mount /devlock/stl10". It will get past the galaxy s boot up video but will hang into black. Its just like my 1st i9000 that didnt have 3-button recovery at the time, I had it replaced. But this one had 3-button recovery out of the box. I am surprised I cannot fix it ATM. I flashed different froyo builds on it and they came up with: "E: can't mount /dev/block/mmcblk0p1". I have read that this has something to do with the filesystem of the phone being corrupt or something of that effect? Which makes sense, Since I did have a lagfix on it when It keeled over.
I hope someone can point me in the right direction
PS: I spent hours researching but I couldn't find anything that worked. I rarely post for help...buuuut, I'm kinda at a loss :S
PPS: I will be playing Dead Rising 2 early as I wait for responses
Click to expand...
Click to collapse
Hello
I had the same and i solved through the guide here:
http://briefmobile.com/how-to-android-2-2-on-galaxy-s
But i think the problem really was that i have make an ext2 partition on sd-card.
I removed the sd-card during flashing.

Works !!!!

omrij said:
Flash jpc with 512 pit and reparation ticked.
Than you can go back to jph by flashing again without pit and without reparation.
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
Worked like a charm for me. Cheers

omrij said:
Flash jpc with 512 pit and reparation ticked.
Than you can go back to jph by flashing again without pit and without reparation.
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
Worked for me too. Thanks!

omrij said:
Flash jpc with 512 pit and reparation ticked.
Than you can go back to jph by flashing again without pit and without reparation.
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
Ok so i used this method to get my phone running again and it worked, which is why i said thanks. But the problem now is that i dont want to flash to jph and it keeps giving me the same error if i flash any other firmware.
Anyone know the soloution for this? All help appreciated thanks.
P.s I've been trying to flash back to lower firmwares so that i can update to froyo officially through kies.
Update:
Nobody seems to be helpful around here when i ask for help but thought id share with the people who have this problem in the future.
Try using a different pit file when flashing, as there are two types of pit files. If you need more details just pm me.

Hi Riverriz , what's jpc stand for?

Flashing JPC with repartition using 512 pit works!
My Internal SD working again just after flashing JPC, now go back to Doc's rom. Thanks.

guys what is JPC and how do you falsh with it im stuck with same issue any links ??

update: did this and the phone gets tsuck in a reboot loop tried two 512 .pit

Is the JPC rom you're talking about the one available on samfirmware.com that unpacks to "I9000XXJPC_I9000OXAJPC With new .PIT and ODIN"?
I've been trying to flash various roms all afternoon with different versions of Odin and different .pits and invariably I get either an stl10 error, an stl11 and mmcblk0p1, or just an mmcblk0p1 error.
The mmcblk0p1 error seems to be pretty much finito as far as these phones are concerned but I was hoping that the fact that various roms would give me the stl10 error from which other people had been able to recover meant that there was still hope.
Is there a possibility for recovery from where I'm at?

I have problem like that on my galaxy tab. i didn't find answer on briefmobile,and i'm very afraid that i broke my device. so please, somebody, tell, how to solve this problem

Miggles said:
Is the JPC rom you're talking about the one available on samfirmware.com that unpacks to "I9000XXJPC_I9000OXAJPC With new .PIT and ODIN"?
I've been trying to flash various roms all afternoon with different versions of Odin and different .pits and invariably I get either an stl10 error, an stl11 and mmcblk0p1, or just an mmcblk0p1 error.
The mmcblk0p1 error seems to be pretty much finito as far as these phones are concerned but I was hoping that the fact that various roms would give me the stl10 error from which other people had been able to recover meant that there was still hope.
Is there a possibility for recovery from where I'm at?
Click to expand...
Click to collapse
I am in a similar situation. Does anyone have any ideas how to fix this? I tried to install Doc's JPU rom with the CWM JPU kernel and now I seem to be chasing partitions that can't mount etc.
Thanks,
David

I eventually gave up on this - it wasn't going to fix itself regardless of what I did.

JPC with the 512 PIT worked for me. Now my I9000 is flying again.

[Q] Which PIT do I use

Hey all,
Ive got a SGS from Optus in Australia but its unbranded. Currently I'm running JG4 rom.
I want to update to the JPO. Ive got the ROM. Ive got Odin and Ive got 3 pits.
Everything is fine, I just don't know which PIT to use. 512, 513 or 803. Could I just flash the rom over without a PIT? Should I repartition? This is the first time Ill be doing a flash.
Any help would be appreciated!

Advice from the experts
Hi,
The quickest and simplest is to go on the samfirmware.com site and register and log in. Everthing you'll need will be found there.

you will first want to flash with the 512 and repartition on.. i dont exactly remember which rom i think jm6 (samsfirmwares has the info on that)
and afterwards u flash the jpo with 813 pit and no repartition.
But yea just read the *info on the roms over there it explains the process.

Putting Pit file 813 without repartition checked is nonsense...
If this box unchecked, then ODIN will ignore Pit file.
At the end, I've never been able to flash whatever firmware with 813 pit file. All went very well with 512 one...
Sent from my GT-I9000 using XDA App

Just a quick question guys: what does re-partition really do and when should it be used ?

Prasad007 said:
Just a quick question guys: what does re-partition really do and when should it be used ?
Click to expand...
Click to collapse
It make the partition in different size. But so far i only use pit 512 for all firmware.
It works best.
You should only use them when you want to wipe you phone clean and need to re-partition the phone.
And yes you must tick the re-partition box to make it work. Else it don't use the pit file.
So samfirmware show wrong.
Sent from GT-I9000 jpo. My own kernel for z4mod and with 342MB Ram

Yeah the pit doesn't really matter, stick with 512.

[Q] Do we need PIT files while flashing ROMs?

Hi people,
Have you seen samfirmware site lately?? They now recommend NO PIT FILES FOR EVERY ROM from Eclier to latest JPX. I think it makes sense. Our phones already come with a pit suited best for them, we actually dont need to do it again.
Imagine re-partitioning your hard-drive every time you want to install linux or windows. We actually don't do that, The max we do is format 1 drive.
This topic doesn't belong in Dev, & can be moved to an appropriate location once this issue has been sorted out.
Thanks.
Update :
1. SEA (South East Asia) is one region where you require to re-partition with a 512 pit if you want to flash other region ROMs.
PS : All the partitions of our SGS are formatted anyway when we flash a FW through Odin.
EDIT : I have had to use a 512 PIT twice when I downgraded from froyo to eclier. Without that I was getting error. Some developer may shed some light on that.
EDIT 2 : I remember that happened because I followed wrong steps & had flashed 803 PIT. I had to reflash 512 to come out of it.

I don't know ragin.
The table with the firmware on samfirmware is still containing PIT-files.
Exeptions are the first 13 firmwares.
Even JPU and JPX need a PIT file.
But thats only how i read the table!

LaurensJ said:
I don't know ragin.
The table with the firmware on samfirmware is still containing PIT-files.
Exeptions are the first 13 firmwares.
Even JPU and JPX need a PIT file.
But thats only how i read the table!
Click to expand...
Click to collapse
I mean this page where they have published their ROMs for downloading.
http://www.samfirmware.com/WEBPROTECT-i9000.htm

76 ROMs published, all with the same note '1 file select NO .PIT'
That includes JPU & JPX.

If your phone is already formatted with 512.pit you can flash any ROM which works on 512.pit without selecting a PIT file and without selecting repartition.

ragin said:
I mean this page where they have published their ROMs for downloading.
http://www.samfirmware.com/WEBPROTECT-i9000.htm
Click to expand...
Click to collapse
Yes i mean that page as well (with the table).
Its also say's:
Please when you have only one file SKIP RE-PARTITION!
Use only .PIT files if you have 3 files!
So the last column of that table i interpret as using no PIT file ONLY when you have one file. But if the you update 3 files you need a PIT-file.

izibi said:
If your phone is already formatted with 512.pit you can flash any ROM which works on 512.pit without selecting a PIT file and without selecting repartition.
Click to expand...
Click to collapse
Exactly my thought, should we all update our guides & tell everyone, NO PIT to be used?
A lot of people get confused over pit, & a lot of guys have faced problems too.
PS : I have International SGS, & I think they all come pre-partitioned with 512.

PIT files are only ever used when you wish to repartition, which is rarely necessary. There has been a lot of confusion in regards to this as in the past samfirmware was telling users to select a PIT file without repartitioning, which does nothing. Odin doesn't really make this clear either. I have tried to make this clear with Heimdall Frontend by only allowing the selection of a PIT file when repartitioning.

LaurensJ said:
Yes i mean that page as well (with the table).
Its also say's:
Please when you have only one file SKIP RE-PARTITION!
Use only .PIT files if you have 3 files!
So the last column of that table i interpret as using no PIT file ONLY when you have one file. But if the you update 3 files you need a PIT-file.
Click to expand...
Click to collapse
One file means a high level package, 3 files means a middle level package, both contain the same information. No difference at all. Richthofen has helped us a lot by converting a lot of high level packages to middle level ones & made it safer to flash because they dont contain boot loaders.
PS : No boot loaders, safer to flash.

ragin said:
One file means a high level package, 3 files means a middle level package, both contain the same information. No difference at all. Richthofen has helped us a lot by converting a lot of high level packages to middle level ones & made it safer to flash because they dont contain boot loaders.
Click to expand...
Click to collapse
OK.... Learned something new today. Thanks.

First- thanks for the clarification. For a newbie all this flashing process is unclear. Now I know I don't have to select a PIT file.
Second- Is it important to have CSC file? In Nokia you had to change your product code to be able to flash different firmwares. Is this the same in SGS?
Thanks!

bomba6 said:
First- thanks for the clarification. For a newbie all this flashing process is unclear. Now I know I don't have to select a PIT file.
Second- Is it important to have CSC file? In Nokia you had to change your product code to be able to flash different firmwares. Is this the same in SGS?
Thanks!
Click to expand...
Click to collapse
I am just an observer. I hope some real developers will really look into the matter & clarify things.
For SGS, you can flash any official firmware with a reg-hack, dont need to change the CSC for it

@ragin,
Not true, if you come from SEA region, pit513 is needed if your rom is from the Europe or US region, else there will be an error.
This apply as well, vice-versa.
Sent from my GT-I9000 using XDA App

I think repartition is necessary when lagfix problem happens, for example.
Sometimes we forgot the unlagfix before running new Roms on Oddin. In this cases repartition and pit flie, may fix the broken partition. Am i right?

criscan said:
I think repartition is necessary when lagfix problem happens, for example.
Sometimes we forgot the unlagfix before running new Roms on Oddin. In this cases repartition and pit flie, may fix the broken partition. Am i right?
Click to expand...
Click to collapse
Lagfixes dont alter partitions. Or am I wrong? They only change the file systems.

g00ndu said:
@ragin,
Not true, if you come from SEA region, pit513 is needed if your rom is from the Europe or US region, else there will be an error.
This apply as well, vice-versa.
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
Do you have to do it everytime? Since you already have a phone thats partitoned with 513.
India is SEA? I haven't used 513 ever.

ragin said:
Do you have to do it everytime? Since you already have a phone thats partitoned with 513.
Click to expand...
Click to collapse
Well, whenever I switched firmwares between the regions, yes, I need to. From DXJG4 to JP3, and from JP3 back to DXJPA.
No, SEA refers to Singapore, Malaysia, Thailand, Vietnam, Philippines, and it is also not the same as Hong Kong, Taiwan and China, that region has the prefix of ZS.
Sent from my GT-I9000 using XDA App

g00ndu said:
Well, whenever I switched firmwares between the regions, yes, I need to. From DXJG4 to JP3, and from JP3 back to DXJPA.
No, SEA refers to Singapore, Malaysia, Thailand, Vietnam, Philippines, and it is also not the same as Hong Kong, Taiwan and China, that region has the prefix of ZS.
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
SO, SEA (South East Asia) is one region where you require a 512 if you want to flash other region ROMs.
Thats a start.

Is there a way to know how my device is partitioned right now (512,513,803)? any app to show this?
I have a phone from Thailand (so, 513?) and would like to flash firmware of another region (probably 512).

I think this is how re-partition and pit files work:
1. Pit files are only needed if you tick the re-partition box.
2. Re-partitioning reformats partitions back to rfs. (Not so sure about this.)
3. When you flash without ticking re-partition, odin overwrites the files without reformatting. This is where not disabling lagfixes can be problematic.
There are a few instances wherein you will need to re-partition:
1. As mentioned earlier, when you flash roms that use different pits, ie, 512 ->513 or 513 -> 512.
2. When you don't want to bother disabling lagfixes, you can do a re-partition to format everything. I've done this before and it's much faster than waiting for the robo-girl voice to finish her job.

[Q] internal memory shrinked to 209 mb !!

am sry if this is a repost i actually searched but couldn't find a post ,
well i flashed my galaxy tab with gingerbread 2.3 everything seems fine but the only problem is that the internal sd card memory just shrinked to 209 mb instead of 16 gb plz any help would be appreciated

Let's see if I can help you, but first can you provide more details on what actual version of GB you flashed and how you flashed it (ODIN or official signed zip)?

first of all i tried the honeycomb by spacemoose1 and after the reboot just got a blank screen so i then flashed this file P1000XXJQ1_P1000XXJQ1_P1000XXJPZ_HOME.tar with P1_EUR.pit as pit file which should have gave me the gingerbread and it does but the 16gb just shrinked to 209 mb

from where u got this pit file ? is not for this rom and for ginger
u need to flash stock froyo with pit to solve this bloody issue and then pleas use one of samfirmware.com gb roms without pit file as inside the tar "rom" there is pit file
chhers

Sort of what I was going to suggest...
Sent from my GT-P1000 using XDA App

thanks bro for ur advice , but all am confused of now is finding the right froyo stock rom with compatible pit file , cuz don't wanna loose my tab for another foolish trial , may u help me on this , and thanks in advance
i got this link hxxp://droidangel.blogspot.com/2011/05/all-samsung-galaxy-tab-froyo-22-and.html[/url] but it has a lot of versions and firmwares am i supposed to choose one of them if yes , according to what am i supposed to shoose it ?or just anyone of them will work ?
i think that P1000JPJis wat i need since am in arabic region, will it b fine to flash this version of froyo ?

Personnally I would go for the P1000XWJJ7 (not the NEW) which appears to actually be JJ5. I found that Kies actually recognized this as a valid version.
Sent from my GT-P1000 using XDA App

so u prefer that i go for the P1000DDJJ5 P1.PIT Version 2.2 October 2010 ?
is this wat u meant by (not the NEW)?

On the list from the link that you sent there are two XWJJ7 roms - I recommend the 1st one; I've tried them all and this was the best one with an unlocked bootloader.
Sent from my GT-P1000 using XDA App

ok after i get the rom what is the best way to flash it ?
open odin, load it in the pda area , check repartition and hit start , after finishing wipe the cache and do hard reset from the recovery mode , that's it ? don't i need to load a certain pit file ,
also i've been told that pit file is used to repartition the internal memory of the tab so wondered if there a certain pit file that can repartition my tab

Yes, except that you should use the associated PIT (P1_add_hidden ) file for that rom as that was probably what went wrong last time - the internal memory wasn't partitioned correctly for the GB release.

did the whole process as k0sh said still the same problem ,the firmware is working perfectly and smooth btw i realized the device memory (1.19gb ) is intact and working all the problem in the USB storage memory instead of being12.8 gb it is 209 mb

Did you flash a stock Froyo release together with the associaated PIT file and with Re-Partition ticked, using Odin3 v1.70?
Sent from my GT-P1000 using XDA App

ya i did exactly what u r saying but unfortunately still 209 mb :S:S

Mmmm.... my next step then would be try and flash a safe stock gingerbread rom as provided by the Overcome development team. Don't flash the overcome rom itself (unless you want too) but just flash the safe stock GB to see if it returns your onboard SD memory.
Sent from my GT-P1000 using XDA App

and that's exactly what i did and it solved the whole sh*t , thanx man for helping throughout this issue, and of course thanx to the overcome team for such rom

Glad to hear it, enjoy.

Trying to solve the Hong Kong N9005 woes using PIT

Samsung released a 16GB variant of the SM-N9005 in Hong Kong. This device comes with a slightly different PIT than the 'international' version of the phone.
I am attaching the PIT files of both.
Many people have soft bricked their phones while tinkering with the 16GB version. And then, people who updated to the KitKat bootloader have no option but to use a custom ROM because an official ROM using that bootloader and the 16GB pit is not out yet.
When trying to flash official 'international' ROMs on the 16GB device, it gives a 'invalid ext4 image' error.
Through some trial and error, I have made this out to be due to the fact that the 16GB pit file has a different size defined for the 'system' partition.
I have been trying to make a PIT file that will account for the 16GB size of the N9005 and will let people flash 'international' ROMs to their devices and have spent many hours on this project of mine.
And well, for the life of me, I cannot figure out how to make the required PIT.
The differences between the 16GB pit and the 32GB pit are in 3 partitions- System, Cache, SGPT.
Also attaching a PIT file that I made but I didn't want to give it out to the community because I wasn't confident about it and didn't wanna risk being the reason for bricking people's phones.
In this PIT, I have changed the system and the cache partition sizes to match the 32GB pit, but the SGPT partition is untouched because it confuses me.
PIT files can be opened, viewed and edited by the software PIT Magic by lyriquidperfection.
I am asking for advice/help, if anybody has any to offer.
Also, I have read the guidelines about these forums and the strict warning. I hope that this is classified as development. If not, I apologize and would request a mod to move this thread to the appropriate forum.

FeralFire said:
Samsung released a 16GB variant of the SM-N9005 in Hong Kong. This device comes with a slightly different PIT than the 'international' version of the phone.
I am attaching the PIT files of both.
Many people have soft bricked their phones while tinkering with the 16GB version. And then, people who updated to the KitKat bootloader have no option but to use a custom ROM because an official ROM using that bootloader and the 16GB pit is not out yet.
When trying to flash official 'international' ROMs on the 16GB device, it gives a 'invalid ext4 image' error.
Through some trial and error, I have made this out to be due to the fact that the 16GB pit file has a different size defined for the 'system' partition.
I have been trying to make a PIT file that will account for the 16GB size of the N9005 and will let people flash 'international' ROMs to their devices and have spent many hours on this project of mine.
And well, for the life of me, I cannot figure out how to make the required PIT.
The differences between the 16GB pit and the 32GB pit are in 3 partitions- System, Cache, SGPT.
Also attaching a PIT file that I made but I didn't want to give it out to the community because I wasn't confident about it and didn't wanna risk being the reason for bricking people's phones.
In this PIT, I have changed the system and the cache partition sizes to match the 32GB pit, but the SGPT partition is untouched because it confuses me.
PIT files can be opened, viewed and edited by the software PIT Magic by lyriquidperfection.
I am asking for advice/help, if anybody has any to offer.
Also, I have read the guidelines about these forums and the strict warning. I hope that this is classified as development. If not, I apologize and would request a mod to move this thread to the appropriate forum.
Click to expand...
Click to collapse
hi
i am a hk guy and luckly i did not buy the note3. but i wonder why the hk pit is different from european's, since i have no problem in using european roms at all. i have not read the pit files yet but i suggest you to repack the images from european roms and see if it work. if it fails, extract the images and tar them and untar the tar files in your phone, which should not be bound by the pit, if any
good luck

ykkfive said:
hi
i am a hk guy and luckly i did not buy the note3. but i wonder why the hk pit is different from european's, since i have no problem in using european roms at all. i have not read the pit files yet but i suggest you to repack the images from european roms and see if it work. if it fails, extract the images and tar them and untar the tar files in your phone, which should not be bound by the pit, if any
good luck
Click to expand...
Click to collapse
I know for a fact that repackaged ROMs don't work.
Can you explain the other idea? I didn't really understand it.
What do you mean by 'untar files in the phone'?
Also, anybody with a 16GB phone brave enough to test things?

FeralFire said:
I know for a fact that repackaged ROMs don't work.
Can you explain the other idea? I didn't really understand it.
What do you mean by 'untar files in the phone'?
Also, anybody with a 16GB phone brave enough to test things?
Click to expand...
Click to collapse
i mean, extracting the system.img, for instance, on a linux. then u can use tar command to create a tar file containing the whole system dir, just like a zip but without compression. finally push the tar file to your phone and then untar it to the /system in recovery. thats it
you don need to worry if u do it correctly, since i always use tar to upgrade my phone

ykkfive said:
i mean, extracting the system.img, for instance, on a linux. then u can use tar command to create a tar file containing the whole system dir, just like a zip but without compression. finally push the tar file to your phone and then untar it to the /system in recovery. thats it
you don need to worry if u do it correctly, since i always use tar to upgrade my phone
Click to expand...
Click to collapse
Yeah. That would work, but I want to solve this thing without using recovery. So that people can flash without tripping knox.
If people are unopposed to tripping knox, they can flash custom ROMs anyway.
I did build a tar file with heimdal using kitkat system and 16GB pit. Will upload it tomorrow in university. My net here sucks.

I built a tar file using Heimdall.
This was made using the 16GB pit but the files from the leaked Kitkat ROM.
It does not include the bootloader, so it shouldn't be harmful. Still, flash at your own risk.
Need a tester with a 16GB device. Preferably running Kitkat with the new bootloader.
But even without, we just need to see if this flashes successfully.
Try flashing it through odin. Repartition ought not to be ticked, but if it doesn't work without, try with it ticked as well.
If neither work, try it with heimdall.
https://mega.co.nz/#!xgZHRSqC!FGevxC9hims_UBt5xXPfWuII6KnFkw9drBRuywXtfFM

So, that didn't work.
Any other ideas?
I am all out.

Starting from SGS4, PITs are signed and cannot be flashed if modified.
So, you can only flash official PIT signed by Samsung.
If signature of HK version is compatible with International version then you can flash any of them.

sorg said:
Starting from SGS4, PITs are signed and cannot be flashed if modified.
So, you can only flash official PIT signed by Samsung.
If signature of HK version is compatible with International version then you can flash any of them.
Click to expand...
Click to collapse
The problem with the HK pit is the different size alloted to the system partition.
Does the signing issue extend to Heimdall as well?

I don't suggest to use any flasher except Odin. I never used Heimdall. Actually, it's possible to flash partitions to any place regardless PIT, but it may lead to different kinds of problems.
Long time ago, i've experimented with PIT on i9500. I've flashed PIT through dd (so, i've skipped signature check) and result was cycling reboot. Initial samsung static logo appear, shortly flash and then appear again. Thus, phone didn't even start to boot kernel. Luckily, Exynos has simple bootloader and work independently from PIT and other partitions. I've booted into download mode and flashed original PIT.
There is PIT signature check not only while flashing, but also while booting. You can flash modified PIT file through 3rd party flasher, but phone won't boot.
I doubt Note 3 has different behavior than SGS4. Especially, with much more complicated booting process on Snapdragon (unlike simple Exynos booting process) you are risking to get hard-brick.

latest lollipop
Any ideas that the hk version 16gb note 3 able to flash the poland lollipop firmware? I really get confuse coz same version n9005 but both cant share same firmware and ao complicated.

I've got the same question as elvin92,
is it possible to install Polish (XEO) Lollipop ROM on 16GB Note 3 with loaded N9005ZHUENJ1 (TGY) on board?
when trying to install via Odin I get:
...
<ID:0/003> system.img.ext4
<ID:0/003> FAIL! (Ext4)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
so it's Pit fault ? wrong sizes ?

Want to update to lollipop..
I have note 3 lte sm n9005 16 gb with TGY frimware and want to update to lollipop XEO... plz help? provide pit file...