Hello
I have been using my int Gs3 for sometime and decided to root and explore the mods and custom fw world. I have started with getting to root access and after that install CWM.
Then I try to install nightly cyanogenmod 10. It didnt work and boot back to normal GS3 Touchwiz interface. After that I tried the GooManager and when the phone is restarted it went to bootloop. I removed the battery and put it back. The problem started there.
The phone does not boot to any OS, I only can see the galaxy s3 9300 black splash screen and awatis there. I can go into download mode, but when I go into recovery mode, I can see the Android robot, and it dies The screen is too fast but what I can see it cannot mount EFS, System and any folder.
So I have tried several different methods
- Tried to flash with original rom, different roms, CWM and what I can find suitable for international model. But everytime I got stucked in Nand Write part. In some of them, the flash started and stucked in installing some parts(passes the cache and hidden and stuck after that)
- Tried with bricked phone roms, different PIT files and Bootloader Vralec methods.
- When I am trying these, I have tried with 3 different PC's with/without KIES and Samsung drivers installed. When I plug the phone in Download mode, the PC recognizes it as Generic device.
- I manage to flash the CWM but when it restarts it does not go any further than the first splash screen, but in Odin, some time later it turns to pass. Funny, when the phone is on Galasy S3 black splash screen, the pc recognizes the phone and starts to install the driver.
So, here is an interesting flashing story of mine. I really would appreciate your valuable comments and suggestions.
Thanks in advance.
cugami said:
Hello
I have been using my int Gs3 for sometime and decided to root and explore the mods and custom fw world. I have started with getting to root access and after that install CWM.
Then I try to install nightly cyanogenmod 10. It didnt work and boot back to normal GS3 Touchwiz interface. After that I tried the GooManager and when the phone is restarted it went to bootloop. I removed the battery and put it back. The problem started there.
The phone does not boot to any OS, I only can see the galaxy s3 9300 black splash screen and awatis there. I can go into download mode, but when I go into recovery mode, I can see the Android robot, and it dies The screen is too fast but what I can see it cannot mount EFS, System and any folder.
So I have tried several different methods
- Tried to flash with original rom, different roms, CWM and what I can find suitable for international model. But everytime I got stucked in Nand Write part. In some of them, the flash started and stucked in installing some parts(passes the cache and hidden and stuck after that)
- Tried with bricked phone roms, different PIT files and Bootloader Vralec methods.
- When I am trying these, I have tried with 3 different PC's with/without KIES and Samsung drivers installed. When I plug the phone in Download mode, the PC recognizes it as Generic device.
- I manage to flash the CWM but when it restarts it does not go any further than the first splash screen, but in Odin, some time later it turns to pass. Funny, when the phone is on Galasy S3 black splash screen, the pc recognizes the phone and starts to install the driver.
So, here is an interesting flashing story of mine. I really would appreciate your valuable comments and suggestions.
Thanks in advance.
Click to expand...
Click to collapse
GO here : http://forum.xda-developers.com/showthread.php?t=1993044
Related
So i recently tried to flash my phone to cynagenmod and i was intensely close to doing so until i noticed what i did wrong.
But then when i rebooted my phone after using clockwork, my phone would not boot up after the start screen.
I am able to use recovery mode and download mode but i cannot go anywhere beyond that.
I also tried restarting it with Odin but it wont recognize the device even though the proper drivers have been installed.
I have tried unplugging it in different usb slots and ive reinstalled Odin.
Is there anyone that could possibly help?
Just get back to recovery and flash the rom, many times if coming from a different version (2.2-->4.2) it requires more than 1 flash
Nexus⁴ PAC 360° Productions
Try this: http://forum.xda-developers.com/showthread.php?p=44794712
And 2 posts down I explain what I did
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..
Hello,
Some threads with similar issues are already around, but I didn't find one with the same problem as me.
What I was doing when the issue happened:
I was trying to install cyanogenmod from the isntaller method (apk isntalled on the phone, application running on windows that installs it automatically). At certain point, it rebooted the device and the cyanogenmod logo was on the screen. After a while, the program gave an error "'We couldn't talk to your phone' - Samsung devices ONLY", which is described in their wiki. So the pc lost connection to the phone.
What I did:
1 - Since I had installed the clockwork recovery and tested it before, I thought "hey, no problem. I'll hust recover this S*it". So I disconnected the SIII from the PC and tried to enter recovery mode pressing "volume ip + home + power". While I have these pressed, the phone in in an infinite loop on the initial screen showing the brand and model. When I release them, it goes straight to the cyanogenmod blue creepy robot just there staring.
2 - Since that didn't work out since I now don't have a recovery mode and I don't have any functioning rom either, I found several tutorials for using Odin and reflashing and or repartitioning. PROBLEM: Odin seems to recognize the phone (com port), I click on the option and... FAIL!
2.1 - What I have tried: Different Odin versions (1.83 and 3.09), stock drivers from Kies, Zadig drivers.
So. There you go. I pretty much exhausted everything I could get from my head and interpret from google. So, No recovery, no ROM, fail at odin.
Any ideas?
Thanks in advance.
Remove kies from the pc reinstall drivers and flash a cwm recovery. From there flash a custom rom in recovery from ext sd. Odin 3.04 is good. I would keep trying to get into recovery though. Do you have that red mark in the corner on Sammy splash screen?
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...