I am sorry if this has been asked and answered, I've been searching the forum board for 4.5 hours trying to find the answer or some sort of point in the right direction. If you know the thread to answer my question, please don't flame me, just point it out...
With that said...
I attempted to upgrade my epic 4G from EB13 to EC05 last night. I did this with Odin3, everything said it passed no problem. Yet, it did not work. It would get to the Samsung screen then vibrate, pause, vibrate, pause, then nothing, just stayed there.
I followed the directions to flash the original EB13 that was on the phone to begin with. I followed the directions exactly, Odin failed, big surprise right? Now, Odin simply verified the MD5 said it was good and stopped. Now my phone just gets the 'phone-!-computer' icon, I can still boot into the downloading screen, but am unable to get Odin to do anything, am I missing something, or is there anything I can do to remedy this?
OK, I just tried the Samsung updater for eb13 and it failed at param.lfs
I am befuddled...
Try downloading the tar file for odin again and see ifthat works u might have a bad tar file
Sent from my SPH-D700 using XDA Premium App
Estewa_619 said:
Try downloading the tar file for odin again and see ifthat works u might have a bad tar file
Sent from my SPH-D700 using XDA Premium App
Click to expand...
Click to collapse
It's worth a try but the Samsung updater has it's own tar already. I think the answer he's looking for is in the Wiki.
I've searched through the wiki. Am I missing something? I find the root/recovery programs, they all say how to root, but I am not finding how to recover. for example, "One Click Root and Recovery", even though I cannot boot my phone, will it still recover? I tried it in the download screen, but it does not connect. How do I use these to recover?
I tried redownloading the tar again, SPH-D700-EB13-8Gb-REL.tar.md5, but I get the same result, Odin checks the file says it's OK then stops doing anything.
Am I using the incorrect tar? is there a tar that's not an MD5?
Are you using your stock samsung cable?
Sent from my SPH-D700 using XDA App
From the Wiki-
"If you get a FAILED error after it writes "param.lfs", try this method:
1. Reboot the phone and reset Odin
2. Load the pit file and place the tar in the Phone section
3. Start the recovery
4. The process will hang while writing "factoryfs.rfs"
5. Reboot the phone and reset Odin
6. Load the pit file, place the tar in the PDA section, and start the recovery again
7. It should now complete in about 3 mins.
8. Congratulations! Thank noobnl
If that doesn't work, take out the battery and reboot into download mode with only the usb cord plugged in."
TimidBull said:
I tried redownloading the tar again, SPH-D700-EB13-8Gb-REL.tar.md5, but I get the same result, Odin checks the file says it's OK then stops doing anything.
Am I using the incorrect tar? is there a tar that's not an MD5?
Click to expand...
Click to collapse
Are u in download mode? (#1 on keyboard + power button) and are u putting the tar file under PDA?
Sent from my SPH-D700 using XDA Premium App
Remove the .md5 extension...it messes up Odin.
Do you BONSAI?
kennyglass123 said:
Remove the .md5 extension...it messes up Odin.
Do you BONSAI?
Click to expand...
Click to collapse
This right here, The tar will be tar.md5, simply remove the .md5 from the end and try it.
Odin gives me problems on certain PCs too, if you have another computer, give that a go.
mattallica76 From the Wiki-
"If you get a FAILED error after it writes "param.lfs", try this method:
1. Reboot the phone and reset Odin
2. Load the pit file and place the tar in the Phone section
3. Start the recovery...
Click to expand...
Click to collapse
I tried this already, same result after 25 attempts.
Are u in download mode? (#1 on keyboard + power button) and are u putting the tar file under PDA?
Click to expand...
Click to collapse
Yes I am in download mode, yellow work sign with digging android, "Downloading... Do not turn off Target.
Also yes, to placing the tar under PDA and using the stock cable, plugged directly into a directly soldered motherboard USB port
I am waiting for the tar to redownload, as soon as it does, I'll remove the .md5 extension.
I was trying to bonsai, that's how I got all screwed up.
Well....that didn't work.
Trying it now with the victory pit, and th eb13 tar. without the .md5 extension.
I got a small blue bar starting to show,
<ID:0/008> Added!!
<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Set PIT file..
<ID:0/008> DO NOT TURN OFF TARGET!!
Been this way for about 5 minutes so far. **CROSSES FINGERS**
An obvious one seems missed. Try it on a different USB port.
Sent from my SPH-D700 using Tapatalk
I tried a different usb port, as well as a different computer, no change. After last attempt as decribed, Odin reported the following
<ID:0/008> Added!!
<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Set PIT file..
<ID:0/008> DO NOT TURN OFF TARGET!!
<ID:0/008>
<ID:0/008> Re-Partition operation failed.
<ID:0/008> Removed!!
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
I attempted this 10 times with the same result.
Hmmm...progress
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Set PIT file..
<ID:0/008> DO NOT TURN OFF TARGET!!
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> boot.bin
<ID:0/008> cache.rfs
<ID:0/008> datafs.rfs
Click to expand...
Click to collapse
Damn....phone shut off.
Trying again.
How did the phone shut off with a USB cable plugged in it? That makes no sense unless you have a really really bad cable.
Sent from my SPH-D700 using Tapatalk
I was just reading a post in which the user had used odin to put on d18 and he had no issue. Would this be detrimental to my phone since I started with eb13?
Do I need a different pit file instead of the victory_8G_100528.pit?
This is my first Android, been a Palm guy for years, but after my pre problems, I made the change. Theoretically going to older version shouldn't hurt, but I wanted to be sure.
One last thing, I seem to currently be getting to the datafs and nothing seems to happen after that, it's been about 10 minutes in this state, normal?
Thanks all for the help and assistance so far! it is much appreciated.
no idea how it shut off, it was on download screen, then black. took out battery, set back into downloading mode (#1 and power), now back at the datafs point, waiting...
oh, and the cable is brand new, using my wifes cable from her two day old epic.
Related
Screen shows a picture of a cell phone and a computer with a yellow triangle.
Any way to get Odin to pick up on this to load the stock image back?
Yes, odin will work. Iv bricked my atleast 4 times.
Sent from my SPH-D700 using XDA App
Can you give me an idea how? I can't get into any other screen except this all black one with a white phone, yellow triangle, and white computer...I'm lost on this one - I never had an issue so far and this is my 3rd rooted android phone. I am far from noob.
Yep, got that screen a few times when first learning the in's and out of this phone.
Hold the #1 key on the slide out keyboard and press power to get into download mode. Use Odin to flash to stock and try again.
Ok - ODIN is giving me:
<ID:0/010> Added!!
<ID:0/010> Odin v.3 engine (ID:10)..
<ID:0/010> File analysis..
<ID:0/010> Get PIT for mapping..
<ID:0/010> Firmware update start..
<ID:0/010> home/n/Desktop/zImage
<ID:0/010>
<ID:0/010> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
What gives here? This is my first samsung, so ODIN is new to me.
Follow this.
http://forum.xda-developers.com/showthread.php?t=773032
Well, ODIN gets to "File analysis" now and just sits there.
Any other ideas?
Odin is now sitting at <ID:0/010> param.lfs
hasn't moved in 4 or 5 minutes....worrying me.
Well since you're not a noob, then I probably don't need to tell you that you should have odin open and ready, then plug the phone in, and THEN boot into download mode. In that order. you need to boot the phone into d/l mode before it starts charging once its plugged in. good luck.
infamousjax said:
Well since you're not a noob, then I probably don't need to tell you that you should have odin open and ready, then plug the phone in, and THEN boot into download mode. In that order. you need to boot the phone into d/l mode before it starts charging once its plugged in. good luck.
Click to expand...
Click to collapse
Yup, done all that. Trying another computer now - not sure why it gets stuck at that stoopid params file....
Got it working now. Thanks for the help guys.
Kcarpenter said:
Got it working now. Thanks for the help guys.
Click to expand...
Click to collapse
OK....
HOW did you get it working? Inquiring minds want to know.
Ok.. I was flashing Cognition to my captivate (using ODIN) when the usb cable came unplugged in the middle of flashing factoryfs.rfs.
I can't even get the phone to power on at all... No connect to computer icon, no recovery screen, no download screen, nothing no screen at all.
Any way to recover this? I tried several things
Three Button combo
VOL+ & VOL- while plugging in usb
remove battery and sim
etc...
Here's the ODIN log.
<ID:0/006> Added!!
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> Sbl.bin
<ID:0/006> boot.bin
<ID:0/006> cache.rfs
<ID:0/006> dbdata.rfs
<ID:0/006> factoryfs.rfs
<ID:0/006> Removed!!
Please help. Anyone know how to recover from this?
maybe needs to be charged?
try leaving it connected to power for a while..
If it will not turn on you might very well be bricked. As previously suggested, you could leave it plugged in and see if your battery is just drained. However, while you are waiting you can still do your research. Look over this thread: http://forum.xda-developers.com/showthread.php?t=775911 for a discussion on how to unbrick a captivate.
I would also suggest you check this one: http://forum.xda-developers.com/showthread.php?t=731989 as often flashing back to stock will "reset" the errors created while updating roms.
Was >90% battery when i started...
sourkrawt said:
If it will not turn on you might very well be bricked. As previously suggested, you could leave it plugged in and see if your battery is just drained. However, while you are waiting you can still do your research. Look over this thread: http://forum.xda-developers.com/showthread.php?t=775911 for a discussion on how to unbrick a captivate.
I would also suggest you check this one: http://forum.xda-developers.com/showthread.php?t=731989 as often flashing back to stock will "reset" the errors created while updating roms.
Click to expand...
Click to collapse
I can't even boot do download to use ODIN...
FIXED
OK... GOT IT... Here's what I did
1. Remove the battery, external SD card and SIM card.
2. Wait 10 seconds.
3. Open odin3
4. Insert battery.
5. Connect usb cable.
6. HOLD VOL+ and VOL- while plugging in USB
Got download screen and flashed with ODIN..
Could swear I tried that at least twice before posting... also, this varied from http://forum.xda-developers.com/showthread.php?t=775911, but was similar, so may be worth noting.
Yay... I feel better Thanks all.
Don't post things like this in development.
Sent from my Captivate
MikeyMike01 said:
Don't post things like this in development.
Sent from my Captivate
Click to expand...
Click to collapse
Issues that arise while working with a beta ROMS, especially flashing with ODIN (something that is experienced mostly by DEVELOPERS) is not for the development forum...
Anyway, thanks to all that helped
Glad you got it working. Gonna close this up.
I deem this closed
been trying forever to fix my phone, finally got it into download mode but odin just hangs? also the phone to PC light goes on when i try to turn it on.. does anyone know what i can do to get my phone back??
Try to odin back to stock and if that doesn't work try a usb jig
Sent from my SGH-T959 using XDA Premium App
odin again on a diff computer. odin can get pissy on some computers. if you can't possibly find another computer to use uninstall the usb drivers, reboot, install usb drivers then try to odin again on a different usb port. also re download the jfd files from here in case of bad d/l's.
Keep trying...Odin likes to be picky sometimes.
Sent from my SGH-T959 using XDA Premium App
And try a newer version of Odin.
k well i went from 1.3 to 1.7 and i was sure it was about to start working because the blue download sign showed up, when it just lagged for a bit.. all of a sudden the screen turned greenish.. and it got stuck at cache.rfs...
<ID:0/003> Added!!
<ID:0/003> Removed!!
<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> cache.rfs
what did i do wrong??? is my phone permanantly bricked now?? first time i see this green screen ever
damn now nothing turns onwhen i plug it in, no phone to pc, no download mode.. i think i bricked it for real this time, shieet
edit: so up/down vol plus pluggin in gets me into download mode, but the thing just wont load, the blue status bar just stays on like 5 percent and it hangs on cache.rfs
any suggestions
Try another usb
Unplug other usb devices, reboot
make sure the files are legit by checking the md5
Guide in my signature if needed
s15274n said:
Try another usb
Unplug other usb devices, reboot
make sure the files are legit by checking the md5
Guide in my signature if needed
Click to expand...
Click to collapse
Also try without the sim and micro sd card.
It worked for me before.
Sent from my SGH-T959 using XDA Premium App
If you are using a 64 bits try a 32 i have seen issues with odin and windows 64b
Sent from my GT-I9000 using Tapatalk
happened to me, it turns out its a usb port.
try another if that doesnt work
uninstall the drivers then reboot pc plug in phone then install drivers
Reboot your computer, once it begins starting immediately hold F8.
After a few seconds you will get the Windows Startup Menu.
Select "Disable Driver Signature Enforcement".
Then after computer starts up odin like you're doing and it wont get stuck at cache.rfs.
Sounds like a bad download to me
Beware of angry gingerbread man
try another usb and PC
VeryCoolAlan said:
happened to me, it turns out its a usb port.
try another if that doesnt work
uninstall the drivers then reboot pc plug in phone then install drivers
Click to expand...
Click to collapse
Was a bad USB port!!
I really messed up my phone :/
Hi, so about one month ago I decided to root my phone, but I did not know what I was doing since it was my first time and I was VERY confused. I ended up causing my phone to go into a bootloop, I'd first to even get it to work make it I'd make it go into download mode then restart from there. It'd just say in the top right corner "kernel is not seandroid enforcing" then afterwords it'd flicker the bottom buttons to just turn off completely. Any advice or help would be amazing , I won't mind spending time just to fix this so I'm all open
I recomend to flash the stock firmware on your phone.
Get the firmware file from fw.updato.com(fast but sometimes website is down)
Or
sammobile.com(slow but reliable)
Since you already sayd you tryed to root ur phone i suppose you know where to get odin3
Extract the firmware zip file y downloaded inside should be a .tar file put that in AP in odin and click start
Also i recomend a wipe but in theory it should* start working without.
Hope this helped you
Rainbow_Dash said:
I recomend to flash the stock firmware on your phone.
Get the firmware file from fw.updato.com(fast but sometimes website is down)
Or
sammobile.com(slow but reliable)
Since you already sayd you tryed to root ur phone i suppose you know where to get odin3
Extract the firmware zip file y downloaded inside should be a .tar file put that in AP in odin and click start
Also i recomend a wipe but in theory it should* start working without.
Hope this helped you
Click to expand...
Click to collapse
I've tried it before but I'll try it again, nothing really happens when I do it but mabey It'll work this time. I'll tell you whether it work or not
Nooooxa said:
I've tried it before but I'll try it again, nothing really happens when I do it but mabey It'll work this time. I'll tell you whether it work or not
Click to expand...
Click to collapse
Quick edit, my phone doesn't show up on the ID:COM area at all, I've tried other cables but it just won't work at all. I'm pretty sure it's from my phone itself and not the program
Nooooxa said:
Quick edit, my phone doesn't show up on the ID:COM area at all, I've tried other cables but it just won't work at all. I'm pretty sure it's from my phone itself and not the program
Click to expand...
Click to collapse
Oh no I forgot y need to have installed special drivers otherwise in some cases it won't show up. Get it from here în my experience first time it can take up to 1 hour for phone to be recognized. Also make sure ur phone is well enterd in download mode (volume down+home+volume up+power) a blueish screen appears and volume up again) there is no way it's bcuz of the phone. Also use the cable that came with the device and if it still doesn't work (for some reason) try in another pc (or mac)
Rainbow_Dash said:
Oh no I forgot y need to have installed special drivers otherwise in some cases it won't show up. Get it from here în my experience first time it can take up to 1 hour for phone to be recognized. Also make sure ur phone is well enterd in download mode (volume down+home+volume up+power) a blueish screen appears and volume up again) there is no way it's bcuz of the phone. Also use the cable that came with the device and if it still doesn't work (for some reason) try in another pc (or mac)
Click to expand...
Click to collapse
I got the driver installed and so far it's actually being able to connect ! but I have no luck at all, I put it in downloading mode, opened up oden then at a certain point my phone randomly went black then said "An error occurred while updating the device software. Use the Emergency recovery function in the smart switch PC software" Which I did end up doing but even while using that it will randomly shut off :/. Here's the oden log
"<ID:0/003> Odin engine v(ID:3.1203)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> sboot.bin
<ID:0/003> cm.bin
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img
<ID:0/003> __XmitData_Write
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)"
Nooooxa said:
I got the driver installed and so far it's actually being able to connect ! but I have no luck at all, I put it in downloading mode, opened up oden then at a certain point my phone randomly went black then said "An error occurred while updating the device software. Use the Emergency recovery function in the smart switch PC software" Which I did end up doing but even while using that it will randomly shut off :/. Here's the oden log
"<ID:0/003> Odin engine v(ID:3.1203)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> sboot.bin
<ID:0/003> cm.bin
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img
<ID:0/003> __XmitData_Write
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)"
Click to expand...
Click to collapse
Nevermind I found the issue! For some reason, my phone wasn't charged and my computer couldn't charge it enough. Dude, I can't thank you enough, I've been at this for a month now and never thought of going onto a forum. I was about to pay some guy $30 to fix it for me.
Nooooxa said:
I really messed up my phone :/
Hi, so about one month ago I decided to root my phone, but I did not know what I was doing since it was my first time and I was VERY confused. I ended up causing my phone to go into a bootloop, I'd first to even get it to work make it I'd make it go into download mode then restart from there. It'd just say in the top right corner "kernel is not seandroid enforcing" then afterwords it'd flicker the bottom buttons to just turn off completely. Any advice or help would be amazing , I won't mind spending time just to fix this so I'm all open
Click to expand...
Click to collapse
do you have flahed a custom rom?
or flash custom kernel? like audax kernel?
So awhile back I bricked my Samsung Galaxy Tablet 4 by installing a 1 click root app and later restarting my tablet. I haven't been able to fix it since. I was using an app because of the locked bootloader. Is there a way to fix this? The tablet uses the T337AUCU2BOH4 firmware which I think I was able to find through google, although it said it only worked for nonrooted apps which I didn't understand.
You could search about Odin. With it you can install samsung stock firmware on your device, if you can still boot to download mode. Also it's best to avoid 1 click root apps(if possible) they seem to cause problems very often.
keikari said:
You could search about Odin. With it you can install samsung stock firmware on your device, if you can still boot to download mode. Also it's best to avoid 1 click root apps(if possible) they seem to cause problems very often.
Click to expand...
Click to collapse
I found the firmware files here
I set my device to download mode and chose the file for the BL, AP, CP, and CSC section of Odin3 and click start. The program than stalls at SetupConnection and fails. I run Odin3 a second time and it's now stalling at Initialization. Later attempts I get a log with "Can't open the serial(COM) port". I Googled something that suggested I download the USB driver for the tablet so I downloaded this, but it didn't help.
Here's my log:
Code:
<ID:0/005> Added!!
<ID:0/005> Odin engine v(ID:3.1203)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Here's my log after running Odin3 a second time
Code:
<ID:0/005> Added!!
<ID:0/005> Odin engine v(ID:3.1203)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
Later attempts it now does this:
Code:
<ID:0/005> Added!!
<ID:0/005> Odin engine v(ID:3.1203)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Can't open the serial(COM) port.
<OSM> All threads completed. (succeed 0 / failed 1)
Can any help me figure out what I'm doing wrong here? I don't really know much about android so this stuff is all new to me.
WeirdoSarah said:
I found the firmware files here
I set my device to download mode and chose the file for the BL, AP, CP, and CSC section of Odin3 and click start. The program than stalls at SetupConnection and fails. I run Odin3 a second time and it's now stalling at Initialization.
Can any help me figure out what I'm doing wrong here? I don't really know much about android so this stuff is all new to me.
Click to expand...
Click to collapse
This guide says that you should only choose file for the AP, but I have no idea is that fix for your problem.
https://forum.xda-developers.com/tab-4/general/guide-how-to-restore-stock-firmware-t2979006
keikari said:
This guide says that you should only chose the file for the AP, but I have no idea is that fix for your problem.
https://forum.xda-developers.com/tab-4/general/guide-how-to-restore-stock-firmware-t2979006
Click to expand...
Click to collapse
Thanks for finding that! I was actually originally following that guide although I had to find the firmware files elsewhere. I tried just selecting the AP, but it didn't work. I'm still getting the same set of errors.
Edit: I restarted Odin3 and unplugged and the cord and plugged it back in and I think it's working now. It started downloading and the tablet rebooted when it was done. At first, it looked promising, but it booted to some AT&T logo in the middle and white background which scared me a little. After a minute or so it booted up to the welcome menu to configure the tablet. Thanks so much for your help!
WeirdoSarah said:
Thanks for finding that! I was actually originally following that guide although I had to find the firmware files elsewhere. I tried just selecting the AP, but it didn't work. I'm still getting the same set of errors.
Edit: I restarted Odin3 and unplugged and the cord and plugged it back in and I think it's working now. It started downloading and the tablet rebooted when it was done. At first, it looked promising, but it booted to some AT&T logo in the middle and white background which scared me a little. After a minute or so it booted up to the welcome menu to configure the tablet. Thanks so much for your help!
Click to expand...
Click to collapse
No problem. About that AT&T logo, you can get rid of it by finding "non-branded firmware" (or something like that I don't know the right term for it) or you can check if SM-T335 has same specs as your tablet(all its firmwares seem to be "non-branded"). Like with sm-t230 you can use sm-t231 roms. But be careful if you do that.
This site might have more firmwares http://forum.youmobile.org/downloads/?cat=151 thought I'm not sure have I ever tried to download from there. Atleast you can find build numbers there.
Or maybe rooting your device and changing boot animation.
Also there is a button for thanking : D (next to reply button) ---------------------------------------------------------------V