Related
I just did the regedit trick and downloaded the froyo update but when i go into the phone i just keep getting error messages about launcher not loading etc.
I have factory resent and cleaned cache but still wont work. I cant download the old updates through kies any more how do i get it back to how it was with the old software? I am stuck and freaking out lol
guess you have to flash an older FW like JM2 with Odin ... check out FAQ in this section (sticky).
I really stuffed it up now i somehow flashed a captivate rom onto it from atnt and now it wont even go past the white screen. I cant use the 3 buttons to get it into recovery mode or download mode. And the computer is not recognising the phone. Have i stuffed it for good?
try volume up + volume down + power
the AT&T / Tmobile version uses that combination
instead of Volume down + home + power
Go into recovery mode and factory wipe if you have issues such as services force quitting.
livefree2x said:
I really stuffed it up now i somehow flashed a captivate rom onto it from atnt and now it wont even go past the white screen. I cant use the 3 buttons to get it into recovery mode or download mode. And the computer is not recognising the phone. Have i stuffed it for good?
Click to expand...
Click to collapse
Captive rom onto Galaxy phone? Curious how did you do that as these two are two different phone. You are not the first one but reading from the posts from people who did the same mistake, I'd say you have bricked it. Sorry to be the bearer of the bad news
i have
I have tried all combinations of keys and it just keeps loading up with white att international phone and then that screen just flashes every few seconds and doesnt go any futher. It wont go into downloadin or recovery.
im thinking of doing the update
did you do anything eles besides the update to cause this
Look, the only possible way to brick the phone (that i know of) is to flash others phone rom(Captivate being the usual suspect) into Galaxy.
This changed the button combo to enter download mode in Galaxy (as Captivate has different combo for download mode) so it is not possible to enter the download mode and reflash. Therefore you are stuck and cant do nothing Im afraid
Just curious , why so many people flashing Samsung Captivate rom into their Galaxy?
Some other examples
http://forum.xda-developers.com/showthread.php?t=749546&highlight=captivate
http://forum.xda-developers.com/showthread.php?t=751712&highlight=captivate
http://forum.xda-developers.com/showthread.php?t=767420&highlight=bricked
ok with that said then will the JPC update work on the bell galaxy s GT-I9000M
Bobler420 said:
ok with that said then will the JPC update work on the bell galaxy s GT-I9000M
Click to expand...
Click to collapse
Since it is the same Galaxy S i9000, I'd say It'll work. But I could be wrong To be on the safe side, you could ask for other Bell Galaxy users' feedback. Dont know about Bell, but Romanian Orange users are getting their phone locked after the flash.
usualy when something wrong w/0 3 buttons
usualy when something wrong w/0 3 buttons the phone rebooting in recovery mode itself to reboot it in download mode install correct adb drivers and use command "adb reboot download"
decided
I have just decided i am going to take it to one of the local Samsung repair centres i explained it over the phone and they said they could fix it for $49.95 or they could try and push for warantee but i told them i would just pay it will take longer for them to apply for warantee get rejected and then i pay anyways.
I miss it already i had to go back to my nokia N95 which was from a few phones ago now lol
i think the benfiets can wait till the official release ryanza lagfix fix all the lag problems that i had how important is flash really use your computer
Please explain exactly where you got the rom from so we don't make a similar mistake.
I'd pay the 50 too instead of waiting weeks and weeks :\
I got
I got the original rom through samsung kies using the reg edit trick that was shown in one of the threads. After a factory reset and a cleared cache it loaded up but started coming up with all these pop ups that things wont load and need to be forced shut etc.
So i decided to just flash it back using Odin but at 12 at night and in a panicy state thinking i have stuffed my phone for good i clicked on a captivate rom without looking at the heading of the thread that a link took me to for the galaxy s.
But as i said before for 49.95 to get it fixed is easier then me trying all these other things and getting in more of a panic about doing worse things to it. I assume it will be easy for them to fix it. A friend said he had a nokia he bricked where USB wasnt connecting and the screen wouldnt come on etc and they just used a computer that does something and fixes it.
got
Just got the phone call they managed to fix my galaxy for $49 and getting it back tomorrow oh how i have missed it i had to go back to a old old phone the nokia 95 lol.
Continuing my quest for confirming an unlocked/locked bootloader, I have stumbled across a key combo for getting into download mode! When the phone is off, hold the volume up button and plug in the micro usb cable, the phone should then boot up (on its own, do not touch the power button) to a screen with a grey box with a down arrow that says download mode. For anyone that used to own a Samsung Galaxy S phone, this mode was the primary mode for flashing roms via Odin and Heimdall. Now we just need a recovery rom and flashing software (possibly [AIO] ROMTools, I will fiddle around with it tonight).
Confirmed on Bell Optimus LTE, unit must be off, hold up while plugging in USB cord.
gte460z said:
Continuing my quest for confirming an unlocked/locked bootloader, I have stumbled across a key combo for getting into download mode! When the phone is off, hold the volume up button and plug in the micro usb cable, the phone should then boot up (on its own, do not touch the power button) to a screen with a grey box with a down arrow that says download mode. For anyone that used to own a Samsung Galaxy S phone, this mode was the primary mode for flashing roms via Odin and Heimdall. Now we just need a recovery rom and flashing software (possibly [AIO] ROMTools, I will fiddle around with it tonight).
Click to expand...
Click to collapse
This is great news! I've been needing to re-flash the stock ROM since day one (when I hosed my root with a bad busybox)...
Very nice find... I had been able to get into download mode before, but I didn't realize it was the usb connection that allowed it.
If you look in some of the other threads you will see that I have been able to locate the boot and recovery partitions - just 'standard' emmc partitions. I have pulled the data off the device and unpacked them so that I am able to look at the data within the partitions. Next is to start to understand what is inside the files - mainly init.rc and the other .rc files.
Currently I think part of the lack of recovery for us has to do with a line in init.rc:
service adbd /sbin/adbd recovery
disabled
Something tells me this will disable the recovery capabilities for the phone... but still looking around to figure it out. Will keep everyone posted.
Please do! Sounds like we are making progress as a whole!
great news guys!
thx 4 ur hard work!
hope ur next good news~
Wonderful news we are getting this past week!! Much progress has been done I'm getting so excited at where all this will lead us to Glad to be part of a sub-forum with tons of fiery passion and dedication. I'm not much of a help since I'm not good with any of these things, but I'll contribute in any way possible
Just got this phone for Christmas, but they were out of stock at 2 nearest stores to me. Have to wait a day or 2 for it to be shipped alas.
If you set it so that start adbd in recovery is enabled, what happens when you use ROM Manager to boot into recovery? I tried booting into recovery without editing the init.rc and I got a little Android guy with an open box and an arrow coming out for a sec, but then it kicked me out by rebooting.
Sent from my LG-P930 using xda premium
I will be attempting to do that some time this evening. Before I attempted it I wanted to be sure I wasn't going to be stuck with a brick. It will also let us finally figure out if out bootloader is locked or not.
schwin97 said:
I will be attempting to do that some time this evening. Before I attempted it I wanted to be sure I wasn't going to be stuck with a brick. It will also let us finally figure out if out bootloader is locked or not.
Click to expand...
Click to collapse
Good luck and God Speed Sir!! Bring home the bacon!
So has anyone figured out what we can use this mode for?
If it means anything, that was the mode I had it in while I flashed the SU640 rom.
Good to know, I figured it was the mode that the LG tool used to flash the phone.
I might ruined my defy+
When I bought it, it was in German, i changed it to dutch and had android 2.3.6
Flashed it with the all-in-one Defy beginners guide
Had a working android version afterwards, only calling/sms/2g and 3g didn't work. Didn't try to fix it because i wanted to flash the latest cm7.2.
Don't know what i did after that (afterwards we went to carnaval, so i drank to much). I know I installed a uk rom 2.3.6 version and here it went wrong. It went into a bootloop. Got the M logo and spinning white thing around. Tried installing differnt roms, none worked. And now my phone doesnt do anything, wont start or go in to bootloader. RDS light find it but white led wont go on.
IMEI/ESN/MEID: N / A
Technology: N / A
Software Version: N / A
Flex Version: N / A
Bootloader Version: v0x000910
DRM Version: N / A
AP Die ID: 1040020f1fab3a0a0000d8ff0100
BP Die ID: 0000000000000000000000000000
AP Public ID: 9aff8fe986ef65565a0a1e805942bbeaa8460f87
BP Public ID: 0000000000000000000000000000000000000000
Tried different roms, didn't work. Tried the following
"Common Problems/Questions
Black Screens when booting up: (!) Tried to install a version of Android with a lower CG Version than the one currently on the phone.
Weird behavior after installing a Fixed SBF: Install a matching Nandroid backup with your SBF, and remember to clear Cache/Dalvik Cache using Recovery.
Installed full Gingerbread SBF and can’t go back to another rom: (!) aha! We have a issue here!, latest Stock Gingerbread full SBFs comes with a Version 5 of the CG, meaning until not long ago you were pretty much screwed. But wait, there is hope! A one kind Éclair has been found in China Defys that comes with Version 5 CG!.
How to fix it:
Download this SBF and Flash it
Root your Phone
Download 2nd Init 1.4.2 and Install ClockworkMod Recovery
Download and install this Nandroid Backupwent wrong here, multiupload is gone so couldnt continue
Enter Recovery, Wipe Data/Cache
After wiping, turn off your phone
Turn it on and get immediately into Bootloader mode
Flash this Fixed SBF
Delete Data/Cache again and reboot"
Anyone got a answer for this? I am searching this forum for over 6 hours in the last days.
Mate, when you say it doesn't start... Nothing happens when you hold the power button? Not even the M logo (bootscreen) shows up?
Can you access stock recovery? When your phone is off, press and hold Volume UP button and power button. Does anything happen?
When you enter the bootloader, what does it say? Please write everything down.
I'm 99% sure that your phone isn't dead, you've just flashed some wrong stuff. First of all, CM7.2 is not compatible with 2.3.6. There is a CM7.2 DEFY+ version, but it works with 2.3.4 only. If you used a normal defy CM7.2, it's for Froyo only. Anyway, whatever version you used, it's not strange that it wasn't successful.
P.S I've done the same thing first time I've tried to update to some custom ROM
One more thing. After CM7.2 flashing resulted in a frozen bootscreen (M logo), please write down all the steps you did? It's kinda hard to figure out from that guide you've posted..!
niksy+ said:
Mate, when you say it doesn't start... Nothing happens when you hold the power button? Not even the M logo (bootscreen) shows up? Yes nothing shows, looks like the batt is empty but that isn't the case
Can you access stock recovery? When your phone is off, press and hold Volume UP button and power button. Does anything happen?
No nothing
When you enter the bootloader, what does it say? Please write everything down.
I'm 99% sure that your phone isn't dead, you've just flashed some wrong stuff. First of all, CM7.2 is not compatible with 2.3.6. There is a CM7.2 DEFY+ version, but it works with 2.3.4 only. If you used a normal defy CM7.2, it's for Froyo only. Anyway, whatever version you used, it's not strange that it wasn't successful.
P.S I've done the same thing first time I've tried to update to some custom ROM
One more thing. After CM7.2 flashing resulted in a frozen bootscreen (M logo), please write down all the steps you did? It's kinda hard to figure out from that guide you've posted..!Didn't came to that
Click to expand...
Click to collapse
Do you have a good link witch describes how to go from 2.3.6 to 2.3.4? For when my phone works again.
thank you.
taarmen said:
Do you have a good link witch describes how to go from 2.3.6 to 2.3.4? For when my phone works again.
thank you.
Click to expand...
Click to collapse
Not really, buddy :-/
You should have answered my questions, that way I could have written you a step-by-step guide
What you should do:
0. Phone's off
1. Enter stock recovery
2. Wipe data and wipe cache
3. Turn off phone
4. Enter bootloader
5. Flash full stock 2.3.4 sbf - http://www.mirrorcreator.com/files/1HLS00W4/
6. Your phone should boot up normally after the process is done
If you can not enter stock recovery, then just enter bootloader and flash the sbf. The thing is, those fixed sbf's don't have all the codegroups, so some stuff from CM7.2 has probably remained in your system. Full sbf should do a much better job. But, it would be great if you can enter stock recovery. That way the flashing must be successful.
Note, I haven't tried that 2.3.4 sbf! But it's the only one I could find. I need it too and I will test it tomorrow morning, so if you want, you can wait for me to test it first. (I need it cause my defy+ is on Froyo now, and Froyo and defy+ don't really like each other ) I have tested one 2.3.5 sbf, I can point it to it if you wish so. (It doesn't matter which android version it is, as they all have version 6 signed codegroups, so you can switch between them without worrying! Only some latest 2.3.6 ROM's are signed as version 7, but it's highly unlikely that you have flashed your phone with one such)
I Agree with niksy+, can't help, I have a Green Lens Defy, so all i have to say is good luck, and a step-by-step would have been nice
Thank you for the effort, my defy+ is braindead. When i connect it to my pc the white top led goes on. And that is it, nothing on RSD, wont boot, wont go in the bootloader
There's a trick for that i think i remeber it's:
Plug phone it with rsd ready (the phone should be dead with white led)
Pull battery out and press vol up + down
Put battery back in
It might not be exactly that but i can assure you i read somewhere what to do with your issue
Sent from my 1Ghz CM7 + CM9 Defy
crakeron said:
There's a trick for that i think i remeber it's:
Plug phone it with rsd ready (the phone should be dead with white led)
Pull battery out and press vol up + down
Put battery back in
It might not be exactly that but i can assure you i read somewhere what to do with your issue
Click to expand...
Click to collapse
That process is called "force bootloader method" and it can be done on any and every Motorola, as far as I know..! (I've done it on my previous E398, ROKR E1 and ROKR E8 phones (yeah, I've killed all my phones dozens of times )) and, yes, sometimes it does get you into the bootloader when the normal way doesn't!
So, as crakeron said:
1. Battery out
2. Wait couple of seconds (to make sure the phone goes completely out of power > completely off)
3. Start up RSDlite (v5.3.1 minimum!)
4. Connect your phone to the usb (yes, without the battery)
5. Now, you need to press and hold a combination of buttons and insert the battery WHILE holding the buttons pressed and keep them pressed for couple of seconds.
*I'm not sure what the combination of keys is it, but I would try:
a) Volume UP and Volume Down
b) Volume UP and Power Button
c) Volume Down and Power Button
d) Volume UP and Volume Down and Power Button (this one is the least likely, I think)
6. Your phone should show up in RSDlite and you can flash it then. The bootloader maybe won't show up on the phone screen, but if it shows up in RSDlite - it's all that you need!
This forcebootloader thing isn't quite easy and it may take couple of tries to hit the exact needed timing, so try all combinations a couple of times. Let us know if you pull this off!
i have the popcorn out for this one - fun thread! will the defy be rescued??? tune in next time, same bat board, same bat sub board!
taarmen said:
I know I installed a uk rom 2.3.6 version and here it went wrong. It went into a bootloop. Got the M logo and spinning white thing around. Tried installing differnt roms, none worked. And now my phone doesnt do anything, wont start or go in to bootloader. RDS light find it but white led wont go on.
Click to expand...
Click to collapse
If the UK 2.3.6 ROM you installed was this one then you will not be able to downgrade to any other 2.3.6 ROM (except I think this one), let alone 2.3.5, 2.3.4 or Froyo (it does say that in the thread you linked).
You should still be able to flash either of those 2.3.6 ROMs with RSD Lite. But no other ROM - until some more with CG 7 or above become available - and it's currently not rootable either. So no chance of CM7 or other such like goodies. At least you should be able to get a working phone that you can sell on eBay if you desperately don't want to be stuck with the T-Mobile 2.3.6 ROM.
Morals of the story:
1) Read before you flash
2) Keep a written record of what you did (I know, boring)
Good luck, let us know how you get on.
niksy+ said:
That process is called "force bootloader method" and it can be done on any and every Motorola, as far as I know..! (I've done it on my previous E398, ROKR E1 and ROKR E8 phones (yeah, I've killed all my phones dozens of times )) and, yes, sometimes it does get you into the bootloader when the normal way doesn't!
So, as crakeron said:
1. Battery out
2. Wait couple of seconds (to make sure the phone goes completely out of power > completely off)
3. Start up RSDlite (v5.3.1 minimum!)
4. Connect your phone to the usb (yes, without the battery)
5. Now, you need to press and hold a combination of buttons and insert the battery WHILE holding the buttons pressed and keep them pressed for couple of seconds.
*I'm not sure what the combination of keys is it, but I would try:
a) Volume UP and Volume Down
b) Volume UP and Power Button
c) Volume Down and Power Button
d) Volume UP and Volume Down and Power Button (this one is the least likely, I think)
6. Your phone should show up in RSDlite and you can flash it then. The bootloader maybe won't show up on the phone screen, but if it shows up in RSDlite - it's all that you need!
This forcebootloader thing isn't quite easy and it may take couple of tries to hit the exact needed timing, so try all combinations a couple of times. Let us know if you pull this off!
Click to expand...
Click to collapse
Wel I hope that iolinux333 has enough popcorn because non of the mentioned forced bootloader steps works
When i put my + on the usb nothing happens for a few minutes after that a withe led will shine. Thats all.
Thank you all!
I asked you already on tweakers.net, but I'll ask the same questions here:
What's the status of your battery? (Full, empty, half-full?) What version of RSD-lite did you use? What version of drivers are installed on your computer? How many times did you try the different key combinations after pulling out battery, connecting to your computer? What did you see at each step?
Fotogravin said:
I asked you already on tweakers.net, but I'll ask the same questions here:
What's the status of your battery? (Full, empty, half-full?) What version of RSD-lite did you use? What version of drivers are installed on your computer? How many times did you try the different key combinations after pulling out battery, connecting to your computer? What did you see at each step?
Click to expand...
Click to collapse
Been away for a few days. Back and ready to repair, I appreciate all your help.
no sim and sd-card
win7 64-bit
Battery is Full
RSD Lite version 5.6
motorola 5.4.0 usb drivers 64-bit
Tried all combinations at least 10 times. First I disconnect usb -> take out bat -> make combination and count to ten -> put in bat -> holds for minimum of 10seconds -> click on "show device" on RSD -> Nothing show
Nothing ever shows.
You really should give us more... What happens when you try to power it on? I think you only get black so, does power+vol(+) give you something or do you get a white led when you plug it in the pc?
If yes, it should be recognizable. I don't think you can get into bootloader mode when power-on gives nothing. Maybe by putting the battery back while holding the volume(+) I think and the power button. (like stated earlier) But I thought the white led was enough.
If you don't get the white LED and you only get black screen, maybe try to borrow a battery from someone...
If you get the white LED but RSD doesn't find it: try a few ports, maybe other PC, ....
I also think a Win7 window should pop up first with something like: 'Motorola diag... device found' (or maybe something completely different)
Then I think the easiest = warranty. I'm from Belgium. Had to send it to a repair center in the Netherlands (for a totally different reason) and it took them a while to fix it (it needed to be send elsewhere, .. ).
Just tell them you tried to update your rom and it wend wrong. Anyway, it takes about a month I think...
labsin said:
You really should give us more... What happens when you try to power it on?
Compleet black nothing happens
I think you only get black so, does power+vol(+) give you something
Still nothing
or do you get a white led when you plug it in the pc?
Yes I got that
If yes, it should be recognizable. I don't think you can get into bootloader mode when power-on gives nothing. Maybe by putting the battery back while holding the volume(+) I think and the power button.
Still nothing, not even the white led
(like stated earlier) But I thought the white led was enough.
If you don't get the white LED and you only get black screen, maybe try to borrow a battery from someone...
If you get the white LED but RSD doesn't find it: try a few ports, maybe other PC, ....
Haven't been able to trie different pc's. Tried differt usb ports, even those of my mouse and keyboard so I know they fully function, only white led
I also think a Win7 window should pop up first with something like: 'Motorola diag... device found' (or maybe something completely different)
nothing to show
Then I think the easiest = warranty. I'm from Belgium. Had to send it to a repair center in the Netherlands (for a totally different reason) and it took them a while to fix it (it needed to be send elsewhere, .. ).
Just tell them you tried to update your rom and it wend wrong. Anyway, it takes about a month I think...
Think i got to trie it,what can hapen if they found out i lied?
Click to expand...
Click to collapse
Thank you for helping me, I just tried RSD Lite 5.7 and also nothing.
Sorry a bit late. You didn't lie
I should be recognizable. Especially with a full battery. If not, you might have had a bad install and they might have to replace the botherboard.
If you don't mind waiting a couple of days longer, bring it to the place you bought it. Then the delivery costs are free. But could take 1-2 weeks longer.
IF they do conclude it is your fault then you have to pay an amount of money to deliver it back or you can pay for repairing it (for motherboard could be 80-100 or more, actually don't know). Again when you went trough shop this takes a week or so. (motorola => shop => 3 days nothing => you => 3 days nothing => motorola).
They are not that picky at motorola except for water damage maybe (check for a red sticker below the battery. If it is still white => no prob)
Thank you all. I've sent my phone to the store where i bought it, on friday and the next friday i got it back. With a fresh stock rom.
Before I begin, this is my first post here. I've used XDA before for help and love you guys. Now I need you more than ever. Thanks in advance for the help!
At first, my phone started to act all weird. By that I mean the Espier launcher wouldn't even load. It kept crashing. So I decided to unroot my phone. I used Odin to attempt to put the factory firmware and stuff on my phone but ended up prematurely ending the install, thus bricking my phone. When I turn my phone on I see the "Firmware upgrade encountered an issue" screen. So I did some research and attempted to fix the problem myself. After downloading and installing Kies (on three computers) I attempted to connect my phone to Kies. The USB port works, but none of my computers sees my phone. I've tried different USB ports, reinstalling Kies, using the connection debugging tool within Kies, changed the USB cable, taking the battery out, everything. If I am able to connect my phone to my computer I'll be able to fix the problem. If anyone could help me, that'd be lovely.
Can you get to download mode?
Sent from my SAMSUNG-SGH-T989 using xda premium
The only USB cable I've been able to use Odin or Kies with is the original cable that came with the phone. I have a ton of other micro USB cables, they all will charge but nothing else will do any sort of data transfer. Even then, I sometimes have to change USB ports and have encountered two PCs with won't recognize the phone no matter what. Keep trying.
It's odd, because my old HTC Hero was happy to connect and charge with any cable that fit.
rdsnyder said:
The only USB cable I've been able to use Odin or Kies with is the original cable that came with the phone. I have a ton of other micro USB cables, they all will charge but nothing else will do any sort of data transfer. Even then, I sometimes have to change USB ports and have encountered two PCs with won't recognize the phone no matter what. Keep trying.
It's odd, because my old HTC Hero was happy to connect and charge with any cable that fit.
Click to expand...
Click to collapse
Maxed22a said:
Can you get to download mode?
Sent from my SAMSUNG-SGH-T989 using xda premium
Click to expand...
Click to collapse
Yeah, I'm able to get into download mode. And I've also used the original cable that has provided with the phone.
Id try to odin the stock rooted kernel with what you have. I assume you still have a copy of what you rooted with... if not
http://forum.xda-developers.com/showthread.php?t=1433101
There you go.
Sent from my SPH-D710 using XDA
drinxtir said:
Id try to odin the stock rooted kernel with what you have. I assume you still have a copy of what you rooted with... if not
http://forum.xda-developers.com/showthread.php?t=1433101
There you go.
Sent from my SPH-D710 using XDA
Click to expand...
Click to collapse
The problem is none of my computers will detect my phone when I plug in the USB. I can't do anything else unless I can plug in my phone. I've tried installing the drivers, everything. Nothing works.
Ayotom said:
The problem is none of my computers will detect my phone when I plug in the USB. I can't do anything else unless I can plug in my phone. I've tried installing the drivers, everything. Nothing works.
Click to expand...
Click to collapse
Try a brand new high quality USB cable. Once in download mode try the new cable and Odin back to stock - sfhubs one-clicks are the life saver here.
Also. Have you tried 'stock' recovery/factory reset? This may get you to a good place. Then you can install a good stock ROM with root and recovery (again check out sfhub's posts)
Factory reset via stock recovery:
Hold down the Volume Up and Power buttons simultaneously.
Continue holding the Volume Up and Power buttons until the Samsung Galaxy S II logo screen is displayed.
When the Galaxy S II logo screen is displayed, release the Power button but continue holding the Volume Up button until the Android System Recovery menu is displayed.
Once you are on the Android System Recovery menu, select the wipe data/factory reset option. Moving the selection up and down is done with the Volume Up and Volume Down buttons. Once you have the wipe data/factory reset option highlighted, you select it by touching the Home button.
Once you have chosen the factory reset option, you will see a confirmation screen. Highlight the Yes — delete all user data option and touch the Home button to select it.
The procees of wiping the phone should only take a few seconds and when it is finished, you will be returned to the Android System Recovery menu.
Highlight and select the reboot system now option.
I sound like a broken record on the USB cable thing in many of my posts but that has been a cause for so much frustration for me and countless others. And the stock cable from Sammy sucks ass too.
Good luck.
leaderbuilder said:
Try a brand new high quality USB cable. Once in download mode try the new cable and Odin back to stock - sfhubs one-clicks are the life saver here.
Also. Have you tried 'stock' recovery/factory reset? This may get you to a good place. Then you can install a good stock ROM with root and recovery (again check out sfhub's posts)
Factory reset via stock recovery:
Hold down the Volume Up and Power buttons simultaneously.
Continue holding the Volume Up and Power buttons until the Samsung Galaxy S II logo screen is displayed.
When the Galaxy S II logo screen is displayed, release the Power button but continue holding the Volume Up button until the Android System Recovery menu is displayed.
Once you are on the Android System Recovery menu, select the wipe data/factory reset option. Moving the selection up and down is done with the Volume Up and Volume Down buttons. Once you have the wipe data/factory reset option highlighted, you select it by touching the Home button.
Once you have chosen the factory reset option, you will see a confirmation screen. Highlight the Yes — delete all user data option and touch the Home button to select it.
The procees of wiping the phone should only take a few seconds and when it is finished, you will be returned to the Android System Recovery menu.
Highlight and select the reboot system now option.
I sound like a broken record on the USB cable thing in many of my posts but that has been a cause for so much frustration for me and countless others. And the stock cable from Sammy sucks ass too.
Good luck.
Click to expand...
Click to collapse
All the help is appreciated, I just wanted to let you know that. If my tone is bitter, I apologize. I use this phone for emergencies. I have indeed tried a high quality USB cable (just bought it) and it will not connect. I attempted to use Odin to restore my phone back to normal but the process was interrupted and caused my phone to be in the phone....!....computer screen with the message "firmware upgrade has encountered a problem" etc. I have attempted to plug in my phone while Odin opened. Nada. I've tried this in download mode using the button commands you have listed. I hope I'm not getting too annoying, I just feel so lost without my phone. Had everything on it. Sorry.
Ayotom said:
All the help is appreciated, I just wanted to let you know that. If my tone is bitter, I apologize. I use this phone for emergencies. I have indeed tried a high quality USB cable (just bought it) and it will not connect. I attempted to use Odin to restore my phone back to normal but the process was interrupted and caused my phone to be in the phone....!....computer screen with the message "firmware upgrade has encountered a problem" etc. I have attempted to plug in my phone while Odin opened. Nada. I've tried this in download mode using the button commands you have listed. I hope I'm not getting too annoying, I just feel so lost without my phone. Had everything on it. Sorry.
Click to expand...
Click to collapse
Are you sure you were installing the right firmware? If you flashed an international verion then you did kill the device and will need to get it jtag'd or replaced.
And exactly how did it 'get interupted? Did it just 'stop' or was it interupted by a power outage, or impatience of quiting the appolication?
How did you get root? Did you use sfhub's autoroot?
And what ROM did you use? Again sfhub's Stock One-Clicks are the safest and only way to go in my book.
Not trying to be a **** just trying to get a better understanding of what happened.
leaderbuilder said:
Are you sure you were installing the right firmware? If you flashed an international verion then you did kill the device and will need to get it jtag'd or replaced.
And exactly how did it 'get interupted? Did it just 'stop' or was it interupted by a power outage, or impatience of quiting the appolication?
How did you get root? Did you use sfhub's autoroot?
And what ROM did you use? Again sfhub's Stock One-Clicks are the safest and only way to go in my book.
Not trying to be a **** just trying to get a better understanding of what happened.
Click to expand...
Click to collapse
I might have accidentally installed the wrong firmware while attempting to repair it. Unless the different SII model firmware wouldn't hurt my phone, such as the AT&T SII.
And battery laptop died.
I had my brother root it. It used Syndicate.
And no worries dude, I'm just glad you're helping!
I am not sure if anyone specifically tried the att gs2 firmware, but since att is gsm, chances are it is the same as flashing the intl gs2 firmware. Flashing the latter would basically disable your usb port. It does sound like that is what happened.
If you still had cwm or root you could flash from the phone, but i think you mentioned you lost those too.
Your remaining options are probably jtag or return to sprint.
Thank you very much for your help. It seriously means a lot. Next time I'll pay more attention so I won't end up screwing things up again.
Well if you tried to use the AT&T SG II (SGH-I777) firmware you did probably kill it for sure. These phones are very specific and individual when it comes to the actual hardware and base firmwares. Kind of like putting diesel into a gas engine - good things don't happen. If you can't get it recognized at all no matter what you do a jtag service or simply taking it back and playing dumb might help. Here is a post with almost the same issue, just a different but still wrong firmware: http://forum.xda-developers.com/showthread.php?t=1506630 As for the guys at ACS they are very good too (most of them are around here too by the way). Spend some time and read a whole lot and you will learn what you need. Best bet if you simply can't get it recognized by Odin is to take it back to Sprint and play dumb and see if they get you a replacement. With insurance you should get it free without I think you pay $35.
This might sound a little crazy... But have you tried heimdall to see if you get dirrerent results?
Update
So I decided to check out the JTAG service. Guess what I found out? The dude that repairs phones lives 20 minutes away from me! I went over to his place yesterday and he fixed my phone right in front of me. It was totally worth the $50! His service is amazing, and he's friendly also. I would highly recommend him! Read my review (I'm John Montoya): http://mobiletechvideos.mybigcommerce.com/samsung-epic-4g-touch-jtag-brick-repair/
Thanks everyone for the help. Next time I'll be sure not to put in the wrong firmware!
LOL that's pretty funny having the mobiletechvideos guy living in your town, and getting to watch the JTAG repair in person. Not many people can say they've seen that in person, myself included. Glad you got it resolved.
Sent from my SPH-D710 using Tapatalk 2
Ayotom said:
So I decided to check out the JTAG service. Guess what I found out? The dude that repairs phones lives 20 minutes away from me! I went over to his place yesterday and he fixed my phone right in front of me. It was totally worth the $50! His service is amazing, and he's friendly also. I would highly recommend him! Read my review (I'm John Montoya): http://mobiletechvideos.mybigcommerce.com/samsung-epic-4g-touch-jtag-brick-repair/
Thanks everyone for the help. Next time I'll be sure not to put in the wrong firmware!
Click to expand...
Click to collapse
Glad to see you got it resolved! I've recommended that service to a few. Thanks for posting. Many don't so we never know the final outcome. This helps the whole community. Enjoy your great phone.
I saw a couple people had the same issue that im now having but none of there solutions solved my problem
i wiped my GS3 for ATT tried to go back to a stock with root rom and when it rebooted it now just hangs at the samsung logo at boot tried re-flashing via odin with no luck also tried flashing a CWM.tar since i cant get into stock or CWM recovery to flash from there is there something im missing i know its late and maybe my brain isnt working like it should
Solved the problem myself.....and rather then just say i figured it out ill share how i did this since i watched countless videos and read endless amounts of threads and since none of them helped mem
First also try t put your phone into stock recovery mode and wipe your phone then flash this should take care of things if it doesnt try what i tried below
and i hope this can help someone else out there who has the same problem that i had all you have to do is the following i did this with obviously an AT&T model should work with others but as always try at your own risk.....
First make sure your battery has a charge even if its stuck on the boot screen its still charging....
then download KIES from samsung update it and make sure you have the latest version.
Next plug in your phone if your stuck at the samsung screen your computer will recognize your phone still at least it did with mine.
Once your done with the above open up KIES goto the top and then TOOLS and Firmware upgrade click on that enter your phone model (ATT SGH-I747) i dont get this part but next it will ask you for your SN and for some reason it doesnt recognize the SN use your IMEI
Now it should ask you a couple questions tell you its wiping your device and you will lose everything etc.....but then it will download the latest FW and begin to install everything and in about 20-25 mins everything will be back to stock
Nvm.. misread.
I'm stuck too...and Kies can't find the phone. Anyone have any other ideas? I can't even get into recovery...only download mode.
dbdynsty25 said:
I'm stuck too...and Kies can't find the phone. Anyone have any other ideas? I can't even get into recovery...only download mode.
Click to expand...
Click to collapse
your computer is not seeing your phone when you plug it in or its just KIES that doesnt see it??
also im guessing you have all the correct drivers installed??
yearziro said:
your computer is not seeing your phone when you plug it in or its just KIES that doesnt see it??
also im guessing you have all the correct drivers installed??
Click to expand...
Click to collapse
Yes, all drivers are installed because that's how I ODIN flashed it in the first place! Just stuck on the damn Samsung screen and I can't get Kies to connect to the phone. Not in Download Mode or when it's just stuck on that screen.
you can just hold VOL UP, HOME , POWER same time enter stock samsung recovery mode and scroll down select wipe data and cache and reboot u should good to go....
whit3gh0szt said:
you can just hold VOL UP, HOME , POWER same time enter stock samsung recovery mode and scroll down select wipe data and cache and reboot u should good to go....
Click to expand...
Click to collapse
Worked, thanks! I appreciate it.
it doesnt work on mine
dbdynsty25 said:
Worked, thanks! I appreciate it.
Click to expand...
Click to collapse
my cellphone reboots by itself on the samsun screen and i cant get on the recovery mode! any ideas!"
me neither
mkstf said:
my cellphone reboots by itself on the samsun screen and i cant get on the recovery mode! any ideas!"
Click to expand...
Click to collapse
Yeah I can't get into recovery either, and its getting really annoying.
indieslap said:
Yeah I can't get into recovery either, and its getting really annoying.
Click to expand...
Click to collapse
With the phone off, hold down VOL UP + HOME + POWER until the phone vibrates. Then let go of the power button. When you see the blue text in the top left corner of the samsung boot screen, let go of the other 2 buttons
xBeerdroiDx said:
With the phone off, hold down VOL UP + HOME + POWER until the phone vibrates. Then let go of the power button. When you see the blue text in the top left corner of the samsung boot screen, let go of the other 2 buttons
Click to expand...
Click to collapse
Okay, this brought the menu up for me, but I removed the data,cache, and reset the phone and it is still not working. Also, my phone just goes black after the Galaxy Samsung S3 logo, but the blue light in the top left is still on. Can anyone help me out?
P.S. Sorry for reviving this thread if it is too old.
Edit: I should also mention that I can still hear the sound of the phone booting up (the sound that typically occurs when the phone is on the white loading screen). However, the screen is black at this point.
cabato said:
Okay, this brought the menu up for me, but I removed the data,cache, and reset the phone and it is still not working. Also, my phone just goes black after the Galaxy Samsung S3 logo, but the blue light in the top left is still on. Can anyone help me out?
P.S. Sorry for reviving this thread if it is too old.
Edit: I should also mention that I can still hear the sound of the phone booting up (the sound that typically occurs when the phone is on the white loading screen). However, the screen is black at this point.
Click to expand...
Click to collapse
You're going to have to tell us what you did (changed, flashed, etc) before all this so that we can help you
xBeerdroiDx said:
You're going to have to tell us what you did (changed, flashed, etc) before all this so that we can help you
Click to expand...
Click to collapse
Ah, sorry about not providing enough information. Please keep in mind that I am very inexperienced and I may get some things incorrect just due to that. To my understanding, I went to try and root my phone, but beforehand I used the guides below to get my phone ready for the root (yes I do realize at this point that using these outdated guides was a clear mistake and I should have come to XDA instead). I flashed my phone to the stock kernel using the file that site provided, and then encountered the problem above. In my panic I have tried to restore the phone through several methods, but every time I try to load anything onto it with Odin, it doesn't complete until my phone restarts (and my phone won't boot up completely) so I can't get the pass message. Interestingly enough I did manage to get clockwork mod installed as that is what shows up when I try a secure boot using the methods that you described.
Ah, I am unfortunately not allowed to post links. The guides were off of Android Authority.
If there is any other information needed to help me please let me know and I will do my best to obtain it.
cabato said:
Ah, sorry about not providing enough information. Please keep in mind that I am very inexperienced and I may get some things incorrect just due to that. To my understanding, I went to try and root my phone, but beforehand I used the guides below to get my phone ready for the root (yes I do realize at this point that using these outdated guides was a clear mistake and I should have come to XDA instead). I flashed my phone to the stock kernel using the file that site provided, and then encountered the problem above. In my panic I have tried to restore the phone through several methods, but every time I try to load anything onto it with Odin, it doesn't complete until my phone restarts (and my phone won't boot up completely) so I can't get the pass message. Interestingly enough I did manage to get clockwork mod installed as that is what shows up when I try a secure boot using the methods that you described.
Ah, I am unfortunately not allowed to post links. The guides were off of Android Authority.
If there is any other information needed to help me please let me know and I will do my best to obtain it.
Click to expand...
Click to collapse
Sounds like you need to clear your cache partition and clear your dalvik cache. There are several guides on this site to help you. Choose the one that is most appropriate to what you are trying to do and follow it EXACTLY. There is one to start. Follow it from the beginning.
http://forum.xda-developers.com/showthread.php?t=2042775
When nothing else works start over from search. You cab use download mode? First make sure you got right drivers as that can mess up Odin. Use one in my Sig if you want. Then flag stock recovery with root someone nice will part a link to it I'm on my phone can't do it. Well fix your phone
Sent from my SGH-I747 using xda premium
allow rldcess
Okay now I am running into another problem. I have tried downloading the drivers from many different places and they always seem to be correctly downloaded. That being said, I can't install the drivers after I plug my phone into the computer (after downloading and installing Samsung USB drivers). Therefore, I cannot access my phone storage to put the root zip file on it. I was still able to download the custom recovery.
Now I have gone to a different computer, and the drivers seem to install correctly, but the phone still does not appear under my computer.
Edit: I do already have a root zip file on my phone from my earlier attempt, but I install it and my phone still doesn't load up. Also, Odin still recognizes the phone.
Edit 2: Windows says that the drivers cannot recognize the device. Edit 3: "Hardware ID Missing"
Bump
Sorry, I really need help for this. I can't install the MTP drivers even through using some of the tips on this site. That seems to be the problem with me accessing the phones storage from my computer. Does anyone have an ideas for what else I could do? Should I just take it to the store and hope they can fix it?
cabato said:
Okay now I am running into another problem. I have tried downloading the drivers from many different places and they always seem to be correctly downloaded. That being said, I can't install the drivers after I plug my phone into the computer (after downloading and installing Samsung USB drivers). Therefore, I cannot access my phone storage to put the root zip file on it. I was still able to download the custom recovery.
Now I have gone to a different computer, and the drivers seem to install correctly, but the phone still does not appear under my computer.
Edit: I do already have a root zip file on my phone from my earlier attempt, but I install it and my phone still doesn't load up. Also, Odin still recognizes the phone.
Edit 2: Windows says that the drivers cannot recognize the device. Edit 3: "Hardware ID Missing"
Click to expand...
Click to collapse
go to your device manager on your computer, locate samsung drivers for your device, uninstall them
restart your computer
then plug in the phone and lets it reinstall by itself
Use my drivers in my signature
They are last good damaging drivers. Don't update them but install them and plug phone in with no internet. after install plug internet in. There good stable drivers
Sent from my SAMSUNG-SGH-I747 using xda premium