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??
Related
I flashed Trigger onto my Vibrant, all seemed well. ROM Manager was FCing, so I reinstalled from market, installed recovery from within ROM Manager, rebooted, went into the regular android recovery. Rebooted again, now it doesn't want to boot. Just loops at the Samsung Galaxy logo (after the vibrant, the little "movie" that plays after the Vibrant logo)
Stubborn bastard won't go into download mode, COM9 shows up in Odin, but it keeps looping the intro thing. If I try to flash, Odin just says SetupConnection and stays there.
Will a JIG do anything at this point?
I will admit, I got too eager and may have flashed a gingerbread ROM on top of a froyo bootloader. >.> I admit, that was stupid, but now all I want is to get the damn thing back into download mode...
It's not bricked. Probably just in a boot loop. Just need to play around and get into download mode.
speedy11131 said:
I will admit, I got too eager and may have flashed a gingerbread ROM on top of a froyo bootloader. >.> I admit, that was stupid, but now all I want is to get the damn thing back into download mode...
Click to expand...
Click to collapse
that doesnt make a difference, i've been on simply honey like 2 month on froyo bootloaders and works fine apart from rainbow on boot and not being able to see recovery
speedy11131 said:
I flashed Trigger onto my Vibrant, all seemed well. ROM Manager was FCing, so I reinstalled from market, installed recovery from within ROM Manager, rebooted, went into the regular android recovery. Rebooted again, now it doesn't want to boot. Just loops at the Samsung Galaxy logo (after the vibrant, the little "movie" that plays after the Vibrant logo)
Stubborn bastard won't go into download mode, COM9 shows up in Odin, but it keeps looping the intro thing. If I try to flash, Odin just says SetupConnection and stays there.
Will a JIG do anything at this point?
I will admit, I got too eager and may have flashed a gingerbread ROM on top of a froyo bootloader. >.> I admit, that was stupid, but now all I want is to get the damn thing back into download mode...
Click to expand...
Click to collapse
That happened to me before, I used and tried a different cable and got into download mode with functioning odin. Also, try removing battery, then put the battery back in. then with pressing volume up and down with power switch plug in usb. Hope this helps. Vibrant is hard to brick.
Sent from my GT-I9000 using xda premium
It is not dead yet, follow the steps as follow thread to go back in beginning and flash rom you want again.
http://forum.xda-developers.com/showthread.php?t=734475
Depending on which version of ODIN you are using the sequence works best like this:
1) Get the phone into a download acceptable mode with use of a usb cable (JIG is most appropriate)
2) Have ODIN running BEFORE connecting the phone
3) Now connect your phone and attempt the flash. Version prior to 1.7 were extremely picky with following this sequence. As of 1.7 POST ODIN seems to not bug so much the sequence of when the phone was plugged in.
Report back with your results...
speedy11131 said:
I flashed Trigger onto my Vibrant, all seemed well. ROM Manager was FCing, so I reinstalled from market, installed recovery from within ROM Manager, rebooted, went into the regular android recovery. Rebooted again, now it doesn't want to boot. Just loops at the Samsung Galaxy logo (after the vibrant, the little "movie" that plays after the Vibrant logo)
Stubborn bastard won't go into download mode, COM9 shows up in Odin, but it keeps looping the intro thing. If I try to flash, Odin just says SetupConnection and stays there.
Will a JIG do anything at this point?
I will admit, I got too eager and may have flashed a gingerbread ROM on top of a froyo bootloader. >.> I admit, that was stupid, but now all I want is to get the damn thing back into download mode...
Click to expand...
Click to collapse
1) take your battery out
2) plug your phone a laptop/desktop
3) hold volume up and volume down + put the battery in
...should be in download mode...I am assuming u have a froyo bootloader...
If that don't work then on step three instead of holding both volume buttons only hold volume up..that works for GB bootloader...
my phone originally started out with the stock 2.1update 1 firmware, t959ujfd...
when i turn on (off then on) the phone it would boot to a "Samsung Galaxy S GT-I9000" logo, then switch to a "Vibrant Samsung" logo.
when i received my phone this was how it booted..
Later, i rooted the phone, and flashed clockwork mod recovery.. I made a CWM recovery back up here..
After creating the backup, i put CM10 on to the internal sdcard and installed it via CWM. During the
installation, it rebooted into the newer version of CWM recovery. After choosing "reboot device", my vibrant
would first load the "Samsung Galaxy S GT-I9000" logo, then the Cyanogen mod logo. but then the screen would
flash, and the cyanogen mod logo would appear again. Shortly it dumps me right back at the new version of CWM recovery..
At this point, i thought i flashed CM 10 incorrectly, so from the CMW recovery, i restored that first back up. after restoring that
back up, my phone no longer boots.. Right now if i leave the batter in and plug in a USB, the circular spinny charging icon appears,
then freezes (it doesnt spin).. i can turn on the phone, but it stays stuck at the "Galaxy S GT-I9000" logo.. I cant boot into recovery.
so i read a bunch of other threads about perhaps when ibought the phone, it had a GB bootloader. and i have tried ways to get my vibrant
into download mode.. which unfortunately i havent.. So i can't use Odin and flash back to stock.. Hopefully you guys can help me get back to stock so i can at least use my phone and/or start over installing CM10..
Note: i did not install/flash anything else other than CM10. i did not use custom kernels, or install Google Apps etc..
Edit: Ok, now i can reliably get into download mode. for some reason, the physical button combinations were wrong for my vibrant.. instead of the
usual 3 button combo, my download mode was volume up + power.. this was also the reason why i had a hard time getting into recovery since it was
volume down + power.. It seems as if, my boot loader was changed when i bought the phone..
That's the combo I use I don't have boot loaders. Son if that worked did you get it fixed with Odin or heimdall
Sent from my SGH-T959 using xda app-developers app
All you had to do is flash cm10 again. Most of the times you have to flash jb roms more than once because of the different cwm versions . Make sure you read the entire thread before taking action, I'm sure it said that somewhere but anyway Gb bootloaders are much more convenient so that's a plus. Just flash back to stock with Odin or if you still want cm10 then boot into recovery and flash again.
Sent from my SGH-T959 using Tapatalk 2
Sent from my SGH-T959 using Tapatalk 2
hey, i'm fairly new to androids and rooting, i was running a biftor rom and everything was going fine, from what i can remember ROM Manager asked me if i'd like to update some binary or something it said it would automatically reboot into CWM but when it rebooted it didn't load CWM instead it just got stuck on the boot screen with an exclamation mark, when i try and enter recovery mode i get the empty battery logo but the circle underneath the battery that usually spins around is froze, the phone has full charge as it's been on charge all night, i can still enter download mode, I've tried to reflash the recovery with 0din but i get more problems with odin getting stuck on 'setup connection' and 'nand write start' can someone give me some advice please? I'm on an S2 i9100 btw, thanks.
Lesmiff said:
hey, i'm fairly new to androids and rooting, i was running a biftor rom and everything was going fine, from what i can remember ROM Manager asked me if i'd like to update some binary or something it said it would automatically reboot into CWM but when it rebooted it didn't load CWM instead it just got stuck on the boot screen with an exclamation mark, when i try and enter recovery mode i get the empty battery logo but the circle underneath the battery that usually spins around is froze, the phone has full charge as it's been on charge all night, i can still enter download mode, I've tried to reflash the recovery with 0din but i get more problems with odin getting stuck on 'setup connection' and 'nand write start' can someone give me some advice please? I'm on an S2 i9100 btw, thanks.
Click to expand...
Click to collapse
reflash the recovery via Odin??? or you mean you flashed a stock rom?
Reflash the ROM or flash back to stock Android via Odin
Sent from my GT-I9100 using xda premium
Above poster is correct, need to re flash a stock ROM via Odin.
Just needed to say here though, never use ROM manager on an i9100. It's a sure-fire way to screw things up or brick, as you unfortunately found out the hard way :/
Sent from a galaxy far, far away
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...