Related
Hello,
I've been having a nightmare with my Galaxy S2 GT-I9100. The phone had been giving me grief for a few months, the occasional freeze which would be fixed by a battery pull, ever since upgrading to an official ICS rom. Unfortunately I can't remember the exact ROM.
A week ago the phone froze, I pulled the battery and hit a bootloop when I tried to restart. I booted into recovery mode and attempted to wipe data. The phone attempted to wipe the data but froze. I left it for a couple of hours with no progress so I pulled the battery. The phone is now still in the same bootloop but cannot enter recovery mode. It can however enter download mode through both the 3 button technique and using a USB jig. My PC only recognises the phone in download mode and fortunately ODIN also recognises the phone. I have tried flashing various stock firmware and kernels and each time ODIN claims the flash was successful, reboots the phone and hits the same bootloop as before. I have also tried flashing CWM recovery to try and boot into that recovery mode but again this is successful but seems to make no difference.
Any help would be much appreciated,
Thanks for your time.
UPDATE:
This is the guide I used to first fix the problem http://forum.xda-developers.com/showthread.php?t=1457458&highlight=recovery+mode
Adding the most recent flashed ROM and kernel
ROM: http://forum.xda-developers.com/showthread.php?t=1608071 - Firmware: I9100XWLPY (4.0.4) (Unbranded UK)
Kernel: http://forum.xda-developers.com/showthread.php?t=1103399 - CF-Root-SGS2_XW_NEE_LPY-v5.6-CWM5.zip
Shilleto said:
Hello,
I've been having a nightmare with my Galaxy S2 GT-I9100. The phone had been giving me grief for a few months, the occasional freeze which would be fixed by a battery pull, ever since upgrading to an official ICS rom. Unfortunately I can't remember the exact ROM.
A week ago the phone froze, I pulled the battery and hit a bootloop when I tried to restart. I booted into recovery mode and attempted to wipe data. The phone attempted to wipe the data but froze. I left it for a couple of hours with no progress so I pulled the battery. The phone is now still in the same bootloop but cannot enter recovery mode. It can however enter download mode through both the 3 button technique and using a USB jig. My PC only recognises the phone in download mode and fortunately ODIN also recognises the phone. I have tried flashing various stock firmware and kernels and each time ODIN claims the flash was successful, reboots the phone and hits the same bootloop as before. I have also tried flashing CWM recovery to try and boot into that recovery mode but again this is successful but seems to make no difference.
Any help would be much appreciated,
Thanks for your time.
UPDATE:
This is the guide I used to first fix the problem http://forum.xda-developers.com/showthread.php?t=1457458&highlight=recovery+mode
Adding the most recent flashed ROM and kernel
ROM: http://forum.xda-developers.com/showthread.php?t=1608071 - Firmware: I9100XWLPY (4.0.4) (Unbranded UK)
Kernel: http://forum.xda-developers.com/showthread.php?t=1103399 - CF-Root-SGS2_XW_NEE_LPY-v5.6-CWM5.zip
Click to expand...
Click to collapse
Hmm ... for bootloop issues, this is the correct guide => http://forum.xda-developers.com/showthread.php?t=1108499
But this requires recovery mode to work.
And you really pressed Volume UP + Home + Power keys, and hold them for about 15 seconds/until recovery menu appears - regardless of any other boot logo or animation which might be displayed inbetween?!
It_ler said:
Hmm ... for bootloop issues, this is the correct guide => http://forum.xda-developers.com/showthread.php?t=1108499
But this requires recovery mode to work.
And you really pressed Volume UP + Home + Power keys, and hold them for about 15 seconds/until recovery menu appears - regardless of any other boot logo or animation which might be displayed inbetween?!
Click to expand...
Click to collapse
Definitely. Booting with Volume UP + Home + Power keys, I am greeted with my usual bootloop Samsung Galaxy SII GT-I9100 boot screen, after around 10 seconds the screen goes black and then the bootloop screen comes back on.
Any other suggestions?
Same problem
Hi,
I have the same problem. I would be interested in a solution for this as well. I've already tried reflashing the ROM, kernel and bootloader, together with repartitioning. Still can't get into recovery mode.
Cheers,
Tudor
need Help
help, I have the exactly same problem, please solve this, I already flash everything, but it no use..
yyanzzz said:
help, I have the exactly same problem, please solve this, I already flash everything, but it no use..
Click to expand...
Click to collapse
Hi,
What I finally managed to do is connect to ADB and do a wipe from there. Connecting to ADB in download mode sometimes works and sometimes doesn't, depends on how lucky you are. Try it a couple of times. Afterwards I was able to re-flash and it started. For me, the problem was also a bit deeper; my USB port was shortcircuiting or something. I just took a toothpick and pushed the USB pin a bit (found the idea online) and haven't had any problems since then.
Cheers,
Tudor
I have flashed a CWM Recovery via odin because my Galaxy S3 was in a boot-loop and I couldn't acces the recovery. After I flashed the recovery (recovery-cwmtouch-6.0.3.2-GTI9300.tar) I flashed the ROM via recovery( Slim-i9300-4.3.build.2.2-OFFICIAL-) After the ROM starts for some weird reason my touchscreen doesnt work. The lock button etc works fine and so do the soft-touch buttons. Also when I press the homebutton a few times it re-boots automaticall
See multiple identical posts
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..
UPDATE: I got stock firmware flashed on it, but as soon as it finished, it just stuck in the Samsung Galaxy S6 Edge boot screen, and it won't even allow me to access recovery mode so I can wipe cache and whatnot. I'm running out of patience with this brick of a phone. It just goes straight to the same boot screen, not allowing me to get to the recovery mode. Are there any alternative ways to enter recovery mode, or alternative ways to wipe cache and partition? Please, any advice is welcomed.
Thanks in advance.
Try different odin version and cable before you messing with pit.
Sent from my SM-N920C
I had tried using three different versions of Odin, 3.07, 3.09, 3.106. I also used multiple cords and multiple versions of stock roms. And still, no success. It won't even stay off, every time it juices up, or is plugged in, it goes straight to the Samsung Galaxy S6 Edge boot screen and stays there.
Mind you, I am not too familiar with anything outside of stock roms, some custom roms and rooting. Have not tested out much more than that. Any noob-friendly advice would be welcomed.
I had nand write start error once during downgrading my s6 from 6.0.1 to 5.1.1. I just tried odin 3.10 and it got flashed successfully. I was lucky then.
Sent from my SM-N920C
Well, I finally got one of the firmwares to work, it ran through Odin and everything just fine, but after it was done, it basically did the same thing, it stayed on the Samsung black screen, except without the red writing at the top..
Sent from my SM-N910W8 using XDA-Developers mobile app
Enter recovery and factory reset
Sent from my SM-N920C
I can't access recovery, the phone won't turn off, so as soon as it has any source of battery life, it just goes straight to the samsung boot screen and stays there.
Hold vol down+power button for 15-20sec. As soon as it reboot, hold vol up+power+home button to enter recovery.
Sent from my SM-N920C
I've tried that at least 50-ish times now, It just does not work, I tried it with a second or two delay, I tried it immediately after screen turns off, tried it so many times. No matter how long I hold them down for, it just stays at the boot screen. I can get to download mode just fine, but for some reason recovery seems to not be working.
is it a bootloop (it keeps restarting or it is frozen on samsung logo) ?
if bootloop you can try: plug in power corde. press and hold both volume buttons + home + power untill it shuts down. unplug power corde. press and hold home volume down and power for download mode. get another rom and flash it.
Hi i am having exactly the same problem can boot to download but not recovery, let the phone run out of battery and as soon as you plug it in again bootloop, i was running crisscross marshmallow rom ,custom kernel i have a backup but am not sure what or how to flash correctly in Odin any help would be much appreciated thanks .
Edit flashed firmware from sammobiles worked a treat .
Any updates on this?
I have this exact problem however I never attempted rooting my phone or changing anything on the firmware, I was on YouTube when my s6 edge crashed then entered boot loop, I CANNOT ACCESS recovery mode ,but I can access Odin mode. WTF everything is stock on my phone, never even heard of 'bootloop, Odin mode' before this happened .or even had to access my recovery mode on my s6. As I search the web for help I find solutions that require recovery mode, but I can access it. Apparently bootloop happens when people try to root but I never tired that. I don't even know what that is!
This just happened to my S6. Was watching YouTube then it crashed and entered a boot loop, can't access recovery, only download mode.
MarkWCAU said:
This just happened to my S6. Was watching YouTube then it crashed and entered a boot loop, can't access recovery, only download mode.
Click to expand...
Click to collapse
Flash stock firmware
Hi Community,
I read some posts how to fix my Problem, but i cant go to a service Point.
So I was using the Evolution X for a long Time (Installed with TWRP 3.1.0).
And now i wanted to change to the Nusantara Project (Vanilla), I did a clean Flash, everything worked i could access the System.
Than i had problems installing Play Store, so i rebooted into Recovery via the System. But now im Stuck in the Loop.
Can i Somehow connect my Phone to the PC and Reset?
Can someone tell me if i Hard/soft bricked my phone ?
Just a little advice, would be really appreciated.
Thanks a lot
Go to TWRP, wipe system, cache, data and dalvik. Now flash nusantra and whichever GApps are recommended for it (if there are no recommendations then use OpenGApps, make sure the architecture is correct). Now wipe dalvik and restart. Sometimes, certain roms begin to bootloop if you boot into the rom first, then try to install gapps later.
If you still have issues, just reflash the stock rom.
I cant access the TWRP anymore, im just stuck on the Bootloader, no matter how i turn on The Phone (Volume Up + Power ON ), (Volume Down + Power), (All 3 Buttons)
Nothing works anymore i dont understand ....
Im searching the net but i cant go to fastboot or something else, its just keeps on rebooting ...
So it's bootlooping, but you cant access recovery?
When the screen turns off, press the key combo and it should go to recovery.
Your best bet is to take it to a service centre, but if that really isn't possible for you, then wait for its battery to drain completely, then when you plug in the charger, instead of turning the phone on, press the key combo to enter the recovery. From there, wipe and flash some other OS.
I've also heard that certain versions of TWRP don't support some roms, leading to a bootloop. In that case, you'll have to use orangefox recovery to flash the rom (orangefox is flashable via twrp)
Yes its Bootlooping.
When i turn it on, on the Left Corner "Recovery Mode" blinks for one second. Than the usual Text appears:
"Orange State
Your Device has been unlocked and cant be trusted
Your Device will boot in 5 Seconds".
So after a couple of seconds (around 10-20 sec)
It turns off and immediately on again. I Just can turn it OFF when i hold all 3 Buttons.
Than i try starting it with Volume up + Power / Volume down + Power, But i cant access Recovery or TWRP.
So i should wait til the battery gets low and try it again ?
Like i said, my custom Rom (Evolutionx) and TWRP just worked fine. I dont know man ...
Well since your bootloader is unlocked, try flashing the stock rom again. Look for a tutorial and follow it.
Hi I managed to unbrick my device with this guide, and im back on a stock rom
Unbrick
i ran following commands to get to my custom rom:
I run adb reboot bootloader,
add executed following commands.
(Pitch Black recovery 3.1)
- adb reboot bootloader
- fastboot flash recovery recovery.img
-fasboot reboot recovery
It just hang up and booted after a while into the normal system.
But im not able to get to the recovery menu ?
When I restart and hold Volume up + Power, i go in a loop and the phone keeps restarting over and over again.
what have i Fu**ed up ?
Do i need another recovery tool ?
sorry guys, i appreciate your help a lot tho !
EDIT: Is my bootloader unlocked ?
I can access via "adb reboot bootloader" the phone
and on the blackscreen on the phone it is written:
oppo verfiy pass
fastboot_unlock_verify ok
Update:
So i tried some Stuff and i got Red State. No Problem i Unbricked it once again and now im on Stock Android 10.
Now im Trying to enable the bootloader again.
I downloaded the In Depth Test_Realme_6.apk but i keep getting the Error that i should update the system.
So should i update the system ?
I cant find a CURRENT Tutorial to make this work, please help...
If you cant find a tutorial for your version, why not downgrade back to a previous one if possible.