PHONE : Samsung galaxy s2 GT 1900T, stock JB 4.1.2, rooted, with jeboo kernel.
About 2 weeks ago, i'm trying to install custom OS (cyanogen 11=kitkat) to my beloved phone.. i got eror when try to install (status 7) but im installing the right version of cyanogen for my phone. so i decide to reboot my phone, then bluffff all gone. i stuck at "samsung galaxy sII" sign. i take out the battery and try to enter recovery mode (cwm) but same!!! stuck at the black logo screen. then i try to flash stock ROM using download mode, but odin doesn't detecting my device
what should i do???
REALLY NEED HELPPP
THANKS!
You need to get a successful Odin flash one way or another. How ? Hopper8's 'Odin troubleshooting' thread stickied in General. Go through as many of the troubleshooting steps in the thread as many times as you need to in order to get a successful flash.
That what i know. Your phone is booting up to download mode
cos it is a second bootloader and it alright with that. Your kernel
partition is a third bootloader and that looks spoiled for me thats
why Odin cant recognize your phone. You need to try to hold
some buttons Vol up down and home while in download mode
combine them together try to plug in your phone before and after
download mode come up. Good luck
the thing is, commonly when i hear Status 7, the first thing came in my mind is update your CWM / TWRP...and most of the time that solved the problem (dunno if theres any other meaning for Status 7)
theres always search option, you know
Related
Hey guys, I'm new to this forum - looks wonderful!
Unfortunetly I got here with a big problem :
I've been trying to flash some ROM but it never succeeded.
When I start my phone I see the CM7 logo coming up, right after that I get a screen like its trying to install the ROM or somthing...few lines being written to a log looks like recovery mode and then the phone is rebooting again and this process happens again...infinite loop!
I cannot get my phone into download mode in any way..tried :
1) vol up/down/both + home + power
2) 301k ohm JIG between the 4th and 5th pins
Nothing helped, cannot see the phone in Odin when its rebooting like that.
Some history - I never been to download mod, but been to recovery.
I had CM7 installed before trying to flash this new ROM.
Any help would be appreciated, if its possible at all.
Thanks!
If yount wont come to download mode it is hsArd to belive you can fix this. As i wrote you also wont get into recovery mode.... are you sure your dooing it right there are lots of youtube vids out there. I have some issues too to get in download or recovery with my galaxy. You hav to stop press once you see the galaxy logo... if you get to recovery mode under advance you can boot to download mode...
Once you are there search a rom you can install over odin like darkys rom 9.2 i think.....
Otherwise bring it to samsung...
Cheers and good luck
Hi guys, hoping someone can shed a little bit of light on my issue.
Rooted my phone- all went fine!.
Went to install CWM and all i got was the e3 recover telling me:
Failed to verify signature.
Instillation failed.
So after a little bit of messing about i decided to just leave it and continue on with my day. My phone then ran out of battery. I put it on charge without turning it on and came to find the phone in recovery mode with a fully working version of Clockwork MOD, suprising to say the least. I rebooted the phone and then tried to reboot back into recovery mode, and since then my phone wont load normally or into recovery past the samsung logo.
I dont know what to do because although my phone will go into download mode, it will not work with ODIN, i simply get the message "failed to open serial port."
So i have a phone that wont load recovery, wont load normally, and wont let me install kernals etc through ODIN, please someone help me!
Any help would be great, thanks people.
Hi
I'm new here & have been reading many threads in preparation before rooting my phone.
Its sounds like your phone is stuck in a boot loop, if so read this tread & it should help you out. (sorry if i got it wrong)
http://forum.xda-developers.com/showthread.php?t=1108499
peace
The above solution will not work for you, because your have no recovery.
How did you root your phone? To summarize:
1. You rooted your phone.
2. You tried flashing CWM (why?)
3. Flashing failed and you have no recovery anymore?
4. Odin does not recognize your phone anymore.
Correct?
Try a different USB cable to make sure it isn't the cable.
Have you stopped kies on your computer before running odin?
Sent from my GT-I9100 using XDA App
I had the same problem get into Cwm the way you'd get into normal Android recovery so hold vol up + home + power then when the boot screen pops up let go for a millisecond then repush vol up + home + power
Sent from my GT-I9100 using XDA App
Your phones only bricked if it wont turn on mate. Relax as its most likely fixable. Do as others have suggested and disable kies as its a pain in the backside. Kies doesnt like odin and will crap it up. Install a kernel like chainfires; get into cwm and wipe everything. Dalvik, cache, system. Get a usb jig off ebay for gs2 if you can as thats helped me out. I only use Siyahs kernel or Chainfires as they are the most stable. Good luck.
Sent from my GT-I9100 using Tapatalk
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
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
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..