Not sure if this is the right section or not, but I felt I would get the best response from this forum.
OK.. so I was running euegene's Vibrant6 ROM, but I was having trouble getting any of the lagfixes to work correctly. So I decided to follow the steps outlined in this post: ((apparently I cannot post links))To flash the stock rom and so on. I had never used odin before, but a quick google search found me some directions and it seemed simple enough. So I try to flash with odin and I kept getting stuck at "File analysis.." After disconnecting my phone and trying to restart it, the phone would just go to the screen with the phone + warning sign + a computer. I was able to get back in to download mode from there. Still could not progress past the file analysis. I tried all of the tips outlined in this thread(apparently I cannot post links)) and after reading that last post, I was able to uninstall my previously existing drivers from my moto cliq.
Finally, odin progressed passed the file analysis and was flashing the filesystem.rfs file. I had a nice blue progress bar on the downloading screen, I thought everything was going to be fine. Then my phone went to a blank Blue Screen. The progress bar in odin seemed stalled at about 25%. As this was my first time using odin, I had no idea if this was normal. I let it sit this way for a good 10 - 15 min. No change. At this point I started getting concerned and thinking this can't be normal. I gave it a few more minutes and still no change. Odin was still just sitting there, right about 25% on filesystem.rfs and blank blue screen on the phone. So then I unplugged the phone, pulled the battery and put it back in, expecting that phone - error sign - computer screen again and hoping to reboot the pc and try again. No such luck.
Now my phone will do nothing. Plugged in to the pc with odin running no response whatsoever from the phone. Plugged in to the wall, no response. It's like I'm trying to turn it on without the battery in. I fear the worst and I'm 99.9% sure you guys will just confirm this as I can't get in to ANYTHING. What I would really like to know though is where I went wrong. Is it really normal for an Odin flash to take that long and to sit at that point?
EDIT: Quick follow-up question, and this is probably going to sound completely stupid, but I don't really care: is the "internal sd" an actual micro sd card that can be accessed at all, so that I can at least get my pictures/videos and such off of if I have to get a new vibrant?
this should be posted in the q/a section
I'm no expert, and I'm not sure what went wrong, but you can try to unplug phone from the USB charger, unplug the battery, put battery back in, hold volume up + volume down and plug back into usb charger (connected to computer) to see if you get a responce from the phone.
Sent from my SGH-T959 using XDA App
merrifield69 said:
this should be posted in the q/a section
I'm no expert, and I'm not sure what went wrong, but you can try to unplug phone from the USB charger, unplug the battery, put battery back in, hold volume up + volume down and plug back into usb charger (connected to computer) to see if you get a responce from the phone.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
Thank you for the quick response. Sorry about the wrong section, wasn't really sure this would fit best. Tried what you said and IT WORKED first try. I'm now in download mode. NOW, I would like to retry the flash with odin, but I also need to know if I'm doing something wrong, or if this was a fluke? Should odin sit at that point (25% flashing filesystem.rfs) for that long with a blue screen on the phone? I was under the impression it should be a pretty fluid and somewhat quick process.
skoozi said:
Thank you for the quick response. Sorry about the wrong section, wasn't really sure this would fit best. Tried what you said and IT WORKED first try. I'm now in download mode. NOW, I would like to retry the flash with odin, but I also need to know if I'm doing something wrong, or if this was a fluke? Should odin sit at that point (25% flashing filesystem.rfs) for that long with a blue screen on the phone? I was under the impression it should be a pretty fluid and somewhat quick process.
Click to expand...
Click to collapse
when i flashed using odin i didnt seen any blue screen only the download screen wha are ou trying to flash are you sure its for the vibrant?
cdw9800 said:
when i flashed using odin i didnt seen any blue screen only the download screen wha are ou trying to flash are you sure its for the vibrant?
Click to expand...
Click to collapse
Yes, I downloaded a rar for stock vibrant, it contains :
s1_odin_20100512.pit which i put in the PIT field, and T959UVJFD.tar, which i put in the PDA field
EDIT: this is from the "odin1.0_T959UVJFD_512.pit_rootupdate.rar" which is linked in a few posts in this forum.
yeah those are correct. try having re-partition checked because that worked for me. also, make sure you dont have any files on the csc field. are you using the correct drivers on your system??
rpesigan6 said:
yeah those are correct. try having re-partition checked because that worked for me. also, make sure you dont have any files on the csc field. are you using the correct drivers on your system??
Click to expand...
Click to collapse
Every time I try it with the re-partition option clicked it seems to hang at this status:
<ID:0/005> Added!!
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
I am retrying this now, I have a small fraction of the blue progress bar on the "Downloading..." screen on my phone. Neither the device nor odin seem to be doing anything. How long should this normally take?
As far as I know the drivers are correct.. I installed the x64 drivers from the link provided in the informative links sticky in this forum. adb was working fine.. device manager lists the phone as "SAMSUNG USB Composite Device" and Driver details window lists three .sys files w/ version 5.16 built by WinDDK
EDIT: not sure if this helps.. here is screen shot of odin & driver details h**p://i37.tinypic.com/2cn8501.jpg (will not allow me to link or post img)
ok instead of flashing the s1_odin_20100512.pit in the PIT field, try flashing the other PIT which should be s1_odin_20100513.pit
THAT IS WITH THE 13, NOT THE 12.
you can find the 13.pit in one of the rar files. look deep into the rar files. im pretty sure you will find it
rpesigan6 said:
ok instead of flashing the s1_odin_20100512.pit in the PIT field, try flashing the other PIT which should be s1_odin_20100513.pit
THAT IS WITH THE 13, NOT THE 12.
you can find the 13.pit in one of the rar files. look deep into the rar files. im pretty sure you will find it
Click to expand...
Click to collapse
Unable to find any such file. After some google'ing, I was able to find an s1_odin20100513.pit from the samsungfirmwareworld i9000 forum. tried that with re-partition still checked. Same result. Tried again with re-partition unchecked, it gets to modem.bin, tries to work and then my phone goes to a blank RED screen.
skoozi said:
Unable to find any such file. After some google'ing, I was able to find an s1_odin20100513.pit from the samsungfirmwareworld i9000 forum. tried that with re-partition still checked. Same result. Tried again with re-partition unchecked, it gets to modem.bin, tries to work and then my phone goes to a blank RED screen.
Click to expand...
Click to collapse
a blank red screen? all i can say is possibly try using another windows computer.
rpesigan6 said:
a blank red screen? all i can say is possibly try using another windows computer.
Click to expand...
Click to collapse
I had a similiar issue but mine was worse, I unplugged on accident during a kernal transfer. Get into download mode and keep the phone plugged in while you load ODIN. Then reset the phone back into download by removing the battery with it still plugged in. This should allow you to put the stock firmware back on. Use the 512/tar you already have. It is usually almost always an ODIN problem and not a truly bricked phone. I've ****ed my phone up a LOT and always able to revert after messing with ODIN.
Regards,
B
vibrantFTW said:
I had a similiar issue but mine was worse, I unplugged on accident during a kernal transfer. Get into download mode and keep the phone plugged in while you load ODIN. Then reset the phone back into download by removing the battery with it still plugged in. This should allow you to put the stock firmware back on. Use the 512/tar you already have. It is usually almost always an ODIN problem and not a truly bricked phone. I've ****ed my phone up a LOT and always able to revert after messing with ODIN.
Regards,
B
Click to expand...
Click to collapse
I'm trying to do this, but if I open ODIN with the phone already in download mode, ODIN does not see it. Pulling the battery and putting back in (downloading screen still up during this) does not change that. Maybe I misunderstood?
yes, i did.. likely at 4 am i guess.. so far its gotten past the modem.bin which it hasnt done in a couple hours of messing with this.. now its on filesystem.rfs again and stalling again, only now its only at about 10 - 15% as opposed to the 25% i was getting a couple hours ago before it stalled. This is with re-partition unchecked, btw. With it checked, odin still just sits at do not remove target.
I had this problem.. what I basically did was:
- Open Odin... add all the PIT and PDA files up (Re-partition UNCHECKED)
- Plug the phone in USB
- When the green battery was on the screen: hold volume buttons (basically.. get into download mode)
- Once in download Odin doesn't detect anything? Unplug USB and replug it back in
- Odin should detect your phone and one of the boxes should be labeled: COM[#]
Any # should be fine as long as you have the proper drivers
Then hit the start button. During this whole process, you should see the Android digging with a blue bar right below it. The screen shouldn't go black, blue, or anything crazy. Just android digging and a blue progress bar.
http://forum.xda-developers.com/showthread.php?t=734475&highlight=Stock Was the thread I used. Download hashtab (google it) and verify that the MD5 checksums are correct, once installed right click the file -> properties -> hashtab and then copy paste the MD5 on that thread an verify that it is correct.
For me the Odin process took less than a minute, the trick for me was to preload everything in Odin before plugging in the phone otherwise it would get stuck.
Personally, I don't think your phone is bricked anyway. Just some technical difficulties with getting Odin to work. The first time around when I was trying out Odin, it was messing up for me. Hope this helps.
Vibrant Drivers: http://forum.xda-developers.com/showthread.php?t=728929 -- If these aren't the set of drivers you're using, then uninstall yours and install this. This one works with no problems.
rpesigan6 said:
a blank red screen? all i can say is possibly try using another windows computer.
Click to expand...
Click to collapse
Was able to try this this morning.. it worked first try. With all the problems I was having, I was dumbfounded with how smooth it went. Don't know what was going on. Thank you all for your help with this
Hey guys, I figured I'll post here since I think I bricked my phone.... I was trying to install Eugene's Vibrant6 and I got stuck on the Vibrant Logo with Samsung at the bottom. I tried to reset with both volume buttons and power button and got to grey battery and nothing else... what can I do? Anyone can help me?
Thanks.
I fear my problem is worse as i was having the same issue with it loading filesystem.rfs and was stalling so i attempted to restart the process and now all that will display on my phone is an image of a cell phone a computer and a yield sign between. Plz help
Sounds like you need to upgrade Odin3 1.0 to Odin3 1.7
Ok i DL'ed Odin3 1.7 and still the same. The vibrant screen doesn't even come up, just an image of a cell phone and a comuter with a yield sign in between.
Start odin on your pc, remove batt, insert USB, hold down volume buttons and pop in the batt. This always gets me into download.
Sent from my SGH-T959 using XDA App
May god bless you and your children, and your childrens children, and their children!!!!!!!!!
Related
My Vibrant is stuck on a screen that shows a phone icon and a PC icon with a yellow exclamation mark between them. It won't go into download or recovery mode, as soon as it turns on after a battery pull, it goes straight to this "connect to pc" screen.
I got a message today that there was an update available, so I accepted it and about 3-5 minutes later it rebooted and has been like this ever since.
Tmobile is sending me an express replacement, but I was hoping someone here would have some ideas.
More information: Odin doesn't light up when I plug it in and I get no USB messages on the pc when I plug it in.
brick help
ok so i brick my phone probably about 2-3 times a day so easies way to get into download mode is make sure your phone is off pull the battery make sure it is unplugged from the mini usb aswell, next step is to hold down both volume buttons and then at the same time plug in the usb into your phone from the computer then when you see activity let go of the buttons it should put you into download mode if you cannot make that happen just pm me
http://www.voiceofandroid.com/component/content/article/3-newsflash/77-bricked-vibrant-fix.html
hope that helps, if link doesn't work this is what it says:
First you take your battery out, sim card and sd card.
Then put the battery back in and sd.
While the phone is off, hold the Volume +/- at the same time and plug your device into the usb which is attached to your pc,(it should go in to download mode).
Then you should be able to reinstall the firmware with no problems.
If your computer is not picking up a "com" unplug and plug back in, that should work.
ProximaC said:
More information: Odin doesn't light up when I plug it in and I get no USB messages on the pc when I plug it in.
Click to expand...
Click to collapse
Did you install the Samsung USB drivers?
http://forum.xda-developers.com/showthread.php?t=728929
Following the above steps I now have it in Download mode. Oden lights up, but it's not pushing the file. It stops at File Analysis. It's been sitting there for about 10 min now.
Pulled the cable, restarted the phone into download mode, and this time it will start downloding. It gets about 20% in and then Odin says Failed.
Added
File analysis..
Get PIT for mapping..
Firmware update start..
cache.rfs
modem.bin
factoryfs.rfs
Complete(Write) operation failed.
All threads completed.
redownload the .tar and 13 pitt file with the newest odin i had issues with it hanging on mine too hence many bricks your files could be corrupted
Ok, downloading the PIT and JFD again fixed it. I am now back to stock.
Thanks everyone! You are life savers.
no prob i bricked my phones so many times its almost a joke if i dont brick it im not happy
How to fix your phone and apply the update:http://forum.xda-developers.com/showthread.php?t=803492
Why does everyone think getting bricked is such a horrible thing? I mean you can get a fresh replacement. I would love to get a brand new vibrant. That reminds me if I got my vibrant used do you think if it bricked with the update I could get a new one free of charge?
Sent from my SGH-T959 using XDA App
if getting a new vibrant, will the previous purchased apps be able to use on a new vibrant?
thenotoriouspie said:
Why does everyone think getting bricked is such a horrible thing? I mean you can get a fresh replacement. I would love to get a brand new vibrant. That reminds me if I got my vibrant used do you think if it bricked with the update I could get a new one free of charge?
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
I've bricked and recovered a few times, but this time it was a screen I'd not seen before and I couldn't get it into download mode at all using the methods I'd been using successfully before. So yeah, I was a bit more stressed this time. Also, when I've bricked before, it was my fault. This time it was the OTA that did it. Somehow that made it worse.
I am on root on 2.2 with Dk28 and epic all in one.Yesterday I decided I wanted to put baked snack on my phone. Everything went great and was working so i decided to install step 2 to get better battery life and I shut down to boot into clockwork. Therein started my problems. It refused to boot in to clockwork, so i tried to boot back up and it wont get past the Samsung with their .com boot screen (sorry first post cant post the full screen due to url). I have nandroid backups but cant make use of it as clockwork wont boot up. Drivers were originally working fine on my pc but overnight they got screwed up. (they working now on my other pc)Before that i tried to use odin to reset with the .tar file pda method and it said invalid image file and wouldnt work. Please leave suggestions as i dont know where to go next. I am working on a new pc now and will try after download, running dsl and slowgoing. Currently my phone is a break
irule9000 said:
I am on root on 2.2 with Dk28 and epic all in one.Yesterday I decided I wanted to put baked snack on my phone. Everything went great and was working so i decided to install step 2 to get better battery life and I shut down to boot into clockwork. Therein started my problems. It refused to boot in to clockwork, so i tried to boot back up and it wont get past the Samsung with their .com boot screen (sorry first post cant post the full screen due to url). I have nandroid backups but cant make use of it as clockwork wont boot up. Drivers were originally working fine on my pc but overnight they got screwed up. (they working now on my other pc)Before that i tried to use odin to reset with the .tar file pda method and it said invalid image file and wouldnt work. Please leave suggestions as i dont know where to go next. I am working on a new pc now and will try after download, running dsl and slowgoing. Currently my phone is a break
Click to expand...
Click to collapse
Which tar are you flashing..whats the filename?
also have you checked to make sure it downloaded correctly without corruption via md5checksum?
checksum and tar
i used this page i used thread number 794138(cant post links) by whosdaman. I tried using dk28 and di18, Dk28 got checksum and di18 got invalid image. I just downloaded a new tar for dk28 and am currently trying odin on a different computer
Let us know what happens,I'm here to help for atleast 2 more hours.
Sent from my Frankenstein FROYO ROM using XDA App
dk28 got checksum, working on di18, i hate you dsl
irule9000 said:
dk28 got checksum, working on di18, i hate you dsl
Click to expand...
Click to collapse
any updates man?
hash dash invalid
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> MD5 hash value is invalid
<OSM> SPH-D700-DI18-8Gb-REL.tar.md5 is invalid.
<OSM> End...
Clockwork fixed
Goodnews bad news, I fixed clockwork and flashed clockwork backup, still wont boot tho
irule9000 said:
Goodnews bad news, I fixed clockwork and flashed clockwork backup, still wont boot tho
Click to expand...
Click to collapse
*Assuming that you want to return to the current official build used by sprint which is at this moment DI18*
*Assuming your phone can power up at all (if it doesn't there's a trick you can try for that mentioned elsewhere in the forums)*
*Only use main/direct-to-motherboard USB slot on PC (not on the face of your PC)*
*Only use high quality USB cable shorter than 3' and not the stock cable*
*Make sure SAMSUNG USB drivers are Installed*
*Make sure your battery is more than 50% charged*
1. SD Card is REMOVED, USB is UNPLUGGED and Battery is REMOVED from phone
2. While Phone is UNPLUGGED from USB, place battery in phone
3. Press and Hold the "1" key and Power button together to reach Download Mode
*KEEP USB UNPLUGGED FROM PHONE and phone in Download Mode*
4. Extract and Run Odin3.exe (Ignore the .pit file included in Odin3+v1.61andepic.pit.zip)
*Leave the "PIT" selection empty*
5. In Odin Uncheck "F. Reset Time", make sure "Auto Reboot" is the only box checked
6. In Odin click PDA and select your .Md5 file (SPH-D700-DI18-8Gb-REL.tar.md5)
7. Plug USB in PHONE and wait for yellow COM box highlight to appear in Odin
8. In Odin Press Start and WAIT patiently
Download SPH-D700-DI18-8Gb-REL.tar.md5 from the link on the first page of this thread where it says DI18 Update:
http://forum.xda-developers.com/showthread.php?t=794138
Download Odin from the link on the Wiki --look for "Odin3+v1.61andepic.pit.zip" under where it says "Odin Stock Flashing" at:
http://forum.xda-developers.com/wiki...Stock_Flashing
Download Samsung USB drivers from the link on the first post of this thread:
http://forum.xda-developers.com/showthread.php?t=770388
fck me
I really shouldnt have screwed with odin while tired and pissed. Lost clockwork mod and tried again. Now im stuck with a paperweight that can go into download mode or boot to a screen that shows an old flip phone triangle with an exclamation mark and a pc/laptop. If anyone knows what that means, please post
I've reached that screen 3 times and twice I've been able to get my phone back out of it (not something I'm exactly proud of).
try:
1. Remove sd card and battery and unplug USB
2. While first holding 1+Power button, re-insert the battery
and if that doesn't work try it with the USB first plugged in.
next try
1. remove battery and sd card
2. insert USB
3. press and hold down vol up + vol down (not power) and Replace battery
next try
1. remove battery sd card
2. plug in USB
3. re-insert battery
4. hold power + vol down only
and lastly try
calling sprint or samsung repair as applicable and plead complete ignorance as to how it happened and any knowledge of smart phones and android beyond what's in the basic user manual. Say something like "It was like that when I woke up"
that seems to be the certain solution for this problem from what I've read.
I see ur problem rename ur .tar.md5 file to just .tar you might have to enable extensions to be seen. I don't remember how I did it but I remember googling something like how to enable file extensions. If you successfully rename it you will get a warning and just click ok on it or whatever enables you to change the extension.then use that file in odin.
Sent from my SPH-D700 using XDA App
The flip phone triangle thing was something I had too. Make sure ur tar file is some where around 150mb to 200mb. The first time download my tar it was like 5mb for some reason
Sent from my SPH-D700 using XDA App
I tried the tar thing it worked better but im having issues with drivers and connection issues with odin. Its working better but im getting stuck at pram or something like that
Sry I really can't help you much more. I'm not a dev so I really don't know. I only speak from experience. Also you should be more specific I posted two things about the tar file.
I also checked how big the tar should be and it is 255 mb
Sent from my SPH-D700 using XDA App
i hate my phone
Every time i fix one problem another appears. My computer wont see my phone. The drivers are fine as my brothers epic 4g appears as normal. It seems that something in the phone is messed up. I have no other computer to test it on. Help me fellow xda members, what should i do.
Are you using the same cable thst your brother used? I couldn't get my computer (or a second one ether) until I used my wife's cable.
George
Sent from my SPH-D700 using XDA App
i tried about 5 different cables, but now for some reason im getting the original recovery? to load. Its really wierd, when i leave the phone something happens even when it is off. is there anyway to restore from the original recovery. Is there anyway to mount an sdcard without loading the phone. I dont have clockwork, but i have an update.zip file on my sd and i want to see if it will load anything. Unfortunately i took it out under the directions of someone else and the phone wont remount it. I was wondering if there is a way to trick the phone to remount it allowing to do the update via stock recovery
I'm sure that would be possible via adb...but I'm not well versed in that lol
Does your phone connect to the computer at all anymore?
Sent from my SPH-D700 using XDA App
thank you all the help. You guys were correct, i had an extension problem. After erasing md5 i was able to use odin. This was after i got lucky and my computer saw it as a modem on my much higher quality microusb. Im in the middle of a nandroid restore bringing back from stock di18 to good old dk28. Thanks all for help.
I was using Odin to install [KERNEL] stock+Voodoo stable 5.x for Vibrant and something went wrong, I'm not sure what but now I am stuck with the phone ! pc screen.
Odin will not recognize that there is a phone there if I just start a download Odin tells me <OSM> All threads completed. (succeed 0 / failed 0)
In another thread (whose fix didn't help me out) I read
masterotaku said:
Because..... "Phone ! PC" is not a hard brick. I've "Phone ! PC" bricked my Vibrant dozens of times.
Glad you've recovered though. It can be a scary screen if you're not used to seeing it!
Click to expand...
Click to collapse
Are there other recovery techniques?
Did you get where it says Download Mode? If not, take the battery out, put it back but don't turn on the phone. Then open Odin load the pit files and pda. The next step with the phone off, hold the volume up and down the same time and plug the usb cable while holding up and down buttons and voila....you will have COM # showing up in your Odin and ready to flash again
Check here :http://forum.xda-developers.com/showthread.php?t=810130&highlight=odin
dany865, following your instructions Odin did recognize that there was a phone attached. 0:[COM5] and I'm flashing the PIT and PDA from the thread you linked me to now. It's a slow moving process!
So slow that I swear it was frozen so I took and chance and closed ODIN, after all what was the worst that could happen I was already staring at a brick, and rebooted the phone. PRESTO, it was back to JI6.
I went straight to MiniKies and put 2.2 on that phone, then spent a bunch of time reinstalling applications and configuring ADWlauncher.
So far all I know for sure that was lost was my finely tuned setup, root access, and a month of SMS messages that were not backed up.
Thank you!
I you are gonna root I would highly recommend to get "Titanium backup pro". It makes the setting up process 10x's faster and has a tin of other great features.
Hey everyone,
so first let me tell you that I am not a newb so I tried every possible solution I could come up with, so this is just a last attempt.
So I wanted to tests some ROMs around since I had a free friday night and Odin screwed me over. I tried to flash JM9 with 512, some other Froyo ROMs and even gave a shot to Darky's resurrection. But no matter what I try, Odin always does one of these things:
It gets stuck at Initializing...
It gets stuck at SET PARTITION...
It gets stuck at Kernel flashing...
It turns my screen into a random colour and gets stuck (green, gray, blue, red so far..)
Tried flashing with/without PIT/Partition, 1 package ROMs, 3 package ROMs, etc.. To no avail. Tried to have the battery out for half an hour, etc..
All I can do with my phone atm is acces Download mode, so that kinda keeps me hoping, however it won't boot or go to recovery..
So any ideas anyone? Thanks for any help..
Download a known working copy of Odin and try that. also download new firmware from samfirmwares too just in case your current firmwares have become corrupted.
used odin 1.0 with pit 512
this was a guide i made for a not so savvy mate. so folder links and other bits you wont have but im sure it will help.
STAGE ONE
You will see in the stage one folder two items one is ODIN the other is a PIT file.
Lets plug your phone cable into a usb port ( on the main board is best not extensions)
Open up ODIN
On the left hand side make sure “Re-Partition” is ticked.
Now click on the words “PIT”
This should bring you up a selection window locate it to the “PIT” file in the same folder as ODIN.
Now put your phone in that downloader mode VOL DOWN+HOME+POWER
Plug the phone into the USB port.
You will now see the first box has a yellow com port under it (top left hand corner)
Now click start.
You will see some text in the bottom left message box.
This may take about 5mins.
But once it is done you will see a big green PASS!! In the top left box.
If its been to long say 10mins take battery out and start again.
If it doesn’t work second time Gtalk.
Once you see PASS!!!! Unplug the phone and take battery out.
STAGE TWO
On the right hand side click RESET ( its next to start)
Now un-tick RE-Partition.
Now in the stage two folder there is three files.
In ODIN click “PDA” this will bring up the selection window
Match it to this file
I9000XXJPY-REV03-PDA-low-CL757011.tar.md5
Phone matches with this file.
MODEM_I9000XXJPY.tar.md5
CSC matches with this file.
GT-I9000-CSC-MULTI-OXAJPY.tar.md5
Now that you have selected the files put the battery back in your phone.
Go back to downloader mode.
Plug phone it when you see the Yellow com port like in stage one click start.
This may take a while but you will see some text in messages box bottom left.
Once this is done we will again get the green PASS!!!!
The phone will proceed to the home screen.
You have successfully updated your phone to the latest version.
Pat on back.
Also make sure kies isnt running and try as many different usb ports as you can.
windows sucks at com port control.
Thanks everyone for the input but as I've mentioned I've tried all possible methods that came to mind. Even the one described above..
Any other ideas? :x
Could it be that your USB driver is screwing things up? Try flashing from a different port or better yet a different computer.
If all else fails maybe you could try to flash with Heimdall instead of Odin.
dakine said:
Could it be that your USB driver is screwing things up? Try flashing from a different port or better yet a different computer.
If all else fails maybe you could try to flash with Heimdall instead of Odin.
Click to expand...
Click to collapse
Different USB ports is always worth trying.
Sent from my GT-I9000 using XDA App
I always use Odin 1.0 but you could try 1.3 or 1.7.
Sent from my GT-I9000 using XDA App
Just throwing ideas around really.
can you get into upload mode? Try clearing SD card. Clearing cashe. All thy kind of thing.
Try flashing a different kernal disable all lax fix stuff.
What was your set up before you tried flashing?
Sent from my GT-I9000 using XDA App
Install (or re-install, whatever) USB drivers. http://forum.xda-developers.com/showthread.php?t=728929
Uninstall Kies (iff installed), it's horrible anyway
Like others said, use a different USB port. Reboot PC (lol, I know).
I like Odin 1.7 best so far...
And I agree, please describe your initial setup. Any fancy kernels? Lagfix/ext4?
Well finally. I did everything on my PC and nothing worked, but managed to try on friend's PC and it worked.
Anyone has an idea on what could have caused this? Hope future flashing will work on my PC
Also thanks to everyone trying to help, limited to 5 thanks only tho
I'm guessing it a driver issue. Assuming you have Windows, whenever you plug a USB device a driver is installed. You can see what these are if you enable the hidden devices: http://www.techrepublic.com/blog/window-on-windows/get-rid-of-old-device-drivers-hidden-in-vista/867 for Vista for example, but it works just like that for others.
Wipe every trace of the Samsung/Android drivers, uninstall Kies, run a registry cleaner, rebbot (obviously), and just reinstall the Samsung/Android drivers. Get the newest Odin. If that doesn't help, I have no idea what the cause might be.
I need some major help.
My Verizon Note 3 was rooted but nothing else special. Recently, it started locking up when I turn it on in the morning, had to remove the battery and restart. Sometimes the power button would stop responding. And finally, after a phone call, it restarted itself and gave me a message "Could not do normal boot." Please see pictures.
It would not go into the recovery mode, but would always go to the Fastboot mode (Download mode). I tried Odin but no success. I talked to Samsung and the rep said that's what happens when you root (standard BS), but still allowed me to send it in. I got it back a week later, not fixed, but with paperwork saying Warranty Void due to Root.
I've been searching everywhere to see if I can find some information on how to recover from this, to no avail. I've installed the correct USB drivers many times, but neither ADB Devices nor Fastboot Devices commands will find anything attached. Odin continues to fail, sometimes with a message saying "Erasing Userdata partition" or something like that. It wouldn't show when I was taking pictures to post here.
Any suggestions or ideas? Again, no access to Recovery. Odin failes with or without the PIT file.
Thank you in advance.
FreaKaDroidXYZ said:
I need some major help.
My Verizon Note 3 was rooted but nothing else special. Recently, it started locking up when I turn it on in the morning, had to remove the battery and restart. Sometimes the power button would stop responding. And finally, after a phone call, it restarted itself and gave me a message "Could not do normal boot." Please see pictures.
It would not go into the recovery mode, but would always go to the Fastboot mode (Download mode). I tried Odin but no success. I talked to Samsung and the rep said that's what happens when you root (standard BS), but still allowed me to send it in. I got it back a week later, not fixed, but with paperwork saying Warranty Void due to Root.
I've been searching everywhere to see if I can find some information on how to recover from this, to no avail. I've installed the correct USB drivers many times, but neither ADB Devices nor Fastboot Devices commands will find anything attached. Odin continues to fail, sometimes with a message saying "Erasing Userdata partition" or something like that. It wouldn't show when I was taking pictures to post here.
Any suggestions or ideas? Again, no access to Recovery. Odin failes with or without the PIT file.
Thank you in advance.
Click to expand...
Click to collapse
Sounds like the flash memory may have failed in some manner. Two words: Warranty replacement. Getting a replacement through Verizon is usually fairly simple once they realize they can't try and fix it by pressing factory reset in the settings. Did you try Verizon first or go straight to Samsung?
Edit: Nevermind, I just realized it says you are "Custom." My reading skills suck tonight. Maybe you can convince someone at Verizon that you tried some stuff on the internet to fix it and then it said custom. I don't know if a JTAG would help or not in this case. Maybe someone can chime in on that...
FreaKaDroidXYZ said:
I need some major help.
My Verizon Note 3 was rooted but nothing else special. Recently, it started locking up when I turn it on in the morning, had to remove the battery and restart. Sometimes the power button would stop responding. And finally, after a phone call, it restarted itself and gave me a message "Could not do normal boot." Please see pictures.
It would not go into the recovery mode, but would always go to the Fastboot mode (Download mode). I tried Odin but no success. I talked to Samsung and the rep said that's what happens when you root (standard BS), but still allowed me to send it in. I got it back a week later, not fixed, but with paperwork saying Warranty Void due to Root.
I've been searching everywhere to see if I can find some information on how to recover from this, to no avail. I've installed the correct USB drivers many times, but neither ADB Devices nor Fastboot Devices commands will find anything attached. Odin continues to fail, sometimes with a message saying "Erasing Userdata partition" or something like that. It wouldn't show when I was taking pictures to post here.
Any suggestions or ideas? Again, no access to Recovery. Odin failes with or without the PIT file.
Thank you in advance.
Click to expand...
Click to collapse
Have you tried factory reset from Android Recovery (vol up, home, pow)?
I haven't run into anyone yet who couldn't undo soft brick from Odin... My only suggestion would be to start from scratch and follow the link in my sig...
I know you said you d/l sammie usb drivers a few times, try uninstalling ANYTHING on your pc from control panel>uninstall programs that says Samsung... THEN download and install newest drivers...
If following the guide in my sig doesn't bring you back, you'll be the first! Best of luck!
I'll try those things. I cannot go into recovery unfortunately. It just says "Recovery Booting" to get my hopes up, and then says "Could not do normal boot." Next line "ddi : mmc_read failed". Then goes into the ODIN Mode.
I'll report back after I try your suggestions... Thank you.
az_biker said:
Have you tried factory reset from Android Recovery (vol up, home, pow)?
I haven't run into anyone yet who couldn't undo soft brick from Odin... My only suggestion would be to start from scratch and follow the link in my sig...
I know you said you d/l sammie usb drivers a few times, try uninstalling ANYTHING on your pc from control panel>uninstall programs that says Samsung... THEN download and install newest drivers...
If following the guide in my sig doesn't bring you back, you'll be the first! Best of luck!
Click to expand...
Click to collapse
Unfortunately it did not work. Same message on the phone "MMC: mmc_read fail", and in ODIN:
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I also tried it with and without the PIT file and both the same result. Do you think this may be an actual hardware flash memory failure? Is there a way to format around the bad portion of the flash memory? I wish I could try some adb or fastboot commands but it does not show in either.
Any other thoughts or suggestions would be very much welcomed and appreciated. There's gotta be a way...
FreaKaDroidXYZ said:
I'll try those things. I cannot go into recovery unfortunately. It just says "Recovery Booting" to get my hopes up, and then says "Could not do normal boot." Next line "ddi : mmc_read failed". Then goes into the ODIN Mode.
I'll report back after I try your suggestions... Thank you.
Click to expand...
Click to collapse
FreaKaDroidXYZ said:
I'll try those things. I cannot go into recovery unfortunately. It just says "Recovery Booting" to get my hopes up, and then says "Could not do normal boot." Next line "ddi : mmc_read failed". Then goes into the ODIN Mode.
I'll report back after I try your suggestions... Thank you.
Click to expand...
Click to collapse
Pull battery in between attempts, and try diff usb ports on pc too
Notorious 3
No success...
az_biker said:
Pull battery in between attempts, and try diff usb ports on pc too
Notorious 3
Click to expand...
Click to collapse
If you can't even get to odin without mmc read, maybe it is your memory. Sorry I couldn't help, can't beat hardware failures. .Best of luck
Notorious 3
not sure it would help but will it safe boot
power plus hit the menu button
Thank you for your inputs. I wish Samsung would've done a bit more than to just reject it with a Fail Description as "Device Rooted." I've been a loyal Samsung fan til now.
az_biker said:
If you can't even get to odin without mmc read, maybe it is your memory. Sorry I couldn't help, can't beat hardware failures. .Best of luck
Notorious 3
Click to expand...
Click to collapse
Unfortunately it goes straight into the Download mode no matter what I try...
NinCaptain said:
not sure it would help but will it safe boot
power plus hit the menu button
Click to expand...
Click to collapse
try the pit file by itself??
lol @ Samsung. That's NOT what usually happens when you're rooted. There's quite a large percentage of us that are rooted with zero issues...shame on them for not replacing it.
Anyway, are you sure you were *only* rooted? You didn't try to flash a ROM or mess with partitions?
And it's vol down + home + power for recovery. Did you pull the battery first before going into recovery?
PS - don't bother with fastboot, this device does not have fastboot enabled, only Odin. You're not gonna get a response that way regardless.
Yes. Tried that. There's only 1 Verizon PIT file I found anywhere. Would a different PIT file work?
oneandroidnut said:
try the pit file by itself??
Click to expand...
Click to collapse
I know, I've been rooting for years, many Samsung S3, S4, Note 2 and 3's. But I wasn't gonna argue with the low-tech rep when she was gonna let me send it in. I was hoping for a motherboard replacement but that did not happen.
Yes, I "only" rooted. I was just about to do some more because of other issues (like the power button and the locking up first thing in the morning) when this happened. I never expected anything I couldn't undo via recovery or ODIN or something I can find on XDA...
I've tried VolUp+Home+Power, VolDown+Home+Power, VolUpDown+Home+Power, just about all combinations, always with a battery pull. It always goes to the Download mode... I cannot get into Recovery. Tried all 4 of my USB ports with a few different USB cables. Tried my Windows 7 laptop and my iMac.
siciliano777 said:
lol @ Samsung. That's NOT what usually happens when you're rooted. There's quite a large percentage of us that are rooted with zero issues...shame on them for not replacing it.
Anyway, are you sure you were *only* rooted? You didn't try to flash a ROM or mess with partitions?
And it's vol down + home + power for recovery. Did you pull the battery first before going into recovery?
Click to expand...
Click to collapse
FreaKaDroidXYZ said:
I know, I've been rooting for years, many Samsung S3, S4, Note 2 and 3's. But I wasn't gonna argue with the low-tech rep when she was gonna let me send it in. I was hoping for a motherboard replacement but that did not happen.
Yes, I "only" rooted. I was just about to do some more because of other issues (like the power button and the locking up first thing in the morning) when this happened. I never expected anything I couldn't undo via recovery or ODIN or something I can find on XDA...
I've tried VolUp+Home+Power, VolDown+Home+Power, VolUpDown+Home+Power, just about all combinations, always with a battery pull. It always goes to the Download mode... I cannot get into Recovery. Tried all 4 of my USB ports with a few different USB cables. Tried my Windows 7 laptop and my iMac.
Click to expand...
Click to collapse
Looks like you've done everything I would do. Maybe list it on Craigslist or swappa as 'dev project' or 'for parts' and get something out of it? Sorry to see you stuck like this.
Notorious 3
I had the same issue, try the steps below:
If your able to go into recovery factory wipe everything (if not go to the next step)
Flash the pit file by itself,
After flash is successful reboot and go straight into recovery, wipe everything
go into download and flash the stock firmware
If this doesn't work also re-download the firmware and pit using a windows PC, I've had issues with Macs download the correct file... Hope this helps, I had the same issues as you, in the end I had to re-download the software and follow the steps above, took me two days to fix the problem but it ended up positive.
---------- Post added at 10:45 AM ---------- Previous post was at 10:41 AM ----------
2swizzle said:
I had the same issue, try the steps below:
If your able to go into recovery factory wipe everything (if not go to the next step)
Flash the pit file by itself,
After flash is successful reboot and go straight into recovery, wipe everything
go into download and flash the stock firmware
If this doesn't work also re-download the firmware and pit using a windows PC, I've had issues with Macs download the correct file... Hope this helps, I had the same issues as you, in the end I had to re-download the software and follow the steps above, took me two days to fix the problem but it ended up positive.
Click to expand...
Click to collapse
Also delete and reinstall your drivers, from time to time they get screwed up on PC. If you want feel free to send me your phone and I will test for you, I've been around the android world for a long time and have f up my phones/tablets many times but never had a hard brick.
Have you tried restoring using Samsung Kies? If you are in stuck in Download mode, this may work. Give it a shot.
Kies 3 is telling me that the device is not supported. It looked so hopeful for a little bit. Trying to find a workaround but haven't found one yet.
ryanbg said:
Have you tried restoring using Samsung Kies? If you are in stuck in Download mode, this may work. Give it a shot.
Click to expand...
Click to collapse