I'm on stock and I decided I wanted to try CM10. I've been flashing for almost 2 years now with my captivate and S2.
I went here: http://galaxys3root.com/galaxy-s3-root/how-to-root-att-galaxy-s3-sgh-i747/
Flashed the first file and noticed no recovery...
I then noticed I had no more internet, so I decided to try and go back to stock.
Now ODIN will recognize, but hangs before any actual flashing. I am at a loss here. The phone works, but I can't flash anything! Help please?
I would suspect the reason Odin isn't working properly is because the one mention on that site is not the proper (or atleast recommended) version to use with i747. Also their logic to flash custom recovery before achieving root, although possible (maybe??), seems flawed to me. Also, flashing anything other than an officially signed .tar through Odin trips the flash counter, which from a so called 'Noob Friendly' guide seems counter intuitive. Try using the guide posted HERE over on in the development forum here on XDA and see if you get better results.
Ok I figured it out. I was using my old Captivate USB cable and not the one that came with the new phone. CM10 is up and running. Thanks for the link btw, that helped.
Good to hear you got it working , glad to help.
offtopicjack said:
Ok I figured it out. I was using my old Captivate USB cable and not the one that came with the new phone. CM10 is up and running. Thanks for the link btw, that helped.
Click to expand...
Click to collapse
I have flashed via Odin with my cappy cable! Maybe it varies in effectiveness? One thing I did notice however is adb can't see my captivate when I use my gs3 cable(odd eh?)
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
It is definitely an intermittent problem that I can recall happening since I started with android back on the Samsung Moment. Some devices like certain cables, and doesn't like others.
Please read forum rules before posting
Questions go in Q&A
Thread moved
Friendly Neighborhood Moderator
Related
I was running the ICS leaked release and decided to try another ROM. I think my mistake was that I didn't flash a custom recovery like Rogue's and just threw the ROM on my SD, went into the stock recovery that came with the ICS leaked ROM, ran Calkulin's wipe and flashed the ROM.
The phone won't boot up. I can get into Download Mode but I don't know where I can download a stock tar to flash in ODIN 1.85. If I try and go to the stock recovery it doesn't work.
Any help would be appreciated.
***EDIT***
It's still stuck at the data.img portion of the process (end process). It's probably not going far from there.
I can't get into the stock recovery but it does allow the download mode still.
Android300ZX said:
I was running the ICS leaked release and decided to try another ROM. I think my mistake was that I didn't flash a custom recovery like Rogue's and just threw the ROM on my SD, went into the stock recovery that came with the ICS leaked ROM, ran Calkulin's wipe and flashed the ROM.
The phone won't boot up. I can get into Download Mode but I don't know where I can download a stock tar to flash in ODIN 1.85. If I try and go to the stock recovery it doesn't work.
Any help would be appreciated.
Click to expand...
Click to collapse
In the dev threads look for sfhubs oneclick el29. Download it and follow instructions. It will be fine.
Team-Nocturnal Blended ICS
Right here is all you need. http://forum.xda-developers.com/showthread.php?p=21134991
Then use autoroot to get cwm back.
Team-Nocturnal Blended ICS
I tried that earlier and it didn't work. I deleted all the files and will try it again. When I tried the steps it just hung at waiting for connection or something to that effect.
Android300ZX said:
I tried that earlier and it didn't work. I deleted all the files and will try it again. When I tried the steps it just hung at waiting for connection or something to that effect.
Click to expand...
Click to collapse
That really sound like you don't have the drivers quite right. When you open the regular odin, and your phone is in download mode, does a yellow box on odin show up? If not its the drivers.
Team-Nocturnal Blended ICS
bigtoysrock said:
That really sound like you don't have the drivers quite right. When you open the regular odin, and your phone is in download mode, does a yellow box on odin show up? If not its the drivers.
Team-Nocturnal Blended ICS
Click to expand...
Click to collapse
Yes. It shows COM port I in yellow which is a good thing because it recognizes something is connected.
Android300ZX said:
Yes. It shows COM port I in yellow which is a good thing because it recognizes something is connected.
Click to expand...
Click to collapse
Then the one click should work just fine. Make sure you follow his instructions to the T. Also on his page he has some drivers, you should install those, it uninstall or over write the old ones. Just to be sure.
Team-Nocturnal Blended ICS
Thanks. It looks like it's working now. It's installing right now and then we shall see but I'm pretty sure it'll work. I'll leave it stock for now until ICS comes out. I'm so buy working on my new car that I barely have time to geek out anymore on my phone.
Don't try to flash anything with stock recovery ...it has to be officially signed by Samsung ...won't work
Sent from my SPH-D710 using XDA App
It didn't work. Last night I went to run the EL29 Restore - Rooted and it got stuck on the data.img portion. The progress bar on the phone and computer just hung there. I disconnected the cable and went to bed (after 1.5 hours of it just sitting there stuck).
I'm trying it again today and lets see if it gets stuck.
I'm reflashing EL29 over the FB21 (w/e the leaked version of ICS was) I had. Is that the issue?
Sorry but I think your bricked. There is a "Stuck at Data.img" thread here in q&a.
The issue still isn't repairable.
The way you went about getting stuck here is a little different tho. So hopefully I'm wrong.
Good luck
Are you stuck in a bootloop? If so, do you get any further than the Samsung splash screen?
Try re-flashing the ICS leak. I read somewhere that it could be a filesystem issue with switching to and from GB. If that doesn't work, maybe you'll have better luck with using ODIN as opposed to the one-click method. You'll find the tars here-
http://forum.xda-developers.com/showthread.php?t=1391732
In most cases you'll be flashing them in PDA, but read everything closely, and follow the steps.
If you have insurance, I almost suggest going to Sprint while it still seems there's no evidence you've been flashing (yellow triangle), as they'll likely just replace it for you.
If none of that works, then it sounds like a rare problem that happened to mine a few months ago. This was the only thread I found at that time, but it was for AT&T's GSII.
http://forum.xda-developers.com/showthread.php?p=20834412#post20834412
I ended up getting a new one, but I would love to finally find a solution since I still have it. Pretty much the only thing I haven't tried is a JTAG service.
Juq said:
Are you stuck in a bootloop? If so, do you get any further than the Samsung splash screen?
Try re-flashing the ICS leak. I read somewhere that it could be a filesystem issue with switching to and from GB. If that doesn't work, maybe you'll have better luck with using ODIN as opposed to the one-click method. You'll find the tars here-
http://forum.xda-developers.com/showthread.php?t=1391732
In most cases you'll be flashing them in PDA, but read everything closely, and follow the steps.
If you have insurance, I almost suggest going to Sprint while it still seems there's no evidence you've been flashing (yellow triangle), as they'll likely just replace it for you.
If none of that works, then it sounds like a rare problem that happened to mine a few months ago. This was the only thread I found at that time, but it was for AT&T's GSII.
http://forum.xda-developers.com/showthread.php?p=20834412#post20834412
I ended up getting a new one, but I would love to finally find a solution since I still have it. Pretty much the only thing I haven't tried is a JTAG service.
Click to expand...
Click to collapse
If I turn on the phone I get a screen that says
"Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
I don't get to the point where it even shows me a Samsung logo; just straight to that screen.
When I go into Download Mode I see
ODIN MODE
Product Name: SPH-D710
Custom Binary DOwnload: No
Current Binary: Samsung Official
Here's the thread caspersfi mentioned. I'm reading through it myself now.
http://forum.xda-developers.com/showthread.php?t=1504808&highlight=stuck+at+data+img
Good luck!
Juq said:
Here's the thread caspersfi mentioned. I'm reading through it myself now.
http://forum.xda-developers.com/showthread.php?t=1504808&highlight=stuck+at+data+img
Good luck!
Click to expand...
Click to collapse
I'm reading it now. I want to add that it was CWM touch that messed up my phone because I had flashed that before attempting to flash another ROM since ICS build came with the default factory recovery. So I'm guessing my file system is corrupt. I'll keep reading through the thread. (I skipped to the last couple of pages.
Hey so can you still get into download mode? I ran into the same problem where it kept getting stuck in odin. Try a different usb cable and a different port. Odin is very fussy with usb cables. When I had the trouble I was using a Logitech usb cable. Switched to the one that came with my phone and it worked like a charm.
rbtrucking said:
Hey so can you still get into download mode? I ran into the same problem where it kept getting stuck in odin. Try a different usb cable and a different port. Odin is very fussy with usb cables. When I had the trouble I was using a Logitech usb cable. Switched to the one that came with my phone and it worked like a charm.
Click to expand...
Click to collapse
I'm using the one that came with the phone and I tried different ports. I don't have another cable to use but I doubt that will help me out. Thanks for the suggestions though.
Android300ZX said:
I'm using the one that came with the phone and I tried different ports. I don't have another cable to use but I doubt that will help me out. Thanks for the suggestions though.
Click to expand...
Click to collapse
I didnt think it was possible that a simple cable swap would help me when I was in the exact same position as you either but it sure did. What could it hurt to just try a different cable? I am sure you could borrow one from a friend just to try it. According to qbking77 samsung cables are pretty bad when it comes to using odin.
rbtrucking said:
I didnt think it was possible that a simple cable swap would help me when I was in the exact same position as you either but it sure did. What could it hurt to just try a different cable? I am sure you could borrow one from a friend just to try it. According to qbking77 samsung cables are pretty bad when it comes to using odin.
Click to expand...
Click to collapse
I will try that shortly then. I have a paper that's due today to write so school before phone, lol.
Alright i really hope it works, let us all know.
Sent from my SPH-D710 using XDA App
Samsung galaxy SIII hard bricked will not boot no power, but ODIN 1.85 can recognize it, (not the new Odins), when I try to re-flash it with Odin I get stuck at setupConnection..
any help? can I use the small USB mod
If you don't mind me asking, how you brick your phone?
Sent from my SGH-T999 using xda app-developers app
i have the same problem i used the Odin3 v1.85 and installed CF-Root-SGS3-v6.4 zip but it failed. so then i tried to reboot it and said firmware update encountered an issue and something else. then i looked up how to unbrick and the post said to downloaded the zip CF-Insecure-SGS3_XX_NEE_ALE8-v1.2 and used Odin to install now i got nothing but a black screen buy it will go into download mode and Odin read it
You're not hard bricked if Odin can read your phone. Reboot your computer then reconnect and flash a stock rom to be safe.
chubby1_8888 said:
i have the same problem i used the Odin3 v1.85 and installed CF-Root-SGS3-v6.4 zip but it failed. so then i tried to reboot it and said firmware update encountered an issue and something else. then i looked up how to unbrick and the post said to downloaded the zip CF-Insecure-SGS3_XX_NEE_ALE8-v1.2 and used Odin to install now i got nothing but a black screen buy it will go into download mode and Odin read it
Click to expand...
Click to collapse
If I'm not wrong ODIN uses TAR files and not ZIP files. Try unziping and see if there is a TAR file if there is then thats what you have to use in ODIN.
Same as OP's phone
Sprint s3 flash pacman JB and google apps the went to reboot recovery ask to reflash su yes phone powered off and no coming back on Odin does detect it on com05 when I plug it in but anything I try to do just says waiting on connection, will not go into recovery or download modes. is there anything I can do to fix it? kies or anything? and I edited the updater scripts to be able to flash pacman because every rom I tried would fail with error 7............ please help
Kevinreid1 said:
Sprint s3 flash pacman JB and google apps the went to reboot recovery ask to reflash su yes phone powered off and no coming back on Odin does detect it on com05 when I plug it in but anything I try to do just says waiting on connection, will not go into recovery or download modes. is there anything I can do to fix it? kies or anything? and I edited the updater scripts to be able to flash pacman because every rom I tried would fail with error 7............ please help
Click to expand...
Click to collapse
Do you get a message when you plug it into your computer? Does the red LED turn on? Editing the scripts is dangerous if you don't know what you are doing!
serio22 said:
Do you get a message when you plug it into your computer? Does the red LED turn on? Editing the scripts is dangerous if you don't know what you are doing!
Click to expand...
Click to collapse
followed the guides about it just removed from top to quotes dealing with checking versions of device.
Kevinreid1 said:
followed the guides about it just removed from top to quotes dealing with checking versions of device.
Click to expand...
Click to collapse
I'm not saying that was the problem or that you did it wrong, but maybe the ROM was forced to flash and was truly not compatible or was corrupt, bricks are highly likely to occur in this case
serio22 said:
I'm not saying that was the problem or that you did it wrong, but maybe the ROM was forced to flash and was truly not compatible or was corrupt, bricks are highly likely to occur in this case
Click to expand...
Click to collapse
The roms I have downloaded are supposed to be for Sprint s3 I was running stock JB 4.3 if that makes any difference, any help on what to do know, thinking of trying the unbrick mmc card trick .... idk what else to do... thanks : ) and something went wrong somewhere for sure... lol I also found out my exact model number if that helps. SPH-L710MBBSPR again thanks for you responses..
Ok, a few things I noticed....
1. You are using a very old version of Odin. I recommend only using 3.07 or 3.09.
2. The COM port box is yellow, which probably was trying to caution you about something.
3. You have a Sprint model S3. This is the T-Mobile S3 forum.
4. You have a Sprint S3, but were trying to flash old T999 firmware! This simply will not work, and if it were to flash, insta-brick!
What you need to do is start using the Sprint forums. Only flash items you find in those forums, and nothing else. While some of our roms might flash and boot on yours, they will never function very well. This is one of the things the asserts in an updater script are intended to protect against.
Finally, just a bit of posting advice. Please use proper punctuation. Small mistakes are ok, but posting with no punctuation at all just makes it difficult for people to read, and many will just close the thread and move to the next without bothering to help.
---------- Post added at 02:28 AM ---------- Previous post was at 02:25 AM ----------
Oops! Just realized the pic in the op wasn't yours! But still, theyre all good points you should check before flashing. Also make sure kies is uninstalled or disabled on your computer.
But most importantly, you need to be in the Sprint forums. We can help a bit here, but you need to ONLY use stuff from your devices forum. And a lot of it we simply may not be familiar with.
Good luck!
DocHoliday77 said:
Ok, a few things I noticed....
1. You are using a very old version of Odin. I recommend only using 3.07 or 3.09.
2. The COM port box is yellow, which probably was trying to caution you about something.
3. You have a Sprint model S3. This is the T-Mobile S3 forum.
4. You have a Sprint S3, but were trying to flash old T999 firmware! This simply will not work, and if it were to flash, insta-brick!
What you need to do is start using the Sprint forums. Only flash items you find in those forums, and nothing else. While some of our roms might flash and boot on yours, they will never function very well. This is one of the things the asserts in an updater script are intended to protect against.
Finally, just a bit of posting advice. Please use proper punctuation. Small mistakes are ok, but posting with no punctuation at all just makes it difficult for people to read, and many will just close the thread and move to the next without bothering to help.
---------- Post added at 02:28 AM ---------- Previous post was at 02:25 AM ----------
Oops! Just realized the pic in the op wasn't yours! But still, theyre all good points you should check before flashing. Also make sure kies is uninstalled or disabled on your computer.
But most importantly, you need to be in the Sprint forums. We can help a bit here, but you need to ONLY use stuff from your devices forum. And a lot of it we simply may not be familiar with.
Good luck!
Click to expand...
Click to collapse
Thank you.. I knew I was in the wrong forum and that is why I said my s3 was a Sprint device... My problem however was the same exact problem. I got it fixed with file from another forum, while follow info from yet another forum, the file that worked for me was HomefixSprint_S3_L710.img the debrick_sph_l710.img would not work for me. I used win32diskimager and burned .img file to class 10 32gb card, stuck it in went in to download mode and used odin to write firmware file... Anyway back up any running.. I didn't download any t-mobile roms or anything that wasn't for the Sprint S3, what I did do was try and load an older JB rom that was under V4.3, it wasn't that long ago when a person could flash any android version one wished, it looks like Samsung is getting as bad as Apple you can move up but not back. Any tips on how to safely downgrade? Anyway thanks for taking the time to respond. : ) Cause no one has in the Sprint S3 forum yet.
Kevinreid1 said:
it wasn't that long ago when a person could flash any android version one wished, it looks like Samsung is getting as bad as Apple you can move up but not back. Any tips on how to safely downgrade?
Click to expand...
Click to collapse
No, Samsung is not turning into apple, there is a reason you cannot downgrade from a Knox bootloader. And to downgrade, with this device we can just flash an older ROM and it will work, maybe its different with the Sprint variant? Try to search in their forums if you haven't already
Does anyone know if there is a more updated way or (cant think of the word for it) rooting a Samsung Galaxy SIII SGH I747? I've wanted to do it for months and months, but I was terrified of screwing something up, and when I finally over came my fear and heavily prepared, researching and everything ( different technique and all) none of them of them worked. I tried toolkits, XDA troubleshooting tips, all kinds of links and etc. I only get so far in the process where there is a quick flash of some sort in the Odin portion where you input the path from the C: drive part and stuff. I've just had so many issues. I feel like giving up so bad. But I'm not that type of person. I'M GOING tO GET THIS IF IT KILLS ME! Yesterday, I stayed on this thing from 9:00 am till 10:00 pm. Trying over and over, recapping my steps, making sure I read and reread the directions, jumping from site to site to see what other folks have tried.
I think I used quickroot method. I tried the toolkit before and it didn't work either. I finally found a correct root method in the i747 Android Development forum. Ill try to find the forum for you.
Sent from my SAMSUNG-SGH-I747 using xda premium
13 hours "trying" to root your phone with no success??? You're way over thinking it! Flash recovery to your phone through odin, then flash superuser through your newly installed recovery. Should take all of 10 minutes...
CF AUTO ROOT! It should take no more than a minute to root but it won't install a custom recovery so you'll need to use Rom Manager for CWM or GooManager to install TWRP after you root.
Sent from my SAMSUNG-SGH-I747 using XDA Premium 4 mobile app
Hi. So I'm totally at a loss as to what to do. I've had a Galaxy S3 for a little over a year now, and just recently decided to try and root it. I'm not very experienced with phone software in general, but I've got enough understanding of how Android works to want to try my hand at this.
I followed mrRobinson's really helpful root via Odin guide, found here: http://forum.xda-developers.com/showthread.php?t=1774722
I never got past step 2, however. I got everything downloaded, got my phone plugged in and going, and...it's stuck now. It still says it's in the middle of download, but it's been downloading "cache.img.ext4" for about an hour now. Clearly there's something not right.
Here is a screenshot of what this has looked like: http://i.imgur.com/jy21pHd.jpg
I'd heard that using a third party cable was not advisable, but unfortunately that was something I learned after the download had already begun. As of right now, my phone is still in download mode. What do I do? Is there a way for me to go back to normal and try rooting it again with a stock cord? Or is there something I haven't done that'll finish the download? I'm terrified of unplugging it or messing with it in any way without knowing what the consequences will be.
PS: Please explain this to me as simply as possible. I'm not familiar with a lot of Android jargon, I apologize.
nuclearteacup said:
Hi. So I'm totally at a loss as to what to do. I've had a Galaxy S3 for a little over a year now, and just recently decided to try and root it. I'm not very experienced with phone software in general, but I've got enough understanding of how Android works to want to try my hand at this.
I followed mrRobinson's really helpful root via Odin guide, found here: http://forum.xda-developers.com/showthread.php?t=1774722
I never got past step 2, however. I got everything downloaded, got my phone plugged in and going, and...it's stuck now. It still says it's in the middle of download, but it's been downloading "cache.img.ext4" for about an hour now. Clearly there's something not right.
Here is a screenshot of what this has looked like: http://i.imgur.com/jy21pHd.jpg
I'd heard that using a third party cable was not advisable, but unfortunately that was something I learned after the download had already begun. As of right now, my phone is still in download mode. What do I do? Is there a way for me to go back to normal and try rooting it again with a stock cord? Or is there something I haven't done that'll finish the download? I'm terrified of unplugging it or messing with it in any way without knowing what the consequences will be.
PS: Please explain this to me as simply as possible. I'm not familiar with a lot of Android jargon, I apologize.
Click to expand...
Click to collapse
I don't think its going to work without the stock cord. But I think unplugging it would just result in a failed root I don't think it would brick. Not positive though
Sent from my SPH-L710 using xda app-developers app
nuclearteacup said:
...
PS: Please explain this to me as simply as possible. I'm not familiar with a lot of Android jargon, I apologize.
Click to expand...
Click to collapse
did you unplug the phone yet? how did it go?
Just FYI since it sounds like you are new to this, there are a few different s3 models depending on carrier. Make sure you flash something compatible with your phone.
From your screenshot, looks like everything flashed except the cache partition. Are there any other images in the .tar.md5 file you downloaded?
Hi friends. Long time lurker here.
I've had many Samsung phones and many other android devices, but this is my first brick.
I had flashed the rooted SM-T217s rom, and the wifi wasn't working, so I tried to reflash it, at which point everything went wonky. I searched the forums and found some threads on bricked 217s's, but nothing specific to my situation.
The tablet went to the emergency firmware update screen, and I haven't been able to get Kies to even recognize it. I try to Odin back to the latest stock (B8) but it fails at 'Get PIT for mapping.' My google-fu tells me this is not a good thing.
Am I hosed here? What else can I try?
Thanks XDA, you're my only hope.
joshuaerda said:
Hi friends. Long time lurker here.
I've had many Samsung phones and many other android devices, but this is my first brick.
I had flashed the rooted SM-T217s rom, and the wifi wasn't working, so I tried to reflash it, at which point everything went wonky. I searched the forums and found some threads on bricked 217s's, but nothing specific to my situation.
The tablet went to the emergency firmware update screen, and I haven't been able to get Kies to even recognize it. I try to Odin back to the latest stock (B8) but it fails at 'Get PIT for mapping.' My google-fu tells me this is not a good thing.
Am I hosed here? What else can I try?
Thanks XDA, you're my only hope.
Click to expand...
Click to collapse
Good news, I guess. I was able to flash TWRP recovery and the stock rooted rom from another computer, but now Wifi is borked and there's no network connection. HALP.
joshuaerda said:
Good news, I guess. I was able to flash TWRP recovery and the stock rooted rom from another computer, but now Wifi is borked and there's no network connection. HALP.
Click to expand...
Click to collapse
Okay well I fixed it.
Turns out, the problem was that I was using Odin on a VM on my Mac. I had tried to use a PC, but I think the USB controller was too old, so that failed too. I had to use Heimdall to flash each of the partitions from the B8 zip manually. It worked, and I'm back in business, though not rooted. I suppose I'll wait until there's a better way to root before I try it again.
254336992952
joshuaerda said:
Okay well I fixed it.
Turns out, the problem was that I was using Odin on a VM on my Mac. I had tried to use a PC, but I think the USB controller was too old, so that failed too. I had to use Heimdall to flash each of the partitions from the B8 zip manually. It worked, and I'm back in business, though not rooted. I suppose I'll wait until there's a better way to root before I try it again.
Click to expand...
Click to collapse
You should have made a backup. I used twrp recovery flashed a rom same thing wifi wouldnt work so I restored back. If you get it working again make a backup imo. Goodluck.
IAMRUDYT said:
You should have made a backup. I used twrp recovery flashed a rom same thing wifi wouldnt work so I restored back. If you get it working again make a backup imo. Goodluck.
Click to expand...
Click to collapse
same here, I have the rom, but hesitated on the firmware, waiting to see if someone gets the wifi working, not to many developers here for this tablet.
sm t217s
Ok guys. Heres my deal with this TAB. Ive rooted... Unrooted. wipe wipe wipe wippty wipe . WiFi not working. Fixed it with NB8. So here now I sit with:
----NB8 Wifi works---
----TWRP-----
Yup, pathetic i know. I cant even get the supersu to flash. TWRP wont move it over to flash off external sd card. Im not hip to abd plus i heard you leave yourself wide opento visitors when using that.
Ive eye hustled a thread on here that some friends are getting back together to rock it on a custom rom so my fingers are crossed. This tab is so neglected i mayjust go get the 210r. But i really dont want to. So my question is....
Can someone please give me links to files that work with the NB8 stock firmware. Some of the links are outdated after sprint uploaded the new bootloader. We are a small community on this tab so lets stick together on this. I dont think cynogen isgoing to do anything for it. As they concentrate on thier new phone which looks pretty sweet by the way. K im done. Going to wait for help and play with this htc one s
thats been collecting dust.
Rooted
Sent from my SM-T217S using XDA Premium 4 mobile app