After running out of battery, I'm not able to get my phone up since battery was fully recharged. All I see is the Samsung boot logo which will stay there. The TWRP recovery system remains fully accessible.
I was running ArchiDroid before, now here's the history of things I have tried so far:
1. Removed battery for a while, replugged.
2. Wiped, formatted and reflashed same and different ROM (ArchiDroid again and ParanoidAndroid) with TWRP. No error during flashing.
Still no event after the Samsung boot logo.
Any advice?
Try the rescue firmware & pit, search general forum.
boomboomer said:
Try the rescue firmware & pit, search general forum.
Click to expand...
Click to collapse
Thanks for that idea. I've done so and am now not anymore on the first (Galaxy GT-I9300) boot logo. Now the melody with the fading SAMSUNG logo comes up but doesn't disappear, even after ~2h. Do I have to be afraid that there is a hardware failure?
Boot into recovery and factory reset, or flash stock firmware for your country first.
Look for any errors in recovery.
Related
i just woke up to find my galaxy s3 dead.
i tried to power it on, to have the "galaxy s3 i9300" logo starts to blink in a continuous way and no matter what i do the blinking continues in an infinite loop, till i remove the battery and power it on again and same loop of logo blinking again
i did access recovery, change recovery--> same loop
i did install original firmware through download mode that i can also access (via Oddin) --> same loop
i tried to install original firmware by different components methods (via Oddin) but IT FAILED.
i tried philz touch 4 recovery and it works like a charm with back up and restore -> same loop
so, what is the problem and how can i turn around it.
factory reset
Glebun said:
factory reset
Click to expand...
Click to collapse
done, but same blinking bootloop
boot to recovery
wipe data, cache and dalvik
reboot to download mode
flash stock rom.
i might be wrong, but worth a try.
magma2000 said:
done, but same blinking bootloop
Click to expand...
Click to collapse
Superwipe ... put factory rom on there odin and start from scratcg to root then unlock bootloader then flash happy.
Sent From *SynergyRom
It's sds mate get in touch with your provider and they should replace mainboard for you
stupidly will be met by sarcasm
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've flashed Archidroid 3.0.1 with Boeffla kernel 2.1
The phone worked well for a day (except i had huge battery drain by google services, and it wasn't because of location settings, but that's another story) and suddenly all by it self it entered in bootloop showing only "Samsung Galaxy SIII GT-I9300" message, and the main problem is that I can't enter the recovery.
I do the three button combination, and it shows CWM recovery 6.0.4.4 for a part of a second and the phone boots again before I can even read anything. Also I've tried to pull out the battery and leave it like that for an hour, and when I put it back in phone the phone powers on by itself and enters the bootloop.
Any suggestions?
Flash stock firmware with Odin, factory reset.
boomboomer said:
Flash stock firmware with Odin, factory reset.
Click to expand...
Click to collapse
I presume that should be XELLA or newer stock ROM?
EMG4 or higher, to avoid efs problems.
boomboomer said:
EMG4 or higher, to avoid efs problems.
Click to expand...
Click to collapse
It didn't help since I can be in download mode for only about second or so, so I wasn't able to do anything with Odin.
I gave it to the service because it could only be the stucked power button or emmc chip gone bad, I would try to replace the power button myself but I don't have solder. However I will keep you posted what exactly went wrong with it.
Hi,
Am new to XDA- Forums so please pardon me if am not clear in my questions/queries.
Issue:
I am using Samsung Galaxy S3 I9300 , few days back it suddenly went into bootloop( every time i switch on the device it starts upto Samsung logo and re-starts the same process again and again).
Details:
OS : 4.3.3 Jelly Bean
Observations:
Recovery mode is not available - it only shows an android icon with an exclamatory mark and a caption 'No Command'.
Resolutions tried:
1) Tried flashing the ROM with Official stock Rom but all practices in vain.
Possible reasons:
Is the device soft bricked. or is it a power button shot which causes it to boot loop.
Kindly assist me. Thanks in Advance
vaibhavS3x2011 said:
Hi,
Am new to XDA- Forums so please pardon me if am not clear in my questions/queries.
Issue:
I am using Samsung Galaxy S3 I9300 , few days back it suddenly went into bootloop( every time i switch on the device it starts upto Samsung logo and re-starts the same process again and again).
Details:
OS : 4.3.3 Jelly Bean
Observations:
Recovery mode is not available - it only shows an android icon with an exclamatory mark and a caption 'No Command'.
Resolutions tried:
1) Tried flashing the ROM with Official stock Rom but all practices in vain.
Possible reasons:
Is the device soft bricked. or is it a power button shot which causes it to boot loop.
Kindly assist me. Thanks in Advance
Click to expand...
Click to collapse
does the phone boot in download mode?
power, home and volume down?
sosolid4u09 said:
does the phone boot in download mode?
power, home and volume down?
Click to expand...
Click to collapse
Yes.. it goes in download mode.
Flash a full stock firmware, the latest for your country, using Odin then factory reset.
If that works then all is well, but you might find Odin fails to flash due to nand memory damage/wear.
Hi,
Thanks to all for your valuable time and suggestions.
Currently my device is started and is working. But there are hick-up's which needs some clarifications.
Below steps were performed:
1) Initially I did not use to get recovery option from where i was not able to wipe data, so after researching a bit i found a suggestion to apply re-partition. So i used 'GT-I9300_mx_20120329_100%.pit' file and started the re-partition. All went fine but in Odin during re-partition it was stuck at a statement 'NAND write start' for about more then 30 minutes. So i was worried n unplugged the device in between. Fortunately after restart, it went into recovery mode and i applied wipe data factory reset.
2) Still the device got stuck in some weird screen called 'installier der anderden'. But now no bootloop (an affirmative sign :laugh.
3)Today i installed the official stock rom of samsung galaxy s3 for india and now its working. But the hick- up is
it restarts/ hangs or it shows Unfortunately so n so app has stopped.
Need guidance on below points:
1)Should i re-partition again using the .pit file. (now i will re-partition using 'SG3 16GB White.pit' got a link for this from xda forum).
2) After re-partition, installation of stock rom.
Thanks in advance.
Flash stock firmware and pit at the same time, then factory reset afterward.
If the phone still freezes or restarts after this then nand memory is worn, for which there is no cure.
Unfortunately every google app stops after some time.
Any solution/recommendations..
Should i apply re-partition and again apply an official stock rom ..
This is the problem I am having with my Samsung Galaxy Note 3 (SM-N900P). This problem just popped up out of the blue on a stock ROM a few days ago and nothing I have tried has gotten close to fixing the issue
Description:
a) The boot sequence repeats in a loop with no more sound. The phone would reboot at the Sprint splash screen
What I've done so far:
a) Pulled the battery and depleted the capacitors
b) Installed TWRP and did a complete wipe
c) Tried installing a custom ROM to see if the issue persisted. ROMs failed to install as /system was being sketchy (at times it was reporting 0MB for partition and then an actual value after repair). When I managed to get a ROM to install still stuck in the boot loop
d) Used Odin to do a full restore to a stock NC5 ROM. The phone got up to initial configuration page and then rebooted, now only gets to the Samsung splash screen before rebooting
Items that I can get into:
Recovery mode
Download mode
I have a 30 second video of it rebooting but cannot post it currently due to the forum rules
Question:
Is this issue fixable or is it a sign of internal memory failure?
Try an older version of TWRP, i.e. 2.8.5.0
Or, try a different recovery.
I'm not sure that it will work, but it's worth a try.
Good luck!
Are you doing it this way?
http://forum.xda-developers.com/showthread.php?t=3069667
rbeavers said:
Are you doing it this way?
http://forum.xda-developers.com/showthread.php?t=3069667
Click to expand...
Click to collapse
I didn't notice that but I just installed TWRP 2.8.0.0 through Odin (like a few minutes ago). Phone actually managed to get to the stock recovery image config screen and was working as long as the cable was still attached to the computer.
As soon as I removed the cable it went straight back to the boot loop
SubRyan said:
I didn't notice that but I just installed TWRP 2.8.0.0 through Odin (like a few minutes ago). Phone actually managed to get to the stock recovery image config screen and was working as long as the cable was still attached to the computer.
As soon as I removed the cable it went straight back to the boot loop
Click to expand...
Click to collapse
Here is what you need to do. First pull battery, reinstall. If you can boot into twrp recovery, fine wipe everything i.e. caches, system, data, etc. If you are on a stock recovery do a factory reset. Pull battery, reinstall and boot into download mode.
NOW let's go to work. First use odin to flash stock NC5 tar. Chances are it will bootloop, STOP !!!! don't panic. Just reflash with odin again. The second time it should take. Remember that your device is setting up for first time use. This will take 3-5 minutes, sitting at the Samsung logo. Since didn't list the most important thing which is what OS you where on where the device Borked, or what you where doing with the device when it Borked. I'm going to assume it was on 4.4.4 and you tried to downgrade to 4.4.2 NC5. In which case a bootloop on the first bootup after a downgrade is normal, you have to flash twice to reset the bootloader. For more info click on rom flashing basics in my signature. Enjoy !!!
Problem solved. I started getting suspicious when the phone would boot up with the charging cable attached to the computer today
The issue was an aftermarket Mugen Power battery that developed a fault. Put the stock battery back in and problem resolved
Thanks for the help guys