CAUTION! Do not attempt to apply this package to a GS4 running any other firmware version than MF3. Doing so causes a brick that cannot be recovered from yet.
This is a resurrection package for Odin3 which is meant to restore an AT&T SGH-I337 to a working state after installing the OTA for I337UCUAMF3 and reinitializing/downgrading with Kies afterward. This causes the "PC--> triangle---> Phone" download mode boot loop. This condition cannot be recovered using Kies at the time of this posting.
This is shared "AS-IS" for those of us who just want a phone that works again and in no way makes me or anyone else responsible for what could happen when using Odin. It's a risky business.
1 - Go here to download and install 7zip: http://www.7-zip.org/
2 - Make sure that you have the latest samsung drivers installed for the SGH-I337 for AT&T
3 - Download "Odin307.zip" and "MF3_BTL_FIX.7z" attached to this post and unzip them
4 - In the "Odin307" folder that you just unzipped, open "Odin3.ini" in Notepad
5 - Change ONLY the value for "PhoneBootUpdate" from "0k" to a "1" making it "PhoneBootUpdate=1", save and close.
6 - Run "Odin3 v3.07.exe" and place "MF3_BTL_FIX.tar.md5" in the "PDA" slot.
You should see this in the white box at the lower left corner:
Enter CS for MD5..
Check MD5.. Do not unplug the cable..
Please wait..
MF3_BTL_FIX.tar.md5 is valid.
Checking MD5 finished Sucessfully..
Leave CS..
If it fails the MD5 check, DO NOT continue. Delete the ".md5" file and the 7z archive, download the fix again, unzip, and restart from step 6.
7 - Use the three button combo (VOL-, HOME, and PWR buttons, then VOL+ at the first screen) to get into download mode.
8 - Place your phone (and laptop if your using one for this) on a table so that you won't be compelled to move anything during the next step.
9 - Plug in the USB cable to your computer and GS4. You should see a Com port display in the top portion of the Odin3 window. You might have to wait a few seconds for automated driver install before seeing the Com port come up.
10 - Click "Start" and calmly tip toe away from the keyboard. This process should take 20 seconds or so, then the phone will reboot into the Samsung swirly boot animation.
This process was done on a laptop with Win 7 64bit using the Samsung drivers installed along with the latest version of Kies.
The boot loader files come from the posted CFG file in this thread: http://forum.xda-developers.com/showthread.php?t=2357039
The boot loaders were packed and hashed with a script program called "TAR.MD5_PACKAGER".
This package includes the following boot loaders from the OTA:
aboot.mbn
rpm.mbn
sbl2.mbn
sbl3.mbn
tz.mbn
The Odin zip is from AdamOutlers Odin stock thread.
Update: No package changes whatsoever, just an update on recent findings. Apparently, this package also works in the case that TWRP recovery is accidentally flashed too. I have no idea why. See here: http://forum.xda-developers.com/showthread.php?p=46075550
OMG!!!
ou812bkewl said:
This is a resurrection package for Odin3 which is meant to restore an AT&T SGH-I337 to a working state after installing the OTA for I337UCUAMF3 and reinitializing/downgrading with Kies afterward. This causes the "PC--> triangle---> Phone" download mode boot loop. This condition cannot be recovered using Kies at the time of this posting.
This is shared "AS-IS" for those of us who just want a phone that works again and in no way makes me or anyone else responsible for what could happen when using Odin. It's a risky business.
1 - Go here to download and install 7zip: http://www.7-zip.org/
2 - Make sure that you have the latest samsung drivers installed for the SGH-I337 for AT&T
3 - Download "Odin307.zip" and "MF3_BTL_FIX.7z" attached to this post and unzip them
4 - In the "Odin307" folder that you just unzipped, open "Odin3.ini" in Notepad
5 - Change ONLY the value for "PhoneBootUpdate" from "0k" to a "1" making it "PhoneBootUpdate=1", save and close.
6 - Run "Odin3 v3.07.exe" and place "MF3_BTL_FIX.tar.md5" in the "PDA" slot.
You should see this in the white box at the lower left corner:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> MF3_BTL_FIX.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
If it fails the MD5 check, DO NOT continue. Delete the ".md5" file and the 7z archive, download the fix again, unzip, and restart from step 6.
7 - Use the three button combo (VOL-, HOME, and PWR buttons, then VOL+ at the first screen) to get into download mode.
8 - Place your phone (and laptop if your using one for this) on a table so that you won't be compelled to move anything during the next step.
9 - Plug in the USB cable to your computer and GS4. You should see a Com port display in the top portion of the Odin3 window. You might have to wait a few seconds for automated driver install before seeing the Com port come up.
10 - Click "Start" and calmly tip toe away from the keyboard. This process should take 20 seconds or so, then the phone will reboot into the Samsung swirly boot animation.
This process was done on a laptop with Win 7 64bit using the Samsung drivers installed along with the latest version of Kies.
The boot loader files come from the posted CFG file in this thread: http://forum.xda-developers.com/showthread.php?t=2357039
The boot loaders were packed and hashed with a script program called "TAR.MD5_PACKAGER".
This package includes the following boot loaders from the OTA:
aboot.mbn
rpm.mbn
sbl2.mbn
sbl3.mbn
tz.mbn
The Odin zip is from AdamOutlers Odin stock thread.
Click to expand...
Click to collapse
YOU'RE A F*CKING GENIUS!!!!!!! How did you figure it out?
circasurvives said:
YOU'RE A F*CKING GENIUS!!!!!!! How did you figure it out?
Click to expand...
Click to collapse
Takes one to know one!
In my research into this, I found this post: http://forum.xda-developers.com/showthread.php?p=43485829 which pointed me I'm the direction of this Qfuse boot loader security feature. As long as this "Qfuse" value is greater than or equal to the boot loader currently on the device, the boot loader won't lock down and cause a halt during the boot loader part of the flashing. If you tried to downgrade with Odin 3.07, it doesn't flash boot loaders unless the ini file is edited.
So, when the boot loader halts with an Odin flash nothing has yet been partially flashed, hence three isn't an emergency download mode screen.
In Kies, however, it seems that the flashing process begins before this Qfuse check is done, causing what remains of the boot loader to detect that a partial flash has occurred. But it can't be corrected because the Qfuse security feature isn't ever disabled, and Kies's firmware serves haven't been brought up to match the current OTA version.
The process here is the only way to recover from this specific situation. It's only the boot loaders that are messed up.
ou812bkewl said:
Takes one to know one!
In my research into this, I found this post: http://forum.xda-developers.com/showthread.php?p=43485829 which pointed me I'm the direction of this Qfuse boot loader security feature. As long as this "Qfuse" value is greater than or equal to the boot loader currently on the device, the boot loader won't lock down and cause a halt during the boot loader part of the flashing. If you tried to downgrade with Odin 3.07, it doesn't flash boot loaders unless the ini file is edited.
So, when the boot loader halts with an Odin flash nothing has yet been partially flashed, hence three isn't an emergency download mode screen.
In Kies, however, it seems that the flashing process begins before this Qfuse check is done, causing what remains of the boot loader to detect that a partial flash has occurred. But it can't be corrected because the Qfuse security feature isn't ever disabled, and Kies's firmware serves haven't been brought up to match the current OTA version.
The process here is the only way to recover from this specific situation. It's only the boot loaders that are messed up.
Click to expand...
Click to collapse
Do you think the same procedure can be done to the stock AMDL firmware TAR to change it so ODIN will then load AMDL back onto phones that currently have MF3 without failing? I am not on MF3 and don't plan to any time soon so I can not test it.
If it works, people that took the MF3 update, or those who will soon be getting phones with it preinstalled can do this edit to the AMDL firmware TAR and then ODIN AMDL back to their phones to apply root and LOKI.
i equate MF3 to AIDS.
scott14719 said:
Do you think the same procedure can be done to the stock AMDL firmware TAR to change it so ODIN will then load AMDL back onto phones that currently have MF3 without failing? I am not on MF3 and don't plan to any time soon so I can not test it.
If it works, people that took the MF3 update, or those who will soon be getting phones with it preinstalled can do this edit to the AMDL firmware TAR and then ODIN AMDL back to their phones to apply root and LOKI.
Click to expand...
Click to collapse
You'd have to pull what pieces of each tar.md5 file you want out, then add all the pieces back together to a tar and re-hash it to an md5. That would be the simple part, thanks to the tool I used to make the tar.md5 I'm the OP.
The $500 question that remains is once you flash all this, would it boot? If it didn't, would you even be able to get to download mode again? If just flashing a previous boot loader through official channels caused the headaches I've had this week, I would expect that anything Frankenstein'd from different ROMs probably wouldn't boot. I would try it out if I had a JTAG box or another phone to take this one's place, but I don't.
ou812bkewl said:
You'd have to pull what pieces of each tar.md5 file you want out, then add all the pieces back together to a tar and re-hash it to an md5. That would be the simple part, thanks to the tool I used to make the tar.md5 I'm the OP.
The $500 question that remains is once you flash all this, would it boot? If it didn't, would you even be able to get to download mode again? If just flashing a previous boot loader through official channels caused the headaches I've had this week, I would expect that anything Frankenstein'd from different ROMs probably wouldn't boot. I would try it out if I had a JTAG box or another phone to take this one's place, but I don't.
Click to expand...
Click to collapse
I'm hoping someone with a JTAG box will try this. Of course, I am just speculating, but I am wondering if the reason (and maybe only reason) that ODIN will not flash the AMDL firmware to a phone with the MF3 firmware is because the checks (the part of the file you modified in the MF3) didn't match the parameters of the MF3 restrictions. In other words, modifying the same part of the AMDL TAR as you modified in the MF3 file might trick ODIN into thinking the AMDL firmware meets the requirements that the MF3 OTA met.
But yea, it could be risky because if their are additional checks with the bootloader itself it will most certainly fail the chain of trust. But the question becomes is the chain of trust in the boot loader what is causing ODIN to fail in the first place.
And then, if AMDL can be successfully reflashed to the phone will the blown Qfuse allow it to function or will the overwriting of the MF3 aboot back to the AMDL aboot not be effected by the Qfuse? I would speculate the Qfuse will still prevent proper function, but I really can't be certain.
So........WOW!
scott14719 said:
I'm hoping someone with a JTAG box will try this. Of course, I am just speculating, but I am wondering if the reason (and maybe only reason) that ODIN will not flash the AMDL firmware to a phone with the MF3 firmware is because the checks (the part of the file you modified in the MF3) didn't match the parameters of the MF3 restrictions. In other words, modifying the same part of the AMDL TAR as you modified in the MF3 file might trick ODIN into thinking the AMDL firmware meets the requirements that the MF3 OTA met.
But yea, it could be risky because if their are additional checks with the bootloader itself it will most certainly fail the chain of trust. But the question becomes is the chain of trust in the boot loader what is causing ODIN to fail in the first place.
And then, if AMDL can be successfully reflashed to the phone will the blown Qfuse allow it to function or will the overwriting of the MF3 aboot back to the AMDL aboot not be effected by the Qfuse? I would speculate the Qfuse will still prevent proper function, but I really can't be certain.
So........WOW!
Click to expand...
Click to collapse
I'm basically going to be forced to test this out next week. My sbl2 and sbl3 are at MF3, whereas everything else is MDL. I'm thinking that the files needed to restore the bootloader via JTAG are likely based on MDL (or MDB), so we shall see if my device will boot with these new bootloaders, whatever version they are.
Aou said:
I'm basically going to be forced to test this out next week. My sbl2 and sbl3 are at MF3, whereas everything else is MDL. I'm thinking that the files needed to restore the bootloader via JTAG are likely based on MDL (or MDB), so we shall see if my device will boot with these new bootloaders, whatever version they are.
Click to expand...
Click to collapse
The only files flashed with this are listed at the bottom of the OP and are all extracted from the MF3 update cfg file posted in the Updare thread. Of course, there are more files that are left untouched, so it really depends on what boot loaders you had to begin with before MF3. Good luck with the flash and I hope all goes well. It was actually one of your posts from the last couple days that got me thinking about how to put this together.
ou812bkewl said:
This is a resurrection package for Odin3 which is meant to restore an AT&T SGH-I337 to a working state after installing the OTA for I337UCUAMF3 and reinitializing/downgrading with Kies afterward. This causes the "PC--> triangle---> Phone" download mode boot loop. This condition cannot be recovered using Kies at the time of this posting.
This is shared "AS-IS" for those of us who just want a phone that works again and in no way makes me or anyone else responsible for what could happen when using Odin. It's a risky business.
Click to expand...
Click to collapse
THANK YOU!
ou812bkewl
DUDE .. YOU ARE A GOD .. THANK YOU. This fixed my phone :victory:
LordGeek said:
ou812bkewl
DUDE .. YOU ARE A GOD .. THANK YOU. This fixed my phone :victory:
Click to expand...
Click to collapse
I'm glad this helped.
ou812bkewl said:
....
1 - Go here to download and install 7zip: http://www.7-zip.org/
2 - Make sure that you have the latest samsung drivers installed for the SGH-I337 for AT&T
3 - Download "Odin307.zip" and "MF3_BTL_FIX.7z" attached to this post and unzip them
....
Click to expand...
Click to collapse
If you switch from 7z to GZ format, you can skip some of these steps. Odin supports the Gzip standard. instead of tar.md5.7z, just make a tar.md5.gz
Code:
zip MF3_BTL_FIX.tar.md5 -c -v > MF3_BTL_FIX.tar.md5.gz;
You can find more in this guide: http://forum.xda-developers.com/showthread.php?t=2082951
verizon version?
AdamOutler said:
If you switch from 7z to GZ format, you can skip some of these steps. Odin supports the Gzip standard. instead of tar.md5.7z, just make a tar.md5.gz
Code:
zip MF3_BTL_FIX.tar.md5 -c -v > MF3_BTL_FIX.tar.md5.gz;
You can find more in this guide: http://forum.xda-developers.com/showthread.php?t=2082951
Click to expand...
Click to collapse
anybody working on a Verizon version of this?
Thank you so much for this, I was worried that I was gonna have to send it in for warranty. Saved me tons of time, money, and hassle.:good:
THANK YOU!!!!
Thank you soo much!!!
thank youuu!
now is there any way to odin back to stock because my phone and messaging keeps force closing so my phone is just like a tablet now but freezes every 2 seconds from the popup lol
lilmikey201 said:
thank youuu!
now is there any way to odin back to stock because my phone and messaging keeps force closing so my phone is just like a tablet now but freezes every 2 seconds from the popup lol
Click to expand...
Click to collapse
Currently, there is no method found to Odin back to stock because Kies hasn't yet been updated to provide the full MF3 update. We just have the OTA. A hard reset should solve your force close problems.
Slade8525 said:
i equate MF3 to AIDS.
Click to expand...
Click to collapse
LMAO!!! :good:
ou812bkewl said:
Currently, there is no method found to Odin back to stock because Kies hasn't yet been updated to provide the full MF3 update. We just have the OTA. A hard reset should solve your force close problems.
Click to expand...
Click to collapse
oh ok i guess ill try that
UPDATE
nope that didnt work
Related
Here was my situation, and how I got out of it:
I was running the Perception build 7 ROM. It was great, no issues except that I needed to get some kernel modules for it, and was unable to get the info I needed to re-create the kernel build environment. I decided to return to stock. There were lots of threads, all going in different directions with inconsistent advice. The wiki I was looking at has what appeared to be a ClockworkMod (CWM) backup.
I had already tried to restore my own CWM backup, but (after disabling lagfix) would restore, but then seemed to loop trying to start the lock screen. Same thing with the version on the wiki. I didn't want to restore to the ATT version and I didn't have windows to run Odin...
So this should work from Windows, Linux and Mac.
get param.lfs from http://forum.xda-developers.com/showpost.php?p=9663090&postcount=58
get FIRMWARE from http://forum.xda-developers.com/showpost.php?p=9109370&postcount=697
Get Odin.rar from http://forum.xda-developers.com/showpost.php?p=8802897&postcount=1
Get Heimdall from http://www.glassechidna.com.au/products/heimdall/
Install Heimdall and any drivers it requires.
Extract the .pit file from Odin.rar. I have heard other people say don't use the pit file…I did…
Unzip the firmware
start Heimdall
FactoryFS
- factory.rfs
Kernel
- zImage
Param.lfs
- param.lfs - though I didn't use this
Primary Bootloader
- I left this blank
Secondary Bootloader
- I left this blank
Cache
- cache.rfs
Modem
- modem.bin
FactoryFS
- factory.rfs
Click Start
Phone will do it's thing. I did receive an error at the very end but all went well. I'd welcome some additional info on the Primary/Secondary Bootloader.
Curious if this restored the bootloader from at&t back to the rogers one?
Excellent! Another successful restore of Rogers stock with Heimdall. Thank you for the write up, gin032.
@Gin Which driver did you install ? WinUSB or libusb ?
Does your Start button starts greyed out ?
I tried both drivers and the only time the Start button is active is when i put a file in primary bootloader. I tried opening heimdall prior and after the phone is in download mode but the Start button always stay inactive. Odin on the other hand always detect my phone in download mode.
Just trying to figure out both apps
I had the same troubles is well.
silvertag said:
@Gin Which driver did you install ? WinUSB or libusb ?
Does your Start button starts greyed out ?
I tried both drivers and the only time the Start button is active is when i put a file in primary bootloader. I tried opening heimdall prior and after the phone is in download mode but the Start button always stay inactive. Odin on the other hand always detect my phone in download mode.
Just trying to figure out both apps
Click to expand...
Click to collapse
Sent from my SAMSUNG-SGH-I896 using XDA App
I'm running on the Mac and Linux so I haven't tried the Windows version yet. I'll try to take a look over the next few days.
silvertag said:
@Gin Which driver did you install ? WinUSB or libusb ?
Does your Start button starts greyed out ?
I tried both drivers and the only time the Start button is active is when i put a file in primary bootloader. I tried opening heimdall prior and after the phone is in download mode but the Start button always stay inactive. Odin on the other hand always detect my phone in download mode.
Just trying to figure out both apps
Click to expand...
Click to collapse
gin032 said:
I'm running on the Mac and Linux so I haven't tried the Windows version yet. I'll try to take a look over the next few days.
Click to expand...
Click to collapse
Heimdall might not work for you on Mac, that requires an official Froyo update with fixed secondary bootloader. Should work fine on Linux if you followed readme file instructions.
Sent from my SAMSUNG-SGH-I896 using XDA App
This seems to be correct. I tried Heimdall on both Windows 7 32-bit and Mac OS X Leopard and neither worked for me.
I could never select the "Start" button on either, and it seems your assertion that a secondary boot loader is required for Mac OS X is bang on.
I instead used Odin with the Pit file from this thread and the stock Rogers firmware and it seems to have worked.
Only the AT&T World Phone boot screen still shows up as a remnant of my previous flashing to Cognition.
I think I would have stayed with Cog if not for the reduced battery life, GPS lock-on slowness and static with BlueTooth head sets, as otherwise it is a fabulous ROM.
Either way, thanks to the OP for at least giving us the tips we needed to restore our older, but better than AT&T firmware!
sshvetsov said:
Heimdall might not work for you on Mac, that requires an official Froyo update with fixed secondary bootloader. Should work fine on Linux if you followed readme file instructions.
Sent from my SAMSUNG-SGH-I896 using XDA App
Click to expand...
Click to collapse
soooo why is the "start" button grayed out???
soooo why is the "start" button grayed out???
Probably because you didn't read instructions and to prevent you from unknowingly bricking your phone. You most likely didn't uncheck the repartition option.
Sent from my SAMSUNG-SGH-I896 using XDA App
SteveCheeseman said:
soooo why is the "start" button grayed out???
Click to expand...
Click to collapse
10ee said:
This seems to be correct. I tried Heimdall on both Windows 7 32-bit and Mac OS X Leopard and neither worked for me.
I could never select the "Start" button on either, and it seems your assertion that a secondary boot loader is required for Mac OS X is bang on.
I instead used Odin with the Pit file from this thread and the stock Rogers firmware and it seems to have worked.
Only the AT&T World Phone boot screen still shows up as a remnant of my previous flashing to Cognition.
I think I would have stayed with Cog if not for the reduced battery life, GPS lock-on slowness and static with BlueTooth head sets, as otherwise it is a fabulous ROM.
Either way, thanks to the OP for at least giving us the tips we needed to restore our older, but better than AT&T firmware!
Click to expand...
Click to collapse
sshvetsov said:
Probably because you didn't read instructions and to prevent you from unknowingly bricking your phone. You most likely didn't uncheck the repartition option.
Sent from my SAMSUNG-SGH-I896 using XDA App
Click to expand...
Click to collapse
sshvetsov is 100% correct. If it wasn't for the fact I put in functionality to grey out the start button you'd now have a bricked device. You can not repartition your device unless you provide all the necessary files.
It doesn't help that for a long time the samfirmware website was spreading misinformation about requiring you specify a PIT file in Odin without repartition checked. There's no need to select a PIT file when you're not repartitioning, in fact Odin will just ignore the fact that you have done so.
The start button isn't greyed out when you don't have a working secondary bootloader. Instead, after you press Start, you will receive a message saying your device couldn't be detected.
Benjamin Dobell said:
sshvetsov is 100% correct. If it wasn't for the fact I put in functionality to grey out the start button you'd now have a bricked device. You can not repartition your device unless you provide all the necessary files.
It doesn't help that for a long time the samfirmware website was spreading misinformation about requiring you specify a PIT file in Odin without repartition checked. There's no need to select a PIT file when you're not repartitioning, in fact Odin will just ignore the fact that you have done so.
The start button isn't greyed out when you don't have a working secondary bootloader. Instead, after you press Start, you will receive a message saying your device couldn't be detected.
Click to expand...
Click to collapse
In my case, I did re-partition....but in the interest of fullness, where can one find such a secondary bootloader?
Bricked my rogers i896 while trying to mash up different kernels for a rom, odin didnt work so i tried heimdall with the procedures thanks to OP.
The only difference was I did not use the pit file. Everything worked flawlessly and I still managed to maintain my data on root sd although i lost root access. The ATT splash screen also was removed (thank goodness) and model number changed back to i896 in the "About". It is now back to pretty much stock, though I did lose the APN settings (can easily reenter it). Last step now is just to re-root and restore via Titanium Backup.
Thanks for the helpful information everyone!
Now that 2.2 is out on Kies, it should become a lot simpler to restore to stock Rogers.
All we need is an ODIN image from the 2.2 release.
loonieryan said:
Now that 2.2 is out on Kies, it should become a lot simpler to restore to stock Rogers.
All we need is an ODIN image from the 2.2 release.
Click to expand...
Click to collapse
This please!
I've tried this, but use zadig.exe my phone shows up as Gadget Serial. So I installed anyways, it says successful, but nothing happens in the frontend that shows the phone and it doesn't allow me to start anything.
ootz0rz said:
Curious if this restored the bootloader from at&t back to the rogers one?
Click to expand...
Click to collapse
+1 this is important!
Tried doing this and my phone is now a brick. It's stuck at the following image:
Phone...Yellow exclamation...PC
Edit: Just got download mode back but still not working for me
Edit: Got Odin3 to work finally. Flashing JL1. Hoping it works.
ok, I have a real challenge.
I made the derp of giving my phone temp root using Z4root, then I ran OneClickLagFix on the phone. The phone rebooted & now just goes to a black screen after the rogers logo. it is on but does not respond to anything (capacitive butons light up when pressed).
I tried the steps listed here to revert to factory but it didn't help. Any ideas?
What do i do?
I didn't brick my phone did I?
I accidently restored an old back up that i thought i created but apparently it was one from Verizon and now i'm stuck, i've tried flashing different roms via Odin with no success
all that comes up when i boot is
-- Bootmode=7 from cmdline...
--Movi_check Start..!!
checksum confirmation need checksum[0]
Not need checksum confirmation
--Movi_check already executed!!...
--movi_checking done!...
# MANUAL MODE #
darrenbanks18 said:
What do i do?
I didn't brick my phone did I?
I accidently restored an old back up that i thought i created but apparently it was one from Verizon and now i'm stuck, i've tried flashing different roms via Odin with no success
all that comes up when i boot is
-- Bootmode=7 from cmdline...
--Movi_check Start..!!
checksum confirmation need checksum[0]
Not need checksum confirmation
--Movi_check already executed!!...
--movi_checking done!...
# MANUAL MODE #
Click to expand...
Click to collapse
sounds like a soft brick, no worries just odin EE4 stock package with PIT file and 'repartition' box checked in odin
blazing through on my 4G Droid Charge
anoninja118 said:
sounds like a soft brick, no worries just odin EE4 stock package with PIT file and 'repartition' box checked in odin
blazing through on my 4G Droid Charge
Click to expand...
Click to collapse
i just tried that... i always fail! i put the PIT file in PIT and the stock bloated EE4 in and... fail.
okay nevermind i got it to pass! thanks so much! i'm at the boot animation now!
darrenbanks18 said:
okay nevermind i got it to pass! thanks so much! i'm at the boot animation now!
Click to expand...
Click to collapse
nice... yeah sometimes it might take a try or two, or you have to use a different USB port, put battery in for the whole thing, etc
I restored and got this exact issue. Continually boots to the Android System Recovery no matter what I do/try.
Where would I get the PIT file?
I think I found a Stock EE4 md5 I can use but I have no clue on the PIT file...
I've spent a while looking around but not sure if I am looking at the correct stuff lol.
Any links would be highly appreciated!
xxJectxx said:
I restored and got this exact issue. Continually boots to the Android System Recovery no matter what I do/try.
Where would I get the PIT file?
I think I found a Stock EE4 md5 I can use but I have no clue on the PIT file...
I've spent a while looking around but not sure if I am looking at the correct stuff lol.
Any links would be highly appreciated!
Click to expand...
Click to collapse
http://db.tt/rJq2x0w and it goes in PIT section of odin and check the 're-partition' box
blazing through on my 4G Droid Charge
Just did the same thing pretty easy fix just get the pit http://www.mediafire.com/?kk62yxpp8b8x918 and the stock file http://www.multiupload.com/LNTF3IKJ21
Make sure the drivers for your phone are installed...that youve connected the phone to the pc before. If you have a newer PC dont use the usb3 slot. Unplug battery from the phone do not connect yet...Open Odin Place the pit in pit section the stock in pda check off repartition. Hold the volume down and plug in the phone to usb. Once odin sees the phone upper left youll see a yellow block replug the battery. (I take my sim card out when I flash dont know if its needed) then click start. After its done unlpug for the boot. Sould be at stock. Replace sim and renable the account.
Just had this problem. Solution worked flawlessly thanks a ton!
zdiddy14 said:
Just had this problem. Solution worked flawlessly thanks a ton!
Click to expand...
Click to collapse
Perfect solution ...glad I click on thread ....I didn't the dummy with the sim card though..gotta stop by VZw...to get a another....
Wow everyone having this issue today =-O
Sent from my SCH-I510 using xda premium
Thank You!!!!!!
Guys , i wanted to thank u for the info in this thread. it helped save my phone.
Hey guys .. im having this issue now , and the solution isnt working for me .. Odin doesnt fail ,it passes , but then just goes back to giving the error in the OP when i boot . Ideas?
are you putting the battery back in before you start to flash? I have seen it pass but still be screwy if not. Also you may want to try to download the files again could be something wrong with the download.
If none of that works, try going to ed2 instead of ee4.
why wouldnt you just do the EP4 full odin instead of any past versions? Odin the EP4 full file and use the PIT file and check repartition in Odin and uncheck the others....when flashing leave your battery in...IE with phone off...hold volume down then plug USB cable to phone
chiahead52 said:
why wouldnt you just do the EP4 full odin instead of any past versions? Odin the EP4 full file and use the PIT file and check repartition in Odin and uncheck the others....when flashing leave your battery in...IE with phone off...hold volume down then plug USB cable to phone
Click to expand...
Click to collapse
Well since he tried ee4 as in the OP and it didnt work I figured instead of messing with new, back was a good start
I'm ready to root but virtually every email I see identifies problems rooting with the latest OTA updates. Even the experts appear to have a problem. Is there a reliable method that does not involve extensive after the fact troubleshooting.
Thanks,
Keith
stedmakr said:
I'm ready to root but virtually every email I see identifies problems rooting with the latest OTA updates. Even the experts appear to have a problem. Is there a reliable method that does not involve extensive after the fact troubleshooting.
Thanks,
Keith
Click to expand...
Click to collapse
You could use my rom or one of the others without any issue or work really.
http://forum.xda-developers.com/gal...t/rom-original-stock-debloated-stock-t2860069
Gatsrom said:
You could use my rom or one of the others without any issue or work really.
http://forum.xda-developers.com/gal...t/rom-original-stock-debloated-stock-t2860069
Click to expand...
Click to collapse
Gatsrom thanks for responding. I gave it a shot and don't know where I am at. I am not rooted. I downloaded and installed Odin and following all the precautions I could find I downloaded TWRP and went through the installation process. Odin showed RESET then PASS. I did this twice and it passed both times. I also tripped knox (which I expected to do). When I boot into recovery there is no sign of TWRP. I go to the standard system recovery.
Did I need to be rooted before TWRP will work? If not, could you point me in the right direction.
Thanks,
Keith
stedmakr said:
Gatsrom thanks for responding. I gave it a shot and don't know where I am at. I am not rooted. I downloaded and installed Odin and following all the precautions I could find I downloaded TWRP and went through the installation process. Odin showed RESET then PASS. I did this twice and it passed both times. I also tripped knox (which I expected to do). When I boot into recovery there is no sign of TWRP. I go to the standard system recovery.
Did I need to be rooted before TWRP will work? If not, could you point me in the right direction.
Thanks,
Keith
Click to expand...
Click to collapse
Hmm let's see what we can do. If you are booting into stock recovery it's not flashing the recovery. You grabbed the recovery for the v1awifi right? https://goo.im/devs/OpenRecovery/v1awifi/openrecovery-twrp-2.8.0.0-v1awifi.img.tar
You put the tar file in the pda slot? It says successful (1/1) in the info/log window at the bottom?
Gatsrom said:
Hmm let's see what we can do. If you are booting into stock recovery it's not flashing the recovery. You grabbed the recovery for the v1awifi right?
You put the tar file in the pda slot? It says successful (1/1) in the info/log window at the bottom?
Click to expand...
Click to collapse
Gatstrom, I believe yes to all of the above. I attached a file that shows the Odin screen (didn't take - screen readout below). The successful line says (succeed 1 /0 failed) The recovery file is correct. Odin 3.09 does not say Note pro. I have also tried Odin 3.09 from a different source with the same result. The other thing I can think of is after flashing and I take the usb cord from the phone my steps are to turn off the phone and turn it on to recovery with the three finger steps. Is their anything else I need to do at this point. Should I be in TWRP now? I find myself in stock recovery system and it gives me I think 5 options. I am just rebooting. Should I be using one of the other options.
I unzipped Odin with 7z. I am using an original samsung USB cable connected directly to the computer and I turned off antivirus before flashing. There is no indication that Kies is operating any services in the background. I also downloaded he latest drivers
Pass
02:02
Auto reboot and f.reset time checked
From message block
added
recovery.img
Nand Write Start!
RQT_CLOSE !!
RES OK!!
Removed!!
Remain Port.... 0
All threads completed. (Succeed 1 / failed 0)
Binary size 8.2mb
Thanks,
Keith
I got it to work. On the TWRP thread at original development forum on page 48 or 49 there was someone with the exact same problem. Bigbiff told the user to uncheck auto reboot in odin and then to boot directly into recovery. I did and it worked. I was unaware that you could root directly from TWRP and a quick stop at the play store. I then loaded your debloated rom and I'll see how it goes once everything updates.
I am so F$%^King excited. I have spent scores of hours attempting to get this to work.
Thanks for all of your help (it helped)
Keith
Ya that was my next suggestion to not reboot and go into twrp directly. Let me know how the rom works. If you have any questions/bugs throw them in the rom thread. I'll see it quicker and it keeps problems and solutions centralized.
I would say give the xposed framework a shot. I put a list of the ones I use. They are incredibly useful.
Ok, here goes.
Have a SM-G930W8 (Canada, Rogers, S7). Was running a 7.0 ROM from XDA (ambassadii? sp?). I disabled developer options to check a possible issue transferring files from my PC to the S7's SD Card. I restarted the device.
Custom binary blocked by FRP lock. No problem, thought I. I'll boot into Download Mode, fire up Odin and flash the stock rom back to the device (also what I've read in most every thread I've come across). Launch ODIN as admin, see the device is connected, select the proper AP(also BL, CSC and CP...I'm thorough) file to flash (from Sammobile I think it was), make sure repartition is unchecked and hit Start.
Here's the result...wait I can't post them but I have the screen shots! The phone shows Secure Check Fail (PIT). Odin gives an error at that step as well.
I've tried Kies (there's no SN anywhere on my device or on the box) so that doesn't work. Smart Switch, same issue.
Does ANYONE out there have any clue what I can attempt next? Sending it in for service will likely cost as much as a new device, with the warranty void. Thank you very much in advance.
chewtoy0 said:
Ok, here goes.
Have a SM-G930W8 (Canada, Rogers, S7). Was running a 7.0 ROM from XDA (ambassadii? sp?). I disabled developer options to check a possible issue transferring files from my PC to the S7's SD Card. I restarted the device.
Custom binary blocked by FRP lock. No problem, thought I. I'll boot into Download Mode, fire up Odin and flash the stock rom back to the device (also what I've read in most every thread I've come across). Launch ODIN as admin, see the device is connected, select the proper AP(also BL, CSC and CP...I'm thorough) file to flash (from Sammobile I think it was), make sure repartition is unchecked and hit Start.
Here's the result...wait I can't post them but I have the screen shots! The phone shows Secure Check Fail (PIT). Odin gives an error at that step as well.
I've tried Kies (there's no SN anywhere on my device or on the box) so that doesn't work. Smart Switch, same issue.
Does ANYONE out there have any clue what I can attempt next? Sending it in for service will likely cost as much as a new device, with the warranty void. Thank you very much in advance.
Click to expand...
Click to collapse
Are you able to boot into recovery?
If not you could try to ONLY flash the stock recovery>boot recovery>wipe everything then boot to download mode and flash complete stock firmware via odin.
or flash stock firmware with the same CSC as your custom rom has/ flash "HOME_CSC" instead of "CSC..."
good luck
mrd0pe said:
Are you able to boot into recovery?
If not you could try to ONLY flash the stock recovery>boot recovery>wipe everything then boot to download mode and flash complete stock firmware via odin.
or flash stock firmware with the same CSC as your custom rom has/ flash "HOME_CSC" instead of "CSC..."
good luck
Click to expand...
Click to collapse
Can't get into Recovery no. Which file of the lot has the stock recovery in it?
chewtoy0 said:
Can't get into Recovery no. Which file of the lot has the stock recovery in it?
Click to expand...
Click to collapse
Try to only flash AP, I did have the same problem as you describe but I cant remember how I resolved it, I'm on G930F tho
Your S/N is on the rear of the phone it can be a pain to see but it is there. Use smart switch to restore the firmware. Just click emergency firmware restore.
It is? The IMEI is there but I didn't see the SN. Also my phone is black so that doesn't help.
I will have another look.
mrd0pe said:
Try to only flash AP, I did have the same problem as you describe but I cant remember how I resolved it, I'm on G930F tho
Click to expand...
Click to collapse
I did that. No dice.
I had the same issue as you. Used the same rom and disabled developer options. I downloaded stock firmware.. flashed it with odin. It actually took 2 tries. The first time I could see only 1/4 of the screen. The second time i flashed stock firmware from another country and it worked. You might actually have to do a hard factory reset if you cant unlock your phone.. for some reason. Then I let kies do its magic because I could then see my S/N. Right now I still feel my phone slightly different. Messenger is unstable for some reason also.
Ok.
Checked the back of the device for a SN#. Mine's black so I used a flashlight. It's not there. The Model #, IMEI, FCC ID# and IC# are all there. Does someone have a blurred out screeny of where THEY found their SN# on the back of the device?
Tried flashing with Odin the CSC(home) and AP files (stock MM from my region). Got: Custom Binary (Boot) blocked by FRP Lock.
Tried flashing TWRP again, to TRY to enter into recovery...same message.
With just the AP selected, ODIN seems to hang at "Get PIT for mapping" and fails. I'm running it again to make sure it's not a bad connection with the device.
Same result, hangs at "Get PIT for mapping".
chewtoy0 said:
Ok.
Checked the back of the device for a SN#. Mine's black so I used a flashlight. It's not there. The Model #, IMEI, FCC ID# and IC# are all there. Does someone have a blurred out screeny of where THEY found their SN# on the back of the device?
Tried flashing with Odin the CSC(home) and AP files (stock MM from my region). Got: Custom Binary (Boot) blocked by FRP Lock.
Tried flashing TWRP again, to TRY to enter into recovery...same message.
With just the AP selected, ODIN seems to hang at "Get PIT for mapping" and fails. I'm running it again to make sure it's not a bad connection with the device.
Same result, hangs at "Get PIT for mapping".
Click to expand...
Click to collapse
Try to flash Nougat firmware, as that was what your custom rom was on right? I dont think it really matters though as I downgraded from stock 7.0 to stock 6.0.1 via odin without errors... But you can try
As an absolute last resort I would try to check the "re-partition"-tab and provide odin with a .pit file, then load everything (BL, AP, CP...) with stock firmware <<<< do this at your own risk, if you are not careful, your phone will be bricked
I am trying to flash MM back to it .
I'm not sure I want to mess with the re partition table...But it's already soft bricked.
Mine is also black. The S/N Is immediately next to the imei number I had to use a flash light to see it but it's deffinatly there.
Matty39856 said:
Mine is also black. The S/N Is immediately next to the imei number I had to use a flash light to see it but it's deffinatly there.
Click to expand...
Click to collapse
I'd show you a photo if I could. The IMEI is by itself on a third line of stuff. There's nothing else around it.
chewtoy0 said:
I'd show you a photo if I could. The IMEI is by itself on a third line of stuff. There's nothing else around it.
Click to expand...
Click to collapse
I'm not sure then. Have you tried flashing the latest unlocked version for your region? I remember on my s6 I had a similar problem that was caused because I was trying to flash a lower version of Android than what I previously had. So ended up flashing the latest unlocked version BTU for my region and it worked. Sorry I can't be of more help. It looks like the latest firmware is still 6.0.1 that's why it's blocking it from downgrading.
Was sent a PM by a person. Was skeptical at first, but in 10 minutes using TeamViewer, they fixed the issue by reflashing the device (as well as repartitioning it properly). I can't thank them enough.
This is the person on Facebook...
Unlock Network FRP Lock Remote Service
We just picked up a pristine unlocked S6 for my wife as a replacement for her beat up old Iphone. The device ran perfectly once it was charged up. I set up WiFi and downloaded a few apps from the Play Store and all seemed perfect. The big UPGRADE message came up, telling me it was due for what I assume was the newly released Android 7 upgrade, and I stupidly said yes. Something must have gone wrong, as the download and install took way less time than I would have thought correct. The phone now bootloops continuously, about every 30 seconds, making it impossible to reach whatever ROM may still be there. I am able to reach Recovery, and Download mode no problem. Numerous wipes and factory resets have done nothing. I downloaded a Lollipop 5.0.2 ZIP, specific to Bell, the MD5 checked out OK. Sammy USB drivers are good. I can connect with Odin but the upload fails right away at sboot.bin.
Am I causing myself problems by trying to flash a stock Bell ROM on an unlocked phone? The ROMS are hard to find and most are stored in pay for use sites that literally take 12 hours to download if the user doesn't set up an account. Any suggestions as to how I can get this back running again, or is it bricked? I've spent about 8 hours on Google and trying everything I could find, and nothing I've come across has worked.
Alternatively, I'm fine with rooting and flashing a custom ROM (I've been doing them for years), though the boss would prefer to stay stock. Trouble is, without access to an existing stable ROM on the phone, I can't see how I can root in the first place. Are some ROMS flashable without rooting, and if so, what are some good ones? Would I simply load them into Odin and flash to the phone?
Thanks in advance.
jp071848 said:
We just picked up a pristine unlocked S6 for my wife as a replacement for her beat up old Iphone. The device ran perfectly once it was charged up. I set up WiFi and downloaded a few apps from the Play Store and all seemed perfect. The big UPGRADE message came up, telling me it was due for what I assume was the newly released Android 7 upgrade, and I stupidly said yes. Something must have gone wrong, as the download and install took way less time than I would have thought correct. The phone now bootloops continuously, about every 30 seconds, making it impossible to reach whatever ROM may still be there. I am able to reach Recovery, and Download mode no problem. Numerous wipes and factory resets have done nothing. I downloaded a Lollipop 5.0.2 ZIP, specific to Bell, the MD5 checked out OK. Sammy USB drivers are good. I can connect with Odin but the upload fails right away at sboot.bin.
Am I causing myself problems by trying to flash a stock Bell ROM on an unlocked phone? The ROMS are hard to find and most are stored in pay for use sites that literally take 12 hours to download if the user doesn't set up an account. Any suggestions as to how I can get this back running again, or is it bricked? I've spent about 8 hours on Google and trying everything I could find, and nothing I've come across has worked.
Alternatively, I'm fine with rooting and flashing a custom ROM (I've been doing them for years), though the boss would prefer to stay stock. Trouble is, without access to an existing stable ROM on the phone, I can't see how I can root in the first place. Are some ROMS flashable without rooting, and if so, what are some good ones? Would I simply load them into Odin and flash to the phone?
Thanks in advance.
Click to expand...
Click to collapse
Just use Samsung smartswitch software to restore firmware.
Your device's model is SM-G920W8, right?
And the only thing you did is flash an firmware via Odin and stuck on sboot.bin?
forumber2 said:
Your device's model is SM-G920W8, right?
And the only thing you did is flash an firmware via Odin and stuck on sboot.bin?
Click to expand...
Click to collapse
He tried to downgrade from marshmallow to lollipop that's why it failed.
sofir786 said:
He tried to downgrade from marshmallow to lollipop that's why it failed.
Click to expand...
Click to collapse
I know that, I want be sure that he/she didn't do anything (like wiping /data) expect trying to downgrade. I'll write my procedure according that for get the device back up and running without any data loss.
And he/she shouldn't use Smart Switch to restore the firmware in first place, it will cause data loss.
forumber2 said:
I know that, I want be sure that he/she didn't do anything (like wiping /data) expect trying to downgrade. I'll write my procedure according that for get the device back up and running without any data loss.
And he/she shouldn't use Smart Switch to restore the firmware in first place, it will cause data loss.
Click to expand...
Click to collapse
Ahh right okay, so using smart switch wipes internal storage? Anyhoo I won't ask too much now don't wanna hijack the post, do your thing
sofir786 said:
Ahh right okay, so using smart switch wipes internal storage? Anyhoo I won't ask too much now don't wanna hijack the post, do your thing
Click to expand...
Click to collapse
Thanks for the quick responses everyone. Apologies, it was very late when I made the OP, and I forgot to mention that I had tried both Kies AND Smartswitch. When I connected the phone while it was bootlooping, and for the brief period while whatever ROM was showing before the reboot, Smartswitch connected with it, but immediately fired back that "USB file transfer is not allowed...". There does seem to be some, or all, of a ROM there, but it is still in the setup stage, which is expected after a full factory reset. I don't have time to go in and enable USB Transfer as it reboots well before I can get into Settings. When I connect while it was in Download mode, SS seems to hang on "Connecting to your device" then fails.
"Your device's model is SM-G920W8, right?
And the only thing you did is flash an firmware via Odin and stuck on sboot.bin?"
SM-G920W8 yes. After the Odin problems, per my original post, I also tried, based on suggestions all over the interweb, a wipe, as well as resorting to a factory reset, through the stock recovery. Nothing worked, the bootloop continues, and the factory reset causes the system to go into setup mode. In the 30 seconds between reboots, I don't have time to get into the ROM to make changes like enabling USB transfer/debugging before it reboots again.
"He tried to downgrade from marshmallow to lollipop that's why it failed"
I assumed, when I first clicked the button and caused the problem, that I was UPGRADING from whatever ROM was properly installed, to Android 7.0/Nougat. This failed and induced the bootloop. I then thought I would try and install Lollipop through Odin, which brings up the sboot.bin fail. From your comment, should I try to find a Nougat 7.0 ROM and do the UPGRADE manually via Odin? Is that more likely to work than a downgrade.
Regarding the comments about data loss, I am not concerned about that, the phone was new and did not contain any data worth saving, it hadn't been set up yet. In any case, I tried a few factory resets, so any data would have been wiped during that action as well.
I'm getting nervous, I seemed to have really borked up this phone, I sure hope you experts can bail me out. ;o(
Thanks again for the help...
jp071848 said:
Thanks for the quick responses everyone. Apologies, it was very late when I made the OP, and I forgot to mention that I had tried both Kies AND Smartswitch. When I connected the phone while it was bootlooping, and for the brief period while whatever ROM was showing before the reboot, Smartswitch connected with it, but immediately fired back that "USB file transfer is not allowed...". There does seem to be some, or all, of a ROM there, but it is still in the setup stage, which is expected after a full factory reset. I don't have time to go in and enable USB Transfer as it reboots well before I can get into Settings. When I connect while it was in Download mode, SS seems to hang on "Connecting to your device" then fails.
"Your device's model is SM-G920W8, right?
And the only thing you did is flash an firmware via Odin and stuck on sboot.bin?"
SM-G920W8 yes. After the Odin problems, per my original post, I also tried, based on suggestions all over the interweb, a wipe, as well as resorting to a factory reset, through the stock recovery. Nothing worked, the bootloop continues, and the factory reset causes the system to go into setup mode. In the 30 seconds between reboots, I don't have time to get into the ROM to make changes like enabling USB transfer/debugging before it reboots again.
"He tried to downgrade from marshmallow to lollipop that's why it failed"
I assumed, when I first clicked the button and caused the problem, that I was UPGRADING from whatever ROM was properly installed, to Android 7.0/Nougat. This failed and induced the bootloop. I then thought I would try and install Lollipop through Odin, which brings up the sboot.bin fail. From your comment, should I try to find a Nougat 7.0 ROM and do the UPGRADE manually via Odin? Is that more likely to work than a downgrade.
Regarding the comments about data loss, I am not concerned about that, the phone was new and did not contain any data worth saving, it hadn't been set up yet. In any case, I tried a few factory resets, so any data would have been wiped during that action as well.
I'm getting nervous, I seemed to have really borked up this phone, I sure hope you experts can bail me out. ;o(
Thanks again for the help...
Click to expand...
Click to collapse
I think Upgrading to nougat via Odin would be best bet @forumber2 has a good set of steps which are easy to follow .
sofir786 said:
I think Upgrading to nougat via Odin would be best bet @forumber2 has a good set of steps which are easy to follow .
Click to expand...
Click to collapse
I did a search under that name, and came across a reference to a great app called SamFirm (not sure if that's what you meant by a good set of steps ;o). I ran SamFirm using SM-G920W8, and tried both Regions BMC (Bell) and XAC (Canada). Downloaded and unzipped, the XAC file name was SM-G920W8_1_20170428185952_f736z32l4i_fac.zip.enc4, and entered the AP, BL, CP and CSC links in Odin. Failed both times with the same Odin message:
<ID:0/004> Odin engine v(ID:3.1203)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1
On the phone, on the Downloading screen, the error was "SECURE CHECK FAIL : (PIT)"
Googling these messages, the general consensus seems to be that these errors indicate an attempt to flash an incorrect ROM, but I'm running out of options for finding a "correct" one.
Thanks again...
jp071848 said:
I did a search under that name, and came across a reference to a great app called SamFirm (not sure if that's what you meant by a good set of steps ;o). I ran SamFirm using SM-G920W8, and tried both Regions BMC (Bell) and XAC (Canada). Downloaded and unzipped, the XAC file name was SM-G920W8_1_20170428185952_f736z32l4i_fac.zip.enc4, and entered the AP, BL, CP and CSC links in Odin. Failed both times with the same Odin message:
<ID:0/004> Odin engine v(ID:3.1203)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1
On the phone, on the Downloading screen, the error was "SECURE CHECK FAIL : (PIT)"
Googling these messages, the general consensus seems to be that these errors indicate an attempt to flash an incorrect ROM, but I'm running out of options for finding a "correct" one.
Thanks again...
Click to expand...
Click to collapse
Samfirm is a great tool to download firmwares. The pit file sets your partition sizes, you need to flash the correct pit file for that firmware otherwise the firmware will fail to flash.
sofir786 said:
Samfirm is a great tool to download firmwares. The pit file sets your partition sizes, you need to flash the correct pit file for that firmware otherwise the firmware will fail to flash.
Click to expand...
Click to collapse
Now we're getting somewhere ;o) I stayed away from PIT files as they seem to be controversial/risky, but the error message I'm seeing would seem to confirm what you're saying. Question is, how do I locate the correct PIT file AND GET IT RIGHT THE FIRST TIME, as I understand that making a mistake with the PIT file can be disastrous.
Thanks so much...
jp071848 said:
Now we're getting somewhere ;o) I stayed away from PIT files as they seem to be controversial/risky, but the error message I'm seeing would seem to confirm what you're saying. Question is, how do I locate the correct PIT file AND GET IT RIGHT THE FIRST TIME, as I understand that making a mistake with the PIT file can be disastrous.
Thanks so much...
Click to expand...
Click to collapse
I think there is a Thread in the general section which has the collection of pit files, you need to make sure the pit file is bmc.
jp071848 said:
Now we're getting somewhere ;o) I stayed away from PIT files as they seem to be controversial/risky, but the error message I'm seeing would seem to confirm what you're saying. Question is, how do I locate the correct PIT file AND GET IT RIGHT THE FIRST TIME, as I understand that making a mistake with the PIT file can be disastrous.
Thanks so much...
Click to expand...
Click to collapse
UPDATE: I found what I assume is the correct PIT file for the G920W8. Also, on another forum, I found the question:
"Okay, according to that guide Odin is smart enough to know the Pit file is in the CSC file, when the re-partition box is checked? ",
so I may not need the PIT file after all? I had always read that when using Odin, Re-partition was always to be left UNCHECKED, but this says otherwise. What further damage could I possibly do if I re-run Odin with the same AP, BL, CP and CSC files as before, but CHECK re-partition. I guess I can't brick it worse than it already is? Or can I?
jp071848 said:
UPDATE: I found what I assume is the correct PIT file for the G920W8. Also, on another forum, I found the question:
"Okay, according to that guide Odin is smart enough to know the Pit file is in the CSC file, when the re-partition box is checked? ",
so I may not need the PIT file after all? I had always read that when using Odin, Re-partition was always to be left UNCHECKED, but this says otherwise. What further damage could I possibly do if I re-run Odin with the same AP, BL, CP and CSC files as before, but CHECK re-partition. I guess I can't brick it worse than it already is? Or can I?
Click to expand...
Click to collapse
I don't think it could go any worse tbh, try it without the pit file and repartition, you can then try the pit file method if it doesn't work
jp071848 said:
UPDATE: I found what I assume is the correct PIT file for the G920W8. Also, on another forum, I found the question:
"Okay, according to that guide Odin is smart enough to know the Pit file is in the CSC file, when the re-partition box is checked? ",
so I may not need the PIT file after all? I had always read that when using Odin, Re-partition was always to be left UNCHECKED, but this says otherwise. What further damage could I possibly do if I re-run Odin with the same AP, BL, CP and CSC files as before, but CHECK re-partition. I guess I can't brick it worse than it already is? Or can I?
Click to expand...
Click to collapse
Moving right along.... I decided to live dangerously by flashing the BMC ROM, obtained through SamFirm, with Odin, with Re-partition checked. In theory, this would have let Odin know that the contents of the PIT file are already inside the CSC file. Sadly, same result "Re-partition Operation Failed". Interestingly, when I click the PIT tab in Odin the popup says "Do not use this tab... Your device will be changed with the PIT in the CSC file", which doesn't appear to be the case.
jp071848 said:
Moving right along.... I decided to live dangerously by flashing the BMC ROM, obtained through SamFirm, with Odin, with Re-partition checked. In theory, this would have let Odin know that the contents of the PIT file are already inside the CSC file. Sadly, same result "Re-partition Operation Failed". Interestingly, when I click the PIT tab in Odin the popup says "Do not use this tab... Your device will be changed with the PIT in the CSC file", which doesn't appear to be the case.
Click to expand...
Click to collapse
That's just a warning more than anything else
jp071848 said:
Moving right along.... I decided to live dangerously by flashing the BMC ROM, obtained through SamFirm, with Odin, with Re-partition checked. In theory, this would have let Odin know that the contents of the PIT file are already inside the CSC file. Sadly, same result "Re-partition Operation Failed". Interestingly, when I click the PIT tab in Odin the popup says "Do not use this tab... Your device will be changed with the PIT in the CSC file", which doesn't appear to be the case.
Click to expand...
Click to collapse
Tried ODIN and included the PIT file I downloaded. Tried with "Re-Partition" on and off, both times failed exactly the same way "Re-partition" Operation Failed"
jp071848 said:
Tried ODIN and included the PIT file I downloaded. Tried with "Re-Partition" on and off, both times failed exactly the same way "Re-partition" Operation Failed"
Click to expand...
Click to collapse
where did you get the pit file from?
look in settings>security>reactivation lock
if its checked/enabled then uncheck it/disable it
fyi, stay away from repartition pit in odin, only for experienced users w/correct files if any
sofir786 said:
where did you get the pit file from?
Click to expand...
Click to collapse
From this 22 page thread here on XDA
https://forum.xda-developers.com/galaxy-s6/general/g920f-pit-file-banded-firmwares-t3118459
There is a specific reference to a Canadian W8 PIT file
SM-G920W8 OYA multi CSC ( BMC BWA ESK FMC GLW KDO MTA RWC TLS VMC VTR )
ZEROFLTE_CAN_BMC.pit
That's the one I unzipped and loaded into Odin.