Related
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 wanting to unroot and return the number of custom flashed roms back to none. I've heard you can do this? I was planning on using this (http://forum.xda-developers.com/showthread.php?t=1342348) to unroot phone and then what would I use to return the custom rom count to none?
There is nothing that can set the custom binary to 0.
jc1337 said:
I'm wanting to unroot and return the number of custom flashed roms back to none. I've heard you can do this? I was planning on using this (http://forum.xda-developers.com/showthread.php?t=1342348) to unroot phone and then what would I use to return the custom rom count to none?
Click to expand...
Click to collapse
appdroid said:
There is nothing that can set the custom binary to 0.
Click to expand...
Click to collapse
I was following the unroot tutorial that I posted a link to in my first post and it just sits there and doesn't do anything after it gets to <ID:0/003> NAND Write Start!!
I watched a youtube video of a guy who was doing a visual step by step of that tutorial and he put his phone into debugging mode and I didn't because I didn't see anything about it in that post. Now my phone won't boot past that yellow exclamation point symbol... did I mess something up?
jc1337 said:
I was following the unroot tutorial that I posted a link to in my first post and it just sits there and doesn't do anything after it gets to <ID:0/003> NAND Write Start!!
I watched a youtube video of a guy who was doing a visual step by step of that tutorial and he put his phone into debugging mode and I didn't because I didn't see anything about it in that post. Now my phone won't boot past that yellow exclamation point symbol... did I mess something up?
Click to expand...
Click to collapse
debugging mode has no bearing whatsoever in download or recovery mode....debugging mode is for the OS only....
Pirateghost said:
debugging mode has no bearing whatsoever in download or recovery mode....debugging mode is for the OS only....
Click to expand...
Click to collapse
\
do you have any idea why it might not be working then? I'm using the .tar from that post about unroot i727 and it's not working. What I'm doing is
1. running odin as admin
2. selecting pda (the SGH-I727-UCKJ2-k0nane.tar)
3. while phone is off pressing both volume buttons and then plugging in usb (putting it into download mode)
4. making sure odin sees my phone
5. clicking start
and this is what it does and it won't go any further
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> boot.img
<ID:0/003> NAND Write Start!!
I've let it sit there for about 30 minutes without it moving any further?
do you comprehend what root actually is?
why are you trying to 'unroot' your phone?
did you have a custom rom on your phone before this?
Pirateghost said:
do you comprehend what root actually is?
why are you trying to 'unroot' your phone?
did you have a custom rom on your phone before this?
Click to expand...
Click to collapse
I'm needing to return the phone to AT&T. Yes, I do comprehend what root is. And yes, I had a custom ROM on it before this.
sorry, i read this all the time about 'unrooting' your phone because so many people use the terminology incorrectly. this isnt about UNROOTING your phone as much as it is restoring STOCK...big difference. UNROOTING implies that you will be removing the su binary and superuser.apk from your /system, but leaving the rest of the system intact....regardless of what rom you are on.
are you using the samsung cable and not some other cable? i have seen bad cables do this. i have also seen front panel USB hubs do this, and you might have better luck finding another USB port to try
Pirateghost said:
sorry, i read this all the time about 'unrooting' your phone because so many people use the terminology incorrectly. this isnt about UNROOTING your phone as much as it is restoring STOCK...big difference. UNROOTING implies that you will be removing the su binary and superuser.apk from your /system, but leaving the rest of the system intact....regardless of what rom you are on.
are you using the samsung cable and not some other cable? i have seen bad cables do this. i have also seen front panel USB hubs do this, and you might have better luck finding another USB port to try
Click to expand...
Click to collapse
All I am really wanting to do is remove superuser stuff so if at&t checks they won't see it. An I am using the cable that came with the phone but I am using the front panel USB hubs so I guess I'll have to try plugging it into the back. Thank you very much for all of your help!
jc1337 said:
All I am really wanting to do is remove superuser stuff so if at&t checks they won't see it. An I am using the cable that came with the phone but I am using the front panel USB hubs so I guess I'll have to try plugging it into the back. Thank you very much for all of your help!
Click to expand...
Click to collapse
if you are on a custom rom, when you get that tar to load, you will be loading STOCK rom....not just removing superuser....that file is meant to restore your phone to STOCK, not 'unroot' it. root only applies within the OS. if you load a new OS that doesnt have root access, its not unrooting it, its loading a new rom.
Pirateghost said:
if you are on a custom rom, when you get that tar to load, you will be loading STOCK rom....not just removing superuser....that file is meant to restore your phone to STOCK, not 'unroot' it. root only applies within the OS. if you load a new OS that doesnt have root access, its not unrooting it, its loading a new rom.
Click to expand...
Click to collapse
I'm just trying to get the phone so that I can return it to at&t, how would you do it if you were me?
jc1337 said:
So, should I just try to find the stock rom online?
Click to expand...
Click to collapse
that k0nane.tar IS the stock rom.....
Pirateghost said:
that k0nane.tar IS the stock rom.....
Click to expand...
Click to collapse
Yeah, I noticed that I worded that wrong and changed it but I guess you'd already seen it. I'm just trying to get the phone so that I can return it to at&t, how would you do it if you were me?
jc1337 said:
Yeah, I noticed that I worded that wrong and changed it but I guess you'd already seen it. I'm just trying to get the phone so that I can return it to at&t, how would you do it if you were me?
Click to expand...
Click to collapse
with that exact file.
it will however, probably trip the download counter
Pirateghost said:
with that exact file.
it will however, probably trip the download counter
Click to expand...
Click to collapse
It is, I've gone from YES(4 counts) to YES(15 counts) I honestly have no idea what I'm doing wrong and why it won't go past NAND Write. I've been working on this for the past three hours though and they close in an hour an 15 minutes so I guess I may not make it tonight...
at this point I would be okay with just getting this phone working again.... I have to be up in a few hours and need to get to sleep
If you are under 30 days than return it to att... all you gotta say is that is getting hot and rebooting or just say you can't go pass the logo screen... if you are under the Samsung 1 year warranty just flast the stock firmware (search on xda on how to do it) and reset it to factory setting. Call Samsung center ask for a replacement or service ticket, send your phone and you'll get a working phone back in about 6 business days...
Hit the thanks button if I helped you with your question!
Thanks.
SkyIce 7.3 Speed
You WILL trip the counter using that stock .tar. I recently went back to stock via the same method your using and I did not have root. I had no SU access for TiBu etc. So no signs AT&T would see other than seeing the counter bring tripped if they boot into DL mode to check. I have since rooted again to freeze bloat in TiBu. My question is did you extract the 7zip file properly and actually flashing a .tar file and not the compressed .zip?
Sent from my SAMSUNG-SGH-I727 using xda premium
r3dp0is0n2012 said:
If you are under 30 days than return it to att... all you gotta say is that is getting hot and rebooting or just say you can't go pass the logo screen... if you are under the Samsung 1 year warranty just flast the stock firmware (search on xda on how to do it) and reset it to factory setting. Call Samsung center ask for a replacement or service ticket, send your phone and you'll get a working phone back in about 6 business days...
Hit the thanks button if I helped you with your question!
Thanks.
SkyIce 7.3 Speed
Click to expand...
Click to collapse
I am under 30 days, but I don't think that'll work if I can't get past the screen that says "Firmware upgrade encountered an issue. Please selecdt recovery mode in Kies & try again." and says I have a custom binary download of 16
hcyplr29 said:
You WILL trip the counter using that stock .tar. I recently went back to stock via the same method your using and I did not have root. I had no SU access for TiBu etc. So no signs AT&T would see other than seeing the counter bring tripped if they boot into DL mode to check. I have since rooted again to freeze bloat in TiBu. My question is did you extract the 7zip file properly and actually flashing a .tar file and not the compressed .zip?
Sent from my SAMSUNG-SGH-I727 using xda premium
Click to expand...
Click to collapse
yeah I did. I'm trying to flash the .tar not the whole zip
Ok, I have read through everything. I have followed all the directions. Here is my situation. Hoping someone can help...
Ok, I purchased a white skyrocket off ebay. It works. Kinda. I can make calls and send txts. Data works. But it is obviously a custom ROM and there is a lot wrong with it. For one, the screen NEVER times out. Even when I set a timeout in the settings. I can push the power button and turn the screen off. I can set a security pattern to unlock the screen, but it never prompts me for it when I power the screen on. The bluetooth radio won't turn off. Many other issues.
I followed the "return to stock method" using ODIN an the ko-kane .TAR, but all it seems to is overwrite SOME of the issues I am having. It's not truly returning to stock. My email settings and txt's are still there even after flashing. It also doesn't prompt me for my gmail setup, do the phone tutorial etc, etc.
So, is there a way for me to TRULY go back to stock? Am I just missing something here? I want to have this be as if it had never powered on before. Is that possible? Thanks in advance for the assistance...
theshifter said:
Ok, I have read through everything. I have followed all the directions. Here is my situation. Hoping someone can help...
Ok, I purchased a white skyrocket off ebay. It works. Kinda. I can make calls and send txts. Data works. But it is obviously a custom ROM and there is a lot wrong with it. For one, the screen NEVER times out. Even when I set a timeout in the settings. I can push the power button and turn the screen off. I can set a security pattern to unlock the screen, but it never prompts me for it when I power the screen on. The bluetooth radio won't turn off. Many other issues.
I followed the "return to stock method" using ODIN an the ko-kane .TAR, but all it seems to is overwrite SOME of the issues I am having. It's not truly returning to stock. My email settings and txt's are still there even after flashing. It also doesn't prompt me for my gmail setup, do the phone tutorial etc, etc.
So, is there a way for me to TRULY go back to stock? Am I just missing something here? I want to have this be as if it had never powered on before. Is that possible? Thanks in advance for the assistance...
Click to expand...
Click to collapse
Yeah, you have to wipe it manually in cwm. Then flash the sammobile tar in odin
xcrazydx said:
Yeah, you have to wipe it manually in cwm. Then flash the sammobile tar in odin
Click to expand...
Click to collapse
OK, I found it, its a zip with a bunch of TAR inside. I cant use CWM to install the zip. I looked for what to do and I am stuck...
theshifter said:
OK, I found it, its a zip with a bunch of TAR inside. I cant use CWM to install the zip. I looked for what to do and I am stuck...
Click to expand...
Click to collapse
found it where? you download from sammobile.com. You have to extract it with 7zip and flash it in odin, not cwm.
slow down and read a bit, no sense in rushing and making a brick
xcrazydx said:
found it where? you download from sammobile.com. You have to extract it with 7zip and flash it in odin, not cwm.
slow down and read a bit, no sense in rushing and making a brick
Click to expand...
Click to collapse
Well, I found it, ran the flash in ODIN. Nothing. Still having all the same issues. I have no clue where to go from here...
theshifter said:
Well, I found it, ran the flash in ODIN. Nothing. Still having all the same issues. I have no clue where to go from here...
Click to expand...
Click to collapse
Did you wipe everything a bunch of times and format everything before flash?
xcrazydx said:
Did you wipe everything a bunch of times and format everything before flash?
Click to expand...
Click to collapse
I did wipe davlik, cache, format, and fix permissions. I can try it again and see what happens...
theshifter said:
I did wipe davlik, cache, format, and fix permissions. I can try it again and see what happens...
Click to expand...
Click to collapse
that was before the ODIN flash though...
theshifter said:
I did wipe davlik, cache, format, and fix permissions. I can try it again and see what happens...
Click to expand...
Click to collapse
wipe data/factory reset x3
wipe cache x3
wipe dalvik cache x3
Format system x3
Format emmc x3
Format sdcard x3
boot back into download mode and odin sammobile tar
That will wipe everything on your internal and external sd cards, so back up whatever you dont wanna lose forever.
Try darkside wipe (search for it and read the thread) and then flash one of the custom GB Roms floating around. It doesn't matter which one, just pick a popular and similar (close to stock) one. If you can find the CWM flashable version of the stock ROM that would be even better. Make sure you flash the necessary radio / modem for the ROM you pick before you flash the ROM just to be safe. After you make sure the phone boots properly but before you set anything up (Email, etc...) do a factory reset. Again, reboot to make sure everything is working. Then, go back and flash (with ODIN) either K0nane's TAR or the SamMobile TAR. The SamMobile Tar will have the proper radio / modem with it.
If you flash the SamMobile TAR without wiping first (ie installing a new ROM that hasn't been set up), the Sammobile TAR will port certain settings over to the new flash. It did for me anyway. If you don't understand the things I posted make sure you take the time on your own to research the topics and find the correct links on your own. All you need is the search function and the time to do the reasearch you need to do and you should be fine. Good luck.
scott14719 said:
Try darkside wipe (search for it and read the thread) and then flash one of the custom GB Roms floating around. It doesn't matter which one, just pick a popular and similar (close to stock) one. If you can find the CWM flashable version of the stock ROM that would be even better. Make sure you flash the necessary radio / modem for the ROM you pick before you flash the ROM just to be safe. After you make sure the phone boots properly but before you set anything up (Email, etc...) do a factory reset. Again, reboot to make sure everything is working. Then, go back and flash (with ODIN) either K0nane's TAR or the SamMobile TAR. The SamMobile Tar will have the proper radio / modem with it.
If you flash the SamMobile TAR without wiping first (ie installing a new ROM that hasn't been set up), the Sammobile TAR will port certain settings over to the new flash. It did for me anyway. If you don't understand the things I posted make sure you take the time on your own to research the topics and find the correct links on your own. All you need is the search function and the time to do the reasearch you need to do and you should be fine. Good luck.
Click to expand...
Click to collapse
I did all the above (darkside wipe, new ROM, etc) and I am still stuck with all the same issues after the new flash. This makes NO SENSE to me at all. I am... frustrated
theshifter said:
I did all the above (darkside wipe, new ROM, etc) and I am still stuck with all the same issues after the new flash. This makes NO SENSE to me at all. I am... frustrated
Click to expand...
Click to collapse
Goto "settings" "about phone". What does the Android version, Baseband version, Kernel version, and Build number say?
It is possible you may need to reformat your internal and external SD cards. You could also have a corrupt Efs partition. Read this:
http://forum.xda-developers.com/showthread.php?t=1611796
If you reformat your SD cards, make sure you backup any information you want to keep.
Even reflash your radio / modem just for the hell of it.
If you try all of this and everything else you said you have tried it would be near impossible for your phone to retain any information from previous flashes.
scott14719 said:
Goto "settings" "about phone". What does the Android version, Baseband version, Kernel version, and Build number say?
It is possible you may need to reformat your internal and external SD cards. You could also have a corrupt Efs partition. Read this:
http://forum.xda-developers.com/showthread.php?t=1611796
If you reformat your SD cards, make sure you backup any information you want to keep.
Even reflash your radio / modem just for the hell of it.
If you try all of this and everything else you said you have tried it would be near impossible for your phone to retain any information from previous flashes.
Click to expand...
Click to collapse
It was the corrupt EFS partition. Ran method #2 (did that first, it seemed easier to be honest) and when the phone rebooted, it had prompted me for the screen lock password. Thanks so much for the advice everybody. Took awhile but I am glad it did because I learned quite a bit going through all of the steps.
Restoring Skyrocket ICS->GB (ClockworkMod Recovery v5.0.2.6 installed)
Need Help,
I want to go back to the gingerbread stock ROM as the ICS installed currently is giving me a lot of problems. My GPS has also stopped working.
I started here http://forum.xda-developers.com/showthread.php?t=1342348 and followed all instructions. But i get stuck because when using Odin i get the following output and that's it, it does not go ahead.
<ID:0/007> Added!!
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
I have the SGH-I727 from AT&T but with leaked ICS and also rooted with ClockworkMod Recovery v5.0.2.6. I cannot seem to go to the "Download Mode" as the process after power off takes me directly to the Recovery options.
Would I need to unRoot the device? or can i use any option available right now in this recovery mode?
What am i doing wrong? or not doing anything at all?
Sorry if this was the wrong thread to post to.
tapan_skyrocket said:
Need Help,
I want to go back to the gingerbread stock ROM as the ICS installed currently is giving me a lot of problems. My GPS has also stopped working.
I started here http://forum.xda-developers.com/showthread.php?t=1342348 and followed all instructions. But i get stuck because when using Odin i get the following output and that's it, it does not go ahead.
<ID:0/007> Added!!
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
I have the SGH-I727 from AT&T but with leaked ICS and also rooted with ClockworkMod Recovery v5.0.2.6. I cannot seem to go to the "Download Mode" as the process after power off takes me directly to the Recovery options.
Would I need to unRoot the device? or can i use any option available right now in this recovery mode?
What am i doing wrong? or not doing anything at all?
Sorry if this was the wrong thread to post to.
Click to expand...
Click to collapse
Pull battery
put battery back in
plug usb cable into computer but not into phone yet
Hold both volume buttons and plug the cable into phone at the same time
after screen pops up press volume up to enter dl mode
I'm in a bit of a similar position, but I simply need to recover from a boot loop.
Can I extract the MD5 from the downloaded SamMobile zip and simply flash away in Odin?
I can access both CWM and download mode, but I've got nothing to flash on the internal SD, don't have an external SD.
I do not have a nandroid backup.
anonomike said:
I'm in a bit of a similar position, but I simply need to recover from a boot loop.
Can I extract the MD5 from the downloaded SamMobile zip and simply flash away in Odin?
I can access both CWM and download mode, but I've got nothing to flash on the internal SD, don't have an external SD.
I do not have a nandroid backup.
Click to expand...
Click to collapse
Yeah.
http://forum.xda-developers.com/showthread.php?t=1668792
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Going back to Gingerbread
I flashed the update sucessfully, thank you for the tip xcrazydx. But started to get errors as soon as i swipe my logonscreen, try to use the phone, calender, change volume etc. Sometimes i got 2-3 errors in succession. An example would be
"Sorry! The application Google Services Framework (process com.google.process.gapps) has stopped unexpectedly. Please try again." - On trying to make a call and then two more errors after that before i go back to home screen.
Also the trip counter on cusom ROM on the download screen shows 1 and it says "current ROM: Custom"
I have now flashed with another ICS ROM which suceeded. My GPS is also working now
Just thought others shoudl know!!
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
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.