Hi i am new on forum, and i was trying to flash a custom ROM on S II Wimax ISW11SC, upgrading the 4.0.4 to 4.1.2, but the process failed at odin, and i tried to restart the odin mode, but the phone died.
When i try to turn on, i can hear the sound of boot, but nothing appears on screen. I tried odin mode, recovery mode, but nothing worked.
Can someone help please?
Related
The Skinny: updated to JB yesterday, worked great! phone died. wouldn't turn on after charging, kept booting to recovery.. so decided to go back to to stock with odin3 and then re-flash JB.
The Problem Now: stuck on "Over Stock" logo. can't get to recovery, or download.. though odin does still recognize the phone in bricked state, it can't effect any change to the device.
is there any hope??
ferther more..
every once in a while it will power on into download mode, but odin doesn't seem to be doing the trick.. but other times it boots into an "upload mode".
well out of my depth.. someone help!
Google ezbase recovery kit and try that. Even when it's for the i9000 you can use it. You can flash to stock after that.
failed
it failed miserably.. now it shows the GT-I9000 boot screen as it loops infinitely. though on the bright side, download mode is accessible again though even flashing stock wont wipe the GT-I9000 residual effects from it. more suggestions??
Hi,
my Samsung Galaxy Ace 2 wont turn on, its stuck on "firmware upgrade encountered an issue, use Kies...".
Recovery mode wont work, cant connect to Kies because phone wont turn on, only thing it works is Odin.
I can enter Download mode.
I have tried:
1) Installed new stock rom with Odin, it says PASS in Odin, no errors, but again i cant turn on the phone, only black screen and "firmware upgrade encountered an issue, use Kies...".
2) Installed new Kernel with CWM in ODIN, it says PASS, but still cant get to Recovery mode and problem still exist.
3) Installed new ROM after Kernel, and everything pass great in ODIN, and when i try to turn on phone or Recovery mode, it just vibrates once.
And when i connect with USB it says "firmware upgrade encountered an issue, use Kies...".
I have tried different Kernels for this phone, different ROMs, different Computer, different USB cable, and problem still apear.
I dont know what to do ?
Download mode working, Odin works fine, but still when i try to turn on Phone, it vibrates and black screen, and when connect to PC it says "firmware upgrade encountered an issue, use Kies...".
Still cant get Recovery mode to work.
Also tried to connect with adb, adb cant see phone. Only Odin can recognize phone on COM port.
Is there something else to do ?
Thank you.
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?
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...
A few months ago, I tried rooting my phone and posted about it:
"I am completely new to rooting and I followed Wolfdroid's tutorial to root my phone.
I got to the point where i had CWM, but when I was trying to install from my SD card there was no option.
I'm stuck with the Samsung "unlock" Custom load up screen and every time i try to go into recovery, it immediately goes to download odin mode, but it still says im not rooted. I know it's possible to boot normally by going to download and pressing Volume down, but if it's possible I would like to get my phone back to an completely unrooted state.
I've tried unrooting with SuperSU but that just ends up freezing.
Samsung Galaxy S4(Verizon) SCH-I545 NK1"
After a while I gave up on bringing my phone back to a completely unrooted state, but now my phone was stuck in a reboot loop, where i would be able to use it for a few seconds then it would reboot. I am completely unable to get into recovery mode, and when I do try, it goes into the downloading screen. So I tried flashing a stock rom onto my phone, but that failed, so now it can either go into downloading screen or go to a screen were it says "Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again." I have no clue what to do at this point.
have you tried surge's emegerncy stock? here. It's an NC5 stock rom, but since bootloader didnt get locked up for kitkat until OC1 it might work.