Hi,
My problem started a couple days ago. I had my Samsung Galaxy S2 (I9100) charging overnight and when I woke up it was off. When I turned it back on it was stuck in a boot loop. I could not access recovery mode (although it would enter recovery mode and then drop out) but I could enter download mode. It was running a stock ROM and I had never played around with flashing before.
After leaving it for about a day without power nothing had changed so I started reading up about recovering from soft-brick and possibly the NAND read-write corruption at the guide on XDA here http://forum.xda-developers.com/galaxy-s2/general/guide-fix-unflashable-soft-bricked-gsii-t1449771
The guide is a bit old now so some links are broken which made it more difficult for me to figure out what I had to do. Particularly with what file should be going where.
I ended up downloading the same ROM that i think was already on my phone from samfirmware and tried to flash it using Odin (various versions) without success. I tried to flash just the kernel using heimdall which now stops me from even entering recovery mode. I tried to flash everything in the ROM from samfirmware using heimdall but it got stuck on the second file (cache) at 62%, the first file was the bootloader which it said was successful. However now I don’t even get the Samsung logo anymore. I only get "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
I still have download mode so I have hope.
I haven’t tried repartitioning yet, is that my next step? Can someone give me instructions on how to determine what the problem is and what I should or shouldn’t be flashing? I’m not against going to a completely new ROM like cyanogen mod either. I need some help from people who have more experience with this.
Thanks for your help, I should be around to answer questions.
Same thing happened to me
Hi, almost the same thing happened to me - except that I was running Cyanogenmod 10 custom rom and I'm not being able to go into recovery mode, but I can go into download mode.
So far I've only managed to worsen things while trying to use odin to write a recovery kernel, so I had a bad firmware upgrade and now instead of powering up to Samsung logo it goes into the "Firmware upgrade encountered an issue" screen. But I'm still able to boot into download mode.
Did you manage to fix your phone? If so, how did you do it?
Related
[Q] Firmware upgrade encountered an issue. Please select recovery mode in Kies..."
Originally my phone stopped working hours ago, applications were forced closed and i decided to force-shutdown my s2. Then i realised i could only enter recovery & download mode. I remembered setting my clock faster for -in game tokens per day- and i thought that was the problem. BUT i couldn't boot my phone. Saw videos on clockwork MOD and i tried with OBIN, but unexpectedly, it failed. As it failed, i couldn't do anything else so i removed USB and tried REBOOTING my phone. However, "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again" came up. I can't enter recovery mode now but only download mode. I've installed Kies on my computer but to no avail. Kies gave me error when i attempted to restore the mods settings using "Firmware upgrade and initialisation" and error was in korean so i did not understand. People stated that there are other ways using stock kernel but i can't obtain my stock kernel of my device as i couldn't even boot it up, let alone going into my phone's setting to check the stock kernel.
Any help? It seemed that i should've done a recovery instead of toying with OBIN and resulting in this. ANY WAYS TO UNDO THE FAILED OBIN MOD? Please, i would rather lose all my data without backup than to never ever start my phone again. Please reply ASAP! I want to restore EVERYTHING, INCLUDING THE FAILED OBIN AND MY MESSING OF THE TIME IN MY PHONE. It doesn't matter if i have to wipe out all my data.
Dear all.
First of all, thanks for your attention, I really appreciate.
I have a GNote 10.1 Wi-Fi version (N8013) with stock Android 4.1.
My S-Pen was getting me crazy, because I was not able to use it correctly on the edges of the device. I tried an app that supposed to reset the alignment, but I did not work, so I googled and found that the only way to fix it was "factory reseting" the tablet.
So, I installed the TeamWin recovery and backed up my data. After that I hit the button "reboot". But before rebooting, the recovery screen "told me" that I was not rooted and "asked" if I would like to install SuperSU to get root access. I checked YES and rebooted.
After that I got stucked at the "Samsung Galaxy Note" screen (see attached file).
I've tried to switch off the note, but the screen goes off for one second and it lights up again at the same screen.
If I plug the USB cable and try to switch it off, the note goes to the battery charging screen. If I remove the USB and push the power button again, the tablet gets back to the "Samsung Galaxy Note" screen.
Odin seems to "connect" with the tablet.
I can enter both the download mode and the recovery mode (not the teamwin recovery).
Attached pictures of what I get.
Any sugestions?
Thanks!!!
Everything is ok now
Dear all,
Hope I can help you if you have a problem similar to mine.
I remembered that a PC with no OS stops on some screen, but everything else works, just as what was happening with my note.
I tought that I might have wiped more things than I should, so, the only thing I had to do was to restore the backup that I had.
To do this I should reinstall the TWRP and the only way was via Odin.
Solved the problem this way:
1. Downloaded the Odin (http://techbeasts.com/2013/08/08/download-odin-pc-latest-version-v-3-07/)
2. Downloaded the TWRP file (http://techerrata.com/get/twrp2/p4noterf/openrecovery-twrp-2.6.1.0-p4notewifi.tar)
3. Connected the Galaxy Note to my PC using the USB cable
4. Entered the "download mode"
5. Loaded the file from step 2 into the tablet using Odin
6. Rebooted the tablet
7. Entered the recovery mode (TWRP was working)
8. Restored the backup that I had
9. Rebooted again
Did the dance of victory!!!
I am so glad to have my device back.
Regards
how to access recovery mode? mine can't access recovery mode with power+volume up :crying:
rizalabd said:
how to access recovery mode? mine can't access recovery mode with power+volume up :crying:
Click to expand...
Click to collapse
Hi all
mine neither.. followed your steps with odin but still stuck in start screen (Samsung Galaxy Note 10.1). By the way mine is the 8010. I tried almost everything. Cant even load the recovery mode!.... And Have no backup either.
PLease someone help me...
Thank you in advance
I have an SM-P600
My Note 10.1 2014 Edition is stuck on the tablet title screen, not sure if its in reboot mode it returns to this screen if I try to shut it off... basically Its frozen, and when I try to shut it off it goes away a few seconds and comes back. This happened after I rooted with KingRoot, and tried to Flash a ROM, Im a complete Noob and should have done my homework... but I didnt. I see everyone suggesting odin and going into download mode... I can get to download mode but I am using a macbook pro, and there are very little options to use odin, I tried Jodin3... and Heimdall... no luck...
PLEASE HELP !
HELP stuck on Samsung screen
I didn't any root or install a different firmware to mine.
But after charging it I removed the cable and it rebooted and got stuck on the Samsung screen. I can only access to Download mode. I didn't have any Recovery mode installed, and now I can't install one successfully via Odin...
I tried to install a new firmware... a recovery mode... nothing is working...
Please I need HELP...
@ agelcer: Was your tablet rooted?
Hello. I havea similar problem with my note 2 phone. It will not get past the
samsung screen. My cpu knowledge is very limited. Are you open to accepting payment for attempting to fix my cell phone? All I want is the pictures off of it if that is all you can do to it. Pleass email me at [email protected] if you or anyone you know can help. Thanks....Jay
Same thing is happening to mine. I tried Odin but after the download the srceen goes black and then comes back to the Samsung Galaxy Note 10.1 screen.
Hello folks.
Same problem here with a n8000.
It had the stock unrooted rom probably JellyBean.
Can only access Download Mode, nothing else.
I get connection to Odin, tried to flash original firmware, 4 file firmware, re-partition with pit file, flash a custom recovery, all seem to pass through but nothing changes, still stuck on 'Samsung Galaxy Note 10.1' screen, never moves on to boot animation and still can't access Recovery Mode.
However, something else I triy with Odin and it FAILS is ticking 'Nand Erase All'. It won't let me erase nand.
Could this mean some kind of memory corruption?
Does it have anything to do with EMMC?
If it does, is there a possible way to fix without replacing the hardware?
What else can I try before giving up?
It would be nice if other users who report this problem attempt to Nand Erase All and see if it also FAILS..
Thanks alot and sorry for the long post.
Edit: after posting I found this which is PROBABLY THE SOLUTION for me.
And here is another topic on this issue.
did you find the solution?
giba_fernando said:
Hello folks.
Same problem here with a n8000.
It had the stock unrooted rom probably JellyBean.
Can only access Download Mode, nothing else.
I get connection to Odin, tried to flash original firmware, 4 file firmware, re-partition with pit file, flash a custom recovery, all seem to pass through but nothing changes, still stuck on 'Samsung Galaxy Note 10.1' screen, never moves on to boot animation and still can't access Recovery Mode.
However, something else I triy with Odin and it FAILS is ticking 'Nand Erase All'. It won't let me erase nand.
Could this mean some kind of memory corruption?
Does it have anything to do with EMMC?
If it does, is there a possible way to fix without replacing the hardware?
What else can I try before giving up?
It would be nice if other users who report this problem attempt to Nand Erase All and see if it also FAILS..
Thanks alot and sorry for the long post.
Edit: after posting I found this which is PROBABLY THE SOLUTION for me.
And here is another topic on this issue.
Click to expand...
Click to collapse
i am looking for any solution since two years without any benefit. did you find any?
chozex said:
i am looking for any solution since two years without any benefit. did you find any?
Click to expand...
Click to collapse
I assumed from my searches the solution would be JTAG or replace the EMMC.
Since I don't have the resources for any of those, I just abandoned it to the dust and rust..
bootloader
Is this after the boot loader is updated?
osirisx69 said:
Is this after the boot loader is updated?
Click to expand...
Click to collapse
I'm not very clear about bootloader upgrading, but I guess it was included in the 4 file firmware I tried flashing and it said 'success' but nothing changed..
I think it ain't just a softbrick since I can't erase nand..
What's your background, osirisx69?
This happened to ours as well just today. Unplugged it rebooted it and it's stuck. Can only access the Odin mode.
Sent from my XT1254 using Tapatalk
i got same issue at last 4 months
just try reset then got same issue.
Same problem for 3 months. Guys have anyone tried jtag flashing firmware as in this post which was provided earlier?
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..
My phone is a verzon note 2 on deodox 4.3 with twrp recovery. The phone only boots to teamwin logo and flickers on and off. my computer will not recognize my phone either at this point.This is what happened. Ive been having some 4g lte loss and unstable wifi issues to i decided to do a factoty reset. when i rebooted into recovery i was stuck at the twrp logo and it would constantly bootloop the twrp logo.. I restarted my phone and did a factory reset from under the general setting. At that point it rebooted int the twrp but continued to just stay at the logo and would not go into recovery. I pulled the battery and restarted the phone but from that point on it would only boot into the twrp logo and stay there. I can get into download mode but my pc (win7) no longer recognizes the phone so i cant attempt to fix this in odin. Im not sure what to do to get this phone to work properly at this point.
yoda254 said:
My phone is a verzon note 2 on deodox 4.3 with twrp recovery. The phone only boots to teamwin logo and flickers on and off. my computer will not recognize my phone either at this point.This is what happened. Ive been having some 4g lte loss and unstable wifi issues to i decided to do a factoty reset. when i rebooted into recovery i was stuck at the twrp logo and it would constantly bootloop the twrp logo.. I restarted my phone and did a factory reset from under the general setting. At that point it rebooted int the twrp but continued to just stay at the logo and would not go into recovery. I pulled the battery and restarted the phone but from that point on it would only boot into the twrp logo and stay there. I can get into download mode but my pc (win7) no longer recognizes the phone so i cant attempt to fix this in odin. Im not sure what to do to get this phone to work properly at this point.
Click to expand...
Click to collapse
My guess is that when you rooted with CASUAL, it changed the Samsung device driver on your computer and you need to reinstall the Samsung driver to get the computer to recognize the phone again in download mode.
Underneath step 7 of section 1b on Droidstyle's restore guide, he discusses issue with CASUAL replacing the Samsung driver... and he gives a link to Jeremy Loper's fix... "If odin no longer recognizes your device, most likely Casual killed the driver for odin!! follow this tutorial for restoring the driver: http://www.youtube.com/watch?v=zzghcV8HVVk"
Once the computer recognizes the phone again, you should be able to use ODIN to restore back to 4.1.2 so you can root/unlock again with CASUAL. After you get the phone restored with Odin, I would recommend booting into Stock Recovery and wiping cache/doing factory reset before running Casual again... this would enure you are starting over with a totally clean slate.
If the above doesn't work, then here's a thread where I tried to help someone else who couldn't get their computer to recognize the phone.... maybe some of those ideas will help - http://forum.xda-developers.com/showthread.php?p=55833998
Good luck!!
1 step forward two steps back. I got my pc /odin to recognizes my note 2(changed usb cords). Then tried to odin back to stock 4.1.2. At first odin kept saying (odin not responding) and would ask to close the program,after several attemps i final got it to flash the 4.1.2 file. When i flashed the file and was at the point where it reboots, it would not get past the samsung note 2 logo and continued to flicker and not boot up even when i tried to put it into download mode like it said to in this thread. http://forum.xda-developers.com/showthread.php?t=2024207. When i tried to reflash the file it failed. when i attempted again it just hangs at setupconnection. Tried again and it failed. Btw thanks for the help mattnmag.
Got it working! i simply forgot to place the sch-i605 pit. into the pit section of odin when i flashed the 4.1.2 rom.
Similar problems
I was running AllianceROM 26. My phone had been spontaneously rebooting for a bit recently. Today, it started to spontaneously reboot again, but this time, it never got past the Galaxy Note 2 screen. After pulling the battery, I tried to boot into TWRP. It just hangs on the twrp boot screen for a few minutes but never goes into twrp.
I figured I would try taking it back to stock. So, I used ODIN to try and put 4.1.2 on it and a new PIT file. That appeared to work fine. I got no errors in ODIN. However, I still cannot get this thing to get past these boot screens, either the Galaxy Note 2 one or TWRP when I try that there. I have tried this twice now, once with re-partition checked and another time with re-partition unchecked (saw conflicting instructions on that so I figured I would try it both ways). I still am not getting past the boot screen.
Any help or ideas are appreciated as right now, my phone appears to be bricked and I am out of ideas.
so what was the solution to the teamwin flashing on and off after a factory reset? this is certainly not a solution, having to reflash the phone...
Hello everybody, My father's old S2 was running well till today, then suddenly it didn't wake up. Tried restarting and got a kernel panic. Then, nothing. The phone stucks on the I9100 logo or sometimes tries to boot, but it's stuck. It DOESN'T enter recovery mode, only download one. I was running a modded Nougat or Marshmallow ROM, and I've found a soft-brick/NAND RW corruption thread here:
https://forum.xda-developers.com/galaxy-s2/help/guide-fix-unflashable-soft-bricked-gsii-t1457458
It's quite old and I don't know if it works, it refers to the old ICS, and, since I don't want to mess up things more than this, I prefer to ask you if someone has some other recent discussions or solutions for me.
Thank you so much in advance!
Guys can someone please help me? I tried that guide but I can't enter recovery mode, I tried flashing the CMW recovery with ODIN and it always get stuck on "NAND write start!". There is no chance to revive the phone? I can't flash a ROM with ODIN too, it gets stuck at the same point..
Also had the issue once that my device suddenly wouldn't boot up anymore. Also recovery didn't work. I fixed by flashing another recovery via Odin in download mode.
Did take quite long though until I finally succeeded, because at some recovery flashes Odin wouldn't pass 'NAND write start' or something. I tried with different recoveries and USB ports and somehow managed to get it working again. Then I wiped data, cache, system and reinstalled the ROM and Gapps.
Hope this helps.