Related
Okay,
There is a growing number of us XDA members on the Vibrant platform who have just bricked out phones. Save for other DEV tools, which I have not used, do not have access, and do not know how to use, for all intensive purposes, this phone is Br'iKTed ! ! !
Here are the series of events
1. flashed the latest Bionix
2. Worked great, some bugs, but for the most part without incident.
3. Flashed new DOW Kernel,
4. worked great for 2 days.
5. then on night 2, the phone was stuck on the DOW Green robot screen
6. could not get into Recovery mode (none of the recovery modes)
7. Phone would not boot
8. ODIN back to stock
9. After Vibrant screen, the phone turns off. No soft keys, Nada!
10. Flashed JI5, Ji6, Eugene's Non Bricking Froyo (ODIN Files)
11. Same result, Turned off after Vibrant
and
12. still cant' get into recovery
I am having problems with the phone starting up and loading what I flashed.
I flashed JI5 Ji6, and Eugene's non bricking Froyo Rom
These 3 are the only ones I was able to find that is ODIN flashable
Why you ask?
I cannot get into Recovery, but I can get into Download mode. I can't get into any recovery at all. NOTHING. This is why ODIN seems to be my only option.
But regardless of any ROM i flash, my phone shuts off right after the Vibrant screen. No splash screen, no loading, no booting. .Nothing. It just shuts off.
I can't charge it either.
i get a Charging bootloop. HOurglass - battery shows up for a bit, then restarts over and over.
So in other words. it's ****ed.
Hope that explains it sufficiently. if you have any more questions or suggestions, Im open man, Im open.
Help me
So I'm not sure how DEVs would like to proceed on this.
TW (I've always loved your roms. Been following you since the first BIONIX 1.8)
Morific (If it's the Kernel, i'd like to know about it)
Thanks for reading guys. I wanted to give everybody a heads up.
I don't know what the problem is, but I do know that the phone does not work.
I'd appreciate some suggestions or anything.
And to inform the community that this problem is out there. I hope there aren't any more bricked phones.
Cheers,
have you tried using odin with the repartition checked
Yes I have.
Tried it with/ Without. Using Just the Tar file, using just the base file. I've tried it all.
Thanks
a4 moda said:
Yes I have.
Tried it with/ Without. Using Just the Tar file, using just the base file. I've tried it all.
Thanks
Click to expand...
Click to collapse
have you tried to odin to ka6 or ka7? something with a bootloader
not to be that guy, but how does this pertain to development? This sounds to me like an individual case of something going wrong and not an overarching issue with current available software. Just in case I am wrong I am flashing Bionix, and the DOW kernel myself to see if I end up with the same issue. My suggestion is flash back to stock, and exchange your device for a new one from T-Mobile.
I totally understand what your going through. I'm having the exact same problem, the DOW kernel flashed ok but then it didn't want to come off and it totally has my phone stuck on that damn green robot screen.
I soft-bricked my phone once by pulling USB cable immediately after ODIN forced my phone to reboot after flashing. It was the first time I ever ODIN'ed my phone, and thought the reboot (ODIN calls it reset) was the final step of flashing, and unplugged the USB cable. Anyway the phone did not initiate final step of the installation of JFD image, and went into boot loop. You can't imagine how freaked I was. It wouldn't go into recovery mode even if I pressed volume up, down and power combo, because it didn't stop rebooting right after the Vibrant logo. I am not sure if bootloader was not installed correctly, though. But I kept the phone rebooting for a while to see what happens. No luck. Eventually, I followed someone's instruction, and pulled my battery out, plugged USB to my laptop and to my phone, started ODIN, and popped in the battery. The phone immediately restarted into download mode, and I was able to flash the phone again.
My experience may not help you as it appears that you are able to flash ODIN-flashables, at least. But I hope this helps someone who's experiencing similar issues. And I would try downloading a JFD image and verifying MD5 before flashing. It could be bad downloads of the image files.
Try to go to eugenes forum and he has a file to download...it is his unofficial jk2 froyo rom. Don't use the old "froyo that does not brick" Try to flash that in ODIN. I just used it tonight when I got stuck in stock recovery with a MBR Check sum failure. That should get u back to where u can fix ur phone. Also I don't click the repartition button in ODIN just causes problems for me. If u need anything feel free to P.M. me.
Sent from my SGH-T959 using Tapatalk
STiGLOGiC said:
not to be that guy, but how does this pertain to development? This sounds to me like an individual case of something going wrong and not an overarching issue with current available software. Just in case I am wrong I am flashing Bionix, and the DOW kernel myself to see if I end up with the same issue. My suggestion is flash back to stock, and exchange your device for a new one from T-Mobile.
Click to expand...
Click to collapse
Completely reasonable. This pertains to development because if there is an endemic problem with one of our ROMS or KERNELS (not pointing fingers, just pointing out the possibilities that I know of, there could be more), people in our community need to know. Hence, I titled it "PUBLIC SERVICE ANNOUNCEMENT"
Thanks. I hear you about Tmobile. I'd rather not have to dump my problem on Tmobile if I can fix it, because I flashed the rom. Despite the fact that Tmobile JFS leaves something to be desired, they did deliver me a working phone. So i'd like to exhaust all possibilities before calling it quits.
hackman17 said:
I totally understand what your going through. I'm having the exact same problem, the DOW kernel flashed ok but then it didn't want to come off and it totally has my phone stuck on that damn green robot screen.
Click to expand...
Click to collapse
Exactly.
jaetm83 said:
I soft-bricked my phone once by pulling USB cable immediately after ODIN forced my phone to reboot after flashing. It was the first time I ever ODIN'ed my phone, and thought the reboot (ODIN calls it reset) was the final step of flashing, and unplugged the USB cable. Anyway the phone did not initiate final step of the installation of JFD image, and went into boot loop. You can't imagine how freaked I was. It wouldn't go into recovery mode even if I pressed volume up, down and power combo, because it didn't stop rebooting right after the Vibrant logo. I am not sure if bootloader was not installed correctly, though. But I kept the phone rebooting for a while to see what happens. No luck. Eventually, I followed someone's instruction, and pulled my battery out, plugged USB to my laptop and to my phone, started ODIN, and popped in the battery. The phone immediately restarted into download mode, and I was able to flash the phone again.
My experience may not help you as it appears that you are able to flash ODIN-flashables, at least. But I hope this helps someone who's experiencing similar issues. And I would try downloading a JFD image and verifying MD5 before flashing. It could be bad downloads of the image files.
Click to expand...
Click to collapse
Thanks for the heads up. I've gone through this myself many times. And i'm sure your post will help others out there. My problem (as well as many others on here with the same ROM and KERNEL I used) seems to be different and unique. Something that ODIN won't cure.
vibrant2010 said:
Try to go to eugenes forum and he has a file to download...it is his unofficial jk2 froyo rom. Don't use the old "froyo that does not brick" Try to flash that in ODIN. I just used it tonight when I got stuck in stock recovery with a MBR Check sum failure. That should get u back to where u can fix ur phone. Also I don't click the repartition button in ODIN just causes problems for me. If u need anything feel free to P.M. me.
Sent from my SGH-T959 using Tapatalk
Click to expand...
Click to collapse
Yes, tried that too. Same result. Vibrant.. then shut off.
Thanks anyway.
I had actually just had Bionix-v 1.2.1 and the new DoW combo to try out Voodoo Sound. I really loved the sound quality, but battery drain was not adequate as being my daily driver, even though I set it to run at 1ghz and used a sleep profile. After just over 2 days of use, I backed out by ODIN'ing to JFD and I installed Bionix-v 1.2.1 again. Only thing I have noticed so far is GPS not initiating immediately after it's turned on. I would go into GPS Test app, and turn on GPS after the app is started, but I get no satellites for at least 1 min. I used to get a lock within seconds, not minutes. I will try ODIN again tomorrow and see if it fixes. I guess I was lucky enough not to get a bootloop again though.
But I can't see why you and I would have any issues after the Bionix+Dow combo. Wouldn't ODIN just clear everything up? I even repartitioned when flashing, so my guess is that my system, data, datadata, etc., are all reformatted completely? Am I missing something?
I had the same problem. I flashed DoW and then the next day my phone didn't want to turn on. I pulled the battery and restarted it. It didn't want to start up all the way. It got to the vibrant screen and shut off. luckily for me, my replacement phone that I ordered a week ago came in the same day. I sent off my old phone letting samsung/tmo take care of it.
This exact same thing happened to me.
I too had the phoen bricked after flashing the DOW after Bionix 1.2.1
I have been flashing since the G1. This is the first time I've ever bricked a phone.
Hoping to get it fixed this weekend
Yo OP
Coming from a very scary brick my self, (phone wouldnt even turn on, bad dead horse test).
When your using Odin, are you using v1.7, are you using the correct stock JFD tar, when you repartion, are you using the correct pit file. Sounds to me that your partions are screwed, so try the pit approach first. If you phone wont boot at all after this, with odin open go into download mode by holding the vol rockers only, and plug USB in.
Then flash JFD.
black spirit said:
Yo OP
Coming from a very scary brick my self, (phone wouldnt even turn on, bad dead horse test).
When your using Odin, are you using v1.7, are you using the correct stock JFD tar, when you repartion, are you using the correct pit file. Sounds to me that your partions are screwed, so try the pit approach first. If you phone wont boot at all after this, with odin open go into download mode by holding the vol rockers only, and plug USB in.
Then flash JFD.
Click to expand...
Click to collapse
I spent over 12 hours working on this when it happened to me yesterday. Tried every tar and pit file and all versions of Odin I could find. There is no way to fix it with Odin. It is BRICKED!
If you have not already done this, I recommend doing this: http://forum.xda-developers.com/showthread.php?t=954509
Bay Wolf made a nice software for the computer that pretty much shows you a step-by-step instruction on how to flash to stock, reroot, and flash the new ROM of your choice. This program will push you into download mode, clockwork recovery, etc. There is a video on that link that will also show you a step-by-step instruction. Try that out if you haven't, and let us know how it goes.
That program comes with a PIT and TAR file for you to use as well.
Even if you say it is, this is not a Development thread and belongs in one of the other forums. I understand your frustration, however TW did not flash your phone, you did. Coming on here with a "PSA" that their ROM or Kernel loaded itself on your phone and broke it is not the way it should be done. Did you, before posting this, go to the TW irc for help or pm Sombionix or any other TW Dev?
Since you can Odin, Odin to stock 2.1 then connect to KIES mini while in download mode, if you can, and take the OTA.
drewdude007 said:
I spent over 12 hours working on this when it happened to me yesterday. Tried every tar and pit file and all versions of Odin I could find. There is no way to fix it with Odin. It is BRICKED!
Click to expand...
Click to collapse
I thought the same when it happen to me.
Nothing would work, but went that approach and happy days.
s1_odin_20100512.pit
and
T959UVJFD.tar
are the only ones you need, and if your good with your flashing, just do a pit first, no pda.
And if your still getting to download mode, ect, and dont have the computer /!\ phone icon on the screen, sounds like a soft brick.
jellette said:
Even if you say it is, this is not a Development thread and belongs in one of the other forums. I understand your frustration, however TW did not flash your phone, you did. Coming on here with a "PSA" that their ROM or Kernel loaded itself on your phone and broke it is not the way it should be done. Did you, before posting this, go to the TW irc for help or pm Sombionix or any other TW Dev?
Since you can Odin, Odin to stock 2.1 then connect to KIES mini while in download mode, if you can, and take the OTA.
Click to expand...
Click to collapse
I see where you're going, but he did not blame TW or anyone else. He may just be warning some people/asking for help. I do however agree that he posted in the wrong section.
Also, why would he need to pm sombionix or a TW dev before posting this?
SamVib said:
I see where you're going, but he did not blame TW or anyone else. He may just be warning some people/asking for help. I do however agree that he posted in the wrong section.
Also, why would he need to pm sombionix or a TW dev before posting this?
Click to expand...
Click to collapse
Because he started off with his problem stated as:
1. flashed the latest Bionix
2. Worked great, some bugs, but for the most part without incident.
3. Flashed new DOW Kernel,
Your phone probably IS charging.
Your /efs nodes may be messed up. Do you have a backup of your /efs?
Try reading here: http://forum.xda-developers.com/showthread.php?t=859914
My original issue got resolved thanks to s15274n. This mans ROOT walkthrough is amazing!!!!!
NOW I have a problem getting my ROM to load.
Im trying to Install the Malice ROM. and nothing is going quite as smoothely as I think it should.
This is attempt 2, the first time I waited an hour to try and install this rom, straight from SD, and I think the furthest it got was "installing ROM"
nothing. pull the batery out (I assume thats a total noob move, and at beast ill-advisable.) rebooted, went about my day. well, im trying again, and now the furthest ive gotten is "Installing update" the status bar is never filling or scrolling though.
Whats the problem? (going on about 15 minutes with no change btw)
You must use Odin to either
-Flash back to stock so you can reinstall packages
or
-Flash a voodoo integrated kernel so you can flash roms w/ CWM/Voodoo Recovery
Download a voodoo kernel and flash it using odin.
ok, I have the kernal and I have ODIN. once again I have never used ODIN< I definately used a one click root.
does anybody have a link to a thread with *detailed*, hold my hand, walk me through it and pat me on the butt at the end Instructions on this? It's a learning process and damn if im not learning something by the time this is all said and done lol.
last time it sat still for me when it said installing update, it was a bad download. I redid my download of the rom and it went through fast and smoothly. Thats how i fixed my prob maybe it will fix it for u.
I really need some help i want to cry
I got the samsung galaxy s(vibrant) and it doesnt go pass the welcome screen im trying to install a rom but i dont know how have looked over thing i installed odin3 and everything else but when i plug it to the usb it doesnt show on my computer idk why and nothing shows on the id com for odin someone plz tell me this can be fixed please can someone plz plz help me i begg you from the bottom of my heart
i always odin to stock whenever i flashed a new rom, works like a champ all the time.
elmoslonely said:
I got the samsung galaxy s(vibrant) and it doesnt go pass the welcome screen im trying to install a rom but i dont know how have looked over thing i installed odin3 and everything else but when i plug it to the usb it doesnt show on my computer idk why and nothing shows on the id com for odin someone plz tell me this can be fixed please can someone plz plz help me i begg you from the bottom of my heart
Click to expand...
Click to collapse
do you have the .pit and .tar files? Also, are you turning your phone off? There is an awesome guide by s15274n called the noob guide. It goes over very specifically how to root, it also has a small tutorial on rooting using ODIN3. Search the q&a forum, i believe thats where the guide is.
Also just to clarify, im not saying ur a noob or inept, im just saying its a super awesome guide. My phones neen rooted for three days now, ive flashef a bunch of roms and i always flash nack to stock...REALLY helpful tutorial. Good Luck!
Hi all,
I think I have soft bricked my S4 i337m rogers Canadian variant.
I had rooted / unlocked the bootloader with motochopper successfully.
- I am using CWM
First thing I tried to do was backup the phone onto the external SD which would not work so I just went onto the next step.
I tried flashing a ROM onto the phone after doing phone restore and clearing cache. All installed correctly (apparently) and now when I boot up the phone the Samsung logo will appear for about 5 seconds then the phone will go black and try to boot up again.
The good:
- i have access the recovery mode still
The bad:
- no recovery made for the phone
- seems to be boot looping
As a side not I have tried installing a couple other ROMs which all result in the same issue.
Is there anything that can possibly be done?
I would happily put the stock ROM back on the phone.
All help would be greatly appreciated!
Rob.
9 times out of 10 a factory reset will get you out of a boot loop. Do that in recovery and reboot.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Hi thanks for the reply. I have tried the factory reset and still does not fix the issue
Robby29 said:
Hi thanks for the reply. I have tried the factory reset and still does not fix the issue
Click to expand...
Click to collapse
If you are flashing a custom ROM that is not specifically for your phone, say a i9505 rom, you need to flash a Canadian kernel right after or you will bootloop. You also cannot flash any loki based roms either. As for the CWM backups, are you trying to back up to your external SD? If so, ensure the card is formatted fat32. To help get through your softbrick, just get into download mode and flash with odin
kiru said:
If you are flashing a custom ROM that is not specifically for your phone, say a i9505 rom, you need to flash a Canadian kernel right after or you will bootloop. You also cannot flash any loki based roms either. As for the CWM backups, are you trying to back up to your external SD? If so, ensure the card is formatted fat32. To help get through your softbrick, just get into download mode and flash with odin
Click to expand...
Click to collapse
Okay great I will try these. Does the kernel have to be specific to the ROM?
Robby29 said:
Okay great I will try these. Does the kernel have to be specific to the ROM?
Click to expand...
Click to collapse
The kernel is specific to your device. so you would use the i337M kernel.
So the procedure would be flash the rom of your choice, then before you boot flash YOUR i337M kernel, it will boot.
Good luck.
And make sure you do not flash a rom for the i9500 as you will hard brick
Also,
Make sure you choose the right i337m kernel. ie. a TouchWiz kernel for TW Roms and an AOSP kernel for CM10.1/AOSP Roms.
You should be able to:
remove your sdcard,
format it to fat32,
download the correct rom and kernel for you i337m to your freshly formatted sdcard,
put the card back into your phone,
boot into recovery,
install ROM zip from ext-sdcard,
install Kernel zip from ext-sdcard,
reboot.
phew....sounds like a lot of steps but not really I guess.
we good up in here....
Soft Brick S4
TheAxman said:
we good up in here....
Click to expand...
Click to collapse
Hello,
Greetings to you, I am sorry you have come to this point. I myself have bricked my phone just yesterday from flashing a bad ROM and not backing up my ROM properly. But I hope I can help you with some tips that i did to recover my phone fully. I apply some links to help you out but I recommend some patience lots of HW. ( Kies didn't work for me bugger =p.)
Unbrick S4 [Guide] -- http://forum.xda-developers.com/showthread.php?t=2265477&page=40
there is a user by the name of samersh72. you can request for a link to download your correct firmware it's best to get back to stock, ( don't forget to thank the user . )
this is someones video on youtube: http://www.youtube.com/watch?v=3a3qghhpDxg ( this helped me out as well)
I have these files/programs readied when I reverted back to stock
odin 1.3 ( i have odin 3.0 and didn't work for me reverting stock as it couldnt detect my tar.md5 file, but for some reason it worked for odin 1.3)
have your correct firmware ( I downloaded mine from http://www.sammobile.com, but for some reason I can't find yours, there is one on this site for sure just have the patience to look) make sure its for your correct carrier too.
im pretty sure you know how to do the DL mode, but just incase ill assume that you may or may not know, ill type this in anyway:
Get your S4 Download mode, [pressing up+power+home], (sometimes if i feel its not kicking in, just quick release then do it again)
open your odin 1.3, plug your phone in, tick auto-reboot, and F. reset time. PDA ticked, then find your correct firmware. hit start, then i hope from this something good will come out.
Best of wishes in your journey here in xda.
Cheers!
car154 said:
Hello,
Greetings to you, I am sorry you have come to this point. I myself have bricked my phone just yesterday from flashing a bad ROM and not backing up my ROM properly. But I hope I can help you with some tips that i did to recover my phone fully. I apply some links to help you out but I recommend some patience lots of HW. ( Kies didn't work for me bugger =p.)
Unbrick S4 [Guide] -- http://forum.xda-developers.com/showthread.php?t=2265477&page=40
there is a user by the name of samersh72. you can request for a link to download your correct firmware it's best to get back to stock, ( don't forget to thank the user . )
this is someones video on youtube: http://www.youtube.com/watch?v=3a3qghhpDxg ( this helped me out as well)
I have these files/programs readied when I reverted back to stock
odin 1.3 ( i have odin 3.0 and didn't work for me reverting stock as it couldnt detect my tar.md5 file, but for some reason it worked for odin 1.3)
have your correct firmware ( I downloaded mine from http://www.sammobile.com, but for some reason I can't find yours, there is one on this site for sure just have the patience to look) make sure its for your correct carrier too.
im pretty sure you know how to do the DL mode, but just incase ill assume that you may or may not know, ill type this in anyway:
Get your S4 Download mode, [pressing up+power+home], (sometimes if i feel its not kicking in, just quick release then do it again)
open your odin 1.3, plug your phone in, tick auto-reboot, and F. reset time. PDA ticked, then find your correct firmware. hit start, then i hope from this something good will come out.
Best of wishes in your journey here in xda.
Cheers!
Click to expand...
Click to collapse
Thanks for posting this. I hope many people read it. Anyone who flashes needs to know how to return to stock before they start flashing roms. You will need it someday!
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
I tried to install CWM earlier today and its gone wrong and now i get the dreaded error message
Firmware upgrade encountered an issue etc
Kies wont recover it either.
Now im hoping i can get it going again quickly
Just from skimming through here while trying to pack i gather i need to use odin to reflash the stock firmware.
I wouldnt normally ask but could some nice person spoon feed me given the circumstances of time constraints
Gavin01 said:
I tried to install CWM earlier today and its gone wrong and now i get the dreaded error message
Firmware upgrade encountered an issue etc
Kies wont recover it either.
Now im hoping i can get it going again quickly
Just from skimming through here while trying to pack i gather i need to use odin to reflash the stock firmware.
I wouldnt normally ask but could some nice person spoon feed me given the circumstances of time constraints
Click to expand...
Click to collapse
All you need to do is search google. No one spoon feeds you in real life so no one shouldn't spoon feed you here also.
http://forum.xda-developers.com/showthread.php?t=2261573
You need to follow these instructions but you need to download your correct firmware.
Sent from my SAMSUNG-SGH-I337
Use Odin to flash stock firmware by following this guide, I assume that you have the i9505, if so then flash this CWM,
thanks i need to find the right rom now
thanks fingers crossed
EDIT
im guessing this is the right rom
I9505XXUBMEA_I9505OXXBMF1_XEF.zip
thanks guys weve done it!
its resurrected!
cheers
I stuffed my phone up again and thought id post here instead of making a new thread.
flashed the latest modem which in turn has for some reason fubored all my dialling out and messages etc so i cant use the phone for anything other than browsing .....
I9505XXUBMEA_I9505OXXBMF1_XEF.zip<<<<<<<<<<<<this is what i used last time and it didnt work this time
so ive now tryed this one I9505XXUFNB8_I9505BTUFNB3_I9505XXUFNB8_HOME.tar.md5
my phone is a sim free s4.
the second one appears to work but wont get passed the lock screen with out continuous errors. (i note i now have the knox label in the bootloader)
How do i find the latest stock rom for my phone? so i can start again?
thanks
I had exact same issue so i falshed XXUFNB9 from sammobile and now im rooted runnin cm11 m9 .
Do suggest UNISTALLING samsung usb drives from pc and reinstalling fresh new ones for your device snd then flashing. I flashed 4 different firmwares. It was only until i reinstalled s4 usb drives my phone becsme alive. Dunno how but i reckon usb drives is the issue
Recently I wanted to unroot my Galaxy S4 ATT I337 and return back to Stock. It hasn't been my first time doing this, so I knew sort of what I was doing. I used Odin v3.10 and flashed an NB1 tar file and it worked fine, but as it finished flashing it said the device had been removed, showing up as a fail. So I disconnected the cable and tried again, and started getting error messages. I guess it might have had to do something with that, but now it keeps giving me a fail message every time I try to flash with Odin.
My phone now shows this firmware error on default and Odin seems to be failing every time. Is there anyway to fix this, or did I just completely screw this up?
I think you might have just screwed it up. If the device is removed in the middle of flashing with Odin that's not a good thing.
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
I think you might have just screwed it up. If the device is removed in the middle of flashing with Odin that's not a good thing.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Well, I guess this is what I get for flashing so carelessly. I hope that this doesn't happen again.
Daze_ said:
Recently I wanted to unroot my Galaxy S4 ATT I337 and return back to Stock. It hasn't been my first time doing this, so I knew sort of what I was doing. I used Odin v3.10 and flashed an NB1 tar file and it worked fine, but as it finished flashing it said the device had been removed, showing up as a fail. So I disconnected the cable and tried again, and started getting error messages. I guess it might have had to do something with that, but now it keeps giving me a fail message every time I try to flash with Odin.
My phone now shows this firmware error on default and Odin seems to be failing every time. Is there anyway to fix this, or did I just completely screw this up?
Click to expand...
Click to collapse
Are you flashing the official odin?
Did you try the Kies emergency recovery?
Did you try a different cable and port?
I always recommend one directly connected to the motherboard.
BehrendsTech said:
Are you flashing the official odin?
Did you try the Kies emergency recovery?
Did you try a different cable and port?
I always recommend one directly connected to the motherboard.
Click to expand...
Click to collapse
I'm not too sure if I'm really flashing the official odin, but I've used it before and it's worked. I've tried the Kies emergency recovery but when I connected the cable to my phone it showed up as an unsupported device. I've tried two different cables but haven't changed the port.
Although after spending 4 hours searching the Internet for a fix, I actually found a website that showed me how to fix it. It worked well, and now I'm back to stock on my phone. The first few tries actually ended up as a fail, but for some reason the last attempt ended up with my phone actually turning on, and I was thankful to see the startup screen.
Daze_ said:
I'm not too sure if I'm really flashing the official odin, but I've used it before and it's worked. I've tried the Kies emergency recovery but when I connected the cable to my phone it showed up as an unsupported device. I've tried two different cables but haven't changed the port.
Although after spending 4 hours searching the Internet for a fix, I actually found a website that showed me how to fix it. It worked well, and now I'm back to stock on my phone. The first few tries actually ended up as a fail, but for some reason the last attempt ended up with my phone actually turning on, and I was thankful to see the startup screen.
Click to expand...
Click to collapse
Good to hear!