Odin Bootloop (firmware update encountered an error) - Galaxy S III Mini Q&A, Help & Troubleshooting

A failed rom flash lead to the phone only turning on for like 2 seconds on the firmware update encountered an error screen.
I can't enter download or recovery mode, if I plug it into a wall it'll stay on for like 15 seconds but I still can't enter download mode or recovery mode.
If I plug it into my pc it stays on for 2 seconds.
Phone wont boot without being plugged in.

Related

[Q] Galaxy Tab GT 1000N won't start

Day 1
Hard reset my device. After rebooting, my tab stuck at Samsung logo and vibrating. But still can enter download mode
Day 2
The device still stuck at Samsung logo and can enter download mode. Then i tried flashing with dbdata.rfs PDA via Odin to try my luck. After reboot , the same things goes up,stuck at Samsung logo. After few minute , i tried flashing the GT-P1000_PRT_P1000XWJQ9_P1000PRTKL1_P1000XXJPZ ROM.During flashing(i don't know either it's finish already or not or either battery problem.Before flash i noticed the battery has low power about less than 10%) ,the device suddenly shutdown by it self. After the shutdown, the device goes black and try to reboot again,nothing comes up.Then i thought the battery was fully drained out, then i decide to charge up till morning.
Day 3
Trying to power up the device but nothing happen.Holding the power button about 20 sec and nothing happen but the device feel a little bit hot at the back.But when i plugged in to USB, it can detect the device and show the MTP Installation has failed.But at My computer shows 2 removable disk which comes from the device it self.After i pressed it,it say Please insert a disk to removable disk.
Can anyone please help me?Help my Old Tab.
Sounds like you have bricked your device. And I mean a real brick, not a "soft brick" as some people like to call it.
You should never try and flash your device if you have low battery as power could fail and corrupt your bootloader.
If you cant get into recovery or download mode your screwed and need to send it away for JTAG fix or board replacement.
Zelz said:
Day 1
Hard reset my device. After rebooting, my tab stuck at Samsung logo and vibrating. But still can enter download mode
Day 2
The device still stuck at Samsung logo and can enter download mode. Then i tried flashing with dbdata.rfs PDA via Odin to try my luck. After reboot , the same things goes up,stuck at Samsung logo. After few minute , i tried flashing the GT-P1000_PRT_P1000XWJQ9_P1000PRTKL1_P1000XXJPZ ROM.During flashing(i don't know either it's finish already or not or either battery problem.Before flash i noticed the battery has low power about less than 10%) ,the device suddenly shutdown by it self. After the shutdown, the device goes black and try to reboot again,nothing comes up.Then i thought the battery was fully drained out, then i decide to charge up till morning.
Day 3
Trying to power up the device but nothing happen.Holding the power button about 20 sec and nothing happen but the device feel a little bit hot at the back.But when i plugged in to USB, it can detect the device and show the MTP Installation has failed.But at My computer shows 2 removable disk which comes from the device it self.After i pressed it,it say Please insert a disk to removable disk.
Can anyone please help me?Help my Old Tab.
Click to expand...
Click to collapse
Try this:
start odin, and press power + volume down for at least 5 seconds, plug to your computer
Odin should recognize your tab. Flash again. Btw jq8, sithout the correct kernel is not for p1000n/m/l.
What u did on day 3 was ALMOST right. But you didn't press the volume down. Hence you didn't go to download mode.
P.s. if you post this in the Q&Asection, we could hv helped you earlier.

Darky 10.2 stuck in bootloop, can't go into recovery, download mode stays for 5 secon

Hi,
Title pretty much says it all. My phone all of a sudden just went into a bootloop, I can't go intro recovery to reflash it and i cant even get into download mode to resurrect it since it it will stay on only for a few seconds. Odin does not recognize the device even with samsung drivers installed and i used a few different usb ports and a different computer.
Is there something i can do? seems like the last days of the device...
Try this
-remove battery
-enter download mode(volume down+home key+power button)
-while in this position, insert the battery
See if it enters download mode and odin recognizes.
If this doesn't work, try USB jig.

Stuck in bootloop, I can't enter in download mode.

Hi
I have a Samsung Galaxy A30, SM-A305G.
I updated Magisk by the app, and when restarted it showed me "Error Validating footer", in the download mode, and it wouldn't let me start.
So I download for the firmware, and just flashed the AP file, the problem started when it rebooted and the bootloader warning appeared to me, then it showed me the Samsung logo and it reboots in an infinite loop. I can't enter into the download mode with Vol +, Vol - and connect the USB. I disconnected the battery and trying, but I could not enter the Download mode either. Also, the computer does not recognize the device. Some help?
Try to go into recovery mode by holding power + volume up
There, you can reboot into bootloader.
If you can turn off your phone then press togethet vol up and vol down and while holding it insert the usb cable in the phone and it will shows the download mode.
itsluquis said:
Hi
I have a Samsung Galaxy A30, SM-A305G.
I updated Magisk by the app, and when restarted it showed me "Error Validating footer", in the download mode, and it wouldn't let me start.
So I download for the firmware, and just flashed the AP file, the problem started when it rebooted and the bootloader warning appeared to me, then it showed me the Samsung logo and it reboots in an infinite loop. I can't enter into the download mode with Vol +, Vol - and connect the USB. I disconnected the battery and trying, but I could not enter the Download mode either. Also, the computer does not recognize the device. Some help?
Click to expand...
Click to collapse
Did you find a fix?
i have exactly the same problem and the thing is that yiu cant disconnect the battery because it is nun removable one so at this stage the only thing i can do is sit and wait for the battery to die one day because it was at 78% when i started the rroot and this the second day
did you find a fix coz have the exact problem but mine can enter recovery mode from there I cant boot into bootloader or fastboot
i have the same problem. the phone boot on download mode, but autoreboot after some seconds. i doesn't have time to install a stock rom
My problem was the battery. After charge a lot, all thing works fine.

A305F/DS bootloop at bootlogo

My boy was having problems with the phone restarting randomly we got phone to check if there was an update and after it downloaded and began to install restarted and got stuck in the bootloop. I put in recovery mode it begins to try update fails at 28%. Pressing power+vol up shows an error. Pls educate me
try to boot into download mode (- and + volume and connect to pc when phone reboot) then flash latest stock ROM.
Thanks already done had to flash csc, instead of home csc to get it to complete and boot

M21 logo loop, can't access recovery

My mum tried to do the last update on her phone, during which most probably battery ran out - now phone is basically a brick.
When turned on it's stuck on logo loop, rebooting itself every 5-10 seconds or so vibrating once and repeating. When unplugged or plugged into the wall none of the button combinations work - the phone basically ignores everything.
When plugged to PC via USB I can invoke "updating process"? with Volume Up + Power / Volume Up combination, which should lead me to recovery menu - instead the phone goes into "update", loads bar up to 25%, gets stuck for about a minute or so, reboots and goes into logo loop.
Hard reset also "works" when plugged into PC - update screen shows up, gets stuck on 1%, phone gets hard rebooted, update comes up again, goes up to 25%, reboots and on to the logo loop...
Can I even somehow get into recovery mode to wipe cache to allow the phone to get update again or even wipe data to flash custom ROM? Screw data, I just want to make it work and not have a brick lying on the desk...
UnableToSee said:
My mum tried to do the last update on her phone, during which most probably battery ran out - now phone is basically a brick.
When turned on it's stuck on logo loop, rebooting itself every 5-10 seconds or so vibrating once and repeating. When unplugged or plugged into the wall none of the button combinations work - the phone basically ignores everything.
When plugged to PC via USB I can invoke "updating process"? with Volume Up + Power / Volume Up combination, which should lead me to recovery menu - instead the phone goes into "update", loads bar up to 25%, gets stuck for about a minute or so, reboots and goes into logo loop.
Hard reset also "works" when plugged into PC - update screen shows up, gets stuck on 1%, phone gets hard rebooted, update comes up again, goes up to 25%, reboots and on to the logo loop...
Can I even somehow get into recovery mode to wipe cache to allow the phone to get update again or even wipe data to flash custom ROM? Screw data, I just want to make it work and not have a brick lying on the desk...
Click to expand...
Click to collapse
Have you tried using reiboot-for-android.exe by Tenorshare Co Ltd? Might help. Or if the device is within warranty then try Service Centers for that device.
You can try flashing stock rom from odin.
Download your current stock rom from samfw.com and extract the zip file.
Install odin and samsung usb drivers (link) and reboot your pc.
Reboot into download mode from your phone and press volume up:
Keep USB connected, Hold Volume Down and Power buttons, When screen turns off, hold Volume Up and Volume Down buttons
Click to expand...
Click to collapse
Open odin and load the files:
AP = AP*.tar.md5, BL = BL*.tar.md5, CP = CP*.tar.md5, CSC = CSC*.tar.md5
Click to expand...
Click to collapse
Click flash and wait till it says pass
Press and hold volume down and power to reboot. The first boot can take a while. Hopefully this will fix it.

Categories

Resources