Related
What this is:
A package to return your device to a completely stock state. It differs from h8rift's packages in that it includes the UCKE3 update.
v2 Changelog:
-All problems should be fixed now
-Package is now pre-rooted (run SuperOneClick unroot if you don't want it)
-Included a working PIT file if you want to repartition (not necessary unless bricked)
Instructions:
1) Make sure the drivers for the Infuse 4G are installed (installing Kies is the best way to accomplish this)
2) Download and unzip Odin_UCKE3.zip
3) Run Odin3 v1.7.exe as administrator
4) Place your phone into download mode (pull battery, replace battery, press and hold both volume buttons while plugging in the USB cable)
5) Make sure your phone shows up in Odin as COM##
6) Click the PDA button and choose PDA_UCKE3_v2.tar.md5
7) Click the PHONE button and choose PHONE_UCKE3.tar.md5
8) Press Start
9) After it completes, it may throw you into 3e recovery. Select "delete all user data" and then select reboot system now.
----Download----
Odin_UCKE3_v2.zip (184MB)
I do this for fun so you shouldn't feel any obligation to donate, but here's a link if you want to. Donations of any amount are very much appreciated.
Trying it now. This is my last try before I spend another $440 on a replacement phone, hehe.
I'm still hanging at the FACTORYFS process just like last night... just goes a little way on the green bar below FACTORY FS, and same on the phone, the blue indicator just gets a little way, here's the log message thus far.... it's been about 15 mins:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> PDA_UCKE3.tar.md5 is valid.
<OSM> PHONE_UCKE3.tar.md5 is valid.
<OSM> CSC_UCKD5.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<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> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> param.lfs
<ID:0/004> zImage
<ID:0/004> factoryfs.rfs
And to confirm when running:
Re-Partition - CHECK
Auto Reboot - CHECK
F. Reset Time - CHECK
Dump - NO CHECK
Phone EFS Clear - NO CHECK
Phone Bootloader Update - NO CHECK
Bootloader - Blank
Dump - Blank
Try rebooting your pc and try a different usb port.
gtg465x said:
Try rebooting your pc and try a different usb port.
Click to expand...
Click to collapse
Trying now. As a FYI, I'm on win 7 home premium, running Odin as admin... should I be running in win xp compat mode or anything? I am sure i've tried it all already, but thought I'd ask.
Also make sure you open Odin by right clicking and selecting run as administrator.
bella92108 said:
Trying now. As a FYI, I'm on win 7 home premium, running Odin as admin... should I be running in win xp compat mode or anything? I am sure i've tried it all already, but thought I'd ask.
Click to expand...
Click to collapse
Yes, xp mode may help too. After trying these suggestions the next step is to try from an actual xp machine.
gtg465x said:
Yes, xp mode may help too. After trying these suggestions the next step is to try from an actual xp machine.
Click to expand...
Click to collapse
Might have something here....
- HTC Sync Cable (the samsung one seems flakey so thought I'd give it a try)
- Odin3 1.70 version
- Windows XP SP2 Compatibility mode
It's getting further in the process than I've been able to get it the last 24 hours!
Standby....
bella92108 said:
Might have something here....
- HTC Sync Cable (the samsung one seems flakey so thought I'd give it a try)
- Odin3 1.70 version
- Windows XP SP2 Compatibility mode
It's getting further in the process than I've been able to get it the last 24 hours!
Standby....
Click to expand...
Click to collapse
Good! You using these Odin files or h8rift's?
gtg465x said:
Good! You using these Odin files or h8rift's?
Click to expand...
Click to collapse
These files, but with Odin3 1.70 not 1.81 ..... some users on others phones reported that 1.70 sometimes worked magic, so with each 1.81 fail I've been trying 1.70 just in case. But using your files provided for PIT, PDA, PHONE, CSC.
It hasn't moved for a it, still at about 85%... on dbadata.rfs now, which is further than I've ever gotten with this process tho... just watching it now.
Try a different Odin version too..I used 1.81 but the other two or three versions may do something different.
Sent from my SAMSUNG-SGH-I997 using XDA App
h8rift said:
Try a different Odin version too..I used 1.81 but the other two or three versions may do something different.
Sent from my SAMSUNG-SGH-I997 using XDA App
Click to expand...
Click to collapse
Seems I have better luck w\ 1.70, but still not accomplishing what I need :-(
Tried again, it failed out, but rebooted to Samsung Logo... lol... they're teasing me :-(
Ok, try this PDA file without dbdata. If it works it will be a miracle... and you will probably be running a different partition layout than stock lol.
http://www.multiupload.com/VI28Y3G8WY
gtg465x said:
Ok, try this PDA file without dbdata. If it works it will be a miracle... and you will probably be running a different partition layout than stock lol.
http://www.multiupload.com/VI28Y3G8WY
Click to expand...
Click to collapse
i dont think you can repartition without the dbdata file. i believe bella92108 had repartitioned. he may need dbdata.
@bella you may also try heimdall, there is a windows version, make sure you see what dependancies it has and that they are installed (drivers, visual c++ redistributable package....)
if you do need to repartition again (not sure that you will, just think you need dbdata and other files now) but, if you do, then only do it as an absolute last resort. you would need bootloaders to repartition in heimdall and the bootloaders are untested.
http://www.glassechidna.com.au/products/heimdall/
Dani897 said:
i dont think you can repartition without the dbdata file. i believe bella92108 had repartitioned. he may need dbdata.
@bella you may also try heimdall, there is a windows version, make sure you see what dependancies it has and that they are installed (drivers, visual c++ redistributable package....)
if you do need to repartition again (not sure that you will, just think you need dbdata and other files now) but, if you do, then only do it as an absolute last resort. you would need bootloaders to repartition in heimdall and the bootloaders are untested.
http://www.glassechidna.com.au/products/heimdall/
Click to expand...
Click to collapse
Problem is he's getting stuck at the dbdata file. I suspect our dbdata partition size does not match the Galaxy S PITs. He's already repartitioned now so no way to get back to stock partitions. Only thing he can do is try to get it working with the 512 PIT. Maybe I can grab a Galaxy S dbdata file and throw it in the package if Odin does indeed require that to be in there.
Bella is a SHE. How many guys would you know with a username like bella? Cmon now
well she didnt correct me, and it could be a last name.
hoofadoo said:
Bella is a SHE. How many guys would you know with a username like bella? Cmon now
Click to expand...
Click to collapse
http://www.belafleck.com/
So basicallly yesterday i tried rooting my sgs4g. I read the bible and the noob flash guide but some how i still messed up. Using super one click i was able to root the phone without any problems. I hooked the phone up to odin 1.7 and tried flashing one of the stock roms recommended in the noob guide to flashing but odin would not finish the flashing sequence and only states that the complete write operation failed. I was freaking out after about four hours and was literally trying tons of .tar files ive tried two from whitehawx off here the two from the noob guide aand no dice i dont know. i know the phone is in download mode i got that down yesterday lol but i still can not complete the flash. I have both 32 and 64 bit drivers installed on my computer but i cannot complete any type of flash. I can turn the phone on but it has no data and vibrates almost every ten seconds. It does say its still on 2.21 but baseband is unknown and kernal is stock i believe. i can pull the number when i get home. I am lost at this point im just tryilng to get back to stock or anything that makes the phone usable again. thanks in advance to any one who helps i wil donate...lol
alberto7939 said:
So basicallly yesterday i tried rooting my sgs4g. I read the bible and the noob flash guide but some how i still messed up. Using super one click i was able to root the phone without any problems. I hooked the phone up to odin 1.7 and tried flashing one of the stock roms recommended in the noob guide to flashing but odin would not finish the flashing sequence and only states that the complete write operation failed. I was freaking out after about four hours and was literally trying tons of .tar files ive tried two from whitehawx off here the two from the noob guide aand no dice i dont know. i know the phone is in download mode i got that down yesterday lol but i still can not complete the flash. I have both 32 and 64 bit drivers installed on my computer but i cannot complete any type of flash. I can turn the phone on but it has no data and vibrates almost every ten seconds. It does say its still on 2.21 but baseband is unknown and kernal is stock i believe. i can pull the number when i get home. I am lost at this point im just tryilng to get back to stock or anything that makes the phone usable again. thanks in advance to any one who helps i wil donate...lol
Click to expand...
Click to collapse
Start with the basics - a factory data reset. See if that helps.
Also, you should not have/need both 32-bit & 64-bit drivers on your PC. That potentially is a conflict within itself. What operating system are you on? If it's 32-bit, only have those drivers. If it's 64-bit, only use those. I'd uninstall them both and then reinstall a clean set based on your OS.
Look for ODIN 1.85. It's out here somewhere. I've had more luck with it than 1.7.
Let me know how things go with this. If you're not working after trying to go this route let us know and we'll push forward.
alberto7939 said:
So basicallly yesterday i tried rooting my sgs4g. I read the bible and the noob flash guide but some how i still messed up. Using super one click i was able to root the phone without any problems. I hooked the phone up to odin 1.7 and tried flashing one of the stock roms recommended in the noob guide to flashing but odin would not finish the flashing sequence and only states that the complete write operation failed. I was freaking out after about four hours and was literally trying tons of .tar files ive tried two from whitehawx off here the two from the noob guide aand no dice i dont know. i know the phone is in download mode i got that down yesterday lol but i still can not complete the flash. I have both 32 and 64 bit drivers installed on my computer but i cannot complete any type of flash. I can turn the phone on but it has no data and vibrates almost every ten seconds. It does say its still on 2.21 but baseband is unknown and kernal is stock i believe. i can pull the number when i get home. I am lost at this point im just tryilng to get back to stock or anything that makes the phone usable again. thanks in advance to any one who helps i wil donate...lol
Click to expand...
Click to collapse
Do you have multiple USB ports on your computer? Make sure you are plugged into one that goes directly to the CPU motherboard - one on the back. I have had issues trying to flash through USB ports that are on the front of a computer. Odin will recognize your phone, but it will freeze during flash. Just something to check.
I'm on windows 7. I have tried every usb on the laptop lol i've had a long time to try it out. So since I'm on windows 7 I should delete the 32 bit right? Thank both of you guys I'm on my way as we speak to fire up the laptop. I'll delete the drivers and search for the newer version of odin. Thank you guys again
alberto7939 said:
I'm on windows 7. I have tried every usb on the laptop lol i've had a long time to try it out. So since I'm on windows 7 I should delete the 32 bit right? Thank both of you guys I'm on my way as we speak to fire up the laptop. I'll delete the drivers and search for the newer version of odin. Thank you guys again
Click to expand...
Click to collapse
Not necessarily. Win7 can be either 32 or 64-bit. If you're not sure, right-click on your Computer/My Computer icon, and go to Properties. I believe it tells you there. I don't have a Win7 PC in front of me so I can't be 100%.
ok i am on 64bit windows.i deleted everything i downloaded yesterday so im starting from complete scratch i also downloaded odin 1.85. I am going to try to flash the .tar that is listed in the noob guide to oden from krylon 360 [ROM-ODIN]T959VUVKB5.
alberto7939 said:
ok i am on 64bit windows.i deleted everything i downloaded yesterday so im starting from complete scratch i also downloaded odin 1.85. I am going to try to flash the .tar that is listed in the noob guide to oden from krylon 360 [ROM-ODIN]T959VUVKB5.
Click to expand...
Click to collapse
Cool, let me know how it goes
do i have to change anything with the .pit file? im barely going to try the downloads from multiupload are taking really long lol
alberto7939 said:
do i have to change anything with the .pit file? im barely going to try the downloads from multiupload are taking really long lol
Click to expand...
Click to collapse
I haven't looked at the KB5 ROM. Does it come with multiple files (pit, pda, csc, phone)? If so, all you should have to do is put the files in the right slots in ODIN, don't mess with the check boxes, and flash it.
<ID:0/015> Added!!
<ID:0/015> Odin v.3 engine (ID:15)..
<ID:0/015> File analysis..
<ID:0/015> SetupConnection..
<ID:0/015> Initialzation..
<ID:0/015> Get PIT for mapping..
<ID:0/015> Firmware update start..
<ID:0/015> factoryfs.rfs
<ID:0/015> NAND Write Start!!
<ID:0/015> cache.rfs
<ID:0/015>
<ID:0/015> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
same thing:/
alberto7939 said:
<ID:0/015> Added!!
<ID:0/015> Odin v.3 engine (ID:15)..
<ID:0/015> File analysis..
<ID:0/015> SetupConnection..
<ID:0/015> Initialzation..
<ID:0/015> Get PIT for mapping..
<ID:0/015> Firmware update start..
<ID:0/015> factoryfs.rfs
<ID:0/015> NAND Write Start!!
<ID:0/015> cache.rfs
<ID:0/015>
<ID:0/015> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
same thing:/
Click to expand...
Click to collapse
Are you getting the phone into download mode?
i was...after that now i have the phone---!----computer logo. odin still reads it but that flash it had the yellow triangle with android inside it
i just tried again but
<ID:0/015> Odin v.3 engine (ID:15)..
<ID:0/015> File analysis..
<ID:0/015> SetupConnection..
<ID:0/015> Initialzation..
<ID:0/015> Get PIT for mapping..
<ID:0/015> Firmware update start..
<ID:0/015> factoryfs.rfs
<ID:0/015> NAND Write Start!!
<ID:0/015> cache.rfs
<ID:0/015>
<ID:0/015> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
What files are you using and where are you putting them?
Sent from my SGH-T959V using xda premium
I've never used KB5 before. What if you were to try something a bit more updated?
If you want to stay Froyo you can grab the stock KD1 from:
http://hotfile.com/dl/120929051/0ea3e13/T959VUVKD1.rar.html
IF you want to go Gingerbread, you can grab chadster's KG4 from:
http://forum.xda-developers.com/showthread.php?t=1183413
Like Exodian alluded to, you have to make sure you have the files in the right places. Let us know what you're doing. If you can snag a screen shot of ODIN and post it, that might help too.
T959VKB5-Custom (1) in the pda file
k i am downloading both
Yeah kg4 is better than froyo. Well, wifi excluded. Just make sure the files are in the correct spot.
Sent from my SGH-T959V using xda premium
alberto7939 said:
k i am downloading the kg4.
Click to expand...
Click to collapse
Cool. That was the first Gingerbread leak that came with the right boot loaders. What you're going to want to do is:
- Put CODE_T959VUVKG4_CL1385158_REV00_user_low_noship.tar.md5 into PDA
- Put hawk_Sidekick_VibrantPlus_831.pit into PIT
- Put SGH-T959V-CSC-TMB-VIBRANTP.tar.md5 into CSC
- Put T959VUVKG4-Phone-CL1037720.tar.md5 into Phone
Don't mess with any of the check boxes, and flash.
Let us know how it goes.
i will, sorry for the delay multiupload is taking forever today. thank you guys i should be able to try this in about 11 min
No rush on our part, man. Just hope you get it working.
Mission Accomplished!
Thanks to all in this thread.
Hi,
I am a idiot...
I have search all over this site and can not find a solution.
I tried rooting my Samsung Galaxy s2 Skyrocket
I used this link... http://galaxys2root.com/galaxy-s2-root/how-to-root-att-galaxy-s2-sgh-i777/#comment-496
After Oden Failed I was stuck in Download Mode.
After a bit it went to " Firmware Upgrade Encountered an issue. Please Select Recovery mode in Kies & try again."
Kies nor Oden recognize the phone anymore...
I came to realize I have a SGH-I727 ERRRR
Anyways I am stuck at this
"ODEN MODE
Product name: SGH-I727
Custom Binary Download: NO
Current Binary: Samsung Official
Firmware Upgrade Encountered an issue. Please Select Recovery mode in Kies & try again."
Is there anyway to get back to factory or root from here a proper way?
Congrats as you are the first victim.
Just wanted to say Congrats you are the first victim of the i777/i727 confusion.
My suggestion is to follow exactly what it tells you to do.
Download Kies 2.0
And hopefully you can recover
OR
Maybe you can just power off and power on the device and see if it will boot maybe Odin never got a chance to write anything.
Thanks
Well
I managed to Find different Kernal to use on Oden
Though its the Telus Kernal
I Need to get the I727 Factory Kernal....
so thats my issue Now ...
I can post a drop box link to the stock boot.img if you need it
Sent from my SAMSUNG-SGH-I727 using XDA App
YAY
That would seriously be awesome if you could
Its in a .TAR file correct?
and id use Oden 1.85 to use it?
playin4sheezy said:
I can post a drop box link to the stock boot.img if you need it
Sent from my SAMSUNG-SGH-I727 using XDA App
Click to expand...
Click to collapse
I unfortunately could use that link as well, however not for quite the same reason.
Sorry but will just be the actual boot.img
Not exactly sure how to make a ODIN tar but can attempt that real quick as well and post on here?
LINK FOR BOOT.IMG
***Working on Odin kernel tar as we speak***
playin4sheezy said:
Sorry but will just be the actual boot.img
Not exactly sure how to make a ODIN tar but can attempt that real quick as well and post on here?
LINK FOR BOOT.IMG
***Working on Odin kernel tar as we speak***
Click to expand...
Click to collapse
Kevin I'll make one when I get and I'll dropbox so you can test before I post it
Sent from my SGH-I777 using xda premium
jivy26 said:
Kevin I'll make one when I get and I'll dropbox so you can test before I post it
Sent from my SGH-I777 using xda premium
Click to expand...
Click to collapse
I ended getting it created myself just now. Thanks a lot though!
HERE IS THE i727 UCKJ2 STOCK KERNEL ODIN
***************MAKE SURE YOU HAVE THE CORRECT SAMSUNG DRIVERS INSTALLED********************
INSTRUCTIONS:
1. Extract the downloaded zip to your preferred folder
2. Go to the folder in which you extracted the zip to. Right-click ODIN3_v1.81.exe and left-click Run As Administrator <----------IMPORTANT
3. Turn off your phone or pull battery and put back in
4. Hold both of the volume keys and plug in the USB cable while still holding the volume keys
5. You will be prompted with needed input. This is now the correct time to make up your mind LOL
6. Open the ODIN window from which we earlier launched
7. Select PDA then browse to the file i727UCKJ2_STOCK_KERNEL.tar.md5
8. ENSURE THAT ONLY **AUTO REBOOT** & **F.RESET TIME** & OF COURSE **PDA(which you just clicked to select the kernel tar)** ARE CHECKED AND NOTHING ELSE
9. Now click START
10. Once the process has completed the phone will have rebooted and you should see "PASS" at the top-left of ODIN. YOU CAN NOW UNPLUG YOUR PHONE AND ENJOY THIS LOVELY STOCK KERNEL!!
****I HAVENT PERSONALLY TESTED THIS AS OF YET BECAUSE I AM AT HOME SO I CANNOT GUARANTEE IT WILL WORK****
I extracted the kernel from the boot.img, created the tar, created the md5 and zipped up the created kernel md5 tar with ODIN and there you have it.
Please give feedback after using it so I can ensure that all is well. ENJOY GUYS!
uh oh
Well Unfortunately it didn't work for me
I tried in both Oden 1.81 and 1.85
Got a Red Fail
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> zImage
<ID:0/008> NAND Write Start!!
<ID:0/008>
<ID:0/008> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Maybe you can't just "pull" the kernel off the rom.... but that's just me
t3chn0v1k1ng said:
Well Unfortunately it didn't work for me
I tried in both Oden 1.81 and 1.85
Got a Red Fail
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> zImage
<ID:0/008> NAND Write Start!!
<ID:0/008>
<ID:0/008> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Very sorry for the failure man. I have my skyrocket now so will be able to figure out what went wrong shortly.
Did you right-click Odin and run as administrator? Could be the culprit. Also I have double checked over the files, pulled kernel from my phone and compared to kernel used in my Odin and they are identical.... Reran the steps to create the Odin tar and file size matches the one already created ???? Wtf!!
Now i'm wondering if there is a specific version of Odin to be used with our phones because besides that i'm stumped at the moment. Any input?
Sent from my SAMSUNG-SGH-I727 using XDA App
t3chn0v1k1ng said:
Well Unfortunately it didn't work for me
I tried in both Oden 1.81 and 1.85
Got a Red Fail
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> zImage
<ID:0/008> NAND Write Start!!
<ID:0/008>
<ID:0/008> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Have you tried renaming i727UCKJ2_STOCK_KERNEL.tar.md5 to just i727UCKJ2_STOCK_KERNEL.tar and see if that works odin is trick is tricky like that
playin4sheezy said:
I ended getting it created myself just now. Thanks a lot though!
HERE IS THE i727 UCKJ2 STOCK KERNEL ODIN
***************MAKE SURE YOU HAVE THE CORRECT SAMSUNG DRIVERS INSTALLED********************
INSTRUCTIONS:
1. Extract the downloaded zip to your preferred folder
2. Go to the folder in which you extracted the zip to. Right-click ODIN3_v1.81.exe and left-click Run As Administrator <----------IMPORTANT
3. Turn off your phone or pull battery and put back in
4. Hold both of the volume keys and plug in the USB cable while still holding the volume keys
5. You will be prompted with needed input. This is now the correct time to make up your mind LOL
6. Open the ODIN window from which we earlier launched
7. Select PDA then browse to the file i727UCKJ2_STOCK_KERNEL.tar.md5
8. ENSURE THAT ONLY **AUTO REBOOT** & **F.RESET TIME** & OF COURSE **PDA(which you just clicked to select the kernel tar)** ARE CHECKED AND NOTHING ELSE
9. Now click START
10. Once the process has completed the phone will have rebooted and you should see "PASS" at the top-left of ODIN. YOU CAN NOW UNPLUG YOUR PHONE AND ENJOY THIS LOVELY STOCK KERNEL!!
****I HAVENT PERSONALLY TESTED THIS AS OF YET BECAUSE I AM AT HOME SO I CANNOT GUARANTEE IT WILL WORK****
I extracted the kernel from the boot.img, created the tar, created the md5 and zipped up the created kernel md5 tar with ODIN and there you have it.
Please give feedback after using it so I can ensure that all is well. ENJOY GUYS!
Click to expand...
Click to collapse
Did you build in ADB?
sfernandez said:
Have you tried renaming i727UCKJ2_STOCK_KERNEL.tar.md5 to just i727UCKJ2_STOCK_KERNEL.tar and see if that works odin is trick is tricky like that
Click to expand...
Click to collapse
OP did you try this and it work?
damn tough luck... but i guess you should have read more clearly that the post was for the I777 lol...hope you can get ur phone up and working...i wonder if theres a way you could flash the kernel via ADB, i know on MOTO you can access ADB before booting Android..Not sure if Samsung has a mode like that.
djkinetic said:
damn tough luck... but i guess you should have read more clearly that the post was for the I777 lol...hope you can get ur phone up and working...i wonder if theres a way you could flash the kernel via ADB, i know on MOTO you can access ADB before booting Android..Not sure if Samsung has a mode like that.
Click to expand...
Click to collapse
Yeah I know how it feels to jump the gun lol but ever since I bricked a captivate because lack of reading first, I make sure and read every word lol
You have to use the t-mobile sgs2 root method. There is a windows batch file that entire process so easy that I caveman could do it
Sent from my SAMSUNG-SGH-I727 using XDA App
Its always great to belittle our poke fun right? I feel if you can't help then don't post. Like its his fault the development section is located in a place that almost promotes this type of incident!
Sent from my SAMSUNG-SGH-I727 using Tapatalk
I personally rooted my SR long before the forum was established... I was probably the first one that did it, and the first to post my results in the I777 sections.
But unlike most people.. I DO READ and study all the possible facts...
I mean it sucks that he is stuck... but hey.. **** happens
As for helping we can only do so much as of what we have. Without a source code or/and a full original dump of the ROM.. it's really hard to "fix" a problem.
sfernandez said:
Have you tried renaming i727UCKJ2_STOCK_KERNEL.tar.md5 to just i727UCKJ2_STOCK_KERNEL.tar and see if that works odin is trick is tricky like that
Click to expand...
Click to collapse
Tried renaming still no luck.
Got it!
Tried the stock kernel that was just posted here
http://forum.xda-developers.com/showthread.php?p=19215598#post19215598
Worked using Oden 1.85
I am back to Factory with no issues
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.
im trying to downgrade my note 8 back to android 8 from the one ui closed beta, ive never been able to use my pc to flash my note 8 even though i have all of the correct drivers, ive reinstalled windows, used usb 2.0 ports i have flashed my phone using other peoples computers successfully but id like to make this work because i was able to flash my galaxy s7 just fine with the latest odin 3.13.1
these are the log files ive gotten
<ID:0/003> Odin engine v(ID:3.1301)..
<ID:0/003> File analysis..
<ID:0/003> Total Binary size: 6321 M
<ID:0/003> SetupConnection..(it just freezes here)]
or
<ID:0/004> Added!!
<ID:0/004> Odin engine v(ID:3.1301)..
<ID:0/004> File analysis..
<ID:0/004> Total Binary size: 6321 M
<ID:0/004> SetupConnection..
<OSM> All threads completed. (succeed 0 / failed 1)(it doesnt have the red FAIL message though which is weird)
Are you using the Mod version? HERE
Did you do a factory reset before trying to Odin back?
kangi26 said:
Are you using the Mod version? HERE
Did you do a factory reset before trying to Odin back?
Click to expand...
Click to collapse
I've used the modded version and it does the same thing, also I havent done a factory reset before trying to Odin back
I'm having the same issue, I cannot go back to CRK1. I have tried 2 different pc's, multiple versions of Odin. I factory reset my phone, still cannot go back to CRK1.
billdauterive23 said:
I've used the modded version and it does the same thing, also I havent done a factory reset before trying to Odin back
Click to expand...
Click to collapse
Did you get it to work? Same thing for me....
jimi_pooh said:
Did you get it to work? Same thing for me....
Click to expand...
Click to collapse
No, I dont know why it wont work because it worked on my s7 using the exact same version of Odin 3.13.1
I got mine back to CRK1 (sort of). I have an unlocked Note 8 (N950U1), I flashed the T-mobile firmware to my phone several months ago, so that made it an (N950U). I took the update last month from T-mobile (CRK1), then updated to the Pie beta DRL6. Upon trying to go back to the T-mobile firmware CRK1, I could not get it to flash with Odin, however something new happened that I had never seen before. My phone went into download mode, it looked normal, it failed in Odin. I held the volume down button and the power button to reboot the phone but it went into upload mode instead and had "unknown error" at the top of the screen. I held the volume down button and the power button and the phone rebooted and everything was still working as it should on the DRL6. No matter which Odin I tried, I had the same outcome. I finally brought my phone to uBreakiFix, after several attemps by them, they finally got it back to CRK1, with a full factory reset (I had done that already), but it was not the T-mobile firmware, it was the unlocked firmware (N950U1). I know that they attempted the T-mobile version first and it would not boot afterwards, that is when they installed the unlocked firmware.
billdauterive23 said:
No, I dont know why it wont work because it worked on my s7 using the exact same version of Odin 3.13.1
Click to expand...
Click to collapse
I ended up going back to CRJ3 then taking the Ota up to CRK1. Something was wrong with my csc file. Got a real error on another computer. Said Odin could not open the pit for CRK1.
billdauterive23 did u make it work. I am on the same boat as u. Cant downgrade back to crk1
d9700380 said:
billdauterive23 did u make it work. I am on the same boat as u. Cant downgrade back to crk1
Click to expand...
Click to collapse
I still haven't, it's not the biggest issue since my phone still works fine I just can't get updates and I was thinking of flashing my phone to the N950U1 firmware and get updates again and maybe at some point get android 9 if they decide to push the update at a decent time
Are u using windows 7 or windoes 10. I find out Odin doesnt like windows 10. If u have a computer with windows 7 try it
d9700380 said:
Are u using windows 7 or windoes 10. I find out Odin doesnt like windows 10. If u have a computer with windows 7 try it
Click to expand...
Click to collapse
I got rid of windows and switched to Ubuntu, I was already going to and I figured that it might fix my issue but I am still thinking about waiting to test but I think it will fix it as long as I can get it to detect my phone(still setting things up as of now) but I was using Windows 10 before and that very well could have been the problem.