[Q] Vibrant boot loop after attempted kernel flash - Vibrant Q&A, Help & Troubleshooting

My vibrant is in a boot loop after I attempted to flash a new kernel, I used Odin to try to go back to stock and it is still looping can anyone hep me?

Try to flash stock jfd using odin. Can u be able to get download mode?
Sent from my vibrant using xda premium

I did flash the jfd with Odin , and I can get to download mode just fine, I hope I didn't irreparably damage the boot loader

Doubt the boot loader is toast - you wouldn't be able to get to recovery/download if its shot.
When you Odin'd to JFD did you repartition?

al the videos and tutorials ive read said to NOT repartition.....should i?

i clicked the repartition box and i get the same result.....could my tar file be bad? or my pit?

If you Odin to JFD you can hit repartition. Thats the only way to get back to a stock setup from CM7 or ICS.
If at first boot it loops from and error when the kernel loads (forget the wording on it) you may need to flash Eugene's froyo that does not brick to clear it out.

There maybe somthenig wrong with your package. Try to download stock rom from samfirmware or vibrant bible. If you are not sure about your bootloader then flash the stock froyo bootloader using odain. Then try to flash stock jfd froyo. If still you have the same problem there may be a hardware issue or not assamble the circuit propely. try to deassamble and reassamble again. Once i got kind of problem, Whenever i give some presure to phones backside phone restart automatically. So i deassamble the phone and reasmble again. After that problem was solved.
www.samfirmware.com/
forum.xda-developers.com/showthread.php?t=771111
Sent from my GT-I9000 using xda premium

This happened to me the first time i flashed to ICS Passion.
Per the instructions in that post, try this:
Remove battery. Hold Vol Down + Home + Power Key. You will enter new recovery mode. Flash the ROM again.
Some users (having Froyo Bootloader) need to press Vol Up Key instead of Home Key to get in Recovery.
Maybe this helps?? Worked for me.

if it makes any difference i was rooted with the stock rom....i never installed a different rom.....

Based off your Youtube vid its looks like you got a bootloop compounded with rainbows. What kernel did you flash with kernel manager? Im betting it was a GB kernel and that is why you 1) have rainbows and 2) have boot loops.
You have 2 Options that come to mind.
1) Try and flash via Odin the overstock Froyo kernel. HERE
In ODIN Un-check Re-Partition - Auto Reboot and F. Reset Time can be checked here, you are justs flashing a kernel.
Click the PDA button and select the Overstock Kernel from the desktop
Boot the phone - does it work?
Option 2 - the dangerous route
Now DO THIS AT OWN RISK - This is what I would try if #1 fails but its up to you to try it.
Flash back to the Froyo boot loaders - if you do this uncheck auto reboot in odin. Cause if it errors when flashing bootloaders and reboots - you are screwed. If you flash them and it says sucess - you can always hold the power button for 10sec to manully reboot it.
Froyo / Ginger Boot loaders thread
(If you flashed a GB kernel via kernel manager that means you already have the Froyo boot loaders, but the general thinking is if you flash back to JFD it may be a good option to flash the Froyo boot loaders first. I have never done that.)
After you load the Froyo boot loaders then try to flash back to JFD with partition check as intructed here (under #4):
http://forum.xda-developers.com/showthread.php?t=1307637
You can get JFD from above thread too.
Hope it works out.

UPDATE! boot loop went away....now its just froze at the boot screen!...lol fu** my life

holy mother of pearl....i called samsung and they said they would reflash it for FREE.....thanks for all your help moped guy.
the guy just probably wrote the servie order for a reflashing and didnt tell them why.....lol yay for waranties!

Related

Real quick question that I can't figure out

OK, so it has been a while since I have had to flash recoveries etc... Anyway, I Odin'ed back to stock today because I had to go to the Verizon store to talk about my replacement phone so I wanted to have it unrooted. Anyway, now I am trying to get CM7 back on for the time being but I can't get in to CWM. I tried pushing the cwm_recovery_all tar file via ODIN and when I do the three finger boot, it still brings me to the stock recovery and when I hit apply update.zip it fails.
What the heck am I doing wrong? I figured I could just get recovery on there and not have to worry about "rooting" since all the ROM's have that built in anyway.
Any help is appreciated!
Nevermind, I think I figured it out
For those of you that don't know, you have to flash a custom kernel before letting the phone boot after flashing CWM, since the stock kernel will overwrite it on boot
Kevin Gossett said:
For those of you that don't know, you have to flash a custom kernel before letting the phone boot after flashing CWM, since the stock kernel will overwrite it on boot
Click to expand...
Click to collapse
Nope, all you have to do is leave the battery out and as soon as ODIN passes and resets the phone, unplug the phone from the PC so it can't reboot. Then just use the 3 button method to get in to recovery.
Overall it is pretty simple. Here were my steps to get back to CM7 from 100% stock ED04:
1) Push cwr_recovery_3_30_fix (or something like that) tar file in ODIN wit hthe battery pulled
2) Let ODIN finish and say RESET, then PASSED and pull the USB cable out so the phone can't reboot.
2a) Put battery back in
3) Once in red recovery, flash jt's cwm4 fix zip in CM7 thread
4) Flash CM7
5) Flash gapps
6) Profit
I didn't have to flash any custom kernels or anything.
xceebeex said:
Nope, all you have to do is leave the battery out and as soon as ODIN passes and resets the phone, unplug the phone from the PC so it can't reboot. Then just use the 3 button method to get in to recovery.
Overall it is pretty simple. Here were my steps to get back to CM7 from 100% stock ED04:
1) Push cwr_recovery_3_30_fix (or something like that) tar file in ODIN wit hthe battery pulled
2) Let ODIN finish and say RESET, then PASSED and pull the USB cable out so the phone can't reboot.
2a) Put battery back in
3) Once in red recovery, flash jt's cwm4 fix zip in CM7 thread
4) Flash CM7
5) Flash gapps
6) Profit
I didn't have to flash any custom kernels or anything.
Click to expand...
Click to collapse
I'm not trying to be a jerk so don't take this the wrong way, but kevin is right..it is the kernel that re-writes recovery on boot.
The way you are doing it, jt has a kernel included with the rom and that kernel Is whats making your recovery stick when you flash the rom. if you were to odin recovery on Stock phone and just flash a rom w/o a kernel and try to get to recovery again it would be the original stock recovery.
Don't get me wrong what you did is correct, I just want to make sure if you have to do this again, you don't have problems, it is the kernel that is what prevents the stock recovery from coming back.
Sent from my SCH-I500 using XDA App
efan450 said:
I'm not trying to be a jerk so don't take this the wrong way, but kevin is right..it is the kernel that re-writes recovery on boot.
The way you are doing it, jt has a kernel included with the rom and that kernel Is whats making your recovery stick when you flash the rom. if you were to odin recovery on Stock phone and just flash a rom w/o a kernel and try to get to recovery again it would be the original stock recovery.
Don't get me wrong what you did is correct, I just want to make sure if you have to do this again, you don't have problems, it is the kernel that is what prevents the stock recovery from coming back.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
My point is that I was able to boot in to red recovery (2.5.1.x) BEFORE flashing any custom kernel. I understand that CM7 has a kernel built in, but I was able to boot in to both the red recovery and jt's cwm 4 fix (4.0.1.0) before flashing any ROMs/Kernels. I wasn't even rooted (flashing CM7 is what rooted me).
After re-reading what he wrote, the way he says it is correct. I must have read it wrong the first time. So I apologize for saying "Nope." For some reason I read it as if he was saying I had to flash a custom kernel before being able to boot in to any recovery. He is just saying that you can't let the phone fully boot after pushed the recovery (which is what I ended up doing in my steps).
Sorry for the confusion.
No problem...glad you didn't take offense I'm just nearly thinking of all the noobs that are just getting into this kind if stuff and when they read the thread they might be misinformed...
that being said I've been on cm7 for a while and I know not to flash with anything other than the included recovery, I can confirm power button menu gets you to the new blue recovery but if you three finger salute it (done on accident just out of habit) you will get to an older recovery! In my case the old red one....Weird having both on the phone simultaneously, but it's no prob as long as we only use the new recovery to flash anything.
Sent from my SCH-I500 using XDA App

[Q] [TELUS]How do I downgrade from 2.3.3 to 2.2

Ok so today i finally figured out how to root my Samsung Galaxy S Fascinate 3g+(Telus and now as I'm going through trying to install custom roms i see that it only uses 3e and not CWR
Is there any solution to my problem and yes I have been looking around the forums for a almost 3 hours and now have become mildly enraged seeing no support for my phone
well, I have been going through alot of the same stuff with my Telus fascinate too.I don't think im capable of writing a full guide, but I can tell you the basics about how I got to CM7 with a working stable kernel.
First Odin back to stock 2.2
A. Download Odin (attached) and the Telus JL3 stock files http://www.megaupload.com/?d=C3DQ1LZF
B. Open Odin, and put the files in the appropriate boxes
s1_odin_20100512.pit in "PIT"
T959TLJL3-REV03-ALL-low-CL763100.tar.md5 in "PDA"
T959TLJL3_FROYO_Phone-CL763100.tar in "PHONE"
SGH-T959D-CSC-TLSJL3.tar.md5 in "CSC"
C. Boot into download mode by turning phone off, then holding "Volume Down" while connecting the phone to the computer
D. The first "ID:COM" box should turn yellow and show a numerical COM port
E. Click "Start" and wait for it to finish and reboot, and unplug the phone after the yellow box turns green and says "PASS"
next
http://www.megaupload.com/?d=GJCCIU4N
Odin this file using the "pda" part of odin. Let your phone boot up and go through the voodoo lagfix. Once your booted up, it might be a good time too root your phone again.
also this might not be needed, but if you get no service once your on your custom rom.this can help.
So while still on stock, download an app called "nitrality" perform an efs backup. Then copy the "insanity" folder from your phone to somewhere safe.
ok, now that your rooted and have a cwm recovery, reboot into recovery and flash the custom kernel zip found here
http://forum.xda-developers.com/showpost.php?p=18268484&postcount=3865
CM7_SGS_20111009_NEO_17-voodoo-col_BLN.zip is what I use
pull battery and reboot into recovery once more. From there flash your rom, CM7 in my case.
http://cm-nightlies.appspot.com/?device=galaxysmtd
After installing the rom, again reflash the platypus kernel, and your all good to go.
If you have no service, then put that "insanity" folder on your phone, install nitrality and perform the efs restore.
Sorry for the all over the place guide.
fromthestars said:
well, I have been going through alot of the same stuff with my Telus fascinate too.I don't think im capable of writing a full guide, but I can tell you the basics about how I got to CM7 with a working stable kernel.
First Odin back to stock 2.2
A. Download Odin (attached) and the Telus JL3 stock files http://www.megaupload.com/?d=C3DQ1LZF
B. Open Odin, and put the files in the appropriate boxes
s1_odin_20100512.pit in "PIT"
T959TLJL3-REV03-ALL-low-CL763100.tar.md5 in "PDA"
T959TLJL3_FROYO_Phone-CL763100.tar in "PHONE"
SGH-T959D-CSC-TLSJL3.tar.md5 in "CSC"
C. Boot into download mode by turning phone off, then holding "Volume Down" while connecting the phone to the computer
D. The first "ID:COM" box should turn yellow and show a numerical COM port
E. Click "Start" and wait for it to finish and reboot, and unplug the phone after the yellow box turns green and says "PASS"
next
http://www.megaupload.com/?d=GJCCIU4N
Odin this file using the "pda" part of odin. Let your phone boot up and go through the voodoo lagfix. Once your booted up, it might be a good time too root your phone again.
also this might not be needed, but if you get no service once your on your custom rom.this can help.
So while still on stock, download an app called "nitrality" perform an efs backup. Then copy the "insanity" folder from your phone to somewhere safe.
ok, now that your rooted and have a cwm recovery, reboot into recovery and flash the custom kernel zip found here
http://forum.xda-developers.com/showpost.php?p=18268484&postcount=3865
CM7_SGS_20111009_NEO_17-voodoo-col_BLN.zip is what I use
pull battery and reboot into recovery once more. From there flash your rom, CM7 in my case.
http://cm-nightlies.appspot.com/?device=galaxysmtd
After installing the rom, again reflash the platypus kernel, and your all good to go.
If you have no service, then put that "insanity" folder on your phone, install nitrality and perform the efs restore.
Sorry for the all over the place guide.
Click to expand...
Click to collapse
EDIT: so at the http://cm-nightlies.appspot.com/?device=galaxysmtd what did you mean my CM7 in your case
EDIT2: Ok so now that platypus is installed my phone is now looping from the SGH screen to Platypus and then for about a second it shows recovery mode
I used the stable RC of cm7. galaxysmtd
I apologize for the boot looping, im not overly technical. Just, those are the steps that got me up and running. Maybe try the other Kernel on that thread?
No its alright. I fixed to looping by flashing the stock froyo. Now i just need to figure out how to not have this happen again
fromthestars said:
I used the stable RC of cm7. galaxysmtd
I apologize for the boot looping, im not overly technical. Just, those are the steps that got me up and running. Maybe try the other Kernel on that thread?
Click to expand...
Click to collapse
which one do i click?
EDIT:Nevermind got everything working Thanks

[Q] Help, flashed wrong kernel on SGS2

So this is the case, I had a rooted sgs2 running on MIUI 2.3.16 and brightly decided to flash the kernel into siyah.
Obviously that didnt work out too well, and I ended up in a situation where the phone stucks at startup showing the sgs2 logo, and wont budge from there.
I have no clue what was the kernels "version". Is there anything that can be done?
Allready tried to search the forums, but didnt find a similar situation.
Boot into recovery & do a factory reset. If that doesn't work, reflash Miui which will reinstate the Miui kernel.
If you can't get into recovery, reflash stock firmware in Odin, CFRoot the phone, then reflash Miui.
I'm assuming you should still be able to enter cwm/recovery... just go in to that and re-flash miui
Sent from my GT-I9100 using Tapatalk
zample87 said:
So this is the case, I had a rooted sgs2 running on MIUI 2.3.16 and brightly decided to flash the kernel into siyah.
Obviously that didnt work out too well, and I ended up in a situation where the phone stucks at startup showing the sgs2 logo, and wont budge from there.
I have no clue what was the kernels "version". Is there anything that can be done?
Allready tried to search the forums, but didnt find a similar situation.
Click to expand...
Click to collapse
You should find out what kernel it MIUI used, else you can end up
try very many different hehe.
But no panic, I guess you have Odin on youre pc?
Just start phones downloadmode by volume down-home, poweron.
Connect to usb cable, fire up Odin, and flash kernel (PDA in Odin)
Good luck man
Cant get to recovery, Only thing that i can do is to use Odin, how do i get back to stock kernel, or, even better, anyone know the MIUI kernel?
Flash stock in Odin as I said, then CFRoot it. If you've got a Nandroid (CWM) backup, you should then be able to restore that rather than flash Miui. If not, flash Miui in CWM. Stock roms/instructions for flashing same can be found here, if links don't work search for stock firmware on Samfirmware.com.
What Siyah kernelndid you flash? I flashed beta6 over the latest MIUI and it just went to a black screen.
Just hold down the power button with vol up + home. It'll eventually boot to recovery where you can flash MIUI again.
Sent from my GT-I9100
odin -> bootloader flash -> wait for logo battery out -> odin flash stock -> odin cf root -> recovery flash ur miui and kernel again
Issue solved!
Thankyou for you all for your quick replies and help!
Good How did you fix it ?
managed to get to cwm recovery after flashing one of the cf-root kernels, and from there on, just flashed miui all over again...
Ahhh OK. Cool. Glad you got it sorted

Help...I am stuck on 2.2 ROM

Here is the story
Last week I was running Cm10 port with datadata without any issues. In a bad time I saw a new kernel version and I flashed that. After flash I got boot loop so I tried to go into recovery but to add to my bad luck recovery didn't work. So I thought Odin is the only option now. I odin back to stock and phone started working. Now time comes for more bad things to me
Day 1
I installed the CWR and tried to install SLIM 4.2 which was on my SD card. Install went fine and system booted. I soon as I booted I saw my SD card got formatted and I lost my IMEI with EFS folfer empty. I tried to restore EFS from backup but it didnt work so I odin back to JFD which gave my IMEI back. I tried slim again and same thing, again lost IMEI.
I thought lets try with different kernel, I flashed subzero kernel and rebooted into recovery again. Flashed zip and all went fine. Rebooted system after flash but system again went back to recovery. Flashed zip 2-3 time but same recovery again and again( Like a recovery loop)
Here I odin back to JFD and also flashed gingerbread bootloaders to make my life easy.
Day 2
Downloaded biwinning redux v1 which is 2.2.1 ROM. Install went smooth and I was able to use it.
Now I got new red recovery and it automatically enabled voodoo.
Here I tried to install HellyBean and got status 7 error. So I tried to flash devil intial package but status 7 again. So I flashed icy glitchy kernel and install went fine.
As soon as I reboot system all I had was small orange bar at the bottom and nothing else.
It was like I only have kernel but no system. Rebooted into recovery and flashed files again. Still same thing. So I flashed initial package on top of icy glitch and again install went fine. Phone got recovery loop again.
Damm...ODIN back to JFD and installed biwinning redux again as nothing else seems to be working for me.
Day 3
ODIN back to JFD and flashed icy glich kernel.
Flashed latest CM9 build. As soon as I flashed it, phone rebooted twice with some fast scrolling text. After that it keeps on rebooting and seems like its trying to find some file as I can see some red exclamation sign when it reboots.
Odin devil kernel tar file and flashed files again. But after cm9 files I just get black screen, waited for 10 minutes and nothing.
I odin again to JFD and restored nandroid of biwinning.
So I am again on 2.2.1 rom and seems like I am stuck on it.
Please suggest me what should I do....and I have already tried more then what I told.
Right now I am on biwinning redux v1(2.2.1 rom) with vodoo enabled and Gingerbread bootloaders
Go back to stock, flash straight from stock one of CM9 nightlies and then you will be able to flash to JB
Sent from my SGH-T959 using xda app-developers app
mikka06 said:
Go back to stock, flash straight from stock one of CM9 nightlies and then you will be able to flash to JB
Sent from my SGH-T959 using xda app-developers app
Click to expand...
Click to collapse
Already tried that. Phone keeps rebooting after flash...script keeps looking for something and gives me loop.
You have to flash twice from stock to CM9. After that you should be good
Sent from my SGH-T959 using xda app-developers app
mikka06 said:
You have to flash twice from stock to CM9. After that you should be good
Sent from my SGH-T959 using xda app-developers app
Click to expand...
Click to collapse
Can you please please give me step by step instructions from stock. I just dont want to odin again...already did like 10 times and now I am at breaking point.
Ok, so flash back to stock. Reroot your phone,so under recovery hit "reinstall packages" (once or twice, i always have to do it twice). Once you're in the new recovery flash any of CM9 nightlies. You will have some bootloops due to the recovery mismatch. Don't panic, take out the battery, put it back and go again in the recovery (vol up+vol down+power button if you're on froyo bootloaders or vol down+power button for gb bootloaders). Once you're in the recovery flash CM9. Once on ICS you should flash JB.
mikka06 said:
Ok, so flash back to stock. Reroot your phone,so under recovery hit "reinstall packages" (once or twice, i always have to do it twice). Once you're in the new recovery flash any of CM9 nightlies. You will have some bootloops due to the recovery mismatch. Don't panic, take out the battery, put it back and go again in the recovery (vol up+vol down+power button if you're on froyo bootloaders or vol down+power button for gb bootloaders). Once you're in the recovery flash CM9. Once on ICS you should flash JB.
Click to expand...
Click to collapse
Trying ..thanks
Update : Everything went smooth. I am on Slim Bean now
So the problem was when I got bootloops with cm9 , I was odin back but instead I had to reboot into recovery and flash again without changing any kernel. When I was getting bootloops I was installing kernel again.
Thank you for all the help
Haha good times .
Sent from my SGH-T959 using xda premium

[Q] Phone stuck in boot loop after returning to stock

Hey all,
I recently got a Nexus 4 and gave my trusty Vibrant to a buddy of mine. However, in the time they had it, they really managed to mess it up(it was running the latest cm10 nightly and semaphore kernel when I handed it over). I got the phone back and have used Odin to flash it back to stock with the original pit and PDA file. Now, the phone simply flashes the I-9000 bootloader splash screen over and over(unless plugged into the PC, then it flashes the loading circle over and over). Any one have any ideas? Normally I would flash stock to resolve this, but flashing stock is the cause of my problem now.
EDIT: I should mention, I can still get to download mode, but not any kind of recovery.
I would just flash a semaphore .tar in Odin, boot directly to recovery afterwards and flash a ROM.
Sent from my SCH-I535 using xda premium
When returning to stock (JFD?) did you repartition it?
Ding!Ding! Repartitioning might be it. Also reflash GB BLers after flashing your first ROM to get rid of the GTi9000 boot splash
Hey guys, thanks for the responses. I've been away, but I've now tried your suggestions. I flashed the semaphore kernel via Odin, and while it no longer boot loops, it won't go into any kind of recovery manager and will simply sit on the Semaphore logo. I tried flashing a gingerbread bootloader via odin as well, but it didn't help.
As for returning to stock. yes I am indeed repartioning it, but it still doesn't boot. If I return to stock form the Semaphore kernel, it beings bootlooping again.
Don't check repartition and see if it boots.
After flashing semaphore did you try the button combo to recovery? If you flashed GB boots it is no longer vol up and vol down +power.
Recovery is power and vol down, DL mode is power vol up.
Sent from my GT-P5113 using xda premium
samsgun357 said:
Don't check repartition and see if it boots.
After flashing semaphore did you try the button combo to recovery? If you flashed GB boots it is no longer vol up and vol down +power.
Recovery is power and vol down, DL mode is power vol up.
Sent from my GT-P5113 using xda premium
Click to expand...
Click to collapse
Yes, I tried it with button combo, I even tried all possible combinations in desperation when it didn't work. I can get it into download mode, but nothing else. I just tried flashing without repartioning, but it resulted in the same bootloop.

Categories

Resources