Database Info

[Q] Possible brick

Hello here is a detailed description of what I did to get my phone in this state of possible brick. Sorry if this does not belong in Q&A.
-I was on GummyCharged 1.8
-I followed the guide on How to get on GummyCharged GBE 1.9RC2.3 with lagfix/EXT4. I did all the steps but in the end, ext4 was not displayed in any of the partitions. I could not enable it through Recovery (even when I pressed "enable lagfix," it still said voodoo was disabled on next boot) and through Voodoo (it did not show status of anything including rfs or ext4).
-So I redid all the steps starting from step 1. This time, everything actually worked on the first boot.
-I rebooted my phone once and the mobile data could not connect.
-I rebooted again and it still couldn't connected. I connected to wifi to see if that was a problem but there was none.
-I thought it could've been a problem with the EP1Q modem so I went to download mode and tried to Odin the EP1Q modem.
-Odin said it failed and now my phone wouldn't boot. I got this image when I tried to boot it with my battery inserted and everything (image attached)
-Now I can't get into download mode. Odin can't detect my phone unless the battery is inserted. And even if the battery is inserted, my phone displays the battery being charged and not the download mode and triangle. (image attached)
- I tried using the guide [HOW-TO]Fix your phone and used GummyCharged 1.8 and GummyCharged FE 1.9.1 full Odin in replace of ED2. Odin can detect it when I'm not in downloading mode and I get the battery charging image (image attached). I tried flashing it but it stays stuck at SetupConnection for more than 10 minutes and stays stuck at the battery image.
<ID:0/010> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> GummyCharged_GBE_1.8_Full_Odin.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/010> Odin v.3 engine (ID:10)..
<ID:0/010> File analysis..
<ID:0/010> SetupConnection..
I'm not sure what other way I can fix this. I was wondering if I did something wrong when I flashed the EP1Q modem. Any help is appreciated thanks!

l0lz0rss said:
Hello here is a detailed description of what I did to get my phone in this state of possible brick. Sorry if this does not belong in Q&A.
-I was on GummyCharged 1.8
-I followed the guide on How to get on GummyCharged GBE 1.9RC2.3 with lagfix/EXT4. I did all the steps but in the end, ext4 was not displayed in any of the partitions. I could not enable it through Recovery (even when I pressed "enable lagfix," it still said voodoo was disabled on next boot) and through Voodoo (it did not show status of anything including rfs or ext4).
-So I redid all the steps starting from step 1. This time, everything actually worked on the first boot.
-I rebooted my phone once and the mobile data could not connect.
-I rebooted again and it still couldn't connected. I connected to wifi to see if that was a problem but there was none.
-I thought it could've been a problem with the EP1Q modem so I went to download mode and tried to Odin the EP1Q modem.
-Odin said it failed and now my phone wouldn't boot. I got this image when I tried to boot it with my battery inserted and everything (image attached)
-Now I can't get into download mode. Odin can't detect my phone unless the battery is inserted. And even if the battery is inserted, my phone displays the battery being charged and not the download mode and triangle. (image attached)
- I tried using the guide [HOW-TO]Fix your phone and used GummyCharged 1.8 and GummyCharged FE 1.9.1 full Odin in replace of ED2. Odin can detect it when I'm not in downloading mode and I get the battery charging image (image attached). I tried flashing it but it stays stuck at SetupConnection for more than 10 minutes and stays stuck at the battery image.
<ID:0/010> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> GummyCharged_GBE_1.8_Full_Odin.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/010> Odin v.3 engine (ID:10)..
<ID:0/010> File analysis..
<ID:0/010> SetupConnection..
I'm not sure what other way I can fix this. I was wondering if I did something wrong when I flashed the EP1Q modem. Any help is appreciated thanks!
Click to expand...
Click to collapse
Well first of all don't use CWM to enable/disable voodoo or to check as it doesn't work/report it correctly.. Second of all I wouldn't try and flash something on to the phone if its not in download mode, that sounds like your problem right there when it comes to stalling at 'SetupConnection'. As for the failed modem flash its not a huge deal I don't think (something the phone can recover from) and I would reinstall the phone drivers, try and get into download mode and odin the EE4 stock rom package with the PIT file to completely start over
edit: oh yeah that first image is a classic soft-brick, you need to try and odin back to absolute stock and start over

Oh I did not know that meant a soft brick. I'm reinstalling the drivers right now. I'll let you know if anything happens.
edit: still not working

l0lz0rss said:
Oh I did not know that meant a soft brick. I'm reinstalling the drivers right now. I'll let you know if anything happens.
edit: still not working
Click to expand...
Click to collapse
ok maybe try a different usb port on your pc, also disable any antivirus software temporarily cuz its known to interfere with odin/phone connections... power the phone completely off, take battery out, open odin, connect phone to pc, and see if it recognizes it then put battery back in the phone and uncheck 'auto reboot' option then flash like normal
edit: also there is currently a temporary VZ network outage for all data (4G, 3G, 1x) so that may have been your problem in the first place so you didn't need to odin the modems and get these problems

I'll do some more trials and pray I get into download mode. I did not know that the network was down. It went down right when I finished flashing. That's why I thought I did something wrong.

Omg i kept powering it on and off and it finally got into download mode. I freaking love you

l0lz0rss said:
Omg i kept powering it on and off and it finally got into download mode. I freaking love you
Click to expand...
Click to collapse
nice, must've got the right combo or something lol.. its very hard to actually permabrick these phones, you just gotta keep trying
hope it gets up and running
blazing through on my 4G Droid Charge

Absolutely Dead after Failed Flash

Phone (Droid Charge) is completely unresponsive after I tried flashing to the factory ROM using Odin per this link: [ODIN][ROM][EP4D][FACTORY] Full factory restore 2.3.6 with radio - unrooted 12/7/11. (Two attempts to flash to this ROM aborted in CWM.)
When I used Odin, I got only <OSM> messages in the message box, ending with this one:
<OSM> All threads completed. (succeed 0 / failed 0)
The green status bar never appeared, and the "Start" button reactivated. I did this twice with repeatable results - nothing flashed. I then made the (apparently) huge mistake of removing the USB cable from the phone. It is now a paperweight. No response to power button, no response to plugging phone into wall outlet for charging (battery symbol doesn't appear).
Any ideas, or am I totally screwed?

My guess is that Odin never picked up your phone when you attempted to flash. Have you tried to re-enter download mode to flash again? Make sure Odin detects your device, otherwise, nothing will happen.

My experience is nothing compared to others but I had a situation similar but for some reason I ended up using the Samsung Flash program instead of Odin and after hours of screwing around it worked.

imnuts said:
My guess is that Odin never picked up your phone when you attempted to flash. Have you tried to re-enter download mode to flash again? Make sure Odin detects your device, otherwise, nothing will happen.
Click to expand...
Click to collapse
I have tried to do this. Nothing appears on the screen when I connect the phone with the volume-down button depressed.
By the way, before I flashed the ROM (or tried to) I first did the PIT thing per the following thread: [HOW-TO]Fix your phone
Additional info: here is the log of ODIN messages.
<ID:0/003> Added!!
<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..
<ID:0/003> Firmware update start..
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CI510_VZW_EP4_ALL_ONE-LTE-CP_REV03_user_CL706183_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> All threads completed. (succeed 0 / failed 0)
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CI510_VZW_EP4_ALL_ONE-LTE-CP_REV03_user_CL706183_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> All threads completed. (succeed 0 / failed 0)
<ID:0/003> Removed!!

Did you check "re-partition" in Odin before you flash?
If your phone doesn't display logo "Samsung" then your bootloader is shot. The phone is brick for good. Only by miracle it may come back to life. Just let it rest for a day then retry....it's in coma...sorry.

buhohitr said:
Did you check "re-partition" in Odin before you flash?
Click to expand...
Click to collapse
I did that before I did the "PIT" thing. Then when flashing the ROM, I unchecked the Re-Partition box and then checked the Auto Reboot and F.Reset Time boxes as directed here. Checked only the PDA box and downloaded the ROM file to actually flash.
Look, guys, I think it's clear that I'm hosed. But don't hesitate to ask for more details so that fixes can be developed to help prevent the next guy from suffering the same fate. Rooting has been an expensive, time-wasting exercise for me, and I'd rather it not be for anyone else, if possible.

based on what you described and the logs(you did everything right), you may have communication(driver) issue between your pc and your phone which cause corruption during flashing. This is the only reason I can come up with. I did pit file and factory stock 6 or 7 times already and no issue.

buhohitr said:
based on what you described and the logs(you did everything right), you may have communication(driver) issue between your pc and your phone which cause corruption during flashing. This is the only reason I can come up with. I did pit file and factory stock 6 or 7 times already and no issue.
Click to expand...
Click to collapse
Your explanation sounds reasonable. And it sounds like the kind of unpredictable problem that could cause bricking for other people who go this route. In other words, not only does your phone need to be handled right, but things related to your main PC setup can also cause the process to go awry.
My goal here is to communicate to people that rooting is by no means "safe" or easy. Got no problem with those who wish to root, but doing so for trivial reasons like "I hate seeing all the bloatware" or "I don't like the way my screen looks" is pretty stupid IMO. In my own case, all the problems that I hoped rooting might solve (battery life; problematic Bluetooth; file backup) were not really solved by rooting - indeed, things got worse. And now I have a $700 paperweight.

The only time removing the USB cable during a flash can result in a brick is while it is flashing sbl.bin AFAIK because that is what contains the "download mode". You can usually recover it without too much trouble otherwise. I don't think that was the root cause.
Sent from my SCH-I510 using Tapatalk

MaxBuck said:
Your explanation sounds reasonable. And it sounds like the kind of unpredictable problem that could cause bricking for other people who go this route. In other words, not only does your phone need to be handled right, but things related to your main PC setup can also cause the process to go awry.
My goal here is to communicate to people that rooting is by no means "safe" or easy. Got no problem with those who wish to root, but doing so for trivial reasons like "I hate seeing all the bloatware" or "I don't like the way my screen looks" is pretty stupid IMO. In my own case, all the problems that I hoped rooting might solve (battery life; problematic Bluetooth; file backup) were not really solved by rooting - indeed, things got worse. And now I have a $700 paperweight.
Click to expand...
Click to collapse
humor me while I go through this.... First things first.. You can't get into download mode? (Using a usb port on back of pc preferable) you opened odin, took battery out f phone, held volume button and than plugged usb end into phone right?
there are a few bad pit files out there. Flashed pit file with the original froyo rom? You flashed pit file and stock froyo rom at the same time with repartition selected right?
If I read it right you flashed just the rom with repartition selected one of those times?
Sent from my SCH-I510 using xda premium

Hindle1225 said:
humor me while I go through this.... First things first.. You can't get into download mode? (Using a usb port on back of pc preferable)
Click to expand...
Click to collapse
That is correct - I can get no response whatever from my phone whether I attempt any of the following:
- going into download mode with battery removed OR installed, using the USB port directly on my computer.
- turning on the phone normally
- turning on the phone with the home button depressed
Hindle1225 said:
you opened odin, took battery out f phone, held volume button and than plugged usb end into phone right?
Click to expand...
Click to collapse
Correct.
Hindle1225 said:
there are a few bad pit files out there. Flashed pit file with the original froyo rom? You flashed pit file and stock froyo rom at the same time with repartition selected right?
Click to expand...
Click to collapse
PIT file came from here: [HOW-TO]Fix your phone
ROM installed at the outset of this process came from here: [12-14-11][ROM][EP4D] InfinityROM
ROM I was trying to flash to came from here: [ODIN][ROM][EP4D][FACTORY] Full factory restore 2.3.6 with radio - unrooted 12/7/11
Hindle1225 said:
If I read it right you flashed just the rom with repartition selected one of those times?
Click to expand...
Click to collapse
Not sure what you're asking here.

Again my knowledge is very limited but all of what you described I went through and eventually recovered. I pulled the cable out while installing. It didnt see it in Odin. Says it installed but didnt. And Im sure several other things. In my mind this thing is really hard to totally brick. I reinstalled all samsung drivers, downloaded the files again but used the Samsung Flash program to get back up.I tried different ports, cables etc.I went through the stuff you are for almost 8 hours lol before I finally got it running but it did. Cant hurt to try everything one more time. If you feel it is a paper weight then and have no recourse such as warranty sell it.Crap I might buy it cheap to waste a couple of hours(lol) just to see what I could do.

MaxBuck said:
I did that before I did the "PIT" thing. Then when flashing the ROM, I unchecked the Re-Partition box and then checked the Auto Reboot and F.Reset Time boxes as directed here. Checked only the PDA box and downloaded the ROM file to actually flash.
Click to expand...
Click to collapse
I have no idea what you're talking about with PIT thing. There is a PIT, you flash it with a ROM at the same time. You can't flash just the PIT to the phone. You have to flash a ROM at the same time. You also shouldn't need to use a PIT file when flashing 99% of the time with the Charge. As for what you can do, you can try a download mode jig, but you may want to figure out your communication issue on your computer before you try anymore flashing, and also read more and learn what you're doing before you ruin another phone.

MaxBuck said:
Not sure what you're asking here.
Click to expand...
Click to collapse
I was making sure I knew the steps you went through. If you really can't get into download mode, thats bad news.
imnuts said:
There is a PIT, you flash it with a ROM at the same time. You can't flash just the PIT to the phone. You have to flash a ROM at the same time.
Click to expand...
Click to collapse
This is what I was getting at.
Sent from my SCH-I510 using xda premium

imnuts said:
I have no idea what you're talking about with PIT thing. There is a PIT, you flash it with a ROM at the same time. You can't flash just the PIT to the phone. You have to flash a ROM at the same time. You also shouldn't need to use a PIT file when flashing 99% of the time with the Charge. As for what you can do, you can try a download mode jig, but you may want to figure out your communication issue on your computer before you try anymore flashing, and also read more and learn what you're doing before you ruin another phone.
Click to expand...
Click to collapse
Look at the steps as I outlined them above. The "How to fix your phone" thread says that once you connect to the phone via Odin, you first check ONLY the "Re-Partition" box and press the PIT button in Odin -- that's what I did, and Odin indicated successful flashing of the charge.pit file.
Then, without disconnecting the phone or doing anything else, I unchecked the Re-Partition box, and checked the Auto Reboot and F.Reset Time boxes, checked the box next to the PDA button, and then pressed the PDA button. I was using the "stock" ROM identified above. The process stalled at the message, "<ID:0/03> Completed..", with no green progress bar at the top.
I think you and buhohitr are correct in that there is a communication issue associated with the USB connection between my computer and phone. That could happen to other people also (I have no other issues when using my computer USB ports) without advance warning. Hence my caution that rooting can be dangerous, even if you follow instructions here to the letter, as I believe I did.
Oh, and don't worry -- I won't be rooting any more phones. This whole experience has been a nightmare. Your comment that I should "learn what I'm doing first" is a nice cheap shot; I read all the threads here on rooting thoroughly before I started anything with the phone, and the initial rooting and flashing went flawlessly, which suggests I read the instructions pretty carefully. BTW, I have BS and MS engineering degrees and substantial computer experience (though no Linux experience whatever, which may in part be my problem).

imnuts said:
...
2. Open up Odin, click PDA, and select the package you downloaded
3. Click on PIT and select the PIT file that you downloaded.
4. Get your phone into Download mode.
...
7. Press "Start" and flash the package.
Click to expand...
Click to collapse
It seems that step 2 is what you were confused on - while I can't speak to how others interpret this my interpretation is that there is something in both PDA and PIT before pressing start. I seem to remember something about folks that "unbricked" phones for something like $40 - mobiltech video or unbrickable mod are terms that come to mind. In the same How-To thread the above instructions are quoted from are folks mentioning such things at least.

Just get your phone unbricked for 40 bucks. then I would either get a new comp to flash with or borrow a friends comp. I suggest using spc latency checker on your comp to see if you have latency issues. Also, try a new cable. I have found that many cables don't work well.
Sent from my SCH-I510 using XDA App

MaxBuck said:
Look at the steps as I outlined them above. The "How to fix your phone" thread says that once you connect to the phone via Odin, you first check ONLY the "Re-Partition" box and press the PIT button in Odin -- that's what I did, and Odin indicated successful flashing of the charge.pit file.
Then, without disconnecting the phone or doing anything else, I unchecked the Re-Partition box, and checked the Auto Reboot and F.Reset Time boxes, checked the box next to the PDA button, and then pressed the PDA button. I was using the "stock" ROM identified above. The process stalled at the message, "<ID:0/03> Completed..", with no green progress bar at the top.
I think you and buhohitr are correct in that there is a communication issue associated with the USB connection between my computer and phone. That could happen to other people also (I have no other issues when using my computer USB ports) without advance warning. Hence my caution that rooting can be dangerous, even if you follow instructions here to the letter, as I believe I did.
Oh, and don't worry -- I won't be rooting any more phones. This whole experience has been a nightmare. Your comment that I should "learn what I'm doing first" is a nice cheap shot; I read all the threads here on rooting thoroughly before I started anything with the phone, and the initial rooting and flashing went flawlessly, which suggests I read the instructions pretty carefully. BTW, I have BS and MS engineering degrees and substantial computer experience (though no Linux experience whatever, which may in part be my problem).
Click to expand...
Click to collapse
I'm pretty sure you did it wrongly.
Like others comment, you only need press START button once, AFTER you select PIT file and ROM file (in PDA section), tick the Re-partition (and leave the other unchanged). No need to press START button twice (it seems you press it twice? based on your explanation) ...
If you still able to enter DOWNLOADING MODE, maybe better if you try to reinstall your samsung driver and maybe change the usb port used to flash, or if needed restart your computer ... and after it is detected by ODIN, do it again in the correct way ...
Hope you can unbrick your phone ...

For what it's worth, I've flashed the PIT file by itself in Odin with no problem. Completely acceptable but like was mentioned, you shouldn't really need it in most cases, even situations like this. But I wonder if somehow Odin attempted to flash sbl.bin and failed. That has the potential to hard brick the phone for sure since that file contains download mode. Does anyone know of another way to push the bootloader files to the phone?
Sent from my SCH-I510 using Tapatalk

Did you ever get this phone recovered and/or try one of those $40 programs someone mentioned? I am in the same boat it seems. =(

How long does flashing a kernel with Odin take?

I'm trying to get my wife's Infuse from stock UCLB3 (no root, not CWM) to CM10. The first step I tried to take was to root the phone so I could install TiBu and back up everything.
I tried flashing a custom kernel (Entropy's DD) that included CWM. Odin saw the phone, I clicked PDA and located the tar.md5 file as the instructions said to do. Clicked Start... got this:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> 2012.04.05-ODIN-Entropy_DD-GB-zImage.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..
Click to expand...
Click to collapse
And it's been sitting there about 20 minutes now. Nothing else happening with Odin. My HD activity light is flashing, so something is happening, but, I thought it should be rather quick.
Has Odin actually done anything on the phone? Is it bricked at this point??
EDIT 1: Gave up, yanked the cable and Odin showed "Failed." Power cycled the phone and got the "uh-oh" Download Mode screen (phone-!-pc). Reconnected to PC, Odin saw it, clicked Start again and the process went all the way through and rebooted the phone. Now I'm looking at the Samsung logo and the female computer voice just told me I had about 2 minutes remaining.
EDIT 2: Phone rebooted. Have red recovery now. All is well. SuperUser installed. Installing TiBu right now.

Sounds like you're on your way. Just make sure that you flash an ICS rom before flashing a JB rom.
But to answer your question, it should only take 10 secs or so to flash a kernel.
Sent from my SGH-I997 using xda premium

Nice job- for a little while I thought we might be reading a story about you sleeping on the couch.
good work !

Pony Express said:
Nice job- for a little while I thought we might be reading a story about you sleeping on the couch.
good work !
Click to expand...
Click to collapse
Yeah, you and me both!! lol

Kies failed installation
Hello,
Thank you for your help with this.
I was trying to free up some space on my wifes Samsung Galaxy Europa GT-I5500 but for some reason Kies 2.2 did not detect pics and vids and asked me to install a firmware update which may resolve this, which I attempted to do somewhat unsuccessfully. I sourced the firmware it recommended and began the installation which it gave an error for and then left her phone somewhat bricked I think.
That's when I started checking the forums because I've updated a few Android phones to new OS's using a variety of aps, I came across this xda-developers blog about how to use odin v.1.85 to correctly install the pda software.
I began the process and then ran into a problem which is instead of flying through the steps it hung at the setup connection stage. I waited over an hour on the second attempt to see if it would continue but no joy, I did keep checking the processes in task manager to see if the software was still responding okay and it seemed fine I checked the communications through com port an there was data being written to the handset aswell.
When I disconnect the phone it does not go in to download screen for what was timed as 40 mins, I am also not sure why this is.
After more reading and research on the concern I found Odin v4.28 worked with Europa_I5500_v1.0.ops which I have somewhat adjusted using a development package but there are other ops files available for many of the handsets on market. This software installed the firmware I downloaded GT-I5500 H3G. I realize the difference in the s/w where one does not support ops files
Its 12:30 now and it is all done phone working okay. No thanks to Kies which caused a me a lot of grief this evening and a wasted night.
Thank you for all your help, if it wasn't for people like you I would still be trying to fix the handset so many thanks.

[Q] Skyrocket Bricked odin stuck

Hi you all guys, few days ago i purshaced an skyrocket sgh i727 and it was working perfect, then when i was using the
internet browser my phone ramdomly turn off, i just powered on but it never boot up so i decide to boot it up on clockwork
mode and restore to factory data after that the phone did no boot anymore neither in clockwork mode, when i try to power it
on it shows the samsung splash but stuck there, the phone can be put on download mode which is a good signal however when i
try to install a stock rom from odin this does no start, it keep saying initializing step, i though my battery was
discharged and i tried the battery in a friend's phone but the battery was full charged, so i discarded that was a battery
issue, i installed the lastest kies driver, i got differents odin version, downloaded few times differents stock rom version and re tried to intalled; but odin keep sticking on initializing step, tried differents batteries (full charged), differents usb cables, differents computers, but its seems the phone is completely bricked i tried almost everything also i found that kies can make an emergency restore but when i try to do it, kies request me the error code to proceed, but i dont have such code since my phone never give me an error on installing, it just doest start the restore with odin, when i plug my phone its recognized from odin and shows as added, can you suggest me something? im tired of trying all what i described above and the phone does no have warranty since i purshaced it on ebay and the seller doesnt no accepted to be responsible since the phone worked when he sold it, i cant find any place to purshace a main board but before to purshace one i think there will be posibility to fix it since its still easy to power it on download mode without the JTAG, i cant get it on clockwork mode anymore http://forum.xda-developers.com/images/smilies/crying.gif

First off, I can't really make complete heads or tails of your problem. Please use sentences and paragraphs.
Second, is Odin recognizing your phone when you plug it in? Read the ODIN sticky.
Third, how long is your phone "stuck" on the Sammy splash for? You're definitely booting into CWM recovery and not factory recovery, right?
Honestly, if your phone turns on, it's not hard-bricked and it can be saved. There are lots of stickies here that walk you through how to root/unroot, restore to stock, use ODIN, etc. Read through those and that'll give you your best shot at finding an answer.

response
Hi im sorry if i writed it with sentences and paragraphs, well actually odin does recognized the phone and shows as added, but when i start the restore the phone keep in download mode and odin just stuck in the step that says initializing.
I used another battery, another usb cable and other computer but odin keep sticking in that step.
I tried downloading differents odin versions and differents stock rom version from differents sites but i can see its not a corrupt download.
the phone had CWM but in the time i made a factory reset from the CWM the phone did no boot anymore on CWM neither the OS because it stuck on the Samsung splash, this splash stuck permanently maybe hours if i dont remove the battery.
I think im booting on CWM im not sure because (it does no appear the menu to install zips make factory reset, clear cache partition etc)
Kies recognize my phone also but unable me to make an emergency restore until i put the error code in the box that pop up (i dont have such error code since my phone does no give me any error the process just doesnt start)
i tried killing kies in the task manager because i read sometimes kies intefere with oding while restoring, i can make put the phone in download mode as i said but im not able to make the restore because ODIN Stuck on INITIALIZING MODE.
I read some forums and post before i post but i havent found nobody with the same issue i just found this http://forum.xda-developers.com/showthread.php?t=1240333 but this didnt work for me

jakeharriss said:
I think im booting on CWM im not sure
Click to expand...
Click to collapse
In fairness, at least you're not out flashing ROMs and saying this.
How are you trying to boot into recovery? Are you holding both volume buttons and the power button down, and keeping them down until the Sammy splash comes up? Or are you just using the power button? If you're just pressing power, you're trying to boot a phone that has no ROM, and you'll have the same result every time.
Second, are you positive you're using the right version of Odin? v1.85?
Third, when you plug your phone into the computer and Odin, does the screen look like the screenshot in the OP of this thread?
http://forum.xda-developers.com/showthread.php?t=1773659
I'll be really honest, this screams of user error, and that's really the only explanation I can think of--especially because the phone can apparently still be forced into download mode. Maybe someone more experienced has seen this happen before and can help more than I can, but from the panicked style of posting and your asking questions about whether it's booting into recovery or not, I have to assume that it's user error. We just have to figure out what that error was.

thanks for your answer to my post i apreciate you all your time, well actually i use the both odin version the Odin v1.85 and the odin v3.04 also the odin rom installer (i mean the odin package that you just need to plug the phone and then press start to update it) yes i hold the both volume button + the power button and i release it when the samsung splash comes up but now it does no give me the CWM since i used it to factory reset the phone and i think neither the factory recovery menu, however i can hold the volume down + plug the phone and then start it on download mode by presing the volume up button.
When i turn the phone in download mode, the phone appear in my odin as added like in the screenshot you sent me, then i select in the pda checkbox, then i choose the stock rom from my desktop, i leave the other checkbox selected like when oddin start ( i mean selected the options on auto reboot and F. Reset Time) then i press start, odin verify the rom and when it follow to the next step, odin stuck on initializing procees but my phone stays on download mode and do not pop any error neither the odin, as i said i dont think is a corrupt rom because i downloaded different isc version isc 4.04 and isc 4.03 also android froyo 2.3.5 but nothing works also i used different computers and usb cables and tried with a friend battery full charged maybe i dont have the OS in my phone as you say but my question is how to reinstall it if oddin doesnt seems to work on my phone also i have a galaxy s3 and i installed the jelly bean without a problem in the same computer with the same odin and cable usb

jakeharriss said:
thanks for your answer to my post i apreciate you all your time, well actually i use the both odin version the Odin v1.85 and the odin v3.04 also the odin rom installer (i mean the odin package that you just need to plug the phone and then press start to update it) yes i hold the both volume button + the power button and i release it when the samsung splash comes up but now it does no give me the CWM since i used it to factory reset the phone and i think neither the factory recovery menu, however i can hold the volume down + plug the phone and then start it on download mode by presing the volume up button.
When i turn the phone in download mode, the phone appear in my odin as added like in the screenshot you sent me, then i select in the pda checkbox, then i choose the stock rom from my desktop, i leave the other checkbox selected like when oddin start ( i mean selected the options on auto reboot and F. Reset Time) then i press start, odin verify the rom and when it follow to the next step, odin stuck on initializing procees but my phone stays on download mode and do not pop any error neither the odin, as i said i dont think is a corrupt rom because i downloaded different isc version isc 4.04 and isc 4.03 also android froyo 2.3.5 but nothing works also i used different computers and usb cables and tried with a friend battery full charged maybe i dont have the OS in my phone as you say but my question is how to reinstall it if oddin doesnt seems to work on my phone also i have a galaxy s3 and i installed the jelly bean without a problem in the same computer with the same odin and cable usb
Click to expand...
Click to collapse
read this, its a sticky for newbs, follow it to the t, read the the whole post 3x b4 you proceed http://forum.xda-developers.com/showthread.php?t=1652398, if that doesnt work, either user error or hardware problem with nand

Make sure in Odin Only the reset time and reboot boxes are checked. Don't re partition.

Hmm... Well I occasionally have your initial problem, where my phone randomly turns off. Here, it doesnt boot right away, but I have to remove all power sources (battery, cable), put the battery back in, then it turns on fine, no questions asked.
What ROM were you using at the time? My phone started doing this after I installed the Liquid Beta 2Jellybean Rom. If you were using that at the time, it may have just been a ROM issue. Hope I helped...
Sent from my SAMSUNG-SGH-I727 using xda app-developers app

Brick LOGS PIT
Hi, well actually i was running the stock rom 2.3.5 GINGERBREAD, that was the rom that came with my phone, i tried the step to enter my skyrocket in recovery mode but im not able to do it, the odin keep sticking on initializing i have tried the steps you gave me, is there a way i can get an error code to try the emergency restore from kies? because i dont know where to get an error code,
i tried to re flash the CWM but odin also stick on initializing
<ID:0/007> Added!!
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
and this is the log when i disconnect the phone from my computer
\<ID:0/007> Added!!
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007>
<ID:0/007> Get PIT for mapping..
<ID:0/007> Removed!!
<ID:0/007> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
i have reading a post about PIT
PIT – the PIT file refers as ‘Partition Information Table’. This is only useful for fixing bricked devices if somehow something changed with the partition table layout of the phone’s system memory. But in normal flashing, you should not use this file, or you may screw up your phone if handed carelessly.
does anyone have any idea how can i remap my partition in my phone or if it nessesary?
also here i leave the log when i try to make a restore with odin to an stock rom
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I727UCLF6_I727ATTLF6_I727UCLF6_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation.. (in this step my phone stuck while trying to install and never advance)
when i unplug this is what appear
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I727UCLF6_I727ATTLF6_I727UCLF6_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007>
<ID:0/007> Get PIT for mapping..
<ID:0/007> Removed!!
<ID:0/007> There is no PIT partition. (It keep saying i dont have a PIT partition)
<OSM> All threads completed. (succeed 0 / failed 1)
do you all guys have any idea what is going wrong? i tried to turn in restore mode following this steps
ENTERING IN TO RECOVERY MODE IS THE SAME METHOD FOR BOTH STOCK AND A CUSTOM RECOVERY (CWM)
Now turn off your phone, unplugged(might work plugged in)
Press and keep both volume keys down
Then press the power button while still holding down the volume keys
When you feel the phone vibrate or see a logo on the screen, release the power button but not the volume keys.
When screen goes black release the volume keys.
Wait a few seconds to boot in to recovery
You are now in recovery mode
But when i release the power but and keep holding the volume button my screen keep stuck in the samsung splash even when i release the volume butto + the power button after the splash comes up
I appreciate your time and im sorry if i dont write in paragraph senteces etc i just tried to explain my issue as it was posible for me thanks

i think your problem was this "odin v3.04 also the odin rom installer", never heard of the odin rom installer used for our phones, you could of fracked up the partitions, but i dont know the fix for that, if there is even a way to fix it
edit: nvm, i read that it was a prob b4 you tried that, then its a bad nand, there might be a way to push a recovery back onto the phone using adb, just cant find the post on how
here it is, it will get you started, you need to learn how to use adb http://forum.xda-developers.com/showpost.php?p=31172875&postcount=19

Can you explain me what does NAND mean please, well when i mean odin installer i mean a comprimed package of odin that comes with the rom but you dont need to download the rom separately because this package include exerything its the same like the other odin but instead of use the PDA box you just plug the phone and once is added, you just press start and this does everything, the only thing that looks weird for me is that the phone can be put on download mode without any problem, and you said that if the phone can be put in download mode without j tag this mean its not breaked, do you have any information about if if i can make a re partition in my phone and resolve the PIT issue that odin says?

jakeharriss said:
Can you explain me what does NAND mean please, well when i mean odin installer i mean a comprimed package of odin that comes with the rom but you dont need to download the rom separately because this package include exerything its the same like the other odin but instead of use the PDA box you just plug the phone and once is added, you just press start and this does everything, the only thing that looks weird for me is that the phone can be put on download mode without any problem, and you said that if the phone can be put in download mode without j tag this mean its not breaked, do you have any information about if if i can make a re partition in my phone and resolve the PIT issue that odin says?
Click to expand...
Click to collapse
The thing you are taking about is an Odin one click.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2

Yes, this is absolutely what im trying to say but i didnt know how to say it, tried to flash a leaked 4.04 isc, that previously worked perfect for 3 skyrockets i had and i updated them without a problem, the matter was i never meant to update this phone but i had to try it due in that moment the phone ramdomly turned off and it did no allow me to boot up my OS, so i got into CWM and press factory reset and then i reset the phone but it never boot up back it just keep sticking in the samsung splash, then i tried to go back to the CWM again but now i couldnt do it again, so i tried to install the rom leaked 4.0.4 with odin one click but it never passed, just stuck in the intializing step, then i tried to use the odin 1.85 and downloading an stock rom and putting in the box PDA, but also kept in sticking in the Intializing step never transfered anything to my phone my phone was always in download mode and never gave me an error, i did tried the odin 3.04 that i used to flash the rom in my galaxy s3 i9300 but also kept with the same issue, im not sure if it hard bricked because i can get into the download mode easily, but im unable to get in the recovery mode following the right steps, im thinking is a PIT issue here i found this threat for another model
http://forum.xda-developers.com/showthread.php?t=1760107
this guy explain he had his phone hard bricked and flashed a PIT file to his phone and could restore it back
Do any of you all guys have ever flashed a pit file or have any idea about what is happening to my phone?

jakeharriss said:
Yes, this is absolutely what im trying to say but i didnt know how to say it, tried to flash a leaked 4.04 isc, that previously worked perfect for 3 skyrockets i had and i updated them without a problem, the matter was i never meant to update this phone but i had to try it due in that moment the phone ramdomly turned off and it did no allow me to boot up my OS, so i got into CWM and press factory reset and then i reset the phone but it never boot up back it just keep sticking in the samsung splash, then i tried to go back to the CWM again but now i couldnt do it again, so i tried to install the rom leaked 4.0.4 with odin one click but it never passed, just stuck in the intializing step, then i tried to use the odin 1.85 and downloading an stock rom and putting in the box PDA, but also kept in sticking in the Intializing step never transfered anything to my phone my phone was always in download mode and never gave me an error, i did tried the odin 3.04 that i used to flash the rom in my galaxy s3 i9300 but also kept with the same issue, im not sure if it hard bricked because i can get into the download mode easily, but im unable to get in the recovery mode following the right steps, im thinking is a PIT issue here i found this threat for another model
http://forum.xda-developers.com/showthread.php?t=1760107
this guy explain he had his phone hard bricked and flashed a PIT file to his phone and could restore it back
Do any of you all guys have ever flashed a pit file or have any idea about what is happening to my phone?
Click to expand...
Click to collapse
We don't have a pit file for the skyrocket. At least as far as i know. You should be able to flash the stock firmware if you can get into dl mode. Use Odin 1.85 and follow vincoms guide
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2

Yes so do i think the same, however for any extrange reason everytime i put my phone in download mode my phone stick in this step
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I727UCLF6_I727ATTLF6_I727UCLF6_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation.. (in this step my phone stuck while trying to install and never advance)
i tried using differents odin version, differents stock roms, different usb cables, differents usb ports and computers, also reinstalled the right drivers for my phone and i verified it in the device manager from my computer, so i can say the issue is in the phone
i tried to reinstall the CWM but it also keep on the initializing step so if this dont pass there is no way to get in CWM and neither to the factory recovery mode, as i said everytime i try to get in factory recovery mode i cant due my phone stuck in the samsung splash and never goes black as it should to say that now is on factory recovery mode.

Install kies, Run odin as administrator, use sammobile stock firmware.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2

xcrazydx said:
Install kies, Run odin as administrator, use sammobile stock firmware.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
I did it but keep sticking in download mode with the odin in initializing step even my kies download the emergency restore firmware and it stuck while trying to install is there a way a can make a dual boot without the cwm or factory recovery working?

I am having the exact same problem and have done just about all the same steps you outlined before I came across this thread. What was the final resolution for getting past the "Initialization.." phase in Odin?

UBetchYa said:
I am having the exact same problem and have done just about all the same steps you outlined before I came across this thread. What was the final resolution for getting past the "Initialization.." phase in Odin?
Click to expand...
Click to collapse
Hi well i tried the whole method i could but i realized that would be quicker buying a new motherboard for the phone i got it on 50 usd on ebay it was a look that a guy tried to change his broken screen but he couldnt and decided to put his phone on auction i won and i repaired my phone however i send the mainboard to a friend of mine and he said the he couldnt repair it, i talked with a guy that said he could create the partition map again but i couldnt understand him maybe you can talk to him but he explained me that what killed my phone was to put a leaked firmware and make a wiping on the partition from the restore mode http://forum.xda-developers.com/member.php?u=3597010 this is the guy just send him a message wish you good luck with that

[Q] GT-S7500T stuck on CWM recovery

Yesterday something happened to my wife's phone - Galaxy Ace Plus GT-S7500T. The details are unclear, but she received notification of some sort of "software or firmware update" that was "not a normal update". After that it told her to reboot and since then the phone has been stuck on the CWM Recovery screen.
Things I have tried:
1. Cleared cache and Dalvik Cache.
2. Wipe data/factory reset
3. Update firmware using Odin 1.85 - gets stuck at "setup connection"
4. Update firmware using Odin 3.09 - gets stuck at "setup connection" - tried various USB cables including original Samsung cable
5. Update firmware using Kies - doesn't seem to do anything
6. Update firmware from CWM Recovery
a) GellyBread ROM
b) Elruki ROM
c) Elruki ROM with boot.img substituted from S7500TDVMJ1_S7500TTLPMJ1_TLP.zip
7. Update using Heimdall from Linux - fails to detect phone
Both the GellyBread and Elruki ROMs are meant for the 7500L but at this point I'm getting desperate.
I've wasted two evenings on this and I am just about ready to give up and buy her a new phone. Is there anything else I should try?

StevePER said:
Yesterday something happened to my wife's phone - Galaxy Ace Plus GT-S7500T. The details are unclear, but she received notification of some sort of "software or firmware update" that was "not a normal update". After that it told her to reboot and since then the phone has been stuck on the CWM Recovery screen.
Things I have tried:
1. Cleared cache and Dalvik Cache.
2. Wipe data/factory reset
3. Update firmware using Odin 1.85 - gets stuck at "setup connection"
4. Update firmware using Odin 3.09 - gets stuck at "setup connection" - tried various USB cables including original Samsung cable
5. Update firmware using Kies - doesn't seem to do anything
6. Update firmware from CWM Recovery
a) GellyBread ROM
b) Elruki ROM
c) Elruki ROM with boot.img substituted from S7500TDVMJ1_S7500TTLPMJ1_TLP.zip
7. Update using Heimdall from Linux - fails to detect phone
Both the GellyBread and Elruki ROMs are meant for the 7500L but at this point I'm getting desperate.
I've wasted two evenings on this and I am just about ready to give up and buy her a new phone. Is there anything else I should try?
Click to expand...
Click to collapse
if you dont have a firmware in your phone and it gets to download mode there is no reason to fail at updating with odin
to solve that try reinstalling your drivers but uninstall KIES!
otherwise try a different port or a different computer but it seems like odin is the only solution

the point from your post "since then the phone has been stuck on the CWM Recovery screen."
It means you have CWM installed device [ Correct me if I'm wrong here ] even I guess you've root.
at this stage even if you get any official firmware/software update you strictly don't have to update your device.
you've rooted device, unlocked system at this stage if you update your device with official firmware you'll surely face these kind of bricking issue.
Solution as given above reinstall kies to update drivers also try to check unroot thread from General section once,
Detailed guide & firmware download links are there...
wish you get back your device soon... ​

ShadowsDie said:
if you dont have a firmware in your phone and it gets to download mode there is no reason to fail at updating with odin
to solve that try reinstalling your drivers but uninstall KIES!
otherwise try a different port or a different computer but it seems like odin is the only solution
Click to expand...
Click to collapse
Just to be clear, the CWM Recovery screen means it is in download mode?
This morning I have uninstalled Kies and tried Odin again.
Then I uninstalled and reinstalled the USB drivers and tried Odin again. It now fails after a while rather than getting stuck.
Code:
<ID:0/016> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> S7500TDVLK1_S7500TTLPLK1_S7500TDVLK1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/016> Odin v.3 engine (ID:16)..
<ID:0/016> File analysis..
<ID:0/016> SetupConnection..
<ID:0/016> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I may be able to try on a different computer tonight.

j.posarekar70 said:
the point from your post "since then the phone has been stuck on the CWM Recovery screen."
It means you have CWM installed device [ Correct me if I'm wrong here ] even I guess you've root.
Click to expand...
Click to collapse
Correct, I rooted it when we first got it. I was hoping to but Cyanogenmod on it but only after buying it discovered it was a 7500T and not a 7500.
j.posarekar70 said:
at this stage even if you get any official firmware/software update you strictly don't have to update your device.
you've rooted device, unlocked system at this stage if you update your device with official firmware you'll surely face these kind of bricking issue.
Click to expand...
Click to collapse
Understood, I am not surprised about this. Just frustrating that I'm having so much trouble getting the phone back to life.
I will try unrooting it.

StevePER said:
Just to be clear, the CWM Recovery screen means it is in download mode?
This morning I have uninstalled Kies and tried Odin again.
Then I uninstalled and reinstalled the USB drivers and tried Odin again. It now fails after a while rather than getting stuck.
Code:
<ID:0/016> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> S7500TDVLK1_S7500TTLPLK1_S7500TDVLK1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/016> Odin v.3 engine (ID:16)..
<ID:0/016> File analysis..
<ID:0/016> SetupConnection..
<ID:0/016> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I may be able to try on a different computer tonight.
Click to expand...
Click to collapse
download mode is not recovery mode,
volume down+home+power
if you are not in download mode odin will not work

ShadowsDie said:
download mode is not recovery mode,
volume down+home+power
if you are not in download mode odin will not work
Click to expand...
Click to collapse
Thank you. I do feel a bit stupid not realising this earlier - but now it seems to be working.
I guess I was confused about what it was that CWM Recovery replaced, and I'm sure I tried Volume Down + Home + Power earlier but obviously didn't press it quite right.