Develop Bugs

[IMPORTANT] Bootloader checksum/signature check

Thread from Chainfire for Galaxy Tab:
http://forum.xda-developers.com/showthread.php?t=888071
Just to be sure, we should check all new inofficial Firmwares from Samsung before posting it here to avoid problems. Maybe they'll do the same for SGS.

Thanks for the info mate! I'll be sure to spread this around but may I ask how do we make sure a ROM includes these new "checksum" bootloaders ?

Extract and look for "boot.bin" or "sbl.bin".
If these files are included, delete them before flashing. ;-)

codeworkx said:
Extract and look for "boot.bin" or "sbl.bin".
If these files are included, delete them before flashing. ;-)
Click to expand...
Click to collapse
Okay thanks again. This should be STICKIED!

I think almosr every new has them, i'm sure that XXJPY also has them too, but since my PC isn't near I can't say for sure. If it has I th en it isn't problem since have reveryed few timrs on older fitmeare without any problem.

00.ante said:
I think almosr every new has them, i'm sure that XXJPY also has them too, but since my PC isn't near I can't say for sure. If it has I th en it isn't problem since have reveryed few timrs on older fitmeare without any problem.
Click to expand...
Click to collapse
jpu only got it, has a low level package

00.ante said:
I think almosr every new has them, i'm sure that XXJPY also has them too, but since my PC isn't near I can't say for sure. If it has I th en it isn't problem since have reveryed few timrs on older fitmeare without any problem.
Click to expand...
Click to collapse
No XXJPY dont have it... I updated the bootloader and switch between roms like allways..
I would also advise not to use KIES anymore..

JPY has no boot.bin and sbl.bin

Time to wait a little more before flashing a future ROM via Kies Hack now and / or switch to a "Odin-only" with middle package ROM method.
Thanks for the Warning !

The latest bootloaders from Samsung are those in the JPU release and are 110% SAFE to be flashed.
We are using them to fix the 3-button combo issue.
After that, be sure NOT to update the bootloaders anymore
RazvanG

thanks for the heads-up codeworkx !
@mods:
*sticky please*

So to sum it up, there is currently no firmware package which includes a checksum check, right? JPU has boot.bin and Sbl.bin but the zImage is only 4.6 MB, so I assume it doesn't suffer from this issue.
Just have to be more careful while flashing any FUTURE firmwares, right?

Yes, these troubles can occur in a future firmware..

Thanks, codeworkx. Just in case, I do have the dxjp1 bootloaders too, if anyone is interested, I can upload those.
Sent from my GT-I9000 using XDA App

push
sticky plx

yeah, thanks for bringing it up. And a sticky would be nice too =)

On a side note, there is no stopping Samsung from implementing the checksum via official Kies update... I'll think twice before using the Kies patcher from now onwards.
Sent from my GT-I9000 using XDA App

Has anyone looked at il2 firmware for the I 9000m. People are reporting that once that flash this firmware flashing anything else will not boot, but they can flash back to il2 fine. Sounds like the first occurance of a locked bootloader on a galaxy s to me?
Sent from my GT-I9000 using Tapatalk

couldnt you reflash the boot/spl using the 3-button combo fix for any firmware version through odin if it ever gets updated.
a program with root can do a check if your boot/spl ever does change after a firmware flash. if it does just adb download, odin and flash the combo fix and you are in the clear to muck around with kernels/roms.
edit: my bad a new firmware will most likely have 3e recovery and no easy root without a kernel flash. can you do a dd dump without root using adb? if you can manually dd dump the boot and spl using adb and hash check with a save that will be able to tell if your boot/spl has been changed.

Hi all
The I9000XWJM5 firmware is known to include the boot.bin and Sbl.bin which erase the 3BR fix.
Could it be usefull in this case ?

Who have T989D PIT file ?

I have a T989 model on Korea.
But T989 stock rom have too many bloatware and too many customized.
(I prefer STOCK ROM more than custom rom)
I was falshed T989D Telus or Koodo rom using Odin.
But always fail during modem.bin
So i think T989 and T989D partition table is different.
PIT file have this partition information and i think T989 and T989D hardware is 100% will be same.
Who have T989D ICS PIT file? If you have it, could you share with it?
Thank you.

Did you try Google?
Sent from my SAMSUNG-SGH-T989 using xda app-developers app

iburnhearts said:
Did you try Google?
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
Click to expand...
Click to collapse
Sure already google it!!
Buy i cant find properly pit file.
Thanks for your reply

Pulverizer said:
Sure already google it!!
Buy i cant find properly pit file.
Thanks for your reply
Click to expand...
Click to collapse
OK so I reread your op I don't think the problem is your pit file...I think its the Odin version your using. Try this version and let me know how it goes
*Note* from my experience in flashing a stock ROM via Odin...you don't need the pit file...just PDA

iburnhearts said:
OK so I reread your op I don't think the problem is your pit file...I think its the Odin version your using. Try this version and let me know how it goes
*Note* from my experience in flashing a stock ROM via Odin...you don't need the pit file...just PDA
Click to expand...
Click to collapse
I followed your mention and re-download binary, its same symptoms as before. (T989D binary burn to my T989 device)
Still stuck during amss.bin
So, it means T989 and T989D model partition is different.
I theink I need a T989D PIT file.
Thanks for your kindly reply.

Hmmm that's not the Odin version I gave to you...it should say epic 4g at the top instead of android + slp. Download and unzip this and give it one more shot. If not then idk how to help you sorry.
Sent from my SAMSUNG-SGH-T989 using xda app-developers app

I believe the issue your having is due to trying to flash a T989D stock ROM on a T989 with ODIN.
Your flash is failing on the modem which makes sense. The T989D and the T989 use different modems and thus the reason your failing on the modem.
You do not need a .PIT file. Odin gets the partition mapping from your devive when a .PIT file is not used. Therefore the partition mapping is correct.
With Odin
-Flash the stock package for a T989
-Flash the recovery of your choice (CWM or TWRP)
From Recovery
-Flash the modem of your choice
-Flash the stock Telus or Koodo ROM
(Optional)
Flash the applicable stock Kernel and stock recovery from Odin if for some reason you dont want to keep CWM or TWRP installed.
Hope that helps!
Chris

iburnhearts said:
Hmmm that's not the Odin version I gave to you...it should say epic 4g at the top instead of android + slp. Download and unzip this and give it one more shot. If not then idk how to help you sorry.
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
Click to expand...
Click to collapse
Always thanks for your kindness.
I compared with my odin.ini and your odin.ini
Just this section difference.
"Android+slp" => "epic 4g"
Thanks for your support & i think its not odin problem.
May be.

Pulverizer said:
Always thanks for your kindness.
I compared with my odin.ini and your odin.ini
Just this section difference.
"Android+slp" => "epic 4g"
Thanks for your support & i think its not odin problem.
May be.
Click to expand...
Click to collapse
I have to agree that this is NOT a partition table issue. I have a SGH-T989D and have flashed a SGH-T989 ROM and Kernel to it with no issues and even followed a rooting guide for the SGH-T989 to root my phone (mind you used the SGH-T989D files). I would suggest using ODIN to get the recovery on your phone (if you haven't already) then use the recovery to flash the custom ROM/Kernel/etc as suggested by other members of this forum.
My advice is to check out the developers section for both the SGS2 toolkit (helps with rooting) and for the ROM\Kernel\Radio you wish to use. And ALWAYS make sure you are using the appropriate ODIN version (the EXE version) as different versions may not be 100% compatible with different phones (newer versions SHOULD be compatible with older phones, but I still try to stick to the recommended and/or tested versions).

Indian 3 file firmware???

Is there any Indian 3 file firmware,,, i have tried all but couldn't find any one???So, If i have to use pit file so i have to use with with one file firmware or there is any Indian 3 file firmware??

Here you have Indian FW but I think they are only One Package.
It doesn't matter when flashing with .pit file.

Memphis_ said:
Here you have Indian FW but I think they are only One Package.
It doesn't matter when flashing with .pit file.
Click to expand...
Click to collapse
ok..thnks ..that's what i wanna know does it matter or not 3 file or one file ,,,
i have just tick these options??
pda
re partition
pit
pda
f rest time
auto reboot??
or there is something else??

No, it doesn't matter. The firmwares for Note 2 come with a single file, generally the Modem is included in the file. You can flash a Modem or a kernel separately later with Odin, if anything is wrong with your current one.
And in Odin you don't need to touch anything, the default settings are okay.
Sent from my GT-N7100 using Tapatalk 2

vasu1 said:
ok..thnks ..that's what i wanna know does it matter or not 3 file or one file ,,,
i have just tick these options??
pda
re partition
pit
pda
f rest time
auto reboot??
or there is something else??
Click to expand...
Click to collapse
Auto reboot is only useful if you want that the phone reboots itself once the firmware is flashed. You can also put the battery out.
There's nothing more before clicking on START expect usual advices about Odin: Run Odin as Admin, battery charged (>70%), Kies process are closed, official usb cable without any extension...
One or 3 files doesn't matter for me. The 3 files are useful if you only want to flash a specific partition like the modem.

what does NAND ERASE do???

I suggest you to do nothing with Nand erase... i have read it can brick ur phone..
Sent from my GT-N7100 using xda premium

[GUIDE] How to Unbrick your AT&T S4 I337 OTA UCUAMF3

With me not reading about Samsung latest OTA locked bootloader , I rooted my phone, installed TWRP and updated SU, them I am stuck at a soft brick at the download mod, I have tried every possible way with ODIN to no luck, I always kept booting to the damn download mod, then accidentally I was able to flash this pit file to bypass the stuck download mod and was able to boot normally
All you need is ODIN and the attached pit file,
1. Download attached file and unzip it
2. Run ODIN
3. Click on pit
4. Loacate the unziped SGS-I337_16GB.pit file and load it
5. Click start, phone will reboot when when compelete
6. Done
Thought to share my findings
Good Luck Don't forget to Hit the Thanks Button

This is interesting. Is the PIT file you linked a "signed" PIT file?
The reason I am asking is because the PIT file listed in this thread...
http://forum.xda-developers.com/showthread.php?t=2323019&highlight=pit
...appears to not be signed and I think people had trouble flashing it through ODIN because it was not signed.
The size of the PIT file in the thread I linked and the PIT file in your post is different so it definitely appears to be a different PIT file.
Where did you get the PIT file from in your post? Was it pulled from a device running MF3 firmware?
Also, people should be aware both PIT files are for 16GB phones. It says so in the file name, but it's worth an extra mention just the same.
Thank, and it will be interesting to find out more information about this.

wait so, this will just fix the fact u tried to flash the recovery on mf3.. u weren't able to downgrade to amdl were u ?

scott14719 said:
This is interesting. Is the PIT file you linked a "signed" PIT file?
The reason I am asking is because the PIT file listed in this thread...
http://forum.xda-developers.com/showthread.php?t=2323019&highlight=pit
...appears to not be signed and I think people had trouble flashing it through ODIN because it was not signed.
The size of the PIT file in the thread I linked and the PIT file in your post is different so it definitely appears to be a different PIT file.
Where did you get the PIT file from in your post? Was it pulled from a device running MF3 firmware?
Also, people should be aware both PIT files are for 16GB phones. It says so in the file name, but it's worth an extra mention just the same.
Thank, and it will be interesting to find out more information about this.
Click to expand...
Click to collapse
The pit is indeed signed, and it should work for both 16GB and 32GB according to the original information
Yes It is the same file
Sent from my GT-N7105 using xda app-developers app

iB4STiD said:
wait so, this will just fix the fact u tried to flash the recovery on mf3.. u weren't able to downgrade to amdl were u ?
Click to expand...
Click to collapse
I didn't try, but I don't see why not, dude, this could be a work around
Thanks
Sent from my GT-N7105 using xda app-developers app

nkhater said:
The pit is indeed signed, and it should work for both 16GB and 32GB according to the original information
Yes It is the same file
Sent from my GT-N7105 using xda app-developers app
Click to expand...
Click to collapse
Can you tell me where the original information came from (a link)?

scott14719 said:
Can you tell me where the original information came from (a link)?
Click to expand...
Click to collapse
Prob his phone...they are simple to pull from your phone, at least with heimdall. Ive been able to pull my pit with heimdall and use it in odin successfully
His is the exact same size of the pit I pulled from my device which confirms my theory on obtaining it
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2

mg2195 said:
Prob his phone...they are simple to pull from your phone, at least with heimdall. Ive been able to pull my pit with heimdall and use it in odin successfully
His is the exact same size of the pit I pulled from my device which confirms my theory on obtaining it
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
Click to expand...
Click to collapse
The reason i am asking is because I think people have tried to use the PIT file (the one I linked above) with ODIN, and although ODIN reported it as successfully flashing, it actually did not flash. Of course, the PIT file I linked above couldn't have been from MF3 (it wasn't released at the time of that post), but I was wondering if it was a signing issue with the PIT file that kept it from actually flashing, and if not, what would be the difference between the PIT file posted by the OP and the PIT file that is in the thread I linked (other than being pulled from different firmwares)?
It is my understanding (I might be wrong here), that flashing a PIT file via ODIN to a phone would erase all partition information including ROM, KERNEL, and boot partitions. Without this information (in this case a MF3 TAR file) being flashed through ODIN directly after a successful PIT file flash, how could the phone successfully boot back up into MF3? And we all know an ODIN flashable MF3 TAR does not yet exist.

scott14719 said:
The reason i am asking is because I think people have tried to use the PIT file (the one I linked above) with ODIN, and although ODIN reported it as successfully flashing, it actually did not flash. Of course, the PIT file I linked above couldn't have been from MF3 (it wasn't released at the time of that post), but I was wondering if it was a signing issue with the PIT file that kept it from actually flashing, and if not, what would be the difference between the PIT file posted by the OP and the PIT file that is in the thread I linked (other than being pulled from different firmwares)?
Click to expand...
Click to collapse
You know...im not sure. I mean...even with new firmwares shouldnt it be the same? Unless they changed the partitions around in mf3...than again...the one I pulled from my phone was from mdl and mine is the same exact size as his...
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2

mg2195 said:
You know...im not sure. I mean...even with new firmwares shouldnt it be the same? Unless they changed the partitions around in mf3...than again...the one I pulled from my phone was from mdl and mine is the same exact size as his...
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
Click to expand...
Click to collapse
I added some Ninja edit info to my last post...

nkhater said:
I didn't try, but I don't see why not, dude, this could be a work around
Thanks
Sent from my GT-N7105 using xda app-developers app
Click to expand...
Click to collapse
i say fire up odin and try to downgrade to amdl :good:

iB4STiD said:
i say fire up odin and try to downgrade to amdl :good:
Click to expand...
Click to collapse
As much as I would like to see it work, I don't think it would be a good idea.
A. If the OP was on MF3, how did he even attempt to install TWRP as was stated?
B. (I mentioned this in one of my lasts posts in this thread) If the PIT fil actually has flashed successfully, how would any information (other than partition information) remain on his phone? Wouldn't the PIT file wipe it completely...requiring the OP to immediately flash a firmware TAR file...which does not exist yet for MF3?
Something either is very right with this (a breakthrough) or is very wrong with this.

scott14719 said:
As much as I would like to see it work, I don't think it would be a good idea.
A. If the OP was on MF3, how did he even attempt to install TWRP as was stated?
B. (I mentioned this in one of my lasts posts in this thread) If the PIT fil actually has flashed successfully, how would any information (other than partition information) remain on his phone? Wouldn't the PIT file wipe it completely...requiring the OP to immediately flash a firmware TAR file...which does not exist yet for MF3?
Something either is very right with this (a breakthrough) or is very wrong with this.
Click to expand...
Click to collapse
see, im hoping very right.. I would love to see people get around the sammy bs.. so im trying to be positive (for once) Im confused how this would work myself.. but hey stranger things have happened.. :good:

iB4STiD said:
see, im hoping very right.. I would love to see people get around the sammy bs.. so im trying to be positive (for once) Im confused how this would work myself.. but hey stranger things have happened.. :good:
Click to expand...
Click to collapse
I am theorizing (just a theory) that the PIT file actually did not flash through ODIN. It reported as flashing correctly (successful), but as others have experienced, it was a false positive and didn't really flash. I am guessing the OP's phone started to work because of the method ODIN used to reboot the phone somehow bypassed the bootloop caused by trying to put TWRP onto MF3. I have seen a couple of recent posts where people were able to boot their phones by somehow getting into recovery and canceling a certain operation out ( I'm not sure which), causing the phone (that was in a previous bootloop) to start booting correctly.
I hope it is a break through as well, but I am leaning towards my explanation (or one close to it) as the reason for the OP's success.

scott14719 said:
I am theorizing (just a theory) that the PIT file actually did not flash through ODIN. It reported as flashing correctly (successful), but as others have experienced, it was a false positive and didn't really flash. I am guessing the OP's phone started to work because of the method ODIN used to reboot the phone somehow bypassed the bootloop caused by trying to put TWRP onto MF3. I have seen a couple of recent posts where people were able to boot their phones by somehow getting into recovery and canceling a certain operation out ( I'm not sure which), causing the phone (that was in a previous bootloop) to start booting correctly.
I hope it is a break through as well, but I am leaning towards my explanation (or one close to it) as the reason for the OP's success.
Click to expand...
Click to collapse
ya, wiping cache in stock recovery, will kick the phone out of bootloop

iB4STiD said:
ya, wiping cache in stock recovery, will kick the phone out of bootloop
Click to expand...
Click to collapse
And here is another example of someone getting out of a bootloop through Download (ODIN) mode:
http://forum.xda-developers.com/showpost.php?p=44433724&postcount=11
Possibly, Odin triggered a similar reaction.
Actually, the original thread i pulled that post out of sounds very similar to what happened to the OP in this post.
Take a look at the OP of this post to see what I mean:
http://forum.xda-developers.com/showthread.php?t=2398336
So, I think my theory is correct. The PIT file never actually flashed, it was the interaction between ODIN and D/L mode that overcame the bootloop.
But hey, feel free to keep messing around with the PIT file because you never know...

I wonder where op went...
Sent from my SGH-I337 using xda premium

orlandoxpolice said:
I wonder where op went...
Sent from my SGH-I337 using xda premium
Click to expand...
Click to collapse
OP was sleeping and just woke up will reply shortly
Sent from my GT-N7105 using xda app-developers app

scott14719 said:
It is my understanding (I might be wrong here), that flashing a PIT file via ODIN to a phone would erase all partition information including ROM, KERNEL, and boot partitions. Without this information (in this case a MF3 TAR file) being flashed through ODIN directly after a successful PIT file flash, how could the phone successfully boot back up into MF3? And we all know an ODIN flashable MF3 TAR does not yet exist.
Click to expand...
Click to collapse
Sorry if this off topic but what's stopping someone from wiping the bootloader partition and flashing the MDL firmware?
I'm not sure if this would be done via a PIT file, ADB script or some other method but in general isn't this the path of last resistance for achieving root/bootloader access?

scott14719 said:
Can you tell me where the original information came from (a link)?
Click to expand...
Click to collapse
Here is the link
http://forum.xda-developers.com/showthread.php?t=2323019&highlight=pit

need 317m PIT file for reparititon

hello,
i need the PIT file from a at&t (rogers) 317m @ android 4.3 official. Mine keep crashing every time I try to load a rom, just sits at the samsung galaxy note II screen. Seems that I need to clean reload the phone using ODIN, including a repartition. I already got the stock image for my phone. Just need the associated PIT file. Could someone please post same? thanks!!!

messerchmidt said:
hello,
i need the PIT file from a at&t (rogers) 317m @ android 4.3 official. Mine keep crashing every time I try to load a rom, just sits at the samsung galaxy note II screen. Seems that I need to clean reload the phone using ODIN, including a repartition. I already got the stock image for my phone. Just need the associated PIT file. Could someone please post same? thanks!!!
Click to expand...
Click to collapse
Only thing u can do without pit. Cause it seems pit wont work since update to 4.3 I tried many different things. Only thing you can do is odin a 4.3 stock rogers. Or the rooted 4.1.2 firmware.
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app

jester12345 said:
Only thing u can do without pit. Cause it seems pit wont work since update to 4.3 I tried many different things. Only thing you can do is odin a 4.3 stock rogers. Or the rooted 4.1.2 firmware.
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Can someone post a pit file for me?

Look in the general section.
Sent from my SAMSUNG-SGH-I317 using Tapatalk

http://forum.xda-developers.com/showthread.php?t=2609871

messerchmidt said:
hello,
i need the PIT file from a at&t (rogers) 317m @ android 4.3 official. Mine keep crashing every time I try to load a rom, just sits at the samsung galaxy note II screen. Seems that I need to clean reload the phone using ODIN, including a repartition. I already got the stock image for my phone. Just need the associated PIT file. Could someone please post same? thanks!!!
Click to expand...
Click to collapse
Before you attempt an Odin + pit recovery have you tried the following:
1 - boot into recovery and do a factory reset
2 - flash the stock image via Odin by itself (please copy and post the results from the status screen) - then repeat step #1
If that doesn't resolve your issue....
It's very rare that a repartition is needed, as I'm not aware of any roms that muck with the partition sizing/data on the i317/i317m .... but depending on what the status screen says it may be worth an attempt. If you visited the link above, you'll see that I've temporarily pulled the files. I have a new files ready and am planning on testing the one for the i317 this weekend. I don't have a i317m so... if you want to test the file (which was pulled correctly from an i317m and is now sized correctly) - send me a PM.

Zen Arcade said:
Before you attempt an Odin + pit recovery have you tried the following:
1 - boot into recovery and do a factory reset
2 - flash the stock image via Odin by itself (please copy and post the results from the status screen) - then repeat step #1
If that doesn't resolve your issue....
It's very rare that a repartition is needed, as I'm not aware of any roms that muck with the partition sizing/data on the i317/i317m .... but depending on what the status screen says it may be worth an attempt. If you visited the link above, you'll see that I've temporarily pulled the files. I have a new files ready and am planning on testing the one for the i317 this weekend. I don't have a i317m so... if you want to test the file (which was pulled correctly from an i317m and is now sized correctly) - send me a PM.
Click to expand...
Click to collapse
I reloaded the stock image (rogers 4.3) via odin and did a factory reset in twrp, but i still cannot get a non-stock rom to work. very annoyed, and was going to try to PIT it.

messerchmidt said:
I reloaded the stock image (rogers 4.3) via odin and did a factory reset in twrp, but i still cannot get a non-stock rom to work. very annoyed, and was going to try to PIT it.
Click to expand...
Click to collapse
Did the stock rom work?
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app

yes using the stock rom atm. as soon as i try to flash a non-stock rom, i it hangs at the boot screen after it retsrats. some older threads suggested re-flashing the phone with a pit file to repartition. I dont know what else to do

Which non-stock rom? After flashing it are you able to get into recovery mode? Does this rom by any chance flash a modem.bin?
If a stock rom loads ok, chances are your pit mapping is OK.
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app

messerchmidt said:
yes using the stock rom atm. as soon as i try to flash a non-stock rom, i it hangs at the boot screen after it retsrats. some older threads suggested re-flashing the phone with a pit file to repartition. I dont know what else to do
Click to expand...
Click to collapse
Sounds to me like ur definitely not giving the roms enough time on the boot. Some could take 5-7 minutes for initial boot. The fact that stock works and EVERY OTHER ROM here doesn't... leads me to believe this. Patience is virtue
Sent from my SAMSUNG-SGH-I317 using Xparent Skyblue Tapatalk 2

also, someone at your skill level should not be messing with partitions; you are just asking for a brick..

Not to mention the likely requirement of fully wiping the internal storage of the device...
Arbitrarily changing frameworks back and forth without wiping the file structure first will give you problems on boot...(boot loops)...
Additionally....once the rom is flashed...it may help to immediately go to recovery and wipe the device caches and data again...g
Sent from my NOTE 2.750...
Courtesy of our amazing developers...

listen to greg; he is an authority on re-partitioning and bricking! :victory:

wase4711 said:
listen to greg; he is an authority on re-partitioning and bricking! :victory:
Click to expand...
Click to collapse
ok i will try again and keep you posted

got it working after several tires, running the 4.3 jedi x2
:good: