Develop Bugs

Flashing a new Bootloader BML

Hi All,
Just curious how I would go about flashing a replacement bootloader to a Samsung Galaxy S?
I am trying to do this because my phone doesn't allow the 3 button boot mode into recovery or download mode.
I know you can activate it by running
adb reboot recovery
or
abd reboot download
However if I end up with a bad flash I will never be able to do that 3 button recovery so in essense I will brick my phone.
From the BML map
http://forum.xda-developers.com/wiki/index.php?title=Samsung_Galaxy_S#Modifications
My guess is the bootloader I am looking for is at BML5
I have sucessfully backed up my BML5 from my 'neutered' phone and tonight will be backing up a BML5 from a phone which has 3 button mode active.
I backed them up using this command
dd if=/dev/block/bml5 of=/sdcard/bml5.bak
I will compare the two after this but am pretty confident they will be different. If they are different how can I go about copying a 3 button recovery mode bootloader to my device?
This post
http://forum.xda-developers.com/showpost.php?p=7610625&postcount=29
suggests there is a way to write to the bml however it is strongly discouraged.
Is there another way I can copy a non 'neutered' bootloader?

keep up the good work,
it'll be cool if you or anyone with that knowledge can get it working.
then we wont have to go back to the stores to exchange the Neutered phones

Odin?
Sent from my GT-I9000 using XDA App

it may be unwise to flash only the bml5. if the bml4 is different between the two phones, and references something in the bml5 that is also different, it may cause a brick state.
i would suggest backing up bml1-12 and comparing them. at the least bml4 and bml5 as they both deal with the secondary program loader, which should enable the 3button boot to recover if there is an error.
good work none the less

Odin doesn't work because one essential condition for Odin working is phone conected in download mode. Or, without phone in downloadmode Odin is no working.

Oef, difficult one. But what is the chance of having a bad flash by flashing a tar-ed Sbl.bin and/or boot.bin with Odin? Just wondering...

dentimarius said:
Odin doesn't work because one essential condition for Odin working is phone conected in download mode. Or, without phone in downloadmode Odin is no working.
Click to expand...
Click to collapse
Well you can get the phone into download mode by running
adb reboot download
so that isn't a problem... however I still am unsure how to flash it...
I suppose this would possibly work (in su)
dd if=/sdcard/bm5.bak of=/dev/block/bm5
but I am not game to run that until someone here with a bit more knowledge knows if it will work.

phoenixdigital said:
Hi All,
Just curious how I would go about flashing a replacement bootloader to a Samsung Galaxy S?
I am trying to do this because my phone doesn't allow the 3 button boot mode into recovery or download mode.
I know you can activate it by running
adb reboot recovery
or
abd reboot download
However if I end up with a bad flash I will never be able to do that 3 button recovery so in essense I will brick my phone.
From the BML map
http://forum.xda-developers.com/wiki/index.php?title=Samsung_Galaxy_S#Modifications
My guess is the bootloader I am looking for is at BML5
I have sucessfully backed up my BML5 from my 'neutered' phone and tonight will be backing up a BML5 from a phone which has 3 button mode active.
I backed them up using this command
dd if=/dev/block/bml5 of=/sdcard/bml5.bak
I will compare the two after this but am pretty confident they will be different. If they are different how can I go about copying a 3 button recovery mode bootloader to my device?
This post
http://forum.xda-developers.com/showpost.php?p=7610625&postcount=29
suggests there is a way to write to the bml however it is strongly discouraged.
Is there another way I can copy a non 'neutered' bootloader?
Click to expand...
Click to collapse
I see that you are going in a very good hackable way ...
Contact @ Cotulla

phoenixdigital said:
Well you can get the phone into download mode by running
adb reboot download
so that isn't a problem... however I still am unsure how to flash it...
I suppose this would possibly work (in su)
dd if=/sdcard/bm5.bak of=/dev/block/bm5
but I am not game to run that until someone here with a bit more knowledge knows if it will work.
Click to expand...
Click to collapse
i would definitely recommend odin for that! did you try to flash a international firmware version like XWJM2 as it contains a bootloader that allows the 3 button goto download/recovery mode? you can use odin to just flash boot.bin and Spl.bin to just replace the 1st and 2nd bootloader...
what is your exact hardware version of the device? i think you have to be very careful when you want to replace the bootloader(s) to not brick your phone!!

jodue said:
i would definitely recommend odin for that!
Click to expand...
Click to collapse
how would I package up the backup via dd into something that odin would be able to use?
jodue said:
did you try to flash a international firmware version like XWJM2 as it contains a bootloader that allows the 3 button goto download/recovery mode? you can use odin to just flash boot.bin and Spl.bin to just replace the 1st and 2nd bootloader...
what is your exact hardware version of the device? i think you have to be very careful when you want to replace the bootloader(s) to not brick your phone!!
Click to expand...
Click to collapse
My device is
My phone specs
Model: GT-I9000
Firmware: 2.1-update1
Baseband: I9000DTJG3
Kernel: 2.6.29 [email protected] #2
Build Number: ECLAIR.DTJG4
Would that be suitable for the XWJM2?
Thanks for the response too.

Ok I have backed BML4 and BML5 for the following
1) My 'neutered' phone on DTJG4 - I will call this NEUT1
2) A 3 click working phone on DTJG3 - I will call this 3Click1
3) A 3 click working phone on DTJG4 - I will call this 3Click2
the BML5 backup from all of the phones just contains FFFFFFFFFF data and nothing else
BML4 is definitely different between NEUT1 and 3Click2
BML4 is the same for 3Click1 and 3Click2 so the JG4 update doesn't touch the bootloader...
Soooooooo.... How do I write this working BML4 to my NEUT1 device
Anyone? Bueller?

phoenixdigital said:
how would I package up the backup via dd into something that odin would be able to use?
My device is
My phone specs
Model: GT-I9000
Firmware: 2.1-update1
Baseband: I9000DTJG3
Kernel: 2.6.29 [email protected] #2
Build Number: ECLAIR.DTJG4
Would that be suitable for the XWJM2?
Thanks for the response too.
Click to expand...
Click to collapse
i think so but i am curious why your device doesn't allow the 3 button combo in the first place? is it provider bound? if yes, which one? i'm not sure if you can flash a open firmware onto a branded sgs but i think so! does anybody else has experience with that? btw. you can find boot.bin & Spl.bin in the pda archive of the firmwares but i wouldn't flash them before you can be sure it won't brick your sgs...

jodue said:
i think so but i am curious why your device doesn't allow the 3 button combo in the first place? is it provider bound? if yes, which one?
Click to expand...
Click to collapse
It is OPTUS Australia... in recent weeks there have been a few phones being released by Optus which have the 3 button click disabled. So it appears either Samsung or Optus are disabling it.
If someone else in Australia who has rooted their phone and knows a bit of unix can run this command from a terminal on their phone
su
dd if=/dev/block/bml4 of=/sdcard/bml4.bak
then post the bml4.bak file up somewhere I can compare it to the ones I have.
It doesn't even have to be australia anyone's would be good to compare.. just let me know what firmware you are running too.. and if the 3 click mode works for you.
jodue said:
i'm not sure if you can flash a open firmware onto a branded sgs but i think so! does anybody else has experience with that? btw. you can find boot.bin & Spl.bin in the pda archive of the firmwares but i wouldn't flash them before you can be sure it won't brick your sgs...
Click to expand...
Click to collapse
I have heard of people in Australia using these Eurpoean firmwares so I should be safe there.
I wont be flashing anything until we get some advice from some senior members of this forum. I am still thinking
dd if=/sdcard/bml4.bak of=/dev/block/bml4
should do the trick but I am too scared to run it

Ok I grew a pair and flashed JM5... It flashed successfully but the 3 button mode still doesn't work...
Hmmmmmm... so the 3 button mode isn't in boot.bin or Spl.bin???
I extracted bml4 and it has not changed at all?

phoenixdigital said:
Ok I grew a pair and flashed JM5... It flashed successfully but the 3 button mode still doesn't work...
Hmmmmmm... so the 3 button mode isn't in boot.bin or Spl.bin???
I extracted bml4 and it has not changed at all?
Click to expand...
Click to collapse
strange because it should be in the 1st bootloader ...
sorry for the stupid question but i haveto ask the obvious. are you sure pressing the 3 buttons doesn't work at all? it can be tricky and often it doesn't work so maybe you are just doing something wrong? have you tried holding home+voldown and then just press power once? this is all very strange! why forbid the key combination and still allow adb boot download? makes no sense to me!

jodue said:
sorry for the stupid question but i haveto ask the obvious. are you sure pressing the 3 buttons doesn't work at all?
This is all very strange! why forbid the key combination and still allow adb boot download? makes no sense to me!
Click to expand...
Click to collapse
Yep definitely pressing them right. I performed it perfectly on the non neutered phone just an hour ago and it worked perfectly.

phoenixdigital said:
Yep definitely pressing them right. I performed it perfectly on the non neutered phone just an hour ago and it worked perfectly.
Click to expand...
Click to collapse
have you tried re-extracting the bml4 from your neut1 phone and see if it is identical to the bml4 you extracted from the 3click phones? maybe it didn't flash correctly if at all?

phoenixdigital said:
Ok I grew a pair and flashed JM5... It flashed successfully but the 3 button mode still doesn't work...
Hmmmmmm... so the 3 button mode isn't in boot.bin or Spl.bin???
I extracted bml4 and it has not changed at all?
Click to expand...
Click to collapse
Here's a Quote from another thread:
mike.sw said:
Hey again
I'm looking the flash.bat and see it need two files that my firmware (I9000JPJG8) don't have in zip/tar file:
-boot boot.bin -sbl Sbl.bin
How heimdall will handle it? Is it safe to go on?
Click to expand...
Click to collapse
Seems like some firmwares out there don't contain the bootloader. Therefore, when you flash such a firmware, the bootloader section will remain unchanged even after flashing. Maybe you should check JM5 if it even contains the bootloader section in it or not.

wang1chung said:
have you tried re-extracting the bml4 from your neut1 phone and see if it is identical to the bml4 you extracted from the 3click phones? maybe it didn't flash correctly if at all?
Click to expand...
Click to collapse
I think that was the issue actually. When I flashed JM5 in odin I selected the
PIT
PDA
PHONE
CSA
I also ticked Re-Partition (Is this really needed if you are remaining on 512-PIT?)
When it rebooted the phone went through some terminal screens and appeared to give an error. Something to do with there being two CSC config files... can't remember the exact error. So it's possible it never got to the section where it replaced the bootloader...
It did however manage to update the firmware for PDA as the JM5 European firmware was definitely installed.
So a few questions about ODIN
Is it flashing the phone directly or just uploading the .bin and .rfs files to the phone?
If it's just uploading the .bin and .rfs files when the phone reboots after a flash does the phone then install/flash these .bin and.rfs files to the final location when it reboots after ODIN?
So in short is ODIN flashing or is the phone actually flashing after ODIN has uploaded the update files?
Do you really need to tick re-partition if you are staying on 512-PIT?

just a FYI
according to a post in the General forums, Samsung is aware of the problem, and might release the fix with their next official ROM

[25.01.2011] WARNING! Do not flash JM*,KA*... README! [Patch released, L/N supported]

DO NOT USE THIS ON THE GINGERBREAD RELEASES ! THE SAMSUNG GINGERBREAD RELEASES DO HAVE SIGNED BOOTLOADERS, BUT THEY ARE NOT LOCKED. In other words, you can still flash custom kernels and such, and the bootloader patch will only break things, not fix them.
To read the history of this problem, see the 2nd post of this thread (scroll down).
A number of new firmwares for the Samsung Galaxy Tab come with "signed / protected" bootloaders. These new bootloaders prevent you from flashing custom or otherwise unsigned kernels on the device. Trying to do so anyway will result in errors and usually requires you to reflash your ROM completely.
I hope everybody here has learned the lesson not to just flash anything that SamFirmware releases
The patch
After a great many hours of researching, testing and coding, myself (Chainfire) and Rotohammer have come up with a patch that works on most devices (currently all known GSM Tab variants), and flashes back unprotected JJ4 (T-Mobile ?) bootloaders, or the original P1000N bootloaders for the Latin models. The app only patches when it finds protected bootloaders, and you have to press a button for that, so the app can also be used to look at your current status.
The patch has been tested repeatedly and with success on (0 bricks so far):
- GT-P1000 Euro/International/Unbranded Galaxy Tab
- SGH-I987 AT&T Galaxy Tab
- SGH-I987 Rogers Galaxy Tab
- SGH-T849 T-Mobile Galaxy Tab
- GT-P1000L Latin Galaxy Tab (use LATIN version!)
- GT-P1000N Latin Galaxy Tab (use LATIN version!)
Additional thanks to: koush, neldar, richardtrip, AColwill, farahbolsey, deezid, wgery, tmaurice, rmanaudio, crisvillani, alterbridge86, ivannw, themartinohana, luisfer691 (in no particular order!)
Please note that even though there have not been any bricks so far, replacing bootloaders is a very dangerous operation that may BRICK your device, and you should think twice before using the patch. Using the patch is completely AT YOUR OWN RISK!
Instructions
Download the attached APK, install it on your device, and run it. It will show you a status screen, and if your device is compatible and you have protected bootloaders, the bottom entry "Patch bootloaders" will become available. Tapping it will start the patch procedure.
Note that the patch requires root !
Mini-FAQ
--- After the fix, my "zImage" still shows signed ! Is this a problem ?
No, this is perfectly fine! What matters is that "PBL", "SBL" and "SBL_Backup" are not signed. If "zImage" is signed, it means this ROM can be flashed onto a device that has signed bootloaders. UNsigned "zImage"s can NOT be flashed on signed bootloaders. This is the origin of the problem, because custom kernels are always UNsigned "zImage"s !
--- Can I now flash any ROM and just use this application to fix the bootloaders ?
Technically yes. But it would be stupid to do so. Flashing bootloaders (what this app does) is VERY dangerous, it is the only way to really brick a Tab. If you want to flash a new ROM, make sure it DOES NOT contain bootloaders. Remove them yourself, or wait for somebody else (like Rotohammer) to remove the bootloaders and post the "safe" ROM. Even though this patch is available, if at all possible, you should always try to avoid having to use it.
CDMA tabs
There is currently no support for CDMA Galaxy Tabs, nor do we know if support is needed at this time.
LINKING
You are expressly forbidden to repost the APK elsewhere. If you post about this, post a link to this thread, not to the download (or a repost of the download).
Download
Don't forget to donate and/or press the thanks button!
For non-XDA members who cannot access the attachment, here are multiupload links:
Euro / International / Unbranded / AT&T / Rogers / T-Mo: http://www.multiupload.com/EMOCU1S0V2
Latin (P1000L and P1000N): http://www.multiupload.com/3TJ3YWMWJR
MAKE SURE TO SELECT THE RIGHT DOWNLOAD!

WARNING! Do not flash JM6/9/A/C/D/E/F... Before reading this !
THIS POST, #2 OF THIS THREAD, IS HISTORICAL AND LEFT HERE "FOR THE RECORD". SEE THE FIRST POST FOR WHAT IS CURRENT!
BREAKING NEWS / JAN 15: A fix has been found ! See this post. Also see the bounty thread: http://forum.xda-developers.com/showthread.php?t=906464.
This really applies to other ROMs as well, but the "new" JM6/9/A/C/D/E/F ROMs specifically.
Some of these ROMs include new bootloaders. These bootloaders check checksums/signatures in various parts of the firmwares. The "normal" Samsung ROMs, nor custom ROMs and kernels, have these checksums.
The result is that once flashed, you cannot revert to older/official/custom Samsung ROMs, and you are pretty much stuck using one of these four ROMs, as they are the only ones containing the right checksums.
At least TRIPLE CHECK if you want to flash one of these ROMs, that what you are flashing DOES NOT include the new bootloaders ( boot.bin and sbl.bin ). I know from the CF-Root thread that a fair number of you are already too late, but I thought to warn new users anyways. Some modders (like rotohammer) already usually remove these parts, but still triple check everything to make sure.
There is no known fix. I know, I've tried all of them some people suggested in other threads. None of them really works. Sure, with some effort, you can get a different firmware to somewhat run, but you'll still be using the "checksum" bootloaders and the kernel will not be modified. You will still be running the kernel from the "checksum" firmware you loaded earlier. You will not be able to do full flashes, nor will KIES updates work.
Hopefully somebody will find a real solution for this issue for those already affected. If so, please post it in this thread.
Are you affected ?
NEW DEC 28: See SGTBootloaderCheck script below!
It is hard to say for sure without actually trying to flash a non-JM6/A/C/D kernel without the correct checksum. Here's a screenshot of the error you'll get:
If you still have the original files for the ROM you flashed, but do not want to try flashing a non-Samsung-stock kernel, there are some indicators:
- Rename all .tar.md5 files to .tar
- Extract all the .tar files with WinRAR
- Look at the resulting files:
--- Includes "boot.bin" (primary bootloader)
--- Includes "sbl.bin" (secondary bootloader)
If one or both are present, this indicates new bootloaders are being flashed. That does not make it certain if they are "protected" or not, though. But if a large zImage is also present (see the next item), it is very likely they are.
- Look at the resulting files:
--- "zImage" (kernel)
If zImage is about 7800 kb (as opposed to 4000 - 5500 kb that is normal), it is very likely this kernel includes a checksum. If you want to be 100% sure, open zImage in a hex editor, and go all the way to the end. There will be a few mb of 0's, followed by 128 bytes checksum - the very last 128 bytes in the file.
Such a zImage can be flashed both on "original" and the new "protected" bootloaders. The "protected" bootloaders can only flash these zImage, not the smaller variants.
If you have boot.bin, sbl.bin and a 7800 kb zImage, it is 99% likely flashing this ROM will give you a "protected" bootloader.
Some tech
Once these ROMs are flashed, it is required updates to "boot", "sbl", "zImage" have a 128-byte checksum/signature. In boot.bin and sbl.bin these are near the end, in zImage (7800 kb files) they are the very last 128 bytes. Only firmwares with a zImage that have this signature will be flashable (which at the time of this writing are only JM6/A/C/D).
I have no idea how this signature is generated as of yet, so "faking it" is also not an option. If somebody figures that out, please post it in this thread. Then we could just insert the signatures in the older bootloaders and flash them back (still a dangerous effort by itself).
I think, and possible others will correct me on this, the verification goes as follows, on a running device:
- PBL ( boot.bin ) checks SBL ( sbl.bin ) signature
- SBL checks kernel ( zImage ) signature
While flashing, I think it's the SBL that verifies the PBL/SBL/kernel flash, and refuses to write if the signature isn't correct.
Possible solutions
Flashing back "unprotected" bootloaders from older ROMs through either Odin or Heimdall does not work. These older bootloaders do not have the required signatures/checksums and thus the flash will fail.
A possible solution would be rooting the device, using Koush' bmlunlock, and dd'ing back bml1 and bml4 from backups, complete bypassing the flash checks. This is a very very dangerous to be trying out though, and unless you really know what you are doing, I wouldn't attempt it. Maybe someone has Samsung repair center contacts or a JTAG unit close by ?
Personal note
I have tried to flash back older bootloaders and kernels several times and in several ways (from for example JJ4) but this fails. Odin said it succeeded the very last time I tried, however it really didn't, as my device is now a full (user-wise) brick. It doesn't even turn on to show me the "phone --- | --- pc" error screen. So I guess I need to make a trip to the nearest Samsung repair center (200 miles away). Too bad my car also broke down today Guess it'll be some time (and money) before I have a working Tab again. Note that the brick was a problem with Odin, probably, not directly caused by the protected bootloaders themselves.
Update: Tab is back and working Replaced mobo, so I no longer have the signed bootloaders myself.
NEW DEC. 28: SGTBootloaderCheck
Attached is also SGTBootloaderCheck. This is a script run on your Windows PC through ADB to check your bootloaders. It requires root, SuperUser, and a working ADB connection.
Just unzip the archive to a new folder, and double-click "check.bat". That should dump your bootloaders and kernel, copy them to your computer, check the content for signatures, and let you know the result.
I can't guarantee it works, but it should
Attached
An archive with some relevant files for those who want to do some research. DON'T FLASH THESE FILES !!!
( 467, 909 )

I'm sorry about your Tab man.

After flashing JM6, I have "zImage" and "Sbl.bin" but no "boot.bin" in my internal SD. Am I affected?
Also, is it safe to delete these files from my internal SD? I'm guessing they were put there temporarily and are now stored somewhere else already?

hey chainfire,
i'm sorry about the brick :/
my english seems to be very bad... could u explain me why ur tab is bricked now?
i think i understood why its not possible to flash to another firmware but why ur tab is bricked now? yesterday i flashed to jm6 from an old arabic fw (i think it was JJ1) with pit p1 and code, modem and csc file with re-part. on. so is anything there i have to look out now?

codewisp said:
After flashing JM6, I have "zImage" and "Sbl.bin" but no "boot.bin" in my internal SD. Am I affected?
Also, is it safe to delete these files from my internal SD? I'm guessing they were put there temporarily and are now stored somewhere else already?
Click to expand...
Click to collapse
You could be affected, I can't say for sure. The only way to be sure is trying to flash a custom kernel and see if Odin gives an error. See the CF-Root thread for screenshots of the error that is produced if you are affected. If there's no error and it boots, you have probably not been affected. Note that you can flash back the original JM6 kernel with both the "protected" as well as the "original" bootloaders.
I'll update the first post to add a bit more information.
Also yes, those files on your internal SD are temporary, you can delete them.
DubZyy said:
hey chainfire,
i'm sorry about the brick :/
my english seems to be very bad... could u explain me why ur tab is bricked now?
i think i understood why its not possible to flash to another firmware but why ur tab is bricked now? yesterday i flashed to jm6 from an old arabic fw (i think it was JJ1) with pit p1 and code, modem and csc file with re-part. on. so is anything there i have to look out now?
Click to expand...
Click to collapse
The brick is a result of a bad bootloader flash... it's not something any of you are likely to encounter (unless you are trying to fix this issue).
If you successfully flashed to JJ1 - Odin did not produce any errors - you are probably safe!

Thanks for the information, but a little bit late for me --> bricked
My luck: Next samsung repair center is 5 kilometers away.
But I don't know what i should tell him.
The truth?

@chainfire
Have your tried hexediting the version of the SBL to a "fake" newer version? or does the check only care about the checksum ? on older phone we used to be able to do this....
I'm unpacking my dev. tab as we speak so I hope to have some time to play between x-mas dinners

chinchen said:
Thanks for the information, but a little bit late for me --> bricked
My luck: Next samsung repair center is 5 kilometers away.
But I don't know what i should tell him.
The truth?
Click to expand...
Click to collapse
Damned lucky the repair center is close!
You wouldn't happen to be living near me and I just never heard of this service center, would ya ?
How exactly is it a brick ? It's only a brick if it doesn't turn on at all anymore (like mine). If you can get anything on screen, you can bring it back to life (although maybe with protected bootloaders).
Jesterz said:
@chainfire
Have your tried hexediting the version of the SBL to a "fake" newer version? or does the check only care about the checksum ? on older phone we used to be able to do this....
I'm unpacking my dev. tab as we speak so I hope to have some time to play between x-mas dinners
Click to expand...
Click to collapse
As far as I have been able to deduce (I have not done a full decompile yet, and not sure if I'm going to) it's only the checksum that matters. But I could be wrong there.
I'll upload some files for you in a minute, so you can look at them yourself as well.

chinchen said:
Thanks for the information, but a little bit late for me --> bricked
My luck: Next samsung repair center is 5 kilometers away.
But I don't know what i should tell him.
The truth?
Click to expand...
Click to collapse
Anything besides truth - tell them that you turn off Tab at evevning, and at the morning he doesnt start... they believe
Chainfire - my condolence... i also cannot flash CF-Root on JMC so i think i have new bootloader - im waiting for next steps when yours Galaxy Tab alive
sorry for my english

@Jesterz:
Some files you might want to look at attached to first post.

Is there any way to check what version of bootloader i have installed? I cannot install CF-Root on JMC -its enough to say i upgrade bootloader in my Tab?

faust86 said:
Is tehere any way to check what version of bootloader i have installed? I cannot install CF-Root on JMC -its enough to say i upgrade bootloader in my Tab?
Click to expand...
Click to collapse
If you get the same error as in the screenshot linked to in the first post, yes, you have the protected bootloaders.

good to know i am not effected. and for people who has effected roms i think as we know the reason there will be a quick solution for this.

Chainfire said:
If you get the same error as in the screenshot linked to in the first post, yes, you have the protected bootloaders.
Click to expand...
Click to collapse
So i install this *** bootloader... maybe i brick my Tab and take it to service point... i have 100 meters :>

Me too
Chainfire said:
If you get the same error as in the screenshot linked to in the first post, yes, you have the protected bootloaders.
Click to expand...
Click to collapse
I have the error and I cant change ROM (a part from switching between JM6, JMA and JMC)... Hope someone soon find a fix!
My tab some ago was in a similar state (complete black and didnt show in ODIN).
My luck was that it was stuck in some kind of download mode. Leaving it connected to the computer has made a miracle: after more than 15 minutes it has appeared as connected in ODIN and was possible to flash back a ROM).

patomas said:
I have the error and I cant change ROM (a part from switching between JM6, JMA and JMC)... Hope someone soon find a fix!
My tab some ago was in a similar state (complete black and didnt show in ODIN).
My luck was that it was stuck in some kind of download mode. Leaving it connected to the computer has made a miracle: after more than 15 minutes it has appeared as connected in ODIN and was possible to flash back a ROM).
Click to expand...
Click to collapse
I'll just try that. I have no hope of it working, but hey, it's not like I'm using the Tab for anything else right now

patomas said:
My tab some ago was in a similar state (complete black and didnt show in ODIN).
My luck was that it was stuck in some kind of download mode. Leaving it connected to the computer has made a miracle: after more than 15 minutes it has appeared as connected in ODIN and was possible to flash back a ROM).
Click to expand...
Click to collapse
While the Tab was at a black screen, did you ever press the power button or did you just leave it alone for Odin to eventually find it?

rotohammer said:
While the Tab was at a black screen, did you ever press the power button or did you just leave it alone for Odin to eventually find it?
Click to expand...
Click to collapse
While you're here... any chance of both STL and BML dumps of your (hopefully proper) PBL and SBL ?

Chainfire said:
While you're here... any chance of both STL and BML dumps of your (hopefully proper) PBL and SBL ?
Click to expand...
Click to collapse
Of course. I have dumps of everything. I'm just about to run some diffs to make sure my current bootloaders are ok, I can't remember what Ive flashed

[Q] Xperia Play cannot boot after trying to update

Help my xperia play cannot boot anymore after trying to update to 2.3.4 (from 2.3.2). It is rooted (though I am not sure whether bootloader is unlocked most probably it isn't). When it was updating, I accidentally pressed the power button and it switched off. The next moment, I found myself with a bricked phone that just vibrates when I pressed the power button. I tried flashing the rom in already but the situation still persists. Can anyone help?

sonyxperiaplayer said:
Help my xperia play cannot boot anymore after trying to update to 2.3.4 (from 2.3.2). It is rooted (though I am not sure whether bootloader is unlocked most probably it isn't). When it was updating, I accidentally pressed the power button and it switched off. The next moment, I found myself with a bricked phone that just vibrates when I pressed the power button. I tried flashing the rom in already but the situation still persists. Can anyone help?
Click to expand...
Click to collapse
Well, you don't mention which model of the Play you have. If you aren't sure, you can remove the battery and look on the sticker. It will say something like "R800x" or "R800i", etc.
Once you know what this is, you can reflash the original firmware. This will put the phone back to the original, unrooted stock version, just like it just came out of the box. Most of the firmwares needed are found in this post right here. The firmware file is usually archived either with rar or zip, so you will need to unarchive it. You will also need to download and install Flashtool which can be found here. In the event you can't access the file from there, a mirror link is found here.
Once you have the necessary files, it's pretty easy to do. There are complete instructions on the Flashtool site, but basically you just copy the ftf file into the firmwares folder within the Flashtool folder. Then launch Flashtool and follow the on screen instructions.
Post back with results or questions. And please hit the Thanks button if I helped you.

Nothing
It is still the same.

My Play is r800i by the way
My Play is r800i by the way

Special ftf file?
I heard that I must use a special ftf file to unbrick my phone. Any ideas? Thanks

I think its from here: http://forum.xda-developers.com/showthread.php?t=1126354

But then the links are not working (I think)

from my noob knowledge if you ota with bootloader unlocked then you will brick the device but in your 1st post you said you aint sure if its locked or unlocked. then in your second last post you tried to download the FOTAunbrick.exe file but you said the download link is unavailable. download FOTAunbrick.exe and run it (the link isn't dead just downloaded it myself for safe keeping) or xperia_relock_bootloader.ftf(2nd option) i have below. you got nothing to lose.
ps
next time you wanna upgrade just use wontan server(not free) or download an ftf. and flash it via flashtool here with the same instructions dude in the second post has given regarding flashtool steps

sonyxperiaplayer said:
I heard that I must use a special ftf file to unbrick my phone. Any ideas? Thanks
Click to expand...
Click to collapse
The link there is dead in some countries, like the US, as it is MultiUpload. @Solomon4400 - I suggest posting that file up to another site that sonyxperiaplayer can access to download it.
@ sonyxperiaplayer - you actually downloaded the ftf and the flashtool program I linked you to? Because normally that ought to do it.

I agree with netizenmt on this one.
the special ftf files you are seeking is the stock rom firmware he already managed.
As you got r800i, you have to flash the international stock firmware (I guess but I am not sure!) you could also just flash stock rom 2.3.4 - So you can upgrage while saving your phone - instead of re-applieing 2.3.2
Just get flashtool and firmware (ftf file) connect phone to pc, put ftf file in flashtool, follow instructions. Good to go

If you need any firmware files, check my signature. The links in that post actually work.
Sent from a Galaxy far, far away

captain67 said:
If you need any firmware files, check my signature. The links in that post actually work.
Sent from a Galaxy far, far away
Click to expand...
Click to collapse
Does that mean the ones in your thread that I linked him to do not?
Sent from my R800x using xda premium

Unbricked it!
Thank all if you guys so much! The phone finally turned on after i used bootloader relock!

netizenmt said:
Does that mean the ones in your thread that I linked him to do not?
Sent from my R800x using xda premium
Click to expand...
Click to collapse
No I was referring to the multiupload links that he mentioned. Didn't see your post up there.
Sent from my Overcome Galaxy Tab 10.1

Any please HELP!! Stock S6 edge firmware.

Does anyone have a stock firmware of their S6 Edge T-Moible? that's ODIN flashable. I bricked my S6 trying to root it and had the KNOX security on. Now it just boot loop. :crying:

Protomize said:
Does anyone have a stock firmware of their S6 Edge T-Moible? that's ODIN flashable. I bricked my S6 trying to root it and had the KNOX security on. Now it just boot loop. :crying:
Click to expand...
Click to collapse
hey you're not alone! a lot of people are in your situation right now including me. we have to wait until there is a firmware available on Sammobile. hang tight.

samanbabah said:
hey you're not alone! a lot of people are in your situation right now including me. we have to wait until there is a firmware available on Sammobile. hang tight.
Click to expand...
Click to collapse
I managed to find a solution. Go here: http://forum.xda-developers.com/tmo...ow-to-brick-s6-s6-edge-knox-security-t3075720

Protomize said:
I managed to find a solution. Go here: http://forum.xda-developers.com/tmo...ow-to-brick-s6-s6-edge-knox-security-t3075720
Click to expand...
Click to collapse
That doesn't fix issues for those of us that need to have the full stock firmware to re-Odin with. Guess those of us in the same boat wait a week or so. My problem was removing the knox files with root explorer. Bad move. Makes the phone unbootable. Called Samsung tech support and they confirmed that. Rooting no problem. Recovery screen totally blank. Never get to see the the white/green screen some say they have for a recovery screen. The magic use volume up keys 7 times etc I have seen posted don't work for me. Samsung specifically told me the stock firmware is proprietary, so they wouldn't give it to me. I can wait a week or so for developers to get their hands on appropriate files, including a custom recovery that actually works...like good old TWRP :victory:

Protomize said:
Does anyone have a stock firmware of their S6 Edge T-Moible? that's ODIN flashable. I bricked my S6 trying to root it and had the KNOX security on. Now it just boot loop. :crying:
Click to expand...
Click to collapse
have you tried to flash the S6 file? not the S6 edge but the S6. Try to get yourself in download mode and do that. Make sure you are using the correct odin. That is what happened to me and I was able to obtain ROOT.

If you can get into download mode, you can now use Kies to install the stock firmware. Just did it about 3 mins ago.

SuperSport said:
If you can get into download mode, you can now use Kies to install the stock firmware. Just did it about 3 mins ago.
Click to expand...
Click to collapse
Where did you get the stock firmware. I'm not talking rooting file. I'm talking the full on tar to use to ODIN and flash the complete full stock firmware.

Docmjldds said:
Where did you get the stock firmware. I'm not talking rooting file. I'm talking the full on tar to use to ODIN and flash the complete full stock firmware.
Click to expand...
Click to collapse
I used Kies to restore the Firmware. Unfortunately, I was unable to find the Firmware file on my computer (Or could not figure out how to use it). I did see a temp file that was the correct size, but it's name and extension were wrong. I tried to open the file using 7-Zip and WinRar, but neither would open it. At that point, I just allowed Kies to do it's job, and it worked well. Removed ROOT and am now running Stock Firmware and Stock Recovery. KNOX is still tripped, but I don't care at this point.
In Kies, use the option: "Firmware Upgrade and Initialization". You will need your Model Name and Serial Number. Found on the box or in Settings if you can get there. I've got a T-Mobile Edge, so my Model Name is SM-G925T. Your serial will be unique.

SuperSport said:
I used Kies to restore the Firmware. Unfortunately, I was unable to find the Firmware file on my computer (Or could not figure out how to use it). I did see a temp file that was the correct size, but it's name and extension were wrong. I tried to open the file using 7-Zip and WinRar, but neither would open it. At that point, I just allowed Kies to do it's job, and it worked well. Removed ROOT and am now running Stock Firmware and Stock Recovery. KNOX is still tripped, but I don't care at this point.
In Kies, use the option: "Firmware Upgrade and Initialization". You will need your Model Name and Serial Number. Found on the box or in Settings if you can get there. I've got a T-Mobile Edge, so my Model Name is SM-G925T. Your serial will be unique.
Click to expand...
Click to collapse
I deleted via root explorer a slew of knox fies. Samsung told me by doing this, it renders the phone non bootable. That is why I need a full stock firmware tar file I can use in Odin, to flash the original complete firmware for my 925 Edge.Removing root, re-rooting, will not help. Chainfire said that SamMobile rleased the firmware files but all I get is web page not available. Grrrrr. Really wish someone would post the file in the Development sections or at least provide a working link.

Docmjldds said:
I deleted via root explorer a slew of knox fies. Samsung told me by doing this, it renders the phone non bootable. That is why I need a full stock firmware tar file I can use in Odin, to flash the original complete firmware for my 925 Edge.Removing root, re-rooting, will not help. Chainfire said that SamMobile rleased the firmware files but all I get is web page not available. Grrrrr. Really wish someone would post the file in the Development sections or at least provide a working link.
Click to expand...
Click to collapse
I had also removed all of the KNOX files, and most of the Samsung Files trying to get close to AOSP, but it became unstable. Kies re-installed the COMPLETE firmware again and all the stock files returned. I don't mean it removed ROOT only, it flashed the complete firmware. Kies uses ODIN internally to do the flash.

SuperSport said:
I had also removed all of the KNOX files, and most of the Samsung Files trying to get close to AOSP, but it became unstable. Kies re-installed the COMPLETE firmware again and all the stock files returned. I don't mean it removed ROOT only, it flashed the complete firmware. Kies uses ODIN internally to do the flash.
Click to expand...
Click to collapse
it's weird I can't use Kies at all.

samanbabah said:
it's weird I can't use Kies at all.
Click to expand...
Click to collapse
I can't use Kies either. Says phone not supported. I get the same exact error message. Oh my life savings for a nice .tar file to odin with

Wait
I think you should wait until pushed ODIN firmware over web...

dreamytricks said:
I think you should wait until pushed ODIN firmware over web...
Click to expand...
Click to collapse
Well, someone (Pagel) already posted the 920 stock tar file in the S6 thread. so there MUST be a source currently. Wish I knew why Sammobile web site returns errors for me about unable to open web page. That's the source most state is where to go.

Docmjldds said:
I can't use Kies either. Says phone not supported. I get the same exact error message. Oh my life savings for a nice .tar file to odin with
Click to expand...
Click to collapse
Okay I was able to find a workaround on how to restore my phone through Kies without getting an error.
do the following: 1) open Kies, click on tools, Firmware upgrade and initialisation, enter your model number and serial number and let it download the firmware, after an hour or so depending on your connection speed the firmware will be downloaded and your phone will reboot into recovery to install the firmware. done

samanbabah said:
Okay I was able to find a workaround on how to restore my phone through Kies without getting an error.
do the following: 1) open Kies, click on tools, Firmware upgrade and initialisation, enter your model number and serial number and let it download the firmware, after an hour or so depending on your connection speed the firmware will be downloaded and your phone will reboot into recovery to install the firmware. done
Click to expand...
Click to collapse
That's exactly what I was saying to do a few posts back. Did it yesterday and it worked fine.
EDIT: I'm going to run through it again and see if I can find the downloaded file. I believe I found it last time, but it was not a TAR file, rather a temp file specific to MY phone. But I'll try again, and if I get it, will post it here.

SuperSport said:
That's exactly what I was saying to do a few posts back. Did it yesterday and it worked fine.
EDIT: I'm going to run through it again and see if I can find the downloaded file. I believe I found it last time, but it was not a TAR file, rather a temp file specific to MY phone. But I'll try again, and if I get it, will post it here.
Click to expand...
Click to collapse
oh OK I didn't see your previews post.

samanbabah said:
oh OK I didn't see your previews post.
Click to expand...
Click to collapse
No problem, as long as we all get there at some point. The temp file that Kies downloads is called tmpE635.tmp It ends up being about 1.6GB in size. I tried to open it using 7-Zip and WinRar, but neither will open it. I'll post it in case anyone wants to try using it in ODIN. I don't know if it is specific to MY phone, or the T-Mobile S6 Edge in general (SM-G295T).
But, honestly, I would suggest you use Kies yourself so you are positive to get the correct file. You WILL get the error message that says Kies does not support your phone, just ignore that and keep going.

Phone Serial Number
I just realized that the Serial Number Kies is asking for is not on my Box. It's in the settings/about/status menu, and also on a sticker that is stuck to the Plastic Wrap that was around the phone in the box. Looks sort of like this: R58G31D1PBA. So, if you cannot get into your settings, or don't have that plastic, I'm not positive how you will get it to start the download. Maybe if you just use someone elses serial number, that will start the download???
EDIT: Link to the Temp File from Kies (not sure you'll be able to do anything with it)
https://mega.co.nz/#!39gwRAKS!H81yfo1vCQkMOujTaQJaU2INXoPNtUF6cgnF46jAfXI

WTF
Had the download stall on me twice, 35 and 47 percent.

SM-T325 PIT

Hi,
Does anyone have one or know how to get it?
Odin is not able to download one.
Thanks,
Maced

maced said:
... Does anyone have one or know how to get it?
Odin is not able to download one......
Click to expand...
Click to collapse
Odin was not made for downloading anything.
Afaik it's integrated in the CSC.... file.
I've extracted it once and you're free to use it of course no warranty or anything.
Btw. what happened that you have to repartition it?

Thanks, actually I am not sure I have to.
To be totally honest - its first time I am trying to install a new OS on this device - it has original version now.
Was just following instructions online - I am not 100% aware about ins and outs. Also it seems JOdin does not allow install without PIT.
It says that the your PIT is corrupted.
Thanks!

maced said:
Thanks, actually I am not sure I have to.
To be totally honest - its first time I am trying to install a new OS on this device - it has original version now.
Was just following instructions online - I am not 100% aware about ins and outs. Also it seems JOdin does not allow install without PIT.
It says that the your PIT is corrupted.
Thanks!
Click to expand...
Click to collapse
Usually you uncheck repartition.
pit may afaik only be needed when device has lost it.
Odin works without.
You only flash TWRP with it and after that you don't need it anymore until you wanna turn back to stock.
Mine is from dbt stock firmware perhaps that's why.
Silly question but you've unpacked it?

@maced now that I'm home I've checked.
Extracted it from this stock file I've got via samfirm_reborn0.3.6.2: "CSC_OXA_T325OXA1BQB3_CL10765915_QB12683141_REV00_user_low_ship_MULTI_CERT.tar" what you can do yourself from the file suitable for your device.