So, I had an old S4, decided using it, worked for a couple weeks, then it just wouldn't turn on.
I'm far from being an expert, I did some research and I understand that its "soft bricked" (not hard bricked, phew!)
It starts, you see the "Samsung Galaxy S4 i9500" screen, and then just turns off.
If I try the recovery boot menu, it wont work, it'll just have the "Downloading, dont turn off target" screen, without the Odin mode, and if I try the download boot, it'll go into the odin mode, which is fine and it's supposed to happen, right?
The thing is when I go to Odin, and try to install the stock firmware, I've tried with and without a PIT file, I've tried with three different USB cords, on two different computers, with three different versions of Odin and with and without the WinXP compatibility mode ON and OFF. I've checked and unchecked the "auto reboot" and "f reset time" boxes, and I've never touched the other boxes (like nand and flash and led)
Odin will always recognize my phone, which is awesome, I always see the message "Added!"
Once I run Odin, which by the way is a picky a** motherf****, it'll stay stuck always here
""There is no PIT partition""
And also it has gotten stuck here
"Complete(Write) operation failed."
"Get pit for mapping (this was the most frequent one until I just always got the first one)"
"SetupConnection.."
This is getting extremely annoying.
I am almost positive I have the correct stock firmware, I got it from the samsung-updates.com website I downloaded the 5.0.1 version, I am curently downloading the 4.4.2 version, just to see what happens.
I do not know what the hell is a PIT file, I am using an "adonis" whatever that I found on some forum.
I also tried to "install" the recovery menu, with a "Philz Touch" TAR MD5 file I found, but I have no idea what that is (also, it didn't work)
Just to double check with you, its a Samsung Galaxy S4 i9500, I do not know which version of android was running, also, i do not know if USB debugging is on or off.
PLEASE HELP!
Product Name: GT-i9500
Current Binary: Samsung Official
System Status: Official
Knox Warranty Void: 0
AP SWREV: A3
Related
I recently used Odin to update to froyo 2.2 from my eclair 2.1, and it "pass"ed but now my phone goes into recovery mode. Boot screen then recovery, even when its off and begins charging goes straight to recovery.
At recovery it says:
"update media, please wait
E: Cant mount /dev/block/mmcblk0p1
(Invalid argument)
E;copy_dbdata_media: Cant mount SDCARD:
your storage not prepared yet. please usee UI menu for format and reboot"
But UI menu doesnt work, doesnt let me select anything, and download mode wont load so Odin gets stuck at "Setup Connection".
Help?
Thanks!
- try different versions of Odin's this is the most common issue.
- Make sure your using the correct Eclair 2.1 files the ones by Eugene the unbrickable one.
Mostly, try a different ODIN, and the one that works, don't switch from it.
Odin is the only thing keeping my phone good as new, and i dont need any updates on that.
xrider is correct, I would recommend the 1.7 Odin. You can then Odin back by first flashing Eugenes Froyo that does not brick, then back to JFD2.1
you can get all you need in the Stickies
From there you can root and then flash away
good luck,
Thanks for the replys.
But for Odin to work, wouldn't the device need to be in Download Mode? Which would explain why it doesn't go beyond "SetupConnection". I used the same Eclair rom as I did for my previous recovery. But it fails now, I also tried different versions of Odin from 1.0 to 1.7. Oh an Odin recognizes my phone as a COM6, if that means anything.
I might just go ahead and call Tmo and get a new one. I still have insurance and a warranty.
Hmmm...
Dark619Cloud said:
Thanks for the replys.
But for Odin to work, wouldn't the device need to be in Download Mode? Which would explain why it doesn't go beyond "SetupConnection". I used the same Eclair rom as I did for my previous recovery. But it fails now, I also tried different versions of Odin from 1.0 to 1.7. Oh an Odin recognizes my phone as a COM6, if that means anything.
I might just go ahead and call Tmo and get a new one. I still have insurance and a warranty.
Hmmm...
Click to expand...
Click to collapse
Wait, if you can't get into Download mode, then how are you getting COM6 on ODIN?
I have no idea. Phone just sits in recovery, I plug in USB and it says
<ID:0/006> Added!!
But when I try flashing anything, it stays at SetupConnection.
When I WAS able to get into download mode, it was COM8.
Wait for more replies, idk the solution. Sorry
Maybe new version of odin?
I really appreciate your help though.
I think it's just bricked. The froyo which I had updated to was probably faulty, causing this to occur. I mean, even the recovery menu is messed up. Up and down are inverted, and power button does nothing. Phone doesn't show charging screen(well it does for a second then go straight to recovery).
I'll just call T-mobile tomorrow. I wouldn't get charged right? I tried updating to THEIR firmware, had they made it OTA this wouldn't have occurred, right?
The fact it sees com 6 or com8 or com 4 really isn't important, sometime mine say com2 sometimes it say 6......... this is unimportant.
Follow this ...this should work, the only other thing I can think of is to get into factory recovery and wipe, cache, and memory, go into advanced and wipe the dalvik, then back to Odin and perform the following:
1. Odin 1.3 or higher I use 1.7 but not real important
2. Have the original JFD Vibrant rom
3. You will need the .pit file (this is for mapping)
4. You will Eugene froyo that does not brick rom.
The order is as follows:
1. Download Eugenes 'Froyo that does not brick' file.
2. Extract the files.
3. Open Odin, plug in your phone, then put it into download mode.
4. load the PIT file in appropriate area.
5. load the .tar file in the PDA area.
6. DO NOT check 're-partition'.
7. Click start, let it finish. Your phone will load and reboot into stock recovery. It will error out again. DONT panic! This is what's supposed to happen.
8. Now, pull your battery.
9. Download the 'True stock 2.1 firmware for the vibrant'.
10. Extract the files.
11. Once again, open Odin, plug in your phone, put into download mode.
12. Load the PIT file into the appropriate area and the .tar in the PDA area.
13. THIS TIME you want to check the 're-partition' box.
14. Now click start, let it finish, and this time your phone will load up just fine! You will have flashed back to the original software. From there, you can do anything !!!
Next root the phone if you are confused about this go to youtube and look up the video by unlocker.com they do a great job showing how it is done.
After all this you can now flash a new rom.
The reason he's getting a COM port without being in D/L mode is because of the secondary bootloader in the sbl.bin. You may just be able to flash JI6.tar without a pit file and get past the Setup Connection
Whoa, nice feedback.
Downloading both Eugenes "Froyo that does not brick" and the JI6.tar.
Will try both methods and reedit my post.
Thanks a lot.
I can't press "Thanks" more than 5 times a day...
UPDATE:
Eh still nothing...Odin gets stuck at SetupConnection.
I believe this will persist until I find a way into download mode. Odin recognizes phone, hence the COM6, but doesn't fully connect since it does not go beyond SetupConnection. The recovery menu also isn't functioning properly, since I can't select anything.
Losing patience with this phone...
I called T-mobile and their sending in a new one.
Told them I was updating and this happened. Do you think I'll get charged?
Well, while you still got time with it...try a different version of ODIN and see if that works... 1.0, 1.3 or 1.7 dunno if there are more
All three versions get stuck at SetupConnection.
I looked into making a JIG, but I only have one USB cord and don't wanna go through the hassle. A JIG would put my phone into download mode, right? Even though it's not really bricked, just completely messed up.
Just now I was messing around with phone, and I got to a different screen!
RST_STAT = 0x1
PMIC_IRQ1 = 0x0
(and some other stuff like that)
Then " POWER RESET OR UNKOWN UPLOAD MODE"
It shows up as COM7 in ODIN But still stuck at SetupCOnnection...grrr
I FIXED IT.
I got the android SDK, and did "adb reboot" which rebooted the phone, and I have froyo and everything.
But ONE problem. T-mobile is sending me a new phone already....what the hell do I do? I can't send this one in, because it's working now.
Nevermind, everytime I rebooted phone it stayed in recovery and I had to always do "adb reboot".
So I did abd reboot download which took me into download mode, but ODIN still stayed at SetupConnection, i took out battery, now I have the indigenous PHONE ! PC error.
NOW I HAVE NO POSSIBLE WAY TO GET INTO DOWNLOAD MODE, Nor have adb connect to phone. No devices are shown when I do "adb devices".
I also tried every variation to get into DL mode, USB, VOl +/-, Battery...etc. Now I think the phone is completely bricked, honestly.
Dark619Cloud said:
I FIXED IT.
I got the android SDK, and did "adb reboot" which rebooted the phone, and I have froyo and everything.
But ONE problem. T-mobile is sending me a new phone already....what the hell do I do? I can't send this one in, because it's working now.
Nevermind, everytime I rebooted phone it stayed in recovery and I had to always do "adb reboot".
So I did abd reboot download which took me into download mode, but ODIN still stayed at SetupConnection, i took out battery, now I have the indigenous PHONE ! PC error.
NOW I HAVE NO POSSIBLE WAY TO GET INTO DOWNLOAD MODE, Nor have adb connect to phone. No devices are shown when I do "adb devices".
I also tried every variation to get into DL mode, USB, VOl +/-, Battery...etc. Now I think the phone is completely bricked, honestly.
Click to expand...
Click to collapse
if you look at ODIN while you plug the phone in with that screen you'll notice it giving you a COM port....weird...but you can still ODIN the phone while on that screen. Flash back to JFD from there.
Yeah I know ODIN should recognize it, because it happened before and it did. But this time it's not. I tried different versions of ODIN as well.
tsk tsk ;P lol
u fixed it? or it remains broken ?
I did fix it, partially. It loaded and everything, but sound wasn't working, and volume rocker was inverted, I guess the rom I flashed was corrupted. So I did "adb reboot download" which took me to download mode to go back to JFD stock, and I did ODIN and everything but it stayed at SetupConnection again. I removed battery to put in download mode manually, and now it's bricked. PHONE /!\ PC. PC doesn't recognize it, and I tried every combo to get into download mode.
So no, it's not fixed.
I tried to flash STOCK ROM. In first attempt, Odin messaged failed. Then I again tried it. Now All thing goes smooth. But when phone is restarted, It doesn't installs anything. And opposite of it shows only samsung vibrant and goes black. I did this couple of time but always same thing.
Now, when I charge phone then it shows up big grey change sign(not green status inside) in loop. And If I press power button, phone shows samsung vibrant and goes black.
After unsuccessful attempt with ODIN, I tried with heimdall. But Heimdall always complains "Failed to detect compatible download-mode device."
Is my vibrant is Hard Bricked. Phone could be sent to download mode by removing battery, holding UP + Down, plugin USB and adding battery back. But Could not go to recovery mode.
Are you sure you used BOTH of the CORRECT files in Odin?
I approve this message.
Try the Tar and Pit from here: http://forum.xda-developers.com/showthread.php?t=1319802
Hello, my phone is apparently soft bricked and stuck on the Samsung logo. I am trying to follow ATT's instructions on how to perform a master reset. These are the instructions I am following:
1. Power off the device.
NOTE: If unable to power off, remove and reinsert the battery.
2. Press and hold the Volume Up + Volume Down and Power key.
3. Release ONLY Power Key when Samsung Logo appears.
4. Use Volume Up and Volume Down to scroll down to "Wipe data/factory reset", and then press Power key to confirm to delete all the user data.
5. Scroll down to "Yes! delete all user data" and press the Power key to confirm.
6. When "Data wipe complete" is displayed, select "Reboot system now" and press Power key to confirm to reboot your handset.
Problem is, when I reach step 3, I get an animated Android with some blue thing in it's belly that spins faster and faster until the Samsung Galaxy SII logo appears and gets stuck again.
I've attached an image of the logo I am seeing.
I'm probably doing something stupid. Anyone have any ideas
EDIT: The phone is completely stock. Not rooted, no ROMS, etc
As far as I can remember, that logo comes with custom recovery but not the stock recovery. What firmware is installed on the phone?
Basically, you are not able to boot into recovery. You should try again, holding down all three keys, vol+ vol- pwr, until: the Galaxy SII logo appears, screen goes black, Galaxy SII logo appears again. Then release all three buttons. Recovery should come up within a few seconds.
If you are unable to get into recovery, you will need to re-flash the stock firmware using Odin. We can guide you through the process if you are unfamiliar with it.
Hi CreepynCrawly. I tried the three button salute, hold down until you see the logo twice thing but it always goes to the animation. No menu! Tried more than just a few times, thinking I was fat fingering something.
So, I gave up and I took the flash to stock firmware route. My phone is at Android version is 4.1.2 and baseband I777UCMD8.
I downloaded Odin 3.0.9 and the stock firmware from Sammobile . It fails when it attempts to write the sbl.bin. (see attached). I've tried a few times and two different machines. I also tried doing a restore from Kies (installed the USB drivers along with it). Should I just keep trying? Seems like some people had success with that (although I don't understand why).
creepyncrawly said:
As far as I can remember, that logo comes with custom recovery but not the stock recovery. What firmware is installed on the phone?
Basically, you are not able to boot into recovery. You should try again, holding down all three keys, vol+ vol- pwr, until: the Galaxy SII logo appears, screen goes black, Galaxy SII logo appears again. Then release all three buttons. Recovery should come up within a few seconds.
If you are unable to get into recovery, you will need to re-flash the stock firmware using Odin. We can guide you through the process if you are unfamiliar with it.
Click to expand...
Click to collapse
I think we need to use Odin 1.8.5 for our device... don't quote me though. You could try that instead
badger109 said:
I think we need to use Odin 1.8.5 for our device... don't quote me though. You could try that instead
Click to expand...
Click to collapse
Thanks Badger, I tried it, but it seems to just hang. I wonder if it is a hardware issue. It just "happened" that way. Had it in my bag. Took it out, and there it was, all soft bricked and what-not with the Samsung logo. Had not installed anything whatsoever in the past few days.
3 months to go before I can upgrade. I can live with my Captivate 'til then I guess.
This sounds like it could be a case of nand read/write corruption. The fix is fairly specific. And it is recommended to use Odin version 1.85 for this phone, although any version of Odin should work (in theory.) There have been some reports where newer versions of Odin did not.
Since you currently have UCMD8, you will be changing to an earlier version of the os during this procedure, so you will need to perform a wipe data/factory reset from within recovery after step 2 before the phone will boot. Please follow the steps in order and exactly.
1)Go to this post and download the Tar version of Siyah 2.6.14 Kernel. Flash it in the PDA slot without ticking Re-Partitioning. If you get a pass, it won't boot, so turn the phone off and then back to download mode and...
2) Flash the full stock Gingerbread distribution from the Download Repository, I777UCKH7 including the bootloaders and everything, in the PDA slot.
3) If you get a pass here, then the phone might boot, or you might have to boot into recovery first and perform a wipe data/factory reset. If you're able to boot the phone, then you are back in business, and can flash whatever firmware you want.
If it is not, then:
4) Download the SBL Bootloader from the Download Repository. Flash it as PDA in ODIN, without ticking Re-Partitioning.
5) Flash the Kernel, as in step 1.
6) Flash the full stock Gingerbread distribution, as in step 2.
erponsha maniacal
Hi CreepynCrawly, I started on your suggestion, but I cannot get past the kernel update. The green progress bar in Odin goes green and then just sits there with "NAND Write Start!!!". I let it sit for 30 minutes the first time, and then I tried with different versions of Odin - 1.3, 3.09, etc...no go. Found an article on here about a similar issue and went through the checklist - different USB ports, different computers, different cables, Odin version, etc, etc...not much success. The download count has increased though, and "Current Binary" says "Custom" on the phone. Any ideas from here on would be great, because my Captivate is kind of sad comparatively speaking .
[EDIT]: I've also tried flashing the SBL from the Download Repository - same issue. It sticks at "NAND Write Start!!"
creepyncrawly said:
This sounds like it could be a case of nand read/write corruption. The fix is fairly specific. And it is recommended to use Odin version 1.85 for this phone, although any version of Odin should work (in theory.) There have been some reports where newer versions of Odin did not.
Since you currently have UCMD8, you will be changing to an earlier version of the os during this procedure, so you will need to perform a wipe data/factory reset from within recovery after step 2 before the phone will boot. Please follow the steps in order and exactly.
1)Go to this post and download the Tar version of Siyah 2.6.14 Kernel. Flash it in the PDA slot without ticking Re-Partitioning. If you get a pass, it won't boot, so turn the phone off and then back to download mode and...
2) Flash the full stock Gingerbread distribution from the Download Repository, I777UCKH7 including the bootloaders and everything, in the PDA slot.
3) If you get a pass here, then the phone might boot, or you might have to boot into recovery first and perform a wipe data/factory reset. If you're able to boot the phone, then you are back in business, and can flash whatever firmware you want.
If it is not, then:
4) Download the SBL Bootloader from the Download Repository. Flash it as PDA in ODIN, without ticking Re-Partitioning.
5) Flash the Kernel, as in step 1.
6) Flash the full stock Gingerbread distribution, as in step 2.
Click to expand...
Click to collapse
Yeah, my wife is still using my old captivate. I just bought her an SII on Swappa, so once I get her new phone set up for her, I'll be selling her captivate.
If steps 1 - 3 didn't work, you should proceed to steps 4 - 6. Loading the secondary bootloader first may allow the kernel to flash, followed by a successful system flash. Try it out and let us know.
The flash counter is really irrelevant now that the phone is out of warranty, but it can be dealt with later once the phone is booting normally. Completing the process will remove the yellow triangle warning boot screen.
Yup - Step 4 hangs - green progress bar and then "NAND Write Start!!" and then...nothing! It just sits there. Am I toast or what?
creepyncrawly said:
Yeah, my wife is still using my old captivate. I just bought her an SII on Swappa, so once I get her new phone set up for her, I'll be selling her captivate.
If steps 1 - 3 didn't work, you should proceed to steps 4 - 6. Loading the secondary bootloader first may allow the kernel to flash, followed by a successful system flash. Try it out and let us know.
The flash counter is really irrelevant now that the phone is out of warranty, but it can be dealt with later once the phone is booting normally. Completing the process will remove the yellow triangle warning boot screen.
Click to expand...
Click to collapse
The common understanding is that if the phone can boot into download mode, it can be recovered to working. This would be true in all but a few rare cases of partial emmc memory damage. I would still assume that your phone can be made to work again.
Please view this post in another thread. I'm not familiar with "hg42's 120824-151927-emmc_find_brick_start.zip" but it would be worth the time to find this file and try it to see what it reports.
There are a large variety of things that can prevent Odin from completing. You need to do some research, and try all the possible issues, but just off the top of my head, it could be due to the cable, the usb port on the computer, the usb port on the phone, the usb driver on the computer, etc. So, try different cables - a Samsung original usb cable is best, try different ports on the computer, try a different computer, reinstall the usb driver, etc.
I have huge problem with my SM-T813. The FRP lock is on; after it receives automatic Samsung software update it cannot boot. It stuck on "Samsung Galaxy Tab S2 Powered by Android" and then it turns off. It cannot go to Recovery Booting (to go back factory reset) ... well after "Recovery Booting" appears, "Installing system update" appears for 20 seconds then it turns off. It can go to Download Mode, however when I try to flash the Stock ROM (.tar or .tar.md5 files downloaded from Sammobile) with Odin, well I have tried many many times the result is always failure. Written in red: "SECURE CHECK FAIL: recovery. Blocked by FRP Lock." I tried to flash the hidden.img.tar with Odin3, on Odin3 "PASS" but in reality my SM-T813 is still facing the exact same problem after this flashing. What should I do, please help. Than you very much.
dama0002 said:
I have huge problem with my SM-T813. The FRP lock is on; after it receives automatic Samsung software update it cannot boot. It stuck on "Samsung Galaxy Tab S2 Powered by Android" and then it turns off. It cannot go to Recovery Booting (to go back factory reset) ... well after "Recovery Booting" appears, "Installing system update" appears for 20 seconds then it turns off. It can go to Download Mode, however when I try to flash the Stock ROM (.tar or .tar.md5 files downloaded from Sammobile) with Odin, well I have tried many many times the result is always failure. Written in red: "SECURE CHECK FAIL: recovery. Blocked by FRP Lock." I tried to flash the hidden.img.tar with Odin3, on Odin3 "PASS" but in reality my SM-T813 is still facing the exact same problem after this flashing. What should I do, please help. Than you very much.
Click to expand...
Click to collapse
Try to obtain your device pit file
And then reparation your device through Odin and fish back your stock rom
Not that easy, mate. I had tried it 10 times and always failed. The FRP lock blocks it and almost everything else.
dama0002 said:
I have huge problem with my SM-T813. The FRP lock is on; after it receives automatic Samsung software update it cannot boot. It stuck on "Samsung Galaxy Tab S2 Powered by Android" and then it turns off. It cannot go to Recovery Booting (to go back factory reset) ... well after "Recovery Booting" appears, "Installing system update" appears for 20 seconds then it turns off. It can go to Download Mode, however when I try to flash the Stock ROM (.tar or .tar.md5 files downloaded from Sammobile) with Odin, well I have tried many many times the result is always failure. Written in red: "SECURE CHECK FAIL: recovery. Blocked by FRP Lock." I tried to flash the hidden.img.tar with Odin3, on Odin3 "PASS" but in reality my SM-T813 is still facing the exact same problem after this flashing. What should I do, please help. Than you very much.
Click to expand...
Click to collapse
Try to boot to download mode
and flash your stock rom via samsung odin
I have a very exaggerated problem for this device, the first time I gave Stock ROM through Download Mode, it started, I went to lunch, when I came back he had given a (Blocked Writing) error in the middle of the process, now at that moment I know how to solve this problem, but as I did not know, I tried to flash ROM again in Odin, and every time I was locking in aboot.mbn, after several attempts, several different computers, different USB cables ... different tests, now in this exact Odin crashes in Initialization, does not leave there for nothing, leave a long time it says that the device did not respond, I tried to reestablish the PIT that is the Partition Table using Odin, however it hangs anyway in initialization, I researched a lot, I tried Unbrick methods through files on SD Card, tried several Rom Stock and also tried to install a Custom Recovery, however everything fails, after all, in all cases it crashes in initialization, hey sso not only happens in a single System, then I decreed this cell phone as deceased .. the ****ing thing died, I saw in some places that they said that the problem was Hard Brick, that is to say, problem in the motherboard parts, and the solution would be change the motherboard of the entire device, but this is very expensive ...
Sansung Kies is only connecting and after a while he says that the device did not respond, if I turn the phone on, and do nothing, it goes to a Download screen only instead of the green android in the middle, a message appears talking to do Firmware Upgrade using Sansung Kies, and if I hold the buttons to enter the recovery mode, nothing happens and it's the same thing to turn it on normally, and if I hold the Download Mode buttons, it goes into Download Mode normally only in both cases Odin locks in initialization ..
Model: Samsung GT-I9192 Galaxy S4 Mini Duos