Hi this is my very first post! I am new to android all together and i was doing pretty well till now. I have a vibrant that i flashed using odin with ICS_4.0.3_MR1-RC4.2_Vibrant. I was successful but i didnt like the rom cuz its still very buggy. So I put my phone in download mode and prepared to flash back to 2.3.6 heres where things got messed up, i forgot to end all kies processes so odin got stuck on "set partition" i ended the processes, closed odin and unplugged usb. i opened odin plugged in usb but now my computer doesnt recognize my vibrant!! i restarted my phone and now its stuck on phone--!--computer screen and my computer still doest recognize it! ive tried putting it into download mode countless times with no success. i also try another computer still doesnt recognize it plz help!!!!
Factory reset your phone might work
Sent from my PG86100 using XDA
Here is a little help I found @ Vibrant Bricked? Maybe not. [E: Can't mount, Solved.] So cheers to him and where he found the info I have no idea so i give him credit for relaying the information.
Here it is:
Recently I bricked my Vibrant pretty seriously, I did a lot of searching and found that many people were experiencing the very same issue but few of them were able to find a solution.
I want to share exactly how I manged to get my phone restored, just in case anyone else finds themselves in the same situation.
*** PLEASE READ FULL POST CAREFULLY BEFORE PROCEEDING ***
The problem
After an Odin restore I found my phone was caught in a recovery loop and I was continually getting the following error:
E:Can't mount /dev/block/st110 (Invalid argument)
E:copy_dbdata_media:Can't mount DBDATA: copy default media content failed
The solution
Eventually I found this bit of info provided by user Windowlicker on the Samsung Galaxy S Forums.
Put your phone to download mode (hold down: volume down, home key, power)
Do not plug in your phone yet.
Start Odin3
Tick "Re-Partition", and also check that "Auto Reboot" and "F. Reset Time" have been ticked.
Click "PIT" button and select s1_odin_20100512.pit file.
Now, plug in the phone and wait until Odin finds it.
Click "Start" button... <Firmware update start...> <Get PIT for mapping...> appear. The phone will turn off and the screen indicates "Reset". Wait until Odin indicates "Pass".
Plug out your phone, remove the battery, put it back in and put phone to download mode again.
Click "Reset" button in Odin and untick "Re-Partition" box.
Do not select PIT file again. Just leave it empty.
Click "PDA" button and select "CODE" file.
Click "MODEM" button and select "MODEM" file.
Click "CSC" button and select "CSC" file.
Plug in the phone and wait until Odin finds it.
Click "Start" button and wait until phone reboots with the new software version.
(When it comes to the restore step I found that I needed to go back to the Stock 2.1 Vibrant ROM, JI2 & JI6 wouldn't work for me.)
I hope this info helps some folks out, I had completely given up on trying to restore, and I ordered a replacement from T-Mobile. A couple days later I found this solution. Now I'm waiting to receive a phone I no longer need, and will find a nice $20 delivery charge on my next TMO bill. The price of giving up too quickly I guess.
***ADDITIONAL NOTES BASED ON USER FEEDBACK***
I've noticed many people are getting stuck on the 7th step, 'where you are asked to remove the battery and place the phone in download mode'. I cannot stress enough that you need to be extremely patient during this step and should not remove the battery until after Odin indicates pass. This could take as long as 10 to 30 minutes, failure to wait could result in a 'true brick'.
Another step missing from the original instructions is to remove the External SD and SIM cards before starting this process. I'm not completely certain what the technical reason is behind this, but it does seem to help the process along.
Before starting it might also be to good make sure the screen saver and sleep modes on your PC are disabled, as some steps take a while and it might be possible for either of these processes to interrupt it.
Finally, I again want to stress patience. If during any step, things seem like they are taking longer than you think they should, go and make a sandwich, maybe play a game or watch some TV and give it a little while longer. Letting the phone sit too long during a step won't cause any problems, but removing it too soon could cause a brick.
Click to expand...
Click to collapse
Try this! Let me Know!
Related
So I was trying to follow the SRE tutorial (new user can't post links)
and I followed step one and pressed start on ODIN and the program seemed to hang on file analysis and then my usb cable came unplugged and now my phone won't come out of download mode.
If I remove the battery think I will reboot to a brick?
From what i've seen, it's impossible to brick a captivate unless you do something to the hardware.
Worst case, you just flash it back to a stock rom and go from there.
So, it might temporarily be a brick, but not permanent.
No worries man.
Pull the battery
Shut down and restart your Odin one click program.
Plug the USB cable back into the phone.
Hold volume up/down and power at the same time ( I find the pinch method works well to acomplish the next step )
Slide the battery back in place.
Let go of the power button.
It should fire up in download mode, click start in Odin one click and watch it do it's thing.
Odin is very picky and it only works when it wants too now, at least with my compy... If it gives you any errors like file analysis, or COM port errors, restart your computer, and give odin another try.
Diametunim said:
If I remove the battery think I will reboot to a brick?
Click to expand...
Click to collapse
Same thing happened here. I visited a tutorial on a website to install the lagfix and the same thing occurred to me. No problems, though. Simply remove your battery and the phone will turn off as usual.
Here's what I did to fix the issue: I'm on Windows 7 32-bit. I simply put Odin in WinXP SP3 compatibility and had it run as Administrator. Once it's opened, I remove my SIM card, and then try the program again.
Strangely, under those settings, Odin worked 100%.
Yesterday my phone started acting up. All running process crashed and not many was able to start. I had to constantly click "force close". I think this started after I installed the Google+ app, but not sure.
I have tried uninstalling all unnecessary apps, without luck. I then tried wiping to factory settings by using the Android menu, but without any changing. I then tried by holding vol+ and power, going in to recovery and wiping both to factory and app cache. This doesn't change anything either. By googling I can see some suggests to hold vol- and power, to get to a another wiping-functionality but this just boots my Nexus S to normal state - no menu appears.
Has anybody an idea of what I can do?
Edit: more info; if I click "Report" and investigate the message sent to Google, I see that error has something to do with SQLite-relatet classes. Which makes some sense, alot of my changes are reset each time the phone is rebooted. For instance did I miss a call a couple of hours before the phone went crazy - this is shown at each boot in the notification area eventhough I clear the area and/or goes to missed call section
Factory reset via menu does delete all your "custom" apps, so I'd say it's not one of the existing apps causing problems.
The way you describe function after your factory reset sounds like factory reset didn't work properly.
If you feel safe I'd recommend rather flashing 2.3.4 again using either Odin or the OTA zip from Google (requires open bootloader).
I think you're right that factory reset doesn't do what is expected. Once I click it, the phone reboots and shows the Android guy next to an unwrapping package. This lasts only 2 seconds, then it reboots itself again and goes into normal phone mode (where all the app-crashing starts again).
I have not flashed or rooted my phone before, but I will consider this now since my NS is pretty much a brick. Thank you for your swiftly response.
Edit: Shouldn't I get a menu, when I push and hold vol- button, while turning on the device? Right now it just boot as normal.
Before you use odin....try going into rom manager a reflashing clockwork! Ive had that android dude on my screeen but reflashibg via rom manager always fixed it. Try that
Sent from my Nexus S using XDA Premium App
Wow my Nexus has totally shut me out.
I cannot use ClockworkMod unfortunately since I am not able to root my phone. It is not detectable via USA (when I use vol+/pwr and connect USB). I am unable to check the USB Debugging option on the phone. Each time I check it, go to home-screen and back to the menu, it has de-selected it again. Also I noticed when I read the info that is sent to Google for all those app-crashes I get, I see SQLiteException and error in an SQLite.java file. So it seems like some database layer is broken.
I read one could copy the ClockWork.img to my phone and use the standard recovery option to flash the img (I think). But when I go into the recovery menu, the file is gone. When I boot the phone again, it has deleted the .img file - eventhough if I copy it to several different folders, they are all gone :-(.
I feel pretty screwed at the moment. How can I else wipe all data?
I'd recommend to check if your device is correctly identified in windows. Missing USB drivers might cause problems. Get the latest drivers and a guide from here.
If you succeed booting into fastboot properly (vol up and power) you can follow this guide. Get the latest cwm recovery.img here.
Last option would be to boot into download mode (vol up + vol down + power + plugging in usb cable) and use Odin from samfirmware.com
--
All options require correctly working USB drivers.
I managed to unlock the bootloader, by quickly turning on USB-debugging (before any processes started to crash) and install the drivers from this post:
http://forum.xda-developers.com/showpost.php?p=6819751&postcount=4
A reboot later, I got this message:
"System UIDs Inconsistent
UIDs on the system are inconsistent, you need to wipe your data partition or your device will be unstable."
Right below was a button saying "Im feeling lucky" (??)
I installed ClockworkMod using fastboot and tried "Fixing permissions" with no luck. I will try some ROM later on, and hope it will bring my phone back
Normally this error happens when you have a faulty app ruining your system, formating/deleting whole sdcard does usually fix this.
rentaric said:
Normally this error happens when you have a faulty app ruining your system, formating/deleting whole sdcard does usually fix this.
Click to expand...
Click to collapse
I can safely mount USB-storage and format the whole bunch?
I been sweating over this stupid issue all day now, all I want is a fac-reset :´(
Edit: "format /sdcard" using CWM didn't do anything
DennisRP said:
I can safely mount USB-storage and format the whole bunch?
I been sweating over this stupid issue all day now, all I want is a fac-reset :´(
Edit: "format /sdcard" using CWM didn't do anything
Click to expand...
Click to collapse
See I'm no expert on this whole thing. At this point I'd just flash a whole new system via Odin. Prolly not the smartest or safest option, but that's what I'd do because I don't know better. If that wouldn't fix it either, I'd return the phone on warranty
I was looking at Odin from the start, since nothing else seemed to be working.
So right now I got started on Odin. Followed the .pdf steps and flashed the bootloader at first succesfully. I was asked to remove the battery and re-connect my NS. Began downloading "pda" and "phone", but at around 10% a big fat red "fail" message appeared and now I just see the Google-logo on startup. I still cant flash any roms via fastboot.
Im too tired too right now, been working with this for 14 hours straight. I will look at it tomorrow evening. Thanks for your help rentaric
Weird, you're not the first one who had trouble running Odin using their guide.
Overall it's pretty simple.
Enter download mode. Vol up vol down and power at the same time while plugging in the USB cable. Start Odin, should show a yellow colored box with a port number. Uncheck everything but reset timer and auto reboot. Unzip the correct zip file from samfirmware.com (check if you got i9020 or i9023 and get the universal Odin exe), apply file from the folder accordingly. Bootloader and bootloader. Phone and modem. Pda and pda. Csc can remain empty (will change carrier info in fastboot).
Double check md5 hash to avoid broken files.
Sent from my Nexus S using XDA App
rentaric said:
Weird, you're not the first one who had trouble running Odin using their guide.
Click to expand...
Click to collapse
Of course I did not go to bed, how should I be able to sleep with a broken phone .
The firmware suggested on samfirmware.com for my phone, was 2.3.3 and some other version (my phone was 2.3.4.2/GRJ22 or something similar, I suspect that might be the cause. Also I unchecked everything, that might also have been of importance). The flash will always fail when everything was downloaded - it then said something about "remote" and "Loke" and then fail. But as I mentioned, I had succesfully flashed boot.img (2.3.3) thus no boot occured now. I googled the correct bootloader, used fastboot and was booting succesfully again.
I began looking more into the sdcard, as error-messages was leading me this way. To compress 4 hours of investigations into a few lines, it seems as my PBA is malfunctioning as other xda-members have experinced. Only solution is sending the phone to Samsung for a PBA replacement. I purchased the phone in Bestbuy USA and the danish Samsung partners are not too joyfull about this - I will contact Samsung and hope they can help me.
I experinced the exact same thing as this poor guy - http://forum.xda-developers.com/showthread.php?t=993403
Every thing you try to do to /sdcard is worthless.
Formatting (USB/using CWM/using adb shell linux commands) says "Succes" but nothing happens.
Copying files says "Succes" but nothing happens. If I boot phone into CWM, mount usb and upload new rom/apk/whatever and try to do a "install update.zip" it fails with some mounting errors.
Im ready to go cry in a corner - I really want this to be fixable via software, but I probably have to realize that this is a hardware issue.
Apparently Samsung doesn't offer worldwide warranty for cellularphones :´(. God it sucks to pay repair-expenses on a 1 month old mobile.
So, I bricked my Infuse last night at work when I tried installing MIUI from ROM Manager. I've been trying to unbrick using gtg's Ultimate Unbrick method, but no luck. I believe it's something to do with the Samsung Drivers since my phone is not recognized in Odin. Tried to redownload the Drivers from Samsung's website, but still doesn't work.
Any ideas?
BTW, running Windows 7 32bit
why would you install a rom that's for a different phone?
can you boot into recovery mode? did you try the "jig"?
Didn't think there would be a listed ROM in the manager if it wasn't for the phone...
Won't boot into recovery at all, Samsung pops up, then it goes blank, and Samsung pops up again. It loops like that until I pull the battery.
Was hoping to avoid having to buy something then waiting for it to arrive, as I need the phone working asap.
the reason other roms pop up in rom manager is because you are using the galaxy recovery. unless it says "for infuse" (there is only one, gtg's rom) it wont work. bummer dude. im all out of ideas, never had this happen. hopefully someone who's been through this can chime in and provide some info that will help you.
on a side note, why cant you take it to an att branch and have them exchange it for you?
Pat713 said:
Didn't think there would be a listed ROM in the manager if it wasn't for the phone...
Won't boot into recovery at all, Samsung pops up, then it goes blank, and Samsung pops up again. It loops like that until I pull the battery.
Was hoping to avoid having to buy something then waiting for it to arrive, as I need the phone working asap.
Click to expand...
Click to collapse
I hope u have USB debugging turned on. If yes, u cud try this:
1. Download and install android SDK (search google for this if don't know how to).
2. Open a command prompt
3. Type in "adb reboot recovery" without quotes, and don't hit enter
4. Connect phone to PC
5. Turn the phone on
6. Wait for "samsung" to appear, and hit enter in command prompt
7. If it says "device not found", use the up arrow to get the command from history, and hit enter again. At some point, it should issue the command to the device.
8. If u can get to recovery, well, u have a way to now try to flash any other ROM.
Don't give up. Samsung has strong phones that could be got out of soft bricks most of the time.
Delete/reinstall the drivers.
Infuse 4G
Just tried Diablo's method, and it tells me command not recognized...
Download Kies on your pc to have it recognize ur phone. Run odin. Put ur phone in download mode (pull out battery, put it back in, hold both volume buttons down, plug in ur usb) and use gtg's unbrick.
Sent from my SAMSUNG-SGH-I997 using XDA App
Tried Kies before and it would never recognize the Infuse. Should I pick Galaxy?
UPDATE!!
Redownloaded Kies and installed the drivers (for the 500th or so time) and now Odin is recognizing a device. It's showing [COM3] instead of COM## but I'm letting Odin do its thing. Seems to be working... Crossing my fingers!
EDIT::
<ID:0/003> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
****in A! Thanks for the help guys!
Pat713 said:
Didn't think there would be a listed ROM in the manager if it wasn't for the phone...
Won't boot into recovery at all, Samsung pops up, then it goes blank, and Samsung pops up again. It loops like that until I pull the battery.
Was hoping to avoid having to buy something then waiting for it to arrive, as I need the phone working asap.
Click to expand...
Click to collapse
You need to buy a jig, that will solve the problem.
The jig is less than $10 bucks shipped if you buy it on ebay.
Here is the link:
http://cgi.ebay.com/Samsung-Galaxy-...0563626533?pt=Cell_Phones&hash=item20ba3eba25
Easy to use.. all U do is pull the battery, plug the jig into usb port on the fone replace battery and you will see the big triangle saying "Download" then unplug the jig and load odin.
Setup the pda/phone/pit/csc files in odin3. Then plug in the usb cable from computer to the phone making sure that where odin says "com" that it is highlighted yellow. Then click start in Odin and wait til it says "reboot" after that you will have a working phone with stock froyo 2.2 . Don't change any default setting in odin.
Use the "Ultimate Unbrick" rom - Here is the link:
http://forum.xda-developers.com/showthread.php?t=1116251
Misterjunky said:
You need to buy a jig, that will solve the problem.
The jig is less than $10 bucks shipped if you buy it on ebay.
Here is the link:
http://cgi.ebay.com/Samsung-Galaxy-...0563626533?pt=Cell_Phones&hash=item20ba3eba25
Easy to use.. all U do is pull the battery, plug the jig into usb port on the fone replace battery and you will see the big triangle saying "Download" then unplug the jig and load odin.
Setup the pda/phone/pit/csc files in odin3. Then plug in the usb cable from computer to the phone making sure that where odin says "com" that it is highlighted yellow. Then click start in Odin and wait til it says "reboot" after that you will have a working phone with stock froyo 2.2 . Don't change any default setting in odin.
Use the "Ultimate Unbrick" rom - Here is the link:
http://forum.xda-developers.com/showthread.php?t=1116251
Click to expand...
Click to collapse
I got it unbricked now, problem was the drivers wouldn't correctly install on Win7.
But, now I have a new problem. Just put 3e recovery on and flashed CWM, only to get bricked again (no problems unbricking this time, taking longer to type this than it took to unbrick...). Also, sometimes apps refuse to download from the Market. I tap "INSTALL" and the notification pops up saying downloading, but then it disappears and nothing happens, its like I hit cancel. I'm going to call it for today and get some sleep. At least the phone is usable now! :-D
Pat713 said:
Just tried Diablo's method, and it tells me command not recognized...
Click to expand...
Click to collapse
That means u do not have android toolkit installed on ur system. You should install it first for the adb commands to work.
I would recommend downloading and learning the basics of adb. This could be a life saver in many no-so-happy situations.
Pat713 said:
I got it unbricked now, problem was the drivers wouldn't correctly install on Win7.
But, now I have a new problem. Just put 3e recovery on and flashed CWM, only to get bricked again (no problems unbricking this time, taking longer to type this than it took to unbrick...). Also, sometimes apps refuse to download from the Market. I tap "INSTALL" and the notification pops up saying downloading, but then it disappears and nothing happens, its like I hit cancel. I'm going to call it for today and get some sleep. At least the phone is usable now! :-D
Click to expand...
Click to collapse
Had this same problem and it turned out to be a hardware problem. There was no gix for it. Also youll notice that gtgs recovery includes a preroot. If you need to send your phonr back like i did youll need to get that off. It was tricky for me because the hardware was so screwey. I got it off after a few reboots of the phone and a couple of trys with superoneclick.
Sent from my SAMSUNG-SGH-I997 using XDA App
So I have royally screwed up my phone :/
I tried to upgrade to 2.2 on my Samsung Showcase for Cellular South, but the re-partition in Odin was checked. Then the phone wouldn't do anything but go into download mode and recovery. I tried to "fix" it myself, don't even remember what I did now, and now the phone won't do anything. I have a JIG to get it into download mode. And I try to fix it in Odin again and it gets almost to the end and i get errors every time. And not always the same error.
I need help! What do I do? What files do I need to fix it? Doesn't have to even be 2.2 at this point or Cellular South, I'll settle for Verizon if it will get if fixed.
Thanks in advance!!
Fix
Despite this being LONG after your issue, just in case there are others who are new to this:
Files: Download #5 of 6 and #6 of 6.
rootzwiki. com/topic/12969-odinshowcaserommodemofficial-ei20-gingerbread-full-flash-and-cs-modems/
Unzip the files (with winzip or winrar) to a location where you can find them.
Download static.droidnetwork. net/da2zoe/ODIN3_v182.exe
Open Odin, Turn your phone off.
Hold the down volume, and plug in the USB cable. A "Downloading..." screen will appear, and you should see the first "ID:COM" box turn yellow and "Added!!" in the Message box.
Click the Pit button, locate the Atlas_v2.2.2.pit and select it.
Click the PDA button, locate the EI20.tar.md5 and select it.
Checkboxes: Repartition, Auto Reboot F.Reset Time, and Phone EFS Clear checked. Nothing else.
Click Start.
If you have any problems, you at least have the basics on how to flash. Google exactly what's wrong and the forums have answers for just about anything.
I have been using android phones for a long time, and used odin before, so I have no idea what is going on here. I was attempting to root my phone using the downloads and info in the sticky here, and now my phone won't turn on. I put the phone in odin mode, it was detected, i flashed the bootchain (step 1) in the PDA section, the screen went blank, odin said "Reset" in the first box, and sat there for a long time. Then it said pass, but there was still nothing on the screen. I waited a bit, but eventually unplugged it and tried to turn it on. I can't get any button combination to work, no recovery, odin mode, or normal powerup, no response if I plug in usb or the charger, the only thing I can get is if I plug the charger or usb in with no battery, the red light will come on for about 15 seconds, then go off. I really am afraid I bricked my phone somehow the first day I got it, and now I'm leaving on a business trip tomorrow and need to get this sorted tonight.
Am I out of luck, or is there something I'm missing?
How exactly did you try to enter recovery mode? I know that when I did this and i attempted to enter recovery i let go of the home and volume up too soon and the same thing would happen to me. Also make sure you are using odin v3.07
Did you verify the md5 signature of the file on your pc before you flashed it in Odin? If not, you should check it now. Could have been a bad download. Knowing what caused the brick can help us figure out how to fix it