Related
Hey guys,
Last night I looked at my phone (which had been on charge for a while) and noticed that it was on the first S3 boot screen. So I assumed it had crashed and got stuck whilst rebooting, so I held the power button to reset it.
Problem is, it came back to the same screen, except this time the black background of the image was distorted - lots of red/green/blue dots on it. So I tried again, and it came back even worse... The third time, it settled on a completely distorted image and is now seemingly stuck like that.
The phone isn't booting, so far as I can tell. If I try to boot to recovery, I just see the same screen. If I boot into download mode, it actually works - the screen is no longer corrupt and it responds to button presses. (Although itnerestingly if I continue to hold Home + Vol Down + Power once the download screen appears, then it does distort).
I have tried plugging it into my PC. I don't see it as a MTP device (no suprises there), and ADB can't find it. It is however recognised by odin. I tried flashing a stock rom via odin, but it complained that there was no PIT found. (Which if I understand if something to do with the partitioning of the device.
Any ideas on how to solve this? Should I find a PIT image for my phone and flash that and the ROM together?
For background, my phone is a i9305 and was running paranoid android (4.2, IIRC).
Dont touch pit
First flash stock rom via Odin
JJEgan said:
Dont touch pit
First flash stock rom via Odin
Click to expand...
Click to collapse
When I try that, I get the following error:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9305XXALI5_I9305EVRALI5_I9305BVALI5_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005>
<ID:0/005> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
That was why I was wondering about the PIT file.
I have also added some pictures (they're pretty low resolution, unfortunately). The first is what I see when I try to boot normally - lots of white and black bands (the yellow and purple you can see is just an artefact of my crappy webcam). The second image is download mode, where I continued to hold down the buttons after it loaded, causing it to reload with the corrupted image (again, this is a bit distorted by the webcam - the text and image aren't blurred).
no access to system and recovery,i doubt theonly way is download mode.just try an stock rom with pit files,agree that the issue have something to with the partition.if you have backup the whole system,even flash a new rom,youdata will be back easy and soon ,so nothing to worried and no way else to go,good luck.
Sent from my GT-I9305
As pit breaks more phones than it fixes its not recommended .
But your phone has no pit so you you have choices .
Warranty void so it would have to be a service repair .
Or you can try flashing a pit file yourself if it fails you will need to buy a new motherboard .
I´ve had the same Problem on my S1.
I Flashed a whole Package from Samsung Stock Firmware ( PIT MODEM PDA ) in Odin.
After that it worked again, i´ve needed some try´s but after that everythin was normal.
Darkangel 142
Darkangel142 said:
I´ve had the same Problem on my S1.
I Flashed a whole Package from Samsung Stock Firmware ( PIT MODEM PDA ) in Odin.
After that it worked again, i´ve needed some try´s but after that everythin was normal.
Darkangel 142
Click to expand...
Click to collapse
Do you mean specifically that you had the same error in odin, or that your S1 had the distorted screen too?
Well, I tried flashing the i9305 pit file and had no luck. The re-partitioning failed to start at all, so it didn't ruin the motherboard, at least.
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9305XXALI5_I9305EVRALI5_I9305BVALI5_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<ID:0/006> FAIL!
<ID:0/006>
<ID:0/006> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Back to orange/samsung it is!
Thanks for your suggestions/help, everyone.
Any joy?
Hi,
I've posted about the same problem. Completely stuck on who to deal with and can fix it How weird to have happened so close and exactly same with black screen then stuck on white, Wonder if others are out there.
Link: http://forum.xda-developers.com/showthread.php?t=2526821
stuck screen
i have the same problem with my s3 and i couldn't do the download mode. im planning to restore on stock rom but i don't know how to fix this issues.
thanks,
einjelhart said:
i have the same problem with my s3 and i couldn't do the download mode. im planning to restore on stock rom but i don't know how to fix this issues.
thanks,
Click to expand...
Click to collapse
Hi mate,
If you can't get in to Download Mode because of boot loop:
Try forcing it by holding all 3 buttons until it turns off, should come up.
Failing that, you can eBay Galaxy USB Jig that plugs in and forces Download Mode.
If you can get to Download Mode, I have written a solution to flash just the ROM.
You can read my solution by following the Link above your post
Have a great day!
-Shaz
Same problem with my s3 ,but Odin doesn't recognise my device ,please help
Debanshu bebartta said:
Same problem with my s3 ,but Odin doesn't recognise my device ,please help
Click to expand...
Click to collapse
I had these prob before; device not recognize in odin, distortion screen with colorful line, stuck at boot logo & splash screen.. I tried flash lot of thing possible to fix it but all fail. Suddenly everything working fine after changing new battery.. Lol. Or maybe im just lucky.
Sent from my GT-I9305 using XDA-Developers mobile app
Hello guys,
i'm new in the forum and this is my first entry.
I got quite a complicated situation with my phone... i try to describe this as good as possible.
My brother gave his old phone, a GT-I9070P with GB (v2.3.6) on it and i wanted to upgrade it to a newer firmware. Unfortunatly I haven't had an Android phone in a long time (2 years or so).
Nevertheless i wanted to upgrade it to 4.1.2 stock and use NFC (for programming a little bit).
I asked the father of a friend of mine to upgrade it because he has much more expirience with flashing and all that stuff ..
He said that this is no problem and after a few days he gave it back to me and told me that there were some difficulties but he did it.
Now i got my phone with JB 4.1.2 but when i tried it out, it didn't recognize the SIM card.
I gave it back to him and said, that the SIM wasn't working.
We found out that he flashed a I9070 stock and that the IMEI was "deleted" but he knows a guy how can fix this.
I read in a few forums about this problems and found out that this has got something to do with the modem (baseband / IMEI).
When i got my phone back, the SIM was recognized again.
But now i got a GT-I9070P with I9070 stock firmware (-> NFC not working)
Today i tried to flash two I9070P stock roms with Odin 3.09 but it didn't work out.
(I can post the LOG from Odin if you want)
When i flashed the I9070 stock again, it worked perfectly.
Sorry for the long post but now my actual question:
Is it possible to get a full functional I9070P with working NFC back on the phone?
(To be honest: i don't have any backups or /lib/tee - folders)
Thank you very much for helping me out!
cheers,
MonkeySon
MonkeySon said:
Hello guys,
i'm new in the forum and this is my first entry.
I got quite a complicated situation with my phone... i try to describe this as good as possible.
My brother gave his old phone, a GT-I9070P with GB (v2.3.6) on it and i wanted to upgrade it to a newer firmware. Unfortunatly I haven't had an Android phone in a long time (2 years or so).
Nevertheless i wanted to upgrade it to 4.1.2 stock and use NFC (for programming a little bit).
I asked the father of a friend of mine to upgrade it because he has much more expirience with flashing and all that stuff ..
He said that this is no problem and after a few days he gave it back to me and told me that there were some difficulties but he did it.
Now i got my phone with JB 4.1.2 but when i tried it out, it didn't recognize the SIM card.
I gave it back to him and said, that the SIM wasn't working.
We found out that he flashed a I9070 stock and that the IMEI was "deleted" but he knows a guy how can fix this.
I read in a few forums about this problems and found out that this has got something to do with the modem (baseband / IMEI).
When i got my phone back, the SIM was recognized again.
But now i got a GT-I9070P with I9070 stock firmware (-> NFC not working)
Today i tried to flash two I9070P stock roms with Odin 3.09 but it didn't work out.
(I can post the LOG from Odin if you want)
When i flashed the I9070 stock again, it worked perfectly.
Sorry for the long post but now my actual question:
Is it possible to get a full functional I9070P with working NFC back on the phone?
(To be honest: i don't have any backups or /lib/tee - folders)
Thank you very much for helping me out!
cheers,
MonkeySon
Click to expand...
Click to collapse
"But now i got a GT-I9070P with I9070 stock firmware" - your phone would be hardbricked if you flashed I9070 firmware on I9070P, so I suppose that is not the case. Did you try to do factory reset after flashing stock firmware for I9070. P.S. We do not have any custom ROM with NFC support as I know.
shut_down said:
"But now i got a GT-I9070P with I9070 stock firmware" - your phone would be hardbricked if you flashed I9070 firmware on I9070P, so I suppose that is not the case. Did you try to do factory reset after flashing stock firmware for I9070. P.S. We do not have any custom ROM with NFC support as I know.
Click to expand...
Click to collapse
Thank you for the quick response.
Hm... but this is exactly whats the case right now...
The back of the phone says "I9070P" and i have the backcover with the NFC "antenna" but the the device information says "Model: GT-I9070... Basebandversion: I9070XXLQG"
Okay, i will try that
But even if this works, wouldn't there the problem with the SIM-recognition again?
I know, that's the reason why i wanted to flash the newest stock rom.
I'd try to flash 9070P lib/tee/folder (use temporary recovery or flash any cocore kernel beforehand) - to be found here: http://forum.xda-developers.com/showthread.php?t=2191628 (use version for stock ROMs)
adamuadamu said:
I'd try to flash 9070P lib/tee/folder (use temporary recovery or flash any cocore kernel beforehand) - to be found here: http://forum.xda-developers.com/showthread.php?t=2191628 (use version for stock ROMs)
Click to expand...
Click to collapse
If i get it right you suggest:
- flash CoCore incl. recovery (for I9070)
- install the I9070P tee folder zip on my 9070 stock
What should theoretically happen then - would i be able to use NFC or flash the 9070P stock rom then?
But now i got a GT-I9070P with I9070 stock firmware (-> NFC not working)
Click to expand...
Click to collapse
Maybe the guy changed the board and you have i9070 without p/nfc ....
MonkeySon said:
If i get it right you suggest:
- flash CoCore incl. recovery (for I9070)
- install the I9070P tee folder zip on my 9070 stock
What should theoretically happen then - would i be able to use NFC or flash the 9070P stock rom then?
Click to expand...
Click to collapse
Try to flash cocore for I9070P as your phone is with NFC,then flash that tee folder zip and see if its working.If it is,download stock rom for P vesion from sammobile.com .I dont remember if flashing stock from there will increase count,but you can reset it later.
@shut_down
Now i did a factory reset after flashing the 9070 stock but i got the same error as before while flashing 9070P stock
@Tarola
Well this could possibly be but i don't think that, i trust them
@Force
Okey thanks, i will try that and report later
BTW: flashing stock also increases counter.
well, lets see..
i installed CoCore-EP-8.6-CWM - everything ok
installed 9070PJBlibteefolder.zip via recovery - no problem
restart the phone - restart to download mode and try to flash P rom.
Exact same error as before, in addition to that, the phone is now unable to read my SIM again
this is my Odin log if somebody is interested:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9070PXXLPJ_I9070PNRJLP2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Added!!
<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> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> cache.img.md5
<ID:0/004> NAND Write Start!!
<ID:0/004> hidden.img.md5
<ID:0/004> kernel.bin.md5
<ID:0/004> kernel2.bin.md5
<ID:0/004> normal.bin.md5
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
MonkeySon said:
well, lets see..
i installed CoCore-EP-8.6-CWM - everything ok
installed 9070PJBlibteefolder.zip via recovery - no problem
restart the phone - restart to download mode and try to flash P rom.
Exact same error as before, in addition to that, the phone is now unable to read my SIM again
this is my Odin log if somebody is interested:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9070PXXLPJ_I9070PNRJLP2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Added!!
<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> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> cache.img.md5
<ID:0/004> NAND Write Start!!
<ID:0/004> hidden.img.md5
<ID:0/004> kernel.bin.md5
<ID:0/004> kernel2.bin.md5
<ID:0/004> normal.bin.md5
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Odin does not complete instalation. It stuck at installing normal.bin.md5
shut_down said:
Odin does not complete instalation. It stuck at installing normal.bin.md5
Click to expand...
Click to collapse
yeah... but does anyone know why it stuck?
i don't think it would be the rom.. because this was the case with every 9070P rom i tried so far.
this whole thing is a little mystrey to me to be honest
EDIT:
I got my IMEI and SIM functionality back by flashing the 9070 stock again.
Just in case someone wants to know
I think i'm gonna ask the guy who did this for me how he achieved it, that the phone thinks its another model
MonkeySon said:
yeah... but does anyone know why it stuck?
i don't think it would be the rom.. because this was the case with every 9070P rom i tried so far.
this whole thing is a little mystrey to me to be honest
EDIT:
I got my IMEI and SIM functionality back by flashing the 9070 stock again.
Just in case someone wants to know
I think i'm gonna ask the guy who did this for me how he achieved it, that the phone thinks its another model
Click to expand...
Click to collapse
Only thing that I can tell you now is that you are lucky that your phone was not hardbricked.
Hi,
I've been searching the net and this forum for a fix, it seems like a few people have had the same issue as me, but either their post is unanswered or they say they've fixed it but never say how.
My phone one day went into a infinite loop of the Samsung Splash screen and I tried fixing it by googling the issue (Over 5 months ago) which may have caused more issues for my phone in the end. I remember entering recovery mode and wiping everything on the phone, then nothing I did could fix the thing.
So I just stopped touching it and left it to collect dust and used my old iPhone 3. My iPhone 3 is now broken and I've come back to my S3, so at the moment:
I can't enter recovery mode on my phone (It just won't start in recovery mode at all)
I CAN enter download mode
I've tried using ODIN (v3.09, 3.07, 1.85) and changing multiple USB ports and I was finally able to get my phone to show up on Odin.
I then downloaded the stock firmware from sammmobile website (It took forever to download) Which I made sure was the right model (GT-I9305) and Carrier (Optus, Australia)
Which is filename: I9305XXALI5_I9305OPSALI5_I9305XXALI5_HOME.tar.md5
I tried flashing that firmware with Odin (All 3 versions) [I reset the phone and Odin after every failed attempt]
and I would get this error:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9305XXALI5_I9305OPSALI5_I9305XXALI5_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003>
<ID:0/003> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
That was WITHOUT having a PIT file included and also the only things ticked were 'Auto Reboot' and 'F. Reset Time'.
Then I searched all over the internet and came across this PIT Partition file
the filename is: m3xx_i9305.pit
which I then used in the PIT section of Odin WITH and WITHOUT the previously mentioned Firmware and I would then get this:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9305XXALI5_I9305OPSALI5_I9305XXALI5_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
Click to expand...
Click to collapse
It would just sit on Get PIT for mapping for a very long time, longest I left it was an hour.
So I can't get it working that way, I also tried ADB Bootloading in the CMD prompt, but the device could never be found that way.
So after spending about 5 hours on this I'm resorting to just asking anyone on here for some help.
Thank you!
Phone Details:
Samsung Galaxy S3 GT-I9305
ODIN MODE:
Product Name: GT-I9305
Custom Binary Download: No
Current Binary: Samsung Official
System Status: Custom
Knox Warranty Void: 0
RP SWREV:
Computer Details:
Windows 8.1 Pro
Intel 2700k @ 3.5Ghz
16gb Ram
Samsung USB Drivers Installed
If there is any additional information required please let me know. This is my first time posting here, so If I did anything wrong please let me know.
Thank you.
Unkiejay said:
Hi,
I've been searching the net and this forum for a fix, it seems like a few people have had the same issue as me, but either their post is unanswered or they say they've fixed it but never say how.
My phone one day went into a infinite loop of the Samsung Splash screen and I tried fixing it by googling the issue (Over 5 months ago) which may have caused more issues for my phone in the end. I remember entering recovery mode and wiping everything on the phone, then nothing I did could fix the thing.
So I just stopped touching it and left it to collect dust and used my old iPhone 3. My iPhone 3 is now broken and I've come back to my S3, so at the moment:
I can't enter recovery mode on my phone (It just won't start in recovery mode at all)
I CAN enter download mode
I've tried using ODIN (v3.09, 3.07, 1.85) and changing multiple USB ports and I was finally able to get my phone to show up on Odin.
I then downloaded the stock firmware from sammmobile website (It took forever to download) Which I made sure was the right model (GT-I9305) and Carrier (Optus, Australia)
Which is filename: I9305XXALI5_I9305OPSALI5_I9305XXALI5_HOME.tar.md5
I tried flashing that firmware with Odin (All 3 versions) [I reset the phone and Odin after every failed attempt]
and I would get this error:
That was WITHOUT having a PIT file included and also the only things ticked were 'Auto Reboot' and 'F. Reset Time'.
Then I searched all over the internet and came across this PIT Partition file
the filename is: m3xx_i9305.pit
which I then used in the PIT section of Odin WITH and WITHOUT the previously mentioned Firmware and I would then get this:
It would just sit on Get PIT for mapping for a very long time, longest I left it was an hour.
So I can't get it working that way, I also tried ADB Bootloading in the CMD prompt, but the device could never be found that way.
So after spending about 5 hours on this I'm resorting to just asking anyone on here for some help.
Thank you!
Phone Details:
Samsung Galaxy S3 GT-I9305
ODIN MODE:
Product Name: GT-I9305
Custom Binary Download: No
Current Binary: Samsung Official
System Status: Custom
Knox Warranty Void: 0
RP SWREV:
Computer Details:
Windows 8.1 Pro
Intel 2700k @ 3.5Ghz
16gb Ram
Samsung USB Drivers Installed
If there is any additional information required please let me know. This is my first time posting here, so If I did anything wrong please let me know.
Thank you.
Click to expand...
Click to collapse
I've read you tried with different USB ports, OK, but did you try with a different USB cable when you use ODIN ? A brand new one ?
Wood Man said:
I've read you tried with different USB ports, OK, but did you try with a different USB cable when you use ODIN ? A brand new one ?
Click to expand...
Click to collapse
i am facing the same exact same probelm. i tried with different usb ports and cable results are the same . please someone help
:crying:
Hello!
Ok, I'll admit I didn't read closely enough in my haste to root my new phone, and now it's softbricked. My phone was brand new and still on the 5.0.2 firmware, and I tried to follow the guide at link here on XDA before updating to 5.1.1. After flashing the sboot.bin, it rebooted, but stuck at the Samsung logo screen with some green text at the top of the screen:
ASV TBL VER = 15
ASV TBL VER2 = 1285
ASV big:10 LITTLE:10 630:11 MIF:10 INT:10 CAM_DISP:10 (I think that's right, it's very tiny!)
I've been stuck there ever since! I can get into download mode, but that's it.
I'm not sure what to do now. I've tried reflashing the sboot.bin file, and I've tried flashing the 5.1.1 stock (COF8) ROM (which fails!)
Am I correct in thinking that the sboot.bin file will only boot 5.1.1 roms? If so, how do I get the ROM flashed if ODIN won't do it?
Any help will be greatly appreciated!
I've been thinking about this problem, and I've come up with two options. Either flash back to the original boot loader, kernel, etc. Or somehow get a stock 5.1 ROM to flash.
Any thoughts?
Sent from my (old) SGH-M919 using XDA Free mobile app
More info...
When I try to flash a 5.1 stock rom, I get the following output from Odin:
<ID:0/004> Added!
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Successfully..
<OSM> Leave CS..
<ID:0/004> Odin engine v(ID:3.1100)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialization..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> sboot.bin
<ID:0/004> NAND Write Start!
<ID:0/004>
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
FYI, the text in my download screen says:
ODIN MODE
PRODUCT NAME: SM-G920T
CURRENT BINARY: Custom
SYSTEM STATUS: Official
Secure Download: Enabled
KNOX WARRANTY VOID: 0 (0x0000)
RP SWREV: B:2 K:2 S:2
Does anyone know if T-mobile or Samsung could/would fix this, assuming I can't get it going in the next day or two?
thx.
SOLVED!
So for anyone else who finds yourself in this foolish situation, here is what worked *for me*.
The problem:
The newer sboot.bin wouldn't allow an older Android version to boot, and I couldn't Odin the newer COF6 or COF8 firmware.
The solution:
I downloaded and unzipped (technically un-tarred) the *STOCK COF8* firmware from Samsung (sammobile.com)
-To do that rename the file by removing the ".md5" extension. Yes Windows, we really do want to change the extension.
-If you don't have a program that recognizes the ".tar" extension, download PeaZip and install it - it's open source & awesome!
-Re-tar all of the files there *EXCEPT* for the sboot.bin.
-Boot into recovery as before, and open Odin - you should be a pro at this by now!
-Click the AP button and select the re-tarred stock firmware, and flash.
-Odin fails after a few files, but this is ok.
-Reboot and you should get a "failed update" error instead of the Samsung logo.
-Now Odin the *STOCK COF6* firmware
-Watch and thank God as it succeeds,and reboots ...normally
-Be patient, it still needs to update Android.
-Decide just how badly you need ROOT.....
Lovetoflyguy said:
SOLVED!
So for anyone else who finds yourself in this foolish situation, here is what worked *for me*.
.
Click to expand...
Click to collapse
You are a lifesaver. More specifically a $579 saver.
Lovetoflyguy said:
The solution:
I downloaded and unzipped (technically un-tarred) the *STOCK COF8* firmware from Samsung (sammobile.com)
-To do that rename the file by removing the ".md5" extension. Yes Windows, we really do want to change the extension.
-If you don't have a program that recognizes the ".tar" extension, download PeaZip and install it - it's open source & awesome!
-Re-tar all of the files there *EXCEPT* for the sboot.bin.
Click to expand...
Click to collapse
Scratch that. I used PeaZip instead of WinRar or 7Zip. I didn't name it tar.md5, flashed and it's booting up now. We'll see if it works.
How did you get the new tarball file you made to pass the MD5 check? I can't get past that check when I make a new .tar file or tar.md5.
Lovetoflyguy said:
SOLVED!
So for anyone else who finds yourself in this foolish situation, here is what worked *for me*.
The problem:
The newer sboot.bin wouldn't allow an older Android version to boot, and I couldn't Odin the newer COF6 or COF8 firmware.
The solution:
I downloaded and unzipped (technically un-tarred) the *STOCK COF8* firmware from Samsung (sammobile.com)
-To do that rename the file by removing the ".md5" extension. Yes Windows, we really do want to change the extension.
-If you don't have a program that recognizes the ".tar" extension, download PeaZip and install it - it's open source & awesome!
-Re-tar all of the files there *EXCEPT* for the sboot.bin.
-Boot into recovery as before, and open Odin - you should be a pro at this by now!
-Click the AP button and select the re-tarred stock firmware, and flash.
-Odin fails after a few files, but this is ok.
-Reboot and you should get a "failed update" error instead of the Samsung logo.
-Now Odin the *STOCK COF6* firmware
-Watch and thank God as it succeeds,and reboots ...normally
-Be patient, it still needs to update Android.
-Decide just how badly you need ROOT.....
Click to expand...
Click to collapse
i did everything you said but after (-Re-tar all of the files there *EXCEPT* for the sboot.bin.) step the new file was not recognized by odin.....any help???
IMP!!!! did you mean to flash odin from download mode or recovery mode because i've never heard of flashing odin from recovery mode
vegeta_badman said:
i did everything you said but after (-Re-tar all of the files there *EXCEPT* for the sboot.bin.) step the new file was not recognized by odin.....any help???
IMP!!!! did you mean to flash odin from download mode or recovery mode because i've never heard of flashing odin from recovery mode
Click to expand...
Click to collapse
Always!!!! flash Odin files in Download mode.
i did everything as u said it...But i can not flash the STOCK (COF6) in odin it fails..plz help:crying:
Lovetoflyguy said:
When I try to flash a 5.1 stock rom, I get the following output from Odin:
<ID:0/004> Added!
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Successfully..
<OSM> Leave CS..
<ID:0/004> Odin engine v(ID:3.1100)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialization..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> sboot.bin
<ID:0/004> NAND Write Start!
<ID:0/004>
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
FYI, the text in my download screen says:
ODIN MODE
PRODUCT NAME: SM-G920T
CURRENT BINARY: Custom
SYSTEM STATUS: Official
Secure Download: Enabled
KNOX WARRANTY VOID: 0 (0x0000)
RP SWREV: B:2 K:2 S:2
Does anyone know if T-mobile or Samsung could/would fix this, assuming I can't get it going in the next day or two?
thx.
Click to expand...
Click to collapse
how did you flash the firmware back to stock because i cant enter download mode:crying:
I recently screwed up my S5 active and am desperate for help.
I only ever really occasionally screw with the OS, and I did a poor job of documenting what I did with this phone, so I will do my best to recollect exactly the state.
The phone is an AT&T Samsung Galaxy S5 active, model G870A
The recovery was some kind of robot icon that would show for maybe ~10 seconds at the start of boot (not a regular android, more square). I've tried searching for it to, as yet, no avail.
I'm fairly certain that the image I put on the device was KoolKit_S5_Active_V1.1.0.
I cannot recall if I used safestrap, towelroot, twrp, or some combination of these in order to get the above on the device. I have copies of each sitting in a folder I created for the phone.
The other day, SuperSU said it needed the binary updated. Me, being dumb, wanting the notification to go away, decided to appease it. It asked if I wanted to do so using recovery. I figured this would be easier, so I clicked "yes". And then my life got a lot more stressful.
When the phone boots now, it goes into ODIN mode and displays the message "android could not do normal boot. ODIN MODE".
I cannot get it to any other screen. Recovery, download mode, whatever. (I'm pretty sure this is download mode, but I cannot initiate any mode, it just goes into this).
I've been poking around on these forums. The first suggestion I thought might work was to use ODIN to (re?) flash towelroot. Or TWRP. I forget which one I tried, but it wound up resulting in a failure in ODIN, and a message on the screen stating something along the lines of "sys rev check fail no version".
I am very confused about what I need to be flashing using ODIN, but I have managed to cobble together that it has to be through ODIN.
I don't necessarily need links, I can find those, and I may already have the files. I'd really like to know which files it is that I need.
Do I need a firmware? What is the file format for that? tar.md5? etc.
Ideally I'd just like to get back to a regular run mode where my worst problem was a wonky USB port. I would deeply appreciate it if anyone could get me in that direction.
Thank you
It's working.
I plugged it in, tried to flash a PIT file. That failed. Apparently one does not flash those alone.
The screen said something like "check failed : PIT" ...
I went here:
http://forum.xda-developers.com/showthread.php?t=2799754
Followed the instructions. Got a failure. (This was, stupidly and fortunately, without restarting phone after pit failure).
Phone rebooted like nothing was ever wrong.
ODIN log:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G870AUCU1ANE4_G870AATT1ANE4_G870AUCU1ANE4_HOME.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> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
<ID:0/005> Added!!
<ID:0/005> Removed!!
<ID:0/005> Added!!
Click to expand...
Click to collapse
P.S.: Previously unidentified robot was safestrap:
http://img.wonderhowto.com/img/96/6...hwiz-launcher-your-samsung-galaxy-s5.w654.jpg
Im glad you could fix it.
I also have a problem with a AT&T S5 active, the phone has horrible screen lag (even the booting screen is slow)
I tried doing a factory reset and also doing a downgrade to kit-kat using Odin, but the problem persists