Hello, my phone is apparently soft bricked and stuck on the Samsung logo. I am trying to follow ATT's instructions on how to perform a master reset. These are the instructions I am following:
1. Power off the device.
NOTE: If unable to power off, remove and reinsert the battery.
2. Press and hold the Volume Up + Volume Down and Power key.
3. Release ONLY Power Key when Samsung Logo appears.
4. Use Volume Up and Volume Down to scroll down to "Wipe data/factory reset", and then press Power key to confirm to delete all the user data.
5. Scroll down to "Yes! delete all user data" and press the Power key to confirm.
6. When "Data wipe complete" is displayed, select "Reboot system now" and press Power key to confirm to reboot your handset.
Problem is, when I reach step 3, I get an animated Android with some blue thing in it's belly that spins faster and faster until the Samsung Galaxy SII logo appears and gets stuck again.
I've attached an image of the logo I am seeing.
I'm probably doing something stupid. Anyone have any ideas
EDIT: The phone is completely stock. Not rooted, no ROMS, etc
As far as I can remember, that logo comes with custom recovery but not the stock recovery. What firmware is installed on the phone?
Basically, you are not able to boot into recovery. You should try again, holding down all three keys, vol+ vol- pwr, until: the Galaxy SII logo appears, screen goes black, Galaxy SII logo appears again. Then release all three buttons. Recovery should come up within a few seconds.
If you are unable to get into recovery, you will need to re-flash the stock firmware using Odin. We can guide you through the process if you are unfamiliar with it.
Hi CreepynCrawly. I tried the three button salute, hold down until you see the logo twice thing but it always goes to the animation. No menu! Tried more than just a few times, thinking I was fat fingering something.
So, I gave up and I took the flash to stock firmware route. My phone is at Android version is 4.1.2 and baseband I777UCMD8.
I downloaded Odin 3.0.9 and the stock firmware from Sammobile . It fails when it attempts to write the sbl.bin. (see attached). I've tried a few times and two different machines. I also tried doing a restore from Kies (installed the USB drivers along with it). Should I just keep trying? Seems like some people had success with that (although I don't understand why).
creepyncrawly said:
As far as I can remember, that logo comes with custom recovery but not the stock recovery. What firmware is installed on the phone?
Basically, you are not able to boot into recovery. You should try again, holding down all three keys, vol+ vol- pwr, until: the Galaxy SII logo appears, screen goes black, Galaxy SII logo appears again. Then release all three buttons. Recovery should come up within a few seconds.
If you are unable to get into recovery, you will need to re-flash the stock firmware using Odin. We can guide you through the process if you are unfamiliar with it.
Click to expand...
Click to collapse
I think we need to use Odin 1.8.5 for our device... don't quote me though. You could try that instead
badger109 said:
I think we need to use Odin 1.8.5 for our device... don't quote me though. You could try that instead
Click to expand...
Click to collapse
Thanks Badger, I tried it, but it seems to just hang. I wonder if it is a hardware issue. It just "happened" that way. Had it in my bag. Took it out, and there it was, all soft bricked and what-not with the Samsung logo. Had not installed anything whatsoever in the past few days.
3 months to go before I can upgrade. I can live with my Captivate 'til then I guess.
This sounds like it could be a case of nand read/write corruption. The fix is fairly specific. And it is recommended to use Odin version 1.85 for this phone, although any version of Odin should work (in theory.) There have been some reports where newer versions of Odin did not.
Since you currently have UCMD8, you will be changing to an earlier version of the os during this procedure, so you will need to perform a wipe data/factory reset from within recovery after step 2 before the phone will boot. Please follow the steps in order and exactly.
1)Go to this post and download the Tar version of Siyah 2.6.14 Kernel. Flash it in the PDA slot without ticking Re-Partitioning. If you get a pass, it won't boot, so turn the phone off and then back to download mode and...
2) Flash the full stock Gingerbread distribution from the Download Repository, I777UCKH7 including the bootloaders and everything, in the PDA slot.
3) If you get a pass here, then the phone might boot, or you might have to boot into recovery first and perform a wipe data/factory reset. If you're able to boot the phone, then you are back in business, and can flash whatever firmware you want.
If it is not, then:
4) Download the SBL Bootloader from the Download Repository. Flash it as PDA in ODIN, without ticking Re-Partitioning.
5) Flash the Kernel, as in step 1.
6) Flash the full stock Gingerbread distribution, as in step 2.
erponsha maniacal
Hi CreepynCrawly, I started on your suggestion, but I cannot get past the kernel update. The green progress bar in Odin goes green and then just sits there with "NAND Write Start!!!". I let it sit for 30 minutes the first time, and then I tried with different versions of Odin - 1.3, 3.09, etc...no go. Found an article on here about a similar issue and went through the checklist - different USB ports, different computers, different cables, Odin version, etc, etc...not much success. The download count has increased though, and "Current Binary" says "Custom" on the phone. Any ideas from here on would be great, because my Captivate is kind of sad comparatively speaking .
[EDIT]: I've also tried flashing the SBL from the Download Repository - same issue. It sticks at "NAND Write Start!!"
creepyncrawly said:
This sounds like it could be a case of nand read/write corruption. The fix is fairly specific. And it is recommended to use Odin version 1.85 for this phone, although any version of Odin should work (in theory.) There have been some reports where newer versions of Odin did not.
Since you currently have UCMD8, you will be changing to an earlier version of the os during this procedure, so you will need to perform a wipe data/factory reset from within recovery after step 2 before the phone will boot. Please follow the steps in order and exactly.
1)Go to this post and download the Tar version of Siyah 2.6.14 Kernel. Flash it in the PDA slot without ticking Re-Partitioning. If you get a pass, it won't boot, so turn the phone off and then back to download mode and...
2) Flash the full stock Gingerbread distribution from the Download Repository, I777UCKH7 including the bootloaders and everything, in the PDA slot.
3) If you get a pass here, then the phone might boot, or you might have to boot into recovery first and perform a wipe data/factory reset. If you're able to boot the phone, then you are back in business, and can flash whatever firmware you want.
If it is not, then:
4) Download the SBL Bootloader from the Download Repository. Flash it as PDA in ODIN, without ticking Re-Partitioning.
5) Flash the Kernel, as in step 1.
6) Flash the full stock Gingerbread distribution, as in step 2.
Click to expand...
Click to collapse
Yeah, my wife is still using my old captivate. I just bought her an SII on Swappa, so once I get her new phone set up for her, I'll be selling her captivate.
If steps 1 - 3 didn't work, you should proceed to steps 4 - 6. Loading the secondary bootloader first may allow the kernel to flash, followed by a successful system flash. Try it out and let us know.
The flash counter is really irrelevant now that the phone is out of warranty, but it can be dealt with later once the phone is booting normally. Completing the process will remove the yellow triangle warning boot screen.
Yup - Step 4 hangs - green progress bar and then "NAND Write Start!!" and then...nothing! It just sits there. Am I toast or what?
creepyncrawly said:
Yeah, my wife is still using my old captivate. I just bought her an SII on Swappa, so once I get her new phone set up for her, I'll be selling her captivate.
If steps 1 - 3 didn't work, you should proceed to steps 4 - 6. Loading the secondary bootloader first may allow the kernel to flash, followed by a successful system flash. Try it out and let us know.
The flash counter is really irrelevant now that the phone is out of warranty, but it can be dealt with later once the phone is booting normally. Completing the process will remove the yellow triangle warning boot screen.
Click to expand...
Click to collapse
The common understanding is that if the phone can boot into download mode, it can be recovered to working. This would be true in all but a few rare cases of partial emmc memory damage. I would still assume that your phone can be made to work again.
Please view this post in another thread. I'm not familiar with "hg42's 120824-151927-emmc_find_brick_start.zip" but it would be worth the time to find this file and try it to see what it reports.
There are a large variety of things that can prevent Odin from completing. You need to do some research, and try all the possible issues, but just off the top of my head, it could be due to the cable, the usb port on the computer, the usb port on the phone, the usb driver on the computer, etc. So, try different cables - a Samsung original usb cable is best, try different ports on the computer, try a different computer, reinstall the usb driver, etc.
Related
EDIT: As I've now gotten Odin to flash again, and my device still won't boot, I'm really starting to think Andromeda's recovery has wiped something vital that isn't restored with a "regular" stock ROM image. PIT? EFS? Partitioning? Something like that? Odin successfully flashes the whole image tar (which I've previously used successfully), and the boot splash now correctly changes to the default Samsung one without triangle, but still the phone won't boot (as described in msg #3). So I'm now wondering if there's any way to a more aggressive restore (whence the topic title change)? Or am I barking up the wrong tree here?
----------
Hi
Okay, so I was testing out different kernels with Paranoid Android. I had the Dorimanx kernel installed at first, but had some volume issues, so I shifted to the Dream kernel, wouldn't boot. Then then the Andromeda kernel, and it still wouldn't boot, so I thought I might try doing a factory wipe in Andromeda's recovery. It then froze, and after about 20 minutes I gave up waiting for it and reset the device.
I then tried using the recovery to reinstall the Dorimanx kernel that worked, but it would fail, too. Just hang. After some attempts, also at just mounting the storage via USB, everything would fail, a couple of times with a message about emmc not mounting IIRC.
I then got a response on PA's forum about which kernel was suggested, and the answer was the stock kernel, so I thought I'd just use Odin to flash a CF kernel.
I think I had to do two attempts, or maybe just one, but it succeeded in installing the kernel, and the device rebooted. Except it didn't really. I can't get a "regular" boot screen (the one with the triangle), and so I can't get into recovery. Also, when the charger is plugged in, instead of showing first the grey battery icon with the spinner in it (which I seem to remember would spin before) and the going to the battery with green, it just show the grey icon with a spinner that doesn't spin. It never goes to the green battery screen.
I could (and can) still get to download mode, so I thought I'd do a back to stock routine. I downloaded a full stock ROM and tried to flash it with Odin. It would then freeze at the setup connection step. I tried a different image, same result. I tried reflashing the CF kernel (which worked just minutes before with Odin), again with the same result. I tried different USB ports and cables (even though I just used Odin successfully before), rebooting, unplugging at the frozen step and plugging back in, but to no avail. Odin won't flash any .tar.md5 anymore AFAICT. At least not with the regular no-frills one-click approach.
I'm fearing a hardbrick here. Except I still have access to download mode, and Odin sees the device. Could the recovery in Andromeda have destroyed the partition table perhaps? Or overwritten something it wasn't supposed to?
Is there a different approach to recovery that I could try out? Or does any one of you have any tips I might try out? Anything would be most welcome and appreciated
Thank you,
Daniel
PS: Oh, I just tried starting it up after it's been without battery and unplugged overnight and all day. I tried starting it into recovery mode, and now I have a different screen altogether: It says, "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again. Well, that sounds tempting! Except - I've never used Kies on this device in the first place, and Kies does not having any clue what I've been doing with this thing... Would it be safe to try out? I'm hesitant...
Daniel Smedegaard Buus said:
Hi
Okay, so I was testing out different kernels with Paranoid Android. I had the Dorimanx kernel installed at first, but had some volume issues, so I shifted to the Dream kernel, wouldn't boot. Then then the Andromeda kernel, and it still wouldn't boot, so I thought I might try doing a factory wipe in Andromeda's recovery. It then froze, and after about 20 minutes I gave up waiting for it and reset the device.
I then tried using the recovery to reinstall the Dorimanx kernel that worked, but it would fail, too. Just hang. After some attempts, also at just mounting the storage via USB, everything would fail, a couple of times with a message about emmc not mounting IIRC.
I then got a response on PA's forum about which kernel was suggested, and the answer was the stock kernel, so I thought I'd just use Odin to flash a CF kernel.
I think I had to do two attempts, or maybe just one, but it succeeded in installing the kernel, and the device rebooted. Except it didn't really. I can't get a "regular" boot screen (the one with the triangle), and so I can't get into recovery. Also, when the charger is plugged in, instead of showing first the grey battery icon with the spinner in it (which I seem to remember would spin before) and the going to the battery with green, it just show the grey icon with a spinner that doesn't spin. It never goes to the green battery screen.
I could (and can) still get to download mode, so I thought I'd do a back to stock routine. I downloaded a full stock ROM and tried to flash it with Odin. It would then freeze at the setup connection step. I tried a different image, same result. I tried reflashing the CF kernel (which worked just minutes before with Odin), again with the same result. I tried different USB ports and cables (even though I just used Odin successfully before), rebooting, unplugging at the frozen step and plugging back in, but to no avail. Odin won't flash any .tar.md5 anymore AFAICT. At least not with the regular no-frills one-click approach.
I'm fearing a hardbrick here. Except I still have access to download mode, and Odin sees the device. Could the recovery in Andromeda have destroyed the partition table perhaps? Or overwritten something it wasn't supposed to?
Is there a different approach to recovery that I could try out? Or does any one of you have any tips I might try out? Anything would be most welcome and appreciated
Thank you,
Daniel
PS: Oh, I just tried starting it up after it's been without battery and unplugged overnight and all day. I tried starting it into recovery mode, and now I have a different screen altogether: It says, "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again. Well, that sounds tempting! Except - I've never used Kies on this device in the first place, and Kies does not having any clue what I've been doing with this thing... Would it be safe to try out? I'm hesitant...
Click to expand...
Click to collapse
the reason for Dream and Andromeda not booting ur phone is that, if ur paranoid rom version was latest, then it comes with the new JB mali drivers for which only Dori v7.4 and siyah v5.0 are compatible
since u have already messed up too much with ur phone, u can try the 'KIES' option as the last resort to restore it back, since odin flash is not wrk'ng for u
Okay, so I tried installing Kies and connecting it. A variety of connection attempts, but it just won't connect to the device.
But, I'm making some progress! I've found that when I can get the phone to boot into the "Firmware upgrade encountered an issue." screen, I can get Odin to flash the stock Gingerbread image (still won't in download mode). And I then get a reboot with the regular Samsung boot splash (no yellow triangle) - except it never gets past it. After about a minute, it'll go black and then boot back up to the same splash screen and the same problem.
This is the exact same image I've used previously to revert the device to stock. So I was kinda hoping to see a normal clean. But unfortunately no donut. It reminds me of a computer I once bricked by screwing with its BIOS - it never got beyond POST and so I couldn't reflash it.
Is there something like a BIOS in this thing that could've gotten damaged in some way? And if so, is there any way to use Odin or another tool to fix that?
Cheers,
Daniel
Tried flashing a couple of matching CF kernels. I now get the green battery after the grey one, but still no boot.
All turned out the be the Shun Andromeda kernel re-introducing the hard brick bug. If you have the same issue, see my reply here for links to where you can get the custom PIT trick up and running.
Hello all,
I've encountered a problem with my Straight Talk Galaxy S II S959G after flashing the CWM from this thread:
http://forum.xda-developers.com/showthread.php?t=2559694
I was running 6.0.1.2 or something along those lines. And I was running the 4.2.2 SuperNexus ROM. I can only get to the Samsung Galaxy S II screen and then it goes blank, but does not shut off, as my computer recognizes as being on. However, I cannot DO anything with it even though it can be connected to my computer. Odin v1.85 does not seem to recognize it either.
If someone could help, it would be much appreciated.
It sounds like you just have a soft brick if you're still getting the Samsung logo.
ODIN is intended to be used in download mode. Are you able to get into download mode (hold vol +/vol -, then plug in the USB cable)? If so, you should be able to reflash the kernel, assuming that's what broke. I like to keep an ODIN flashable full stock ROM (minus bootloaders) handy in the event that I mess things up badly.
I don't have experience with the specific ROM you are trying to flash (I was actually planning on playing around with that one soon).
jpasher said:
It sounds like you just have a soft brick if you're still getting the Samsung logo.
ODIN is intended to be used in download mode. Are you able to get into download mode (hold vol +/vol -, then plug in the USB cable)? If so, you should be able to reflash the kernel, assuming that's what broke. I like to keep an ODIN flashable full stock ROM (minus bootloaders) handy in the event that I mess things up badly.
I don't have experience with the specific ROM you are trying to flash (I was actually planning on playing around with that one soon).
Click to expand...
Click to collapse
I'm not very experienced with all of this, but, I have tried Odin mode. My computer does not recognize my phone when it is plugged in.
I do have the stock rom that my phone came with too, but I do not have a Samsung official USB cable to use with it, which, supposedly, is required for this to work. And I do not know if my Odin version on my computer is outdated either.
Epications said:
I'm not very experienced with all of this, but, I have tried Odin mode. My computer does not recognize my phone when it is plugged in.
I do have the stock rom that my phone came with too, but I do not have a Samsung official USB cable to use with it, which, supposedly, is required for this to work. And I do not know if my Odin version on my computer is outdated either.
Click to expand...
Click to collapse
Many usb cables will work just fine. The original cables are known to be of good quality. Odin3 v1.85 is recommended for this phone, although any version of Odin should work.
Did you open Odin on the desktop before putting the phone into download mode? Sometimes the problem is as simple as wrong sequence.
If you have a USB jig, use that to put the phone into download mode. Then connect it to the computer while Odin is open on the desktop.
Make sure you have the correct driver installed. You should have "SAMSUNG USB driver for mobile phones" in your add/remove programs dialog in windows. If not, install it. If so, uninstall it, reboot, reinstall it.
Try different cables, different usb ports, even different pc's.
I'll try not to butt in too much, since creepyncrawly obviously has a lot of experience.
(at this point, I'm assuming you're on Windows)
Like he said, it's sounds like it's most likely a driver issue. When you first plugged in the phone, did you get a Windows balloon notification saying "Installing drivers"? If you open up device manager, do you have any devices with an exclamation point next to them, indicate a device that failed to start? If so, make sure the Samsung drivers are installed.
A USB jig is definitely nice to have handy. I use this one (as long as you can wait a few weeks on shipping). If you can get into download mode, your bootloaders are probably safe (meaning you should be able to recover easily).
I actually installed that CM11 ROM yesterday on my SGH-I777 (I can't say anything specific about your model and how it may differ, but it seems to basically be the same phone as the I777). I was running stock non-rooted JB 4.1 with stock recovery, so I had to take a little more of a convoluted route to get there.
In the end, here's the thread for you. Once you can get ODIN download mode working again, you should be well on your way to fixing it (flash CWM 6.0.4.5 from ODIN, boot into recovery, then try the ROM install again).
Well, I've tried flashing CWM again using Odin. While I actually can USE Odin this time, it just isn't working... My phone still only turns on and goes blank after the Galaxy S II screen.
I had something similar happen the other night when I flashed a kernel that was apparently incompatible with my Captivate (although it should have been fine). The phone would get stuck on the Galaxy S boot screen. I had to reflash a known good kernel to get it working again.
If you can get into the recovery, you can try a wipe/factory reset + wipe cache.
Is ODIN detecting the phone but just failing to flash the files? What error is it getting?
If ODIN is flashing the files properly, but still preventing full boot up, it's probably easiest at this point to flash back to a stock ROM. The previous thread link has the instructions and flash files (I personally have an S2, not an S959G, so it's a slightly different process).
Hi - I don't know if it is a completely outdated method, but this worked on my father's SII skyrocket yesterday when I was encountering a similar softbrick issue:
Get zadig (http://zadig.akeo.ie/), start zadig, get the phone in download mode, hit Options -> List All Devices, select the Samsung or similar device from the dropdown and replace the default USB driver.
Then use heimdall (http://forum.xda-developers.com/showthread.php?t=755265) to flash in a replacement recovery.
Double check that your phone is detected in download mode: heimdall detect
Then flash the recovery: heimdall flash --RECOVERY recovery.img (try CWM for your phone version)
(some places will have you add --no-reboot. that didn't work for me. let it auto reboot)
After it powers down, quickly disconnect the USB cable and put your fingers on the +/- buttons to get into recovery mode. From there push over whichever ROM via adb, etc. etc.
jpasher said:
I had something similar happen the other night when I flashed a kernel that was apparently incompatible with my Captivate (although it should have been fine). The phone would get stuck on the Galaxy S boot screen. I had to reflash a known good kernel to get it working again.
If you can get into the recovery, you can try a wipe/factory reset + wipe cache.
Is ODIN detecting the phone but just failing to flash the files? What error is it getting?
If ODIN is flashing the files properly, but still preventing full boot up, it's probably easiest at this point to flash back to a stock ROM. The previous thread link has the instructions and flash files (I personally have an S2, not an S959G, so it's a slightly different process).
Click to expand...
Click to collapse
It says Odin is successful, but still nothing happens. And I cannot get into recovery no matter how many times I try.
It seems flashing the stock ROM with Odin has worked now, but, now my phone has the tracfone start up animation just looping over and over.
Epications said:
It seems flashing the stock ROM with Odin has worked now, but, now my phone has the tracfone start up animation just looping over and over.
Click to expand...
Click to collapse
Boot into recovery and wipe caches; sometimes you have to do an extra wipe to get out of this type of bootloop.
SteveMurphy said:
Boot into recovery and wipe caches; sometimes you have to do an extra wipe to get out of this type of bootloop.
Click to expand...
Click to collapse
I'm having difficulties booting into recovery.
Epications said:
I'm having difficulties booting into recovery.
Click to expand...
Click to collapse
If you have the stock boot animation you should have recovery. Take the battery out, then put it back in and hold power+volume +/- until you get recovery. I have sometimes had to do this extra step after restoring stock.
Make sure your phone isn't plugged in while you're trying this, btw.
grand quattro CWM TRAPPED
Epications said:
Hello all,
I've encountered a problem with my Straight Talk Galaxy S II S959G after flashing the CWM from this thread:
http://forum.xda-developers.com/showthread.php?t=2559694
I was running 6.0.1.2 or something along those lines. And I was running the 4.2.2 SuperNexus ROM. I can only get to the Samsung Galaxy S II screen and then it goes blank, but does not shut off, as my computer recognizes as being on. However, I cannot DO anything with it even though it can be connected to my computer. Odin v1.85 does not seem to recognize it either.
If someone could help, it would be much appreciated.
Click to expand...
Click to collapse
HI BROOOO I M A GRAND QUATTRO USER EVERYTIME I SWITCH ON MY CELL MY CELL DIRECTLY GOES IN CWM MOD M WORRIED ALOT HELPPPPPPPPPPP ME
Hello,
I have a S3 which is stuck in a bootloop at the samsung logo.
when i turn it on it shows the logo for some seconds then the screen goes black and the logo re-appears.
i can not boot into recovery mode, but download mode is working without a problem every time.
i tried flashing stock firmwares with odin and also tried kies emergency firmware recovery. the flashing always went without any problem, but it had effect. whatever i try, i am never able to boot into recovery and still stuck in the bootloop.
in some tries after flashing the screen just shows the samsung logo forever, but after rebooting it once it then is stuck in a bootloop again (shows the logo - screen goes black - shows the logo...)
i also tried flashing TWRP and CWM via odin, but again i can never boot into recovery mode.
what should i try next?
thx alot for any helpful comment
Varjo said:
Hello,
I have a S3 which is stuck in a bootloop at the samsung logo.
when i turn it on it shows the logo for some seconds then the screen goes black and the logo re-appears.
i can not boot into recovery mode, but download mode is working without a problem every time.
i tried flashing stock firmwares with odin and also tried kies emergency firmware recovery. the flashing always went without any problem, but it had effect. whatever i try, i am never able to boot into recovery and still stuck in the bootloop.
in some tries after flashing the screen just shows the samsung logo forever, but after rebooting it once it then is stuck in a bootloop again (shows the logo - screen goes black - shows the logo...)
i also tried flashing TWRP and CWM via odin, but again i can never boot into recovery mode.
what should i try next?
thx alot for any helpful comment
Click to expand...
Click to collapse
You can Try this:
1.) Pull out battery
2.) Put it in again
3.) Press Vol up + home + power
4.) When the Samsung Logo appears let it off
I think you press the Buttons too long.
I had the same problem!
S1ay3r666 said:
I think you press the Buttons too long.
Click to expand...
Click to collapse
i really tried everything, it's not working. btw with i am stuck at the very first image, where it says "samsung Galaxy sII GT-I9300".
i dont think it's just the way i press the buttons because i can reach it on my s1 and s2 without a problem, it's just not working on this device.
could some setting like "nand erase all" in odin help? in other threads there is sometimes mentioned that the internal file system might be screwed up and in those cases a simple odin reflash does not help anymore...
Nand erase will usually hard brick it. Try the rescue firmware from general forum, sticky thread. Follow the guide exactly as it includes a pit file.
Sent from my GT-I9300 using Tapatalk
boomboomer said:
Try the rescue firmware from general forum, sticky thread. Follow the guide exactly as it includes a pit file.
Click to expand...
Click to collapse
thx, but i already did that (multiple times) and flashing via odin always succeeds. then the phone reboots and is stuck at the first samsung galaxy s.. screen. twice i managed somehow to get into recovery (after flashing cwm6) but it then randomly rebooted.
and i dont think that the power button is stuck because when i am in download mode it is perfectly fine it never reboots itself unexpectedly.
Had a similar issue on my tab2 p3100. It all happened when I tried flashing a custom recovery from rom manager.
A bad flash of anything related to recovery or bootloader could be a probable cause.
I remember a knowledge share on one of the threads describing this issue and as mentioned on it all I had to do is this:
1) switch off the device and plug in the charger. This would light up the display showing you the charging status. The status has to show if at least your bootloader part of the phone is fine.
2) plug out the charger and immediately press the three buttons (home + vol up + power) get into recovery mode. This step has to work and help you get to recovery mode.
***Note : the interval within which this step has to be performed is too short since the display would turn off immediately as soon as you plug out the charger. A bit tricky too so you have to be fast. If this misses getting you into recovery, pull out the battery and put it back again. Repeat step1 and 2 again.
3) upon successfully getting into recovery, perform wipe data, cache and select reboot phone from option available on recovery again.
Allow the device to boot. This could take a while since you have performed a data wipe and may prompt for first time set up.
I was able to restore functionality on my tab after these steps and like ppl learn from their mistakes, I then learnt that recoveries and bootloaders are things that needs to be done with a pc only.
Worth a try if you have tried other alternatives and found no go. may help. Who knows..
all the best.
thats also not working. i tried to get into recovery since two days now...
i also tried the steps from this thread: http://forum.xda-developers.com/galaxy-s3/help/solved-pit-bricked-dead-problem-gt-t2535367
but again, after i flash the cf-root (successfully) the phone does neither boot into recovery by itself nor can i do it by hand...
its crazy... in download mode i can see the model number (GT-I9300) and i thought as long as the model number is there and i can enter download mode there should be a way to recover the device.
but i cannot think of anything to try that i have not done yet
If the rescue firmware didn't help then it looks like the emmc chip is damaged.
Sent from my GT-I9300 using Tapatalk
boomboomer said:
If the rescue firmware didn't help then it looks like the emmc chip is damaged.
Click to expand...
Click to collapse
is there a way to make certain of this? how can i tell if it is really a hardware damage and not just a software brick?
i just dont want to let the phone go, it looks still so shiny
is there anything else that could cause the phone not booting into recovery mode after flashing custom recoveries?
Varjo said:
is there a way to make certain of this? how can i tell if it is really a hardware damage and not just a software brick?
i just dont want to let the phone go, it looks still so shiny
is there anything else that could cause the phone not booting into recovery mode after flashing custom recoveries?
Click to expand...
Click to collapse
http://forum.xda-developers.com/gala...-help-t2737707
Same here, still didn't found how to fix it.. I guess our motherboard just died..
Howewer I have a solution that "almost" worked for me.
Get a stock firmware in odin and turn on Nand erase and T-flash
When it's done phone reboots and you'll see just "Downloading..." mode when you turn it on.
Then got to Kies and Select firmware recovery...
Enter s/n and model name and wait for the flash to complete.
With it , I got past boot logo and actually booted into android but the phone crashed because I guess I have a memory issue..
Well , gl. If you don't find anything else helpful , try going with this method..
I have an S3 GT-I9300 and about a week ago it started refusing to turn on. It was fully charged, and I'd get LED indicators for messages, emails etc, but none of the buttons would switch on the screen, neither would unplugging the cable. The only way to fix it was to remove the battery, and after removing it one time, it refused to boot, sticking at the Samsung logo screen. Recovery mode wouldn't work, I tried resetting to factory settings, and wiping the phone, but it kept sticking (I think at cache), and wouldn't boot whatever I did.
I tried to update the firmware through Kies, which just froze at 94% every time. I also tried Odin, which again froze about the same point. So I tried following this guide, but when the phone restarted it tried looking for files on an SD card (which I don't have), so no luck. I tried repartitioning, but it keeps failing and if I try to flash the phone it now fails with "there is no PIT partition". I can't remember at which point it started happening, but although I can still get into download mode, switching the phone on any other way gives me a glitched screen something like this.
Is there any way at all to fix this phone at this point?
@edwards87: I'm confused about your description: no recovery mode, but factory reset? A root tool for rescue?
If you can boot into download mode, download actual firmware and Odin from sammobile.com (all new, delete old stuff) and try to flash it.
rp158 said:
@edwards87: I'm confused about your description: no recovery mode, but factory reset? A root tool for rescue?
If you can boot into download mode, download actual firmware and Odin from sammobile.com (all new, delete old stuff) and try to flash it.
Click to expand...
Click to collapse
I can get into download mode (power + home + vol down), but can no longer get into recovery mode (power + home + vol up). When I could get into recovery mode right at the start, none of the recovery options did anything because it said there were missing files or directories.
I've tried several firmwares from sammobile through different versions of Odin and they all froze at the same place towards the end. Now none of them go anywhere because there's no PIT partition.
Then my next step would be a 3part-firmware +PIT-file.
rp158 said:
Then my next step would be a 3part-firmware +PIT-file.
Click to expand...
Click to collapse
Finally found a 3-part firmware but I get the same problem - repartition operation failed.
@edwards87: sounds like broken internal storage. Can't help you, sorry.
I need a pit file for galaxy s3 i9300 16GB please help me
Hello a few days i restored my galaxy to factory settings from inside the own phone settings everything was working fine until a couple days ago the phone started to rebooting every now and then
Right now is stuck on the samsung logo after you turn it on and in the recovery menu i got this error
E: failed to mount /efs (invalid argument)
I try to wipe the cache date and even doing a wipe from the recovery menu but nothing when the phone turn on and gets to the samsung logo it stays there a while and reboots again
I try doing this instructions from this post from another forum
The key for me was selecting the second item in the Tools menu (Firmware Upgrade and Initialisation?) - it seemed to bypass that whole 'connecting' process and just went to work. Here's the writeup that I put together (I need to insert the Kies screenshots that I captured).
- if you don't already have the Kies software installed on your PC, download it (just search Google) and install it. The first time it runs it'll update itself to the latest version so make sure you run it once before proceeding.
- put your phone in Download mode: with the phone completely off, press and hold the Volume Down and Home and Power buttons simultaneously, and release them all when you see the Samsung splash screen
- connect the phone to your PC with the USB cable that came with the phone
-- if you've never had the phone connected to your Windows-based computer before, you'll see messages about installing drivers, etc - just wait until this is done (may take 5 or 10 minutes) [I don't know what happens if you have a Mac - it probably just works]
- in the Kies software, select the second item in the Tools menu and just follow the prompts to enter the model number (in CAPS) and IMEI/Serial Number (both found under the battery - it's ok to remove the battery at this point)
- the Kies software should start downloading the correct firmware for your phone from the Internet; once that's done (depending on your Internet connection speed) it'll begin downloading that to the phone (this probably takes 10 minutes or so)
Click to expand...
Click to collapse
I manage to do all the steps but nothing now the phone turns on and it gets stuck on the samsung logo but this time it doesn't reboot it just stays there and in the recovery menu still have the same error
Does anyone have any solucion or a guide that explaings well how can i fix this?
I have seen other guides that saids i need to either root the phone and install a custom recovery menu but since the phone doesn't boot i have no clue how to do this
Edit: A few moments ago i tried doing this as well (i cant post the complete youtube link)
watch?v=xJMJLdzHaAY
The phone now turn on but i have a black box with some yellow letters i'm guessing is the called safe mode is there anything i can do from here?
Been honest i'm completely lost here
Can someone please give a valid link to download?
Edit: Sorry, wrong post.
You can try flashing a recovery (cwm official is best) via odin but most likely you'll need to flash a stock rom, definitely if the cwm flash doesn't solve it.
Beamed in by telepathy.
shivadow said:
You can try flashing a recovery (cwm official is best) via odin but most likely you'll need to flash a stock rom, definitely if the cwm flash doesn't solve it.
Beamed in by telepathy.
Click to expand...
Click to collapse
is there any tutorial on how to that for the I9300? because i to be honest without a tutorial i dont have a clue on how to start doing this, i will actually prefer a stock rom is by stock rom is a official firmware from samsung