I used Odin yesterday to Flash the new JI6 OTA update, after doing so it Odin said Pass but on my phone the error message read:
E:Cant mount/dev/block/stl10
I flashed stock ROM T959UJFD prior to flashing the new JI6 and went without cause. I pretty comfortable with Odin and have used it many times.
After the error the phone with boot up into the Vibrant Boot screen then go straight to Recovery. I tried rebooting and same result.
I tried Deleting all user data and same result.
I tried all the options available in recovery and still will only boot into recovery mode.
I tried plugging it into my pc and using adb to reboot into download mode but it will only reboot back to recovery.
When i have it Plugged into my pc and Odin open, Odin sees the device and opens up the COM line but won't do anything unless its in download mode.
Any help would be appreciated. "Crap now I'm one of those threads"
Ugh... I know this problem all too well. Did you click on the partition option in Odin when flashing to JI6??? If so, I hope you don't have a hardware locked phone!
Edit: Should probably elaborate a bit more.
To fix this simply get yourself into download mode manually by powering off your phone/removing battery/etc, and then power it back up while holding vol up + vol down. There are numberous methods to get into this mode unless you're hardware locked like me. Hopefull this will throw you into download mode and allow you to flash back to stock rom. If you're able to get this far simply try flashing the update again.
If you're hardware locked the only way I know of to fix the phone is either have TMO replace it with a phone that's not HW locked, or get Samsung's customer service center to give you an RMA for replacement. Either should work since what is now an official update borked your phone. I'm still waiting for my wife's phone to be returned in a hopefully non-Hw locked state. We'll see!
Good luck!
Mod close thread please, phone being replaced.
Listen i'm somewhat new so forgive me if i posted in the wrong place.
Just hear me out please.
Ok heres a little s/a. I have a samsung vibrant, last night i flashed my vibrant which was on a rooted vibrant9 rom. To bionix 1.9.1 w/ jacs oc kernal and the voodoo lagfix. Before flashing to the bionix i switched the boot logo and .wav file to one i perfered, i also did the same for the shutdown logo. Now, per the instructions for installing bionix 1.9.1 i took a nandroid backup of my phone on vibrant9 before performing the flash. After i did i flashed using clockwork. Everything went fine, the phone flashed, rebooted and was working great. However i rebooted the phone and relized that the shutdown screen wasnt working as it should because i forgot to include the shutdown.cfg thats required. What i did was took the bionix.zip off my sd card went into it and added the .cfg file i needed. I added it back to the sd card and figured i'd just reflash and all would be fine. Not so lucky however, i tried to reflash using clockwork (which took me to the regular recovery menu you would get to holding down the volume buttons and power) and it failed giving me an error which said "error on line 80". Relizing that the instruction said that if you had the voodoo lagfix you should disable it, i decided to do a factory wipe of all data (thinking that would definitly disable voodoo) after the factory wipe i attempted to flash bionix 1.9.1 again with no luck. After the last attempt i decided to just restore using the nandroid backup of vibrant9 i had taken earlier, the phone went through the restore process with waht appeared to be no problems. After it finished i rebooted from the recovery menu then bammmm. The phone is stuck in a boot loop. Its not a normal boot loop though the initial samsung logo will pop up for a sec then the phone screen will show what looks like tv static for a sec, it just keeps repeating this. To get it to stop i have to pull the battery. Ive tried booting into recovery by holding the volume buttons and the power button, but all that happens is the phone starts into the above mentioned bootloop. As a note whenever i plug the phone up via usb to my computer a grey battery screen pops up but it dosent charge it just sits there, and if i unplug the usb it goes right back into the bootloop. Also my computer will not recognize the phone so using odin seems like a lost cause. I read in a forum for this phone just a bit earlier that its nearly impossible to brick this phone. Have i done the impossible?
Well it sounds like you have hardware locked phone. Also you cannot do a nand restore w/ voodoo enable. That's your problem. There are threads on xda about recovering hardware lock phones. You need to search. If you can get into download mode, you need to flash eugene373's "Froyo that does not brick". Also, once you get phone working, isuggest you keep a disable-lagfix zip on your internal sd.
Sent from my SGH-T959 using Tapatalk
Great Success
Ok, ok after what seems like a million tries i finally got my vibrant working. After finally getting my vibrant into download mode (by removing the battery, putting the battery back into the phone, holding down both volume buttons and plugging in the phone via usb) i used odin to try and flash back to the factory rom. The flash worked except for an error i noticed when the phone was kicked into factory recovery mode to format itself. There i noticed that at the point when all user data was supposed to be wiped it would have a failure to wipe data. After the flash completed with this error i was able to get past the boot loop. At this point my phone would finish the boot sequence but after the samsung s disappeared the screen would just stay black. However, when ever i pushed any of the soft keys on the front they would light up. So what i did was followed the instructions in the above post and used odin to flash eugenes froyo rom that wont brick. Again the flash would complete but when the phone was kciked into factory recovery mode i got an error and it wouldnt complete it would just hang. So what i did next was use odin to again flash the factory rom and to my surprise it worked. So my vibrant is now restored to its full glory. I owe everything to the patrons of this community. Thanks all.
So on Thanksgiving my phone freaked out. blah blah blah. Used Odin and went back to stock. Since then i can not enter recovery mode at all. Not by pressing correct buttons or by using Rom Manager.
What it does is it boots up and goes to the first vibrant screen and will just sit there until I pull the battery.
I used to be able to get in to recovery mode with no problem... my phone was not hardware locked before. I just did not know if by flashing to stock would cause it to become hwl, or if anyone knew what the hell was going on with it! I also pushed in a button combo into the phone and wiped it to a factory fresh state also.
EDIT:
Now my phone would just not go past the first vibrant screen. Had to use odin to go back to stock once again... accept when it was done it did that error where i get red font at the bottom.... i was able to get it in to clockwork recovery... then i just flashed a zip that i had on it.. took a while but its working
ironically, and i stress.
IRONICALLY.
as soon as 2011 rolls around, i suddenly loose service?
and i figure it's a problem with the rom that conflicting with the radio, so i restore using Clockwork ROM Manager.
upon doing so, I first get a Yellow Exclamation point, so I restart my phone.
it goes through the process, and then it stays at the "Vibrant" screen for a good 20 minutes.
did I do something wrong? :/
Were you going from froyo to an eclair backup? Backup's don't restore the kernel, hence hanging.
Most would suggest to odin back to stock.
no, it was from Eugene's 2.3 clone to stock.
and I already backed up my stock rom, but I think I used the wrong method of restoring.
like, I went to ROM Manager, Restore Backup, and I had a big exclamation point.
I let it sit for 5 minutes, nothing happened so I restarted.
It restored and everything, and then it just bricked at the Vibrant screen.
to be more specific, i used this rom:
http://eb-productions.proboards.com/index.cgi?board=samsungsgs&action=display&thread=144
i backed up using both nandroid and rom manager.
i hope this can be restored.
because it's not a critical brick.
but just a soft one.
it won't boot into download mode with the power button/vol trick because I tried it before.
it just flashes on a black screen, and i usually use cmd to do it.
but because it's possibly hardware locked, i cannot do anything from cmd because it says "the device is not ready" even though it's plugged in to my computer.
please tell me someone can help me.
i think it's unfixable because of two reasons:
1. i am hardware locked, and i cannot boot it with the power key trick.
2. cmd can't find the device, even though it's recognized by my computer and odin.
primarily, my computer sees the drive i need to access, but i cannot connect to it because my phone won't get past the vibrant screen.
so, i think it might be full bricked and there isn't anything i can do to fix it.
but it's weird, because ODIN sees my phone, but there is no way to download the stuff i need from odin on my phone.
sorry to spam like this, but i really need the help.
I've had this problem in the past but I got my phone back in september/october so my vibrant isn't hardware locked
I would keep trying, last night I bricked my phone while flashing a rom and I was barely able to get it into download mode...
Try this combo:
1. Hold power + 2 volume buttons while plugged into computer
2. Keep holding until vibrant logo flashes 3 times
3. Right before the vibrant logo shows for the fourth time RELEASE VOLUME UP BUTTON
4. Odin back to stock
This always works for me, but liked I said, my phone is not hardware locked this may or may not work
Sent from my SGH-T959 using XDA App
it's not going to work because my phone is hardware locked.
but i'll try. :/
Try pulling the battery and sim and try odin again...should be working if you see a com port in odin.
no it didn't work.
would i be able to call t-mobile and tell them that upon a soft reset, the phone stopped booting?
Are you sure it's a hardware locked? Even before you flashed a custom rom you can't access the recovery through the 3 buttons?
Sent from my SGH-T959 using XDA App
Edit: see following post
You went from eugene r2 to stock? Stock meaning 2.1 that came with your phone? It definitely sounds like a soft brick due to kernel mismatch...
I tried updating my ROM (to CM11) and came across so many issues. For some reason, it kept rebooting and then at one point just got stuck at the animation screen. So I decided to just start everything from scratch again.
I tried to get into download mode to install CWM, but the phone kept shutting off as soon as I got in. After MANY tries, I finally got in and got it installed. When it finally worked, I tried to get into recovery mode and the same thing happened. Finally after many tries I was able to get in there too. I then installed my ROM and then when it finally loaded, the phone then shut off and tried rebooting but wouldn't get passed the animation screen again.
I did a lot of research and found that some people had their internal power button either get stuck or become defective. Mine clicks so I don't know if that's the problem, but the symptoms that others have mentioned have all happened to me.
Does this in fact sound like a button issue to anyone? Any help is appreciated.
moraha1287 said:
I tried updating my ROM (to CM11) and came across so many issues. For some reason, it kept rebooting and then at one point just got stuck at the animation screen. So I decided to just start everything from scratch again.
I tried to get into download mode to install CWM, but the phone kept shutting off as soon as I got in. After MANY tries, I finally got in and got it installed. When it finally worked, I tried to get into recovery mode and the same thing happened. Finally after many tries I was able to get in there too. I then installed my ROM and then when it finally loaded, the phone then shut off and tried rebooting but wouldn't get passed the animation screen again.
I did a lot of research and found that some people had their internal power button either get stuck or become defective. Mine clicks so I don't know if that's the problem, but the symptoms that others have mentioned have all happened to me.
Does this in fact sound like a button issue to anyone? Any help is appreciated.
Click to expand...
Click to collapse
Seems like your hardware button could be broken, I would all do in this order:
Download Philz Touch Recovery from here: https://goo.im/devs/philz_touch/CWM_Advanced_Edition/i9300/
Official Firmware from here: http://www.sammobile.com/firmwares/3/?download=28378
Flash Philz touch through Odin
Reboot to Recovery, selct "Clean to install a new rom"
Wipe cache and dalvik cache
Go to downoad mode and flash the md5.tar file through odin