Related
I'm sorry about this new thread, but I couldn't manage to find the right answer for me.
I flashed to JPC and my product code has changed. I don't have any problems with network/sim lock, but I wonder If I can revert to my original product code.
My SGS is rooted and I have this program Root Explorer, but when I get into the EFS folder there is nothing, no files at all. Can somedoby please tell me where's the problem? By the way this code *#272..... doesn't work also
How can i see changed product code?,i am using JPC too.
posted about this this morning!
Don't know if this will help you... but I posted this this morning on another thread:
http://forum.xda-developers.com/showthread.php?p=7997364#post7997364
Thanks, but my EFS folder is empty
This is not a problem as long as I can install another new firmware without any problems. And I think that Samsung MUST create an option to select your region and this fix your product code. And I'm sure that they already know about their fault with this stupid KOR :|
celeronix said:
Thanks, but my EFS folder is empty
This is not a problem as long as I can install another new firmware without any problems. And I think that Samsung MUST create an option to select your region and this fix your product code. And I'm sure that they already know about their fault with this stupid KOR :|
Click to expand...
Click to collapse
If root explorer isnt working for you, try EStrongs File Explorer (enable Root option in settings), its free so no need to buy anything. I dont have root explorer so cant help you with that.
Thanks, this Estrongs Explorer works. I have managed to find my .nv_data.bak files and they are dated 07/02/10
The question now is how can I fix my product code without reflashing my firmware to another version. This JPC is good for me at this point
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
Before flashing a custom rom on my new tab I decided to make a Roto Backup for myself and to share for anyone else with a Telstra tab who might need to go back to stock.
Please note this is not an official rom, for more information please see Roto's thread
http://forum.xda-developers.com/showthread.php?t=850359
I followed his instructions exactly, including generating the tar for flashing with Odin which is what I'm posting here.
I have a Desire but doing this sort of thing with Samsung devices is new to me, however I have successfully flashed this on my Tab with Odin, once saving me after trying to flash a bad download of the MCR kernel.
I factory reset beforehand so it's clean except for superuser & root Z4Root worked straight up on this so I imagine it should unroot just as easy.
If you have converted your filesystem then you will need to re-partition with Odin, I don't think this rom will work with ext4. I originally attached my backup pit but it doesn't seem to work, I've attached the pit from Roto-JME-Full-v4.
http://www.multiupload.com/KQF09AELMR
Tar MD5SUM - A75722008429EF469568E96F6F81F40A
Telstra modem.bin
http://www.multiupload.com/T04FXM8R5B
Bin MD5SUM - D1857CF262EFB929F73533C79D6B71AC
All thanks to rotohammer!
Thank you very much for your sharing!!!!
I'm using Galaxy Tab P-1000T Telstra, too.
Thank you - tucked away safely
thank you kind sir!
Many thanks for this - have used it several times now as I was too lazy to make an initial backup. Works just fine, and prerooted too!
Sent from my GT-P1000T using XDA Premium App
legand
I am on telstra also.
first of all, thank you.
my question here is how do i restore the stock firmware? i have a desire and restoring it to stock is just running the RUU provided but with GT, i'm clueless.
I was able to restore this with Odin happily. Just use it with the 'PDA' option.
BeauGiles said:
I was able to restore this with Odin happily. Just use it with the 'PDA' option.
Click to expand...
Click to collapse
Hi BeauGiles, will you be able to provide some simple instructions? what version of odin you are using? i found 2 version on the xda (odin3_1.70 and 1.31)
thank you.
I suggest having a look at the installation guide for the Overcome ROM, specifically the "Re-stocking" section as it has photos and things for Odin which makes it pretty clear. It's attached to the first post here
http://forum.xda-developers.com/showthread.php?t=932082
The process is basically the same, use the pit file and re-partition and select the telstra rom under PDA, you won't need to add the modem separately as it's already inside the telstra rom tar.
If any apps or settings carry over just do a factory reset.
Sarsippius said:
The process is basically the same, use the pit file and re-partition and select the telstra rom under PDA, you won't need to add the modem separately as it's already inside the telstra rom tar.
Click to expand...
Click to collapse
thank you.
Hi Sarsippius,
Thank you for the TELSTRA ROM.
I have a problem here, everytime i press the power button, my tab reboots, and also when the tab autolock. It also doesn't load the recovery mode when i press the power + up button(and then release the power button). Does anyone here having the same problem? Please share the solution.
Thank you again!
You hold the volume up button until the samsung logo appears, I personally hold it in until the recovery mode appears. Up to you...
Sarsippius said:
it's clean except for superuser & root
Click to expand...
Click to collapse
So how did you root it and how do I unroot it?
Only asking cause I suspect that not removing z4root is what baffed my official gingerbread update.
z4root is an app you can use to root certain Samsung devices, it worked on early Tab firmwares like those on the Telstra tab, it doesn't work on more recent firmwares but I haven't really looked at it lately.
Anyway, you open the app, hit the root button and it roots the tablet, it will also unroot although I never tested this. Give that a go otherwise do a search as there are instructions on this forum to manually unroot.
All good and sorry for the dumb question. was tired and late when I posted .
I assumed having z4root still kicking around when I let the official GB upgrade install was what was stopping me root using Doomlords method
Turns out samsungs use/abuse of the system directory was the issue and using the instructions later in the post Post 208sorted things out.
FYI: If anyone uses the above the code sample goes into the bat file after...
"@echo --- remounting /system
@files\adb shell "/data/local/tmp/busybox mount -o remount,rw /system"
do you think this would work on an australian optus tablet providing I change the modem to suit..?
I don't know of any reason why it wouldn't work but I'm not sure why you would want to do that.
ahh because i want the "stock" ROM so I can sell it.
I forgot to take a backup before I put Overcome then CM7 on it
senectus said:
do you think this would work on an australian optus tablet providing I change the modem to suit..?
Click to expand...
Click to collapse
Remembering that you'll have the stock Telstra bloat.. Er, apps on there such as Foxtel, BigPond, etc.
---
I am here: http://maps.google.com/maps?ll=-33.897667,151.175675
Hi guys, i seriously need help here. Please refer to attached screenshot.
I came here after flashing sokp 4.2.2 rom, and it prompted me an error saying encryption was unsuccessful. After which, i wasnt able to use my phone since then.
I tried to flash stock rom, and I end up with this. Please dont tell me to search the forums because Ive been to them countless times. I suppose this is a efs issue, because baseband and imei are unknown and I do not have a backup for it. Tried with the writing tool for imei, doesnt work as well.
Pls ask me for any info u might need/i missed out to help with this issue.
I think it's in the efs folder, you have to use a root browser and edit factory mode to off instead of on. It's been a long time since I saw factory mode so I'm not 100%
Sent from my GT-N7105 using Tapatalk
sawdoctor said:
I think it's in the efs folder, you have to use a root browser and edit factory mode to off instead of on. It's been a long time since I saw factory mode so I'm not 100%
Sent from my GT-N7105 using Tapatalk
Click to expand...
Click to collapse
Thanks for your reply. But even if I off factory mode, will the baseband and imei be unknown?
I'm not sure but if it doesn't the 2 things that might be worth trying are, emergency firmware recovery with kies or mskips toolkit has a rescue package but I think you have to go to skipsoft.net now as the thread was closed
Sent from my GT-N7105 using Tapatalk
It's current value is "OFF"...u have to write "ON"...i know it sounds weird but that is the value. Amd if u don't have any previous back up of EFS then there's nothing u can do at home to bring it back. Same thing happened to mine and i got it repaired from a local shop for cheap...they used z3x box...the problem is my IMEI is correct and network works fine...but everytime i flash a ROM i have to take it to the shop and get the modem patched or else it doesn't connect to network. So go to Samsung service centre and get it fixed by them...they'll charge u more but their fix is permanent.
Sent from my GT-N7100 using XDA Free mobile app
Alright, it seems like i have a backup of the efs, bt the nv_data.bin file is not included, and i read on other threads that this file is responsible for the imei and all? This backup is dated in aug2013, but it doesnt help in restoring my phone because the efs pro software doesnt see this as a backup file. Im actually looking for one of the thread that actually taught how to edit the nv_data.bin file, but no luck till date.
This thread might help
http://forum.xda-developers.com/showthread.php?t=1946915
[WARNING! + GUIDE] Backup and Restore IMEI / NV Data Procedure for GT-I9305. There is another post in this thread where they flashed the param.bin file
Check out the last post in this thread
http://forum.xda-developers.com/showthread.php?t=2724169
[Q]Null Imei, Baseband Unknown N7105
Sent from my GT-N7105 using Tapatalk
is it safe to flash the file that is intended for i9300? i dare not do that in case it doesnt work coz is different models.
ok my phone's all fixed up now. If anyone is interested to know, samsung kies original firmware helped.
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.