Related
Well...long story short, I flashed ICS but I got locked out so I had to Nandroid back to my original ROM, but some error happened and now my phone won't turn on and I can't access my internal SD card. Using Rogue Recovery, when I try to Restore, my internal SD card isn't detected and I get E:/ Can't mount /emmc. Any way to fix this? Or am I bricked? Please help ASAP
I think my entire internal SD has been fried... If anyone has information, please tell me ASAP
I would start by seeing if you can get into download mode. Sorry if you've already tried this. Otherwise, pull the battery for 10 secs and then hold the volume down button and power key until your screen enters download mode. If that works, you can then Odin back to whatever you want.
I got into Odin, but I'm not really sure what to do with it. I'm not experienced with Odin. Should I push a Kernel? a ROM? My phone won't turn on regularly so a ROM would be pointless
Read along with this http://forum.xda-developers.com/showthread.php?t=1274337
If I tried to explain it, I'd for sure leave something out and you'd really be bricked. It sounds like you're phone is fine. It sounds like you just need to download a stock ROM .tar and flash it via Odin, then re-root, etc. Good luck.
Thanks. I pushed a kernel through but I'm hesitant to take the step for flashing a whole ROM. Also, by stock, do you mean a stock rooted ROM or a blank stock ROM?
in recovery, try to mount the SD card and connect it to your computer. See if it shows up in the computer and if your files are there and you can access it.
If you follow the steps in that guide, you'll be fine. I've done it a bunch of times. I keep a couple of stock ROM .tars on my laptop in case I screw something up while flashing. If I can do it, anyone can.
s9amme said:
in recovery, try to mount the SD card and connect it to your computer. See if it shows up in the computer and if your files are there and you can access it.
Click to expand...
Click to collapse
It won't let me. I think my internal memory is fried. But if I can get my phone working again, I don't care about the internal memoru
I'm on my way to bed. But, I can tell you that some of the vets around here have said time after time that if you're able to get into download mode, chances are your phone will be fine if you know how to Odin back to stock. Good luck to you.
iniz94 said:
It won't let me. I think my internal memory is fried. But if I can get my phone working again, I don't care about the internal memoru
Click to expand...
Click to collapse
It's fine. Mine was doing the same thing with Blazer ICS.
Basically, the way ICS handles USB mount is absurd. Makes no sense.
You have to flash clockworkmod touch from a zip file.
Just follow Phantoms steps exactly, only what's in bold:
To recover recovery:
Thru Odin:
Boot into Download Mode
Open ODIN
Download and Put this in PDA http://forum.xda-developers.com/showthread.php?t=1390393
Flash
Thru Recovery:
Temp CWM How-To (Thanks to overstew for the concept)
1. Download CWM Touch 5.8.1.5 for Epic 4G Touch
http://clockworkmod.com/rommanager
2. Reboot into Stock Recovery
3. "apply update from external storage"
4. Find CWM T ouch 5.8.1.5 zip file and flash it
5. Using Touch Recovery flash ICS-4-ICS v1.0 (FOR THE ICS THEME ONLY)
6. Reboot and enjoy.
Thank you very much, rde. I'm currently flashing sfhub's factory reset from Odin (http://forum.xda-developers.com/showthread.php?t=1383678)
I pray that my phone is okay, lol.
VoX_XDA said:
It's fine. Mine was doing the same thing with Blazer ICS.
Basically, the way ICS handles USB mount is absurd. Makes no sense.
You have to flash clockworkmod touch from a zip file.
Just follow Phantoms steps exactly, only what's in bold:
To recover recovery:
Thru Odin:
Boot into Download Mode
Open ODIN
Download and Put this in PDA http://forum.xda-developers.com/showthread.php?t=1390393
Flash
Thru Recovery:
Temp CWM How-To (Thanks to overstew for the concept)
1. Download CWM Touch 5.8.1.5 for Epic 4G Touch
http://clockworkmod.com/rommanager
2. Reboot into Stock Recovery
3. "apply update from external storage"
4. Find CWM T ouch 5.8.1.5 zip file and flash it
5. Using Touch Recovery flash ICS-4-ICS v1.0 (FOR THE ICS THEME ONLY)
6. Reboot and enjoy.
Click to expand...
Click to collapse
I've done that already but my phone was still acting up so I flashed Rogue Stock Kernel thru Odin and now I'm flashing a factory reset tar.
Awesome. glad you got it figured out.
Stuck at data.img
Gonna have to follow this
http://forum.xda-developers.com/showthread.php?t=1504808
rde34 said:
I'm on my way to bed. But, I can tell you that some of the vets around here have said time after time that if you're able to get into download mode, chances are your phone will be fine if you know how to Odin back to stock. Good luck to you.
Click to expand...
Click to collapse
We've actually found 2 cases where this isn't true:
1) if you flash the intl ICS release (which includes the intl bootloader) This seems to disable the USB port even though you can boot into ODIN D/L mode
2) some process people were doing early on when the FB02 release first came out (not saying it is the FB09 release causing issues, just some unidentified process people were doing at that time) seems to hoars the /data partition and even ODIN repartition doesn't help. I don't want to point fingers but there seemed to be pattern of CWM Touch being involved doing restores, but that was not scientifically proven.
I've learned that no matter what happens, this file will always fill the cracks in mah heart.
SPH-D710.EL29_CL852097_ROOTED-OneClick
afterwards I can begin anew
VoX_XDA said:
I've learned that no matter what happens, this file will always fill the cracks in mah heart.
SPH-D710.EL29_CL852097_ROOTED-OneClick
afterwards I can begin anew
Click to expand...
Click to collapse
Tried that... stuck at data.img like 10 other ppl. I hope there's a fix soon :/ Only just got this phone.
iniz94 said:
Tried that... stuck at data.img like 10 other ppl. I hope there's a fix soon :/ Only just got this phone.
Click to expand...
Click to collapse
If you just got the phone and can get it replaced, I would just do that.
sfhub said:
If you just got the phone and can get it replaced, I would just do that.
Click to expand...
Click to collapse
Got it around a month ago and didn't get insurance... is it possible to suddenly add insurance and go next week to get it replaced? Or do I need to bring the phone in?
I have a rooted Galaxy S3 that is running the ATT Jelly Bean update.
Last night, while looking at ROM manager I got a popup saying there is a newer version of CWM and did I want to install it.
After installing it, the phone will only boot into recovery. I cannot get it to start. And when I tried to restore from a backup that I have used successfully before, I got an error while restoring data.
At this point, I am thinking that I might have bricked this phone. Searching on the ATT Galaxy S3 forum hasn't turned up anything relevant.
Does anyone have an idea what I can try next?
Thanks
northstar7 said:
I have a rooted Galaxy S3 that is running the ATT Jelly Bean update.
Last night, while looking at ROM manager I got a popup saying there is a newer version of CWM and did I want to install it.
After installing it, the phone will only boot into recovery. I cannot get it to start. And when I tried to restore from a backup that I have used successfully before, I got an error while restoring data.
At this point, I am thinking that I might have bricked this phone. Searching on the ATT Galaxy S3 forum hasn't turned up anything relevant.
Does anyone have an idea what I can try next?
Thanks
Click to expand...
Click to collapse
If you a can boot into recovery than you aren't bricked.
You can do a factory reset that might clear it up.
Worst case go into download mode and use Odin to reinstall the stock ROM.
Sent from my SGH-I747 using xda app-developers app
northstar7 said:
I have a rooted Galaxy S3 that is running the ATT Jelly Bean update.
Last night, while looking at ROM manager I got a popup saying there is a newer version of CWM and did I want to install it.
After installing it, the phone will only boot into recovery. I cannot get it to start. And when I tried to restore from a backup that I have used successfully before, I got an error while restoring data.
At this point, I am thinking that I might have bricked this phone. Searching on the ATT Galaxy S3 forum hasn't turned up anything relevant.
Does anyone have an idea what I can try next?
Thanks
Click to expand...
Click to collapse
Im assuming you powered down, did a battery pull and powered back up? Factory reset?
What error message is displayed when trying to restore a backup?
The latest cwm release is 6.0.2.8. If you came from 6.0.2.3, I would download a cwm flashable zip of that recovery and flash that. Perhaps try a reboot then. If it's still a no-go, try restoring a backup with the cwm you had just downloaded and flashed to see if it will restore without an error message
Different CWM
xBeerdroiDx said:
Im assuming you powered down, did a battery pull and powered back up? Factory reset?
What error message is displayed when trying to restore a backup?
The latest cwm release is 6.0.2.8. If you came from 6.0.2.3, I would download a cwm flashable zip of that recovery and flash that. Perhaps try a reboot then. If it's still a no-go, try restoring a backup with the cwm you had just downloaded and flashed to see if it will restore without an error message
Click to expand...
Click to collapse
Thanks very much for the advice.
For the record, my phone is displaying "ClockworkMod Recovery v6.0.2.9"
I just has this happen to me as well. I just put the s3 in download mode and used Odin to re flash cwm. I'm using the same version cwm.
Sent from my SAMSUNG-SGH-I747 using xda premium
I as well. Tried everything and no go. Will try ODIN and see if it works.
Domoo said:
I just has this happen to me as well. I just put the s3 in download mode and used Odin to re flash cwm. I'm using the same version cwm.
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
stranglely pressing the recovery button combo fixed it and im back in CM10.1 #lolwut?
In the end I got the phone working again
For whatever reason, after getting that update to ClockworkMod, the phone would not boot.
I followed the Beginners' Guide to Rooting the Galaxy S3 forum. When I was finished I immediately got an OTA update from ATT.
So now the phone is running again, but I've lost most of my customization and personal data.
What is with this CWM "upgrade?" Or is the problem with ROM Manager?
More likely is that I did something wrong.
At least I can make calls now.
Same here, stay away from that update! Bad things!
This also happened to me. Cwm is showing up as .9 instead of .8. I flashed a previous version of twrp and it still proceeded to go into recovery mode after selecting reboot. I did a factory reset and re flashed aokp and also cm10.1 (along with gapps of course) and it still did it. So I pulled the battery and put it into download mode and reset it from there. That's the only way to get the phone to boot up. From what I see here, is the basic fix for this problem flashing an older cwm in Odin?
Having the same issue, version .9 No amount of clearing data/wipe/reflash/restore will do anything for me either. So much for a lunchtime AOKP update...
I've looked in several different forums on xda and the general fix seems to be flashing a previous version of cwm. No need to reset your phone and flash roms all day long.
Download prior cwm release (.tar)
pull battery and replace
boot to download mode
connect to pc and flash cwm
Disconnect, pull battery, reboot
Here's the 6.0.2.3 release. You can grab the .8 in the Android dev section if you wish
https://www.dropbox.com/s/sfkjtndn7k0urmh/recovery-clockwork-6.0.2.3-d2att.tar
Let me know if this does not work. If your device is not recognized by your pc, you can try flashing this cwm zip in recovery itself (if you have a micro sd card):
http://d-h.st/8qP
I flashed with the same version of cwm I had previously before this issue (6.0.28). It seems to be an issue with 6.0.29 if so many people have this same issue.
Sent from my SAMSUNG-SGH-I747 using xda premium
xBeerdroiDx said:
I've looked in several different forums on xda and the general fix seems to be flashing a previous version of cwm. No need to reset your phone and flash roms all day long.
Download prior cwm release (.tar)
pull battery and replace
boot to download mode
connect to pc and flash cwm
Disconnect, pull battery, reboot
Here's the 6.0.2.3 release. You can grab the .8 in the Android dev section if you wish
https://www.dropbox.com/s/sfkjtndn7k0urmh/recovery-clockwork-6.0.2.3-d2att.tar
Let me know if this does not work. If your device is not recognized by your pc, you can try flashing this cwm zip in recovery itself (if you have a micro sd card):
http://d-h.st/8qP
Click to expand...
Click to collapse
I flashed the CMW-recovery_ATT-6.0.2.3_zip directly from the external sd card to the phone and the phone is now working. but I did have to reboot phone twice. the first time it stayed in recovery.
THANK YOU!!
xBeerdroiDx said:
I've looked in several different forums on xda and the general fix seems to be flashing a previous version of cwm. No need to reset your phone and flash roms all day long.
Download prior cwm release (.tar)
pull battery and replace
boot to download mode
connect to pc and flash cwm
Disconnect, pull battery, reboot
Here's the 6.0.2.3 release. You can grab the .8 in the Android dev section if you wish
https://www.dropbox.com/s/sfkjtndn7k0urmh/recovery-clockwork-6.0.2.3-d2att.tar
Let me know if this does not work. If your device is not recognized by your pc, you can try flashing this cwm zip in recovery itself (if you have a micro sd card):
http://d-h.st/8qP
Click to expand...
Click to collapse
I believe this can even be simplified a bit more. At least for me, some people may find Odin to be the simple way to do things. So you're stuck at recovery:
Hold the power button for 10 seconds to power off.
Boot to download mode by holding volume down and home. The phone will probably start to boot right away after releasing the power button. If it doesn't go to download, then your timing is off, try again.
Hold the power button for 10 seconds to power off and reboot.
It should boot regularly now.
Flash a new recovery. You can download CWM 6.0.2.8 or use this as an opportunity to move to TWRP. Once you have the img file on your phone, go to a terminal and (after su, if needed) run dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p18 (replace "/sdcard/recovery.img" with the path and name of the img file you downloaded. You can also flash the recovery using whatever other on-phone method you prefer.
The CWM download page is now showing that 6.0.2.8 is the newest version for many of the S3 variants, so they've certainly noticed the bug.
J M L said:
I believe this can even be simplified a bit more. At least for me, some people may find Odin to be the simple way to do things. So you're stuck at recovery:
Hold the power button for 10 seconds to power off.
Boot to download mode by holding volume down and home. The phone will probably start to boot right away after releasing the power button. If it doesn't go to download, then your timing is off, try again.
Hold the power button for 10 seconds to power off and reboot.
It should boot regularly now.
Flash a new recovery. You can download CWM 6.0.2.8 or use this as an opportunity to move to TWRP. Once you have the img file on your phone, go to a terminal and (after su, if needed) run dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p18 (replace "/sdcard/recovery.img" with the path and name of the img file you downloaded. You can also flash the recovery using whatever other on-phone method you prefer.
The CWM download page is now showing that 6.0.2.8 is the newest version for many of the S3 variants, so they've certainly noticed the bug.
Click to expand...
Click to collapse
How is this simpler? There are left out bits and errors all through your instructions. My steps were for odin so I'm not sure why you thought they were not.
Can anyone assist me with the issue of how to get this SGSIII out of boot recovery mode/
Odin gives a FAIL, PIT Partition not found error! The phone itself gives Odin: Flash read failure
N2PC Tech said:
Can anyone assist me with the issue of how to get this SGSIII out of boot recovery mode/
Odin gives a FAIL, PIT Partition not found error! The phone itself gives Odin: Flash read failure
Click to expand...
Click to collapse
Some more details would help me understand better. What I'd love to know is.
1. What is the current state of the phone ?
2. Is it rooted or Are you trying to root ? If so what process.
3. Are you trying to flash a rom or Recovery or what ?
4. Last but not least. What rom and version you currently have on there ?
Perseus71 said:
Some more details would help me understand better. What I'd love to know is.
1. What is the current state of the phone ? Stuck in "Boot recovery mode"
2. Is it rooted or Are you trying to root ? If so what process. not rooted at all.
3. Are you trying to flash a rom or Recovery or what ? was trying to install stock rom.
4. Last but not least. What rom and version you currently have on there ? I currently have no rom on here at all!
Click to expand...
Click to collapse
N2PC Tech said:
Some more details would help me understand better. What I'd love to know is.
1. What is the current state of the phone ? Stuck in "Boot recovery mode"
2. Is it rooted or Are you trying to root ? If so what process. not rooted at all.
3. Are you trying to flash a rom or Recovery or what ? was trying to install stock rom.
4. Last but not least. What rom and version you currently have on there ? I currently have no rom on here at all!
Click to expand...
Click to collapse
You didn't specify how you got here .What did you try to do, that left you in this state ? Am I assuming correctly that you somehow managed to wipe system partition and have only the stock recovery ?
If the phone is in Recovery mode, Odin will not work. You will need to reboot the phone into Download mode. To do this, you pull the battery out, volume down, home, and power button at the same time until you see the Samsung logo, and then release. You will see a warning message with bright yellow triangle and will say Downloading. Once that is done, connect to the PC.
Using ODIN, first flash a custom recovery such as TWRP. If you want to go back to stock, this is the time you flash Stock rom instead of the recovery.
If you want custom rom, copy the rom zip to the External SD card and then put that in the phone and flash via Custom Recovery.
Perseus71 said:
You didn't specify how you got here .What did you try to do, that left you in this state ? Am I assuming correctly that you somehow managed to wipe system partition and have only the stock recovery ?
If the phone is in Recovery mode, Odin will not work. You will need to reboot the phone into Download mode. To do this, you pull the battery out, volume down, home, and power button at the same time until you see the Samsung logo, and then release. You will see a warning message with bright yellow triangle and will say Downloading. Once that is done, connect to the PC.
Using ODIN, first flash a custom recovery such as TWRP. If you want to go back to stock, this is the time you flash Stock rom instead of the recovery.
If you want custom rom, copy the rom zip to the External SD card and then put that in the phone and flash via Custom Recovery.
Click to expand...
Click to collapse
Sorry.....
the phone was loading that QHSUSB_DLOAD driver on windows every time i plugged into my PC. I then tried to Odin to a Stock TMO Rom, and that was when i got the Boot recovery mode screen. i have been trying to use the buttons to get into download mode, but that doesnt work either!
N2PC Tech said:
Sorry.....
the phone was loading that QHSUSB_DLOAD driver on windows every time i plugged into my PC. I then tried to Odin to a Stock TMO Rom, and that was when i got the Boot recovery mode screen. i have been trying to use the buttons to get into download mode, but that doesnt work either!
Click to expand...
Click to collapse
QHSUSB_DLOAD means your device is hard Bricked. Please follow De-Bricking thread in this sub forum.
Perseus71 said:
QHSUSB_DLOAD means your device is hard Bricked. Please follow De-Bricking thread in this sub forum.
Click to expand...
Click to collapse
Thats how i got it out of hard brick mode. i used the sdcard image method, and that was as far as the phone went: boot recovery mode!:fingers-crossed:
N2PC Tech said:
Thats how i got it out of hard brick mode. i used the sdcard image method, and that was as far as the phone went: boot recovery mode!:fingers-crossed:
Click to expand...
Click to collapse
Then perhaps you should have asked on that thread for next steps. Anyway, if you are still getting the Qsub message when connecting to pc that means its not out of de-brick yet. I'd suggest following there.
Also please first put the phone in download mode and THEN connect to the PC. Tell me what happens in that case.
Perseus71 said:
Then perhaps you should have asked on that thread for next steps. Anyway, if you are still getting the Qsub message when connecting to pc that means its not out of de-brick yet. I'd suggest following there.
Also please first put the phone in download mode and THEN connect to the PC. Tell me what happens in that case.
Click to expand...
Click to collapse
Perhaps not Perseus! AS stated........Its out of the brick mode and is now stuck in boot recovery mode! The method to get it into download mode is null, because it will only go into the boot recovery mode when i push those buttons to try and get it there! NOTE: its now in MSM9860 when plugged into the PC.
N2PC Tech said:
Perhaps not Perseus! AS stated........Its out of the brick mode and is now stuck in boot recovery mode! The method to get it into download mode is null, because it will only go into the boot recovery mode when i push those buttons to try and get it there! NOTE: its now in MSM9860 when plugged into the PC.
Click to expand...
Click to collapse
Please note, the button combo slightly differs for Recovery versus Download mode
Recovery Booting - Power +Home + Volume UP
Download Mode - Power +Home + Volume DOWN
Do you still have the sd setup from the debrick thread? Can you see if you can get back to download mode by booting from that again?
If so, try flashing the Stock firmware again, and if you still end up in the same spot maybe try again, but this time flash CWM or TWRP recovery from Odin, then flash a Rom from recovery.
And I can't remember right off but did you try factory resetting from recovery?
Sent from my SGH-T999N using Tapatalk
Perseus71 said:
Please note, the button combo slightly differs for Recovery versus Download mode
Recovery Booting - Power +Home + Volume UP
Download Mode - Power +Home + Volume DOWN
Click to expand...
Click to collapse
Sorry, but those methods aren't and haven't worked since my phone came out of brick mode! I had already constantly tried that!
N2PC Tech said:
Sorry, but those methods aren't and haven't worked since my phone came out of brick mode! I had already constantly tried that!
Click to expand...
Click to collapse
In that Case boot the phone using the files of the SD Card as per the De-Brick Thread. See if you can into Downloading mode that way.
Perseus71 said:
In that Case boot the phone using the files of the SD Card as per the De-Brick Thread. See if you can into Downloading mode that way.
Click to expand...
Click to collapse
Tried that method also and no luck!
Just to clarify, the boot recovery mode you are referring to, does it have the binary/flash count, system status, etc? Basically what do you see?
It sounds in some ways you are in download mode, but recovery is a very different mode, so just to clear up any confusion.....
Sent from my SGH-T999N using Tapatalk
I've been trying to get cyanogenmod 10.2.1 to work for my phone, and I was getting assert failures in recovery. I found an AIO firmware update by freeza and flashed it in CWM and rebooted and now my device is hard bricked. I can't access recovery, download mode, and the phone will not power on. I flashed this file; Galaxy-S-fre3-MB1FirmwareModemAIO.zip, specifically. Is there any way to revive my device without having to JIG it or is it just done for? I was also on a KitKat rom.
PandaDan said:
I've been trying to get cyanogenmod 10.2.1 to work for my phone, and I was getting assert failures in recovery. I found an AIO firmware update by freeza and flashed it in CWM and rebooted and now my device is hard bricked. I can't access recovery, download mode, and the phone will not power on. I flashed this file; Galaxy-S-fre3-MB1FirmwareModemAIO.zip, specifically. Is there any way to revive my device without having to JIG it or is it just done for? I was also on a KitKat rom.
Click to expand...
Click to collapse
Sounds like its toast without a jig or JTAG. You could have switched to PHILZ ADVANCED CWM recovery. This recovery works better than TWRP or regular CWM. I had many of different issues with these 2. This zip is not a ROM, but a modem zip.
JB india firmwares link please. I cant download via Samsung link
Sent from my GT-S5830 using Tapatalk 2
PandaDan said:
I've been trying to get cyanogenmod 10.2.1 to work for my phone, and I was getting assert failures in recovery. I found an AIO firmware update by freeza and flashed it in CWM and rebooted and now my device is hard bricked. I can't access recovery, download mode, and the phone will not power on. I flashed this file; Galaxy-S-fre3-MB1FirmwareModemAIO.zip, specifically. Is there any way to revive my device without having to JIG it or is it just done for? I was also on a KitKat rom.
Click to expand...
Click to collapse
If you have a Virgin Mobile SPH-L710, you can use the de-brick image below, otherwise you need to search around Google for one. You would search for "debrick image for <model numeber>".
I got this problem solved with the help of zachf714, invisiblek and a special thanks to xstefen for providing a working debrick image. Here is the link to the working debrick image that xstefen provided: http ://download.xstefen.net /getdownload.php?file=./xstefen/mmcblk0_backup.bin.zip. (Remove spaces) all you need to do, is write this image to a micro SD card using linux's
Code:
dd
command or Win32 Disk Imager. Then put the sd card in your phone, boot into download mode and flash a stock ROM using Odin.
Wish anyone else who have this problem luck.
P.S. I am not responsible if anything happens to your phone because of this.
I follow this thread: http://forum.xda-developers.com/showthread.php?t=2549068
I put this file on the sd card debrick-SGH-I747U-CUEMJB3.img, made sure phone battery was charged up. Tried to enter download mode, it completely skipped it and phone is now running stock 4.3?? I try to enter recovery mode and it still just starts up with Stock 4.3.
So I assume it is running completely of the sd card. I can enter Stock Recovery but not sure what I do now. If i pull the card the phone is dead like before. Red light when plugged in, nothing happens with any button pushes.
I guess I am wondering what my next step is?
Thanks
Ruscicap said:
I follow this thread: http://forum.xda-developers.com/showthread.php?t=2549068
I put this file on the sd card debrick-SGH-I747U-CUEMJB3.img, made sure phone battery was charged up. Tried to enter download mode, it completely skipped it and phone is now running stock 4.3?? I try to enter recovery mode and it still just starts up with Stock 4.3.
So I assume it is running completely of the sd card. I can enter Stock Recovery but not sure what I do now. If i pull the card the phone is dead like before. Red light when plugged in, nothing happens with any button pushes.
I guess I am wondering what my next step is?
Thanks
Click to expand...
Click to collapse
The device is indeed booting off the SD card. However, if you can boot into system, you should also be able to boot into download and recovery modes using the 3-button combo. If you can get into download mode, you can try using Odin v 3.07 to flash the complete 4.3 stock image. Download the Odin flashable zip file from the link below to your computer. Extract the tar.md5 file and verify the MD5 to be sure it downloaded correctly.
http://www.androidfilehost.com/?fid=23329332407590581
Download Odin v3.07 and run Odin.exe for the flashing tool. With your debrick card, boot into download mode by pressing the Volume Down, Home and Power button. If you can't get into download mode with the 3-button combo, suggest you try a USB jig. Use Odin to flash the stock file to your phone. If the flashing is successful, the device should be able to boot normally after this without the debrick card.
Cool thanks Larry2999. I will have to go the USB jig route it won't go into recovery or download. I can only get into Stock recovery. Any specifics I need to know when getting a usb jig? Thanks again for you response. I am just glad it is working now. But probably don't want to run off SD forever.
Ruscicap said:
Cool thanks Larry2999. I will have to go the USB jig route it won't go into recovery or download. I can only get into Stock recovery. Any specifics I need to know when getting a usb jig? Thanks again for you response. I am just glad it is working now. But probably don't want to run off SD forever.
Click to expand...
Click to collapse
There is a thread somewhere on how to make a D-I-Y jig. You can, however, buy it cheaply online for about $3. In buying one, you'd only need to be sure it states that it works with the S3.
Looks like you are able to get into recovery now but you have stock, rather than custom, recovery. There is only one recovery partition and the default is stock, unless, you flash a custom recovery. If you had custom recovery, it would have been possible to flash a 4.3 stock restore zip via (custom) recovery. To flash custom recovery, however, you'd need Odin in download mode so we are back to the problem with getting into download mode.
Thanks Larry ordering jig tomorrow
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Larry2999 said:
There is a thread somewhere on how to make a D-I-Y jig. You can, however, buy it cheaply online for about $3. In buying one, you'd only need to be sure it states that it works with the S3.
Looks like you are able to get into recovery now but you have stock, rather than custom, recovery. There is only one recovery partition and the default is stock, unless, you flash a custom recovery. If you had custom recovery, it would have been possible to flash a 4.3 stock restore zip via (custom) recovery. To flash custom recovery, however, you'd need Odin in download mode so we are back to the problem with getting into download mode.
Click to expand...
Click to collapse
Do you suggest a reliable 4.3 stock to flash or install through ODIN? This is how I got to where I am, something screwed up trying to install stock 4.3 through ODIN.
Thanks again for your help. Jig should be here in a couple days.
Ruscicap said:
Do you suggest a reliable 4.3 stock to flash or install through ODIN? This is how I got to where I am, something screwed up trying to install stock 4.3 through ODIN.
Thanks again for your help. Jig should be here in a couple days.
Click to expand...
Click to collapse
Yes, the ONLY way to recover is to flash a complete 4.3 stock image. Are you sure you bricked in the first instance by flashing 4.3 via Odin? The only Odin compatible stock 4.3 file I'm aware of is the one in the link I forwarded earlier. This was only recently developed and appears to have been used by several people without problem. You may check to be sure you were not trying to flash a 4.1.1 file in error. Apologies if I sound like I'm second guessing you but flashing 4.1.1 via Odin usually results in the kind of hard brick you experienced.
The other alternative would be to flash custom recovery (TWRP or CWM) via Odin and then use custom recovery to flash a complete 4.3 stock image. You will find the instructions in the following thread ...
http://forum.xda-developers.com/showthread.php?t=2658486
Download the stock restore zip for your preferred custom recovery option to your PC and save to your phone's internal storage. If you want to use TWRP, you can find the Odin flashable file for TWRP via the link below ...
http://techerrata.com/file/twrp2/d2att/openrecovery-twrp-2.6.3.1-d2att.tar
If, however, you go the first option and flash the 4.3 file via Odin, be sure to use Odin v 3.07. You'll see the Odin flashable file and instructions on page 4 of the following thread ...
http://forum.xda-developers.com/showthread.php?t=2722660&page=4
or you can download directly from here ...
http://www.androidfilehost.com/?fid=23329332407590581
Thanks again. Not really sure what went wrong, tried to use odin to install 4.3 Stock from this thread. http://forum.xda-developers.com/showthread.php?t=2658486
I will try to follow your threads and get it right this time.
Ruscicap said:
Thanks again. Not really sure what went wrong, tried to use odin to install 4.3 Stock from this thread. http://forum.xda-developers.com/showthread.php?t=2658486
I will try to follow your threads and get it right this time.
Click to expand...
Click to collapse
The file from that thread is for (custom) recovery only. You can't flash zips via Odin so if you are using that file, you would need to first install custom recovery via Odin and then flash the zip via custom recovery.
Hey Larry, just wanted to say thanks. Phone is back working properly, 4.3 installed with no problem. Took me awhile never had the time. So fathers day was my chance to get this working. Flashed twrp and then the stock zip. Worked great.
Thanks again for all your help, I very much appreciate it.
Ruscicap said:
Hey Larry, just wanted to say thanks. Phone is back working properly, 4.3 installed with no problem. Took me awhile never had the time. So fathers day was my chance to get this working. Flashed twrp and then the stock zip. Worked great.
Thanks again for all your help, I very much appreciate it.
Click to expand...
Click to collapse
Glad to know it's working OK now. Kind regards