Hello everyone,
I'll start explaining very quickly. this morning, the home button suddenly dead. it NOT works at all. an it's an hardware problem, because I can't either access recovery mode. and that's the point. I was using cyanogenmod 9 with ICS, and when I flashed the samsung STOCK rom with ODIN, I get bootlops. I tried with the ICS samsung stock and the GB one, same thing. I saw the guide in the other section of the forum, BUT they say that I have to do a full wipe in recovery... well, I can't, my home button is dead. I'm trying to do this because the service center will "test" the home button with the phone turned on, but if I get bootlops... well, He will suspect that there is something wrong (the unofficial roms, etc...) any idea to correctly flash a samsung stock rom with odin without getting bootlops? thank you so much :crying:
I have the same problem (my home button died). However I still can boot the phone. I think what I am going to do is order the JIG to boot into download mode and delete the number of custom flashes and then install the Stock ICS and send it to Samsung. Maybe you can do the same.
You can try soft reboot to cwm. But download mode? I don't remember if any kernel had option to boot directly to download mode. Maybe old Glitch have this. Then you will be able to flash stock via odin.
But if there are bootloops than only jig is an option.
i9.0.1.3k galaxy imperator
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
Hello all,
I've encountered a problem with my Straight Talk Galaxy S II S959G after flashing the CWM from this thread:
http://forum.xda-developers.com/showthread.php?t=2559694
I was running 6.0.1.2 or something along those lines. And I was running the 4.2.2 SuperNexus ROM. I can only get to the Samsung Galaxy S II screen and then it goes blank, but does not shut off, as my computer recognizes as being on. However, I cannot DO anything with it even though it can be connected to my computer. Odin v1.85 does not seem to recognize it either.
If someone could help, it would be much appreciated.
It sounds like you just have a soft brick if you're still getting the Samsung logo.
ODIN is intended to be used in download mode. Are you able to get into download mode (hold vol +/vol -, then plug in the USB cable)? If so, you should be able to reflash the kernel, assuming that's what broke. I like to keep an ODIN flashable full stock ROM (minus bootloaders) handy in the event that I mess things up badly.
I don't have experience with the specific ROM you are trying to flash (I was actually planning on playing around with that one soon).
jpasher said:
It sounds like you just have a soft brick if you're still getting the Samsung logo.
ODIN is intended to be used in download mode. Are you able to get into download mode (hold vol +/vol -, then plug in the USB cable)? If so, you should be able to reflash the kernel, assuming that's what broke. I like to keep an ODIN flashable full stock ROM (minus bootloaders) handy in the event that I mess things up badly.
I don't have experience with the specific ROM you are trying to flash (I was actually planning on playing around with that one soon).
Click to expand...
Click to collapse
I'm not very experienced with all of this, but, I have tried Odin mode. My computer does not recognize my phone when it is plugged in.
I do have the stock rom that my phone came with too, but I do not have a Samsung official USB cable to use with it, which, supposedly, is required for this to work. And I do not know if my Odin version on my computer is outdated either.
Epications said:
I'm not very experienced with all of this, but, I have tried Odin mode. My computer does not recognize my phone when it is plugged in.
I do have the stock rom that my phone came with too, but I do not have a Samsung official USB cable to use with it, which, supposedly, is required for this to work. And I do not know if my Odin version on my computer is outdated either.
Click to expand...
Click to collapse
Many usb cables will work just fine. The original cables are known to be of good quality. Odin3 v1.85 is recommended for this phone, although any version of Odin should work.
Did you open Odin on the desktop before putting the phone into download mode? Sometimes the problem is as simple as wrong sequence.
If you have a USB jig, use that to put the phone into download mode. Then connect it to the computer while Odin is open on the desktop.
Make sure you have the correct driver installed. You should have "SAMSUNG USB driver for mobile phones" in your add/remove programs dialog in windows. If not, install it. If so, uninstall it, reboot, reinstall it.
Try different cables, different usb ports, even different pc's.
I'll try not to butt in too much, since creepyncrawly obviously has a lot of experience.
(at this point, I'm assuming you're on Windows)
Like he said, it's sounds like it's most likely a driver issue. When you first plugged in the phone, did you get a Windows balloon notification saying "Installing drivers"? If you open up device manager, do you have any devices with an exclamation point next to them, indicate a device that failed to start? If so, make sure the Samsung drivers are installed.
A USB jig is definitely nice to have handy. I use this one (as long as you can wait a few weeks on shipping). If you can get into download mode, your bootloaders are probably safe (meaning you should be able to recover easily).
I actually installed that CM11 ROM yesterday on my SGH-I777 (I can't say anything specific about your model and how it may differ, but it seems to basically be the same phone as the I777). I was running stock non-rooted JB 4.1 with stock recovery, so I had to take a little more of a convoluted route to get there.
In the end, here's the thread for you. Once you can get ODIN download mode working again, you should be well on your way to fixing it (flash CWM 6.0.4.5 from ODIN, boot into recovery, then try the ROM install again).
Well, I've tried flashing CWM again using Odin. While I actually can USE Odin this time, it just isn't working... My phone still only turns on and goes blank after the Galaxy S II screen.
I had something similar happen the other night when I flashed a kernel that was apparently incompatible with my Captivate (although it should have been fine). The phone would get stuck on the Galaxy S boot screen. I had to reflash a known good kernel to get it working again.
If you can get into the recovery, you can try a wipe/factory reset + wipe cache.
Is ODIN detecting the phone but just failing to flash the files? What error is it getting?
If ODIN is flashing the files properly, but still preventing full boot up, it's probably easiest at this point to flash back to a stock ROM. The previous thread link has the instructions and flash files (I personally have an S2, not an S959G, so it's a slightly different process).
Hi - I don't know if it is a completely outdated method, but this worked on my father's SII skyrocket yesterday when I was encountering a similar softbrick issue:
Get zadig (http://zadig.akeo.ie/), start zadig, get the phone in download mode, hit Options -> List All Devices, select the Samsung or similar device from the dropdown and replace the default USB driver.
Then use heimdall (http://forum.xda-developers.com/showthread.php?t=755265) to flash in a replacement recovery.
Double check that your phone is detected in download mode: heimdall detect
Then flash the recovery: heimdall flash --RECOVERY recovery.img (try CWM for your phone version)
(some places will have you add --no-reboot. that didn't work for me. let it auto reboot)
After it powers down, quickly disconnect the USB cable and put your fingers on the +/- buttons to get into recovery mode. From there push over whichever ROM via adb, etc. etc.
jpasher said:
I had something similar happen the other night when I flashed a kernel that was apparently incompatible with my Captivate (although it should have been fine). The phone would get stuck on the Galaxy S boot screen. I had to reflash a known good kernel to get it working again.
If you can get into the recovery, you can try a wipe/factory reset + wipe cache.
Is ODIN detecting the phone but just failing to flash the files? What error is it getting?
If ODIN is flashing the files properly, but still preventing full boot up, it's probably easiest at this point to flash back to a stock ROM. The previous thread link has the instructions and flash files (I personally have an S2, not an S959G, so it's a slightly different process).
Click to expand...
Click to collapse
It says Odin is successful, but still nothing happens. And I cannot get into recovery no matter how many times I try.
It seems flashing the stock ROM with Odin has worked now, but, now my phone has the tracfone start up animation just looping over and over.
Epications said:
It seems flashing the stock ROM with Odin has worked now, but, now my phone has the tracfone start up animation just looping over and over.
Click to expand...
Click to collapse
Boot into recovery and wipe caches; sometimes you have to do an extra wipe to get out of this type of bootloop.
SteveMurphy said:
Boot into recovery and wipe caches; sometimes you have to do an extra wipe to get out of this type of bootloop.
Click to expand...
Click to collapse
I'm having difficulties booting into recovery.
Epications said:
I'm having difficulties booting into recovery.
Click to expand...
Click to collapse
If you have the stock boot animation you should have recovery. Take the battery out, then put it back in and hold power+volume +/- until you get recovery. I have sometimes had to do this extra step after restoring stock.
Make sure your phone isn't plugged in while you're trying this, btw.
grand quattro CWM TRAPPED
Epications said:
Hello all,
I've encountered a problem with my Straight Talk Galaxy S II S959G after flashing the CWM from this thread:
http://forum.xda-developers.com/showthread.php?t=2559694
I was running 6.0.1.2 or something along those lines. And I was running the 4.2.2 SuperNexus ROM. I can only get to the Samsung Galaxy S II screen and then it goes blank, but does not shut off, as my computer recognizes as being on. However, I cannot DO anything with it even though it can be connected to my computer. Odin v1.85 does not seem to recognize it either.
If someone could help, it would be much appreciated.
Click to expand...
Click to collapse
HI BROOOO I M A GRAND QUATTRO USER EVERYTIME I SWITCH ON MY CELL MY CELL DIRECTLY GOES IN CWM MOD M WORRIED ALOT HELPPPPPPPPPPP ME
I'm using v40 of temasek unofficial cm11, Boefflea version 11 kernel.
while I was using my phone, the phone suddenly went into a reboot and started the boot-loop, even when I pull the battery out and put it back in it starts booting immediately and goes into the boot-loop , whenever I try to go into download mode or recovery mode, once or twice I will be able to reach it, but 3 seconds in, it restarts and goes into the boot loop again (I can't choose between restarting or going into download mode)
would a USB jig help me getting into the download mode or will it be 3 seconds in and restarts?
would a service center help me retain my data as I need them?
Thank you.
momentarily I've managed to be able to access download mode and the laptop started making a sound trying to identify the device, too bad the battery fell off (or the phone restarted) lol
anyways I still need help because I couldn't get into any of them
If the phone starts the moment a battery is inserted then usually the power button is stuck -try giving it a wiggle, or get it replaced.
boomboomer said:
If the phone starts the moment a battery is inserted then usually the power button is stuck -try giving it a wiggle, or get it replaced.
Click to expand...
Click to collapse
yeah will do that once this gets fixed lol ..
for some awkward reason, I found out that once I pull out the battery I can use download mode
what should I download?
I tried flashing CWM but I get back to the bootloop ... should I install a newer bootloader?
No, bootloader is irrelevant to firmware. You would be best to flash a full stock rom with odin then factory reset and see if it will boot. I would suspect the power cycling may have caused partition problems if recovery got wiped.
Sent from my GT-I9300 using Tapatalk
boomboomer said:
No, bootloader is irrelevant to firmware. You would be best to flash a full stock rom with odin then factory reset and see if it will boot. I would suspect the power cycling may have caused partition problems if recovery got wiped.
Sent from my GT-I9300 using Tapatalk
Click to expand...
Click to collapse
which would mean I would lose all the data in the previous cm11 right?
I'm trying my best to flash a recovery but I think it got wiped for good.. I'm trying to flash it over and over again .. (I unplug the battery once I'm in download mode to prevent the sudden restart) .. before I flashed the CWM through odin I was able to go into a glimpse of a recovery mode, now I can't seem to see it at all...
is there a way to just copy the data (mostly pictures) through odin or adb with my phone current state?
Google says it might be possible
http://codebin.co.uk/blog/samsung-galaxy-s3-boot-loop-backup-without-root/
boomboomer said:
Google says it might be possible
http://codebin.co.uk/blog/samsung-galaxy-s3-boot-loop-backup-without-root/
Click to expand...
Click to collapse
only through recovery mode or hoping your phone would suddenly connect after many boots lol
I don't think that will be my case .. oh well
as long as I can get my phone working again
going back to stock rom didn't fix the issue. can't access anything yet.
any help?
if anyone is reading this, I've been looking everywhere for a stock rom with pit file, I think that's the problem I'm facing since I have different bootloaders and different modes, somewhere around that I jacked my partitions and I think this would help putting it all back
I've found ones for android 4.1 but nothing of 4.3 .. since I came from 4.3 stock rom and then 4.4 kitkat temasek I think 4.1 won't help me at all
time to go to a service center I guess.
OK this is weird...
after I gave up I put my phone on a recover firmware that for some bizarre reason brought it back to life!!! I just put the phone back and left .. 5 hours later it was on and working.. I was able to access the phone for a brief moment.. but for some reason again I wasn't able to get the touch screen to work... I was able to raise the volume.. restart the phone.. but nothing on touch screen..
then it went back to the dead state...
any ideas?
@boomboomer
Motherboard component or connect lose or failing .
Hello same problema with mY S3 , the power button was damaged. and now I need to enter download mode to flash the firmware.... is there a way to enter download mode on S3 without using power key?
danieldp1990 said:
Hello same problema with mY S3 , the power button was damaged. and now I need to enter download mode to flash the firmware.... is there a way to enter download mode on S3 without using power key?
Click to expand...
Click to collapse
USB JIG
Hello xda, first post n00b here,
I recently got my hands on a SIII (lot better then my old htc one V), and I wanted to install cyanogenmod on it. So I installed the i9300 recovery rom on it and for a short while it seemed to work, but when I tryed to sideload cyanogenmod something went wrong. Everytime I rebooted I got thrown into the downloading, do not power off target!!-screen.
I quickly found my mistake, I did not have an i9300 I had an i9305. With some help from the lovely people at #cyanogenmod (shout out to you PsychoI3ob) I figured out I had to flash the stock rom. I could not figure out how to do this with heimdall, so I downloaded Odin. With Odin, everything went right untill it was somewhere around 99%. The write failed. Now the only thing I see when I but the batteries in my phone is: Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again.
So now I would like to know: Did my phone just become a paperweight or is there still anything I can do?
Thanks a lot for reading trough!
If you can get back into download mode by shutting down your phone, and then boot while holding the volume down, home button and power button simultaneously you could try reflashing stock ROM through Odin.
If the phone turns on as soon as you put the battery in then you will have to take the battery back out, and then whilst pressing Vol Down and Home button put the battery in (I've had the same issue on a Galaxy Ace II with the phone booting as soon as the battery was put in, but managed to get back into download mode and reflash by doing as I described)
If you manage to successfully reflash, boot into recovery (turn off, then hold Vol Up, Home and Power) and do a factory reset from there just for good measure.
Good luck :good:
"Firmware upgrade encountered an issue..." It is also download mode. You can use Odin to flash while this screen has been displayed or launch Kies and restore your original firmware by firmware initialization option from tools menu.
Write model name GT-I9305 and your phone serial number (under battery). Kies will check what version of firmware was originally pre-installed on that device. Will download and flash it automatically. After that you can upgrade to newest stock. Write custom recovery via Odin, flash custom rom from CWM.
____________________________________________
P3110 / I9300 / I9100 / NEXUS 5 / iPAD2
So I have a Samsung Galaxy SII i9100 that I haven't used in months because the USB port wasn't working, therefore, cannot charge. I fixed it today, charged it and it as working (it as slow though, running CM13)
I wanted it to downgrade it back to JB so I can give it to mom but I didn't flash a suitable recovery first, so I flashed JellySnap ROM on TWRP recovery for CM13 and now it's stuck on bootloop (reboots every 4 seconds but skips the Samsung GS2 intro)
No the big problem is that the home button along with the menu key and the back key don't work, so I can't boot into recovery or download mode, so can't use ODIN.
Is there anything else I can do? Can I get to flash it or wipe it or at least access recovery/download mode through the PC (adb?) or using another phone via OTG?
zedex39zeo said:
So I have a Samsung Galaxy SII i9100 that I haven't used in months because the USB port wasn't working, therefore, cannot charge. I fixed it today, charged it and it as working (it as slow though, running CM13)
I wanted it to downgrade it back to JB so I can give it to mom but I didn't flash a suitable recovery first, so I flashed JellySnap ROM on TWRP recovery for CM13 and now it's stuck on bootloop (reboots every 4 seconds but skips the Samsung GS2 intro)
No the big problem is that the home button along with the menu key and the back key don't work, so I can't boot into recovery or download mode, so can't use ODIN.
Is there anything else I can do? Can I get to flash it or wipe it or at least access recovery/download mode through the PC (adb?) or using another phone via OTG?
Click to expand...
Click to collapse
What you mean "home, menu and back button don't work"? They are broken or you can't use them to get into recovery or download mode? You may be able to make or but a JTAG to get into download mode. If you get this far, you should be able to flash a recovery/kernel or stock rom with odin. Otherwise, you may have to take it to a repair center