I flashed Devil kernel over my Paranoid Android 2.18 rom, and it booted into devil recovery, with lots of errors. It wouldn't let me flash my previous rom, so I restored a previous jb "boot" [recovery] from a nandroid [advanced restore], then it went into a bootloop.
I tried heimdall, flashing the cwm boot.img from the parandoid android rom [extracted from .zip], still got the recovery bootloop. Then I tried repartitioning with atlas2.2.pit, and thought I was out of the woods when it booted into cwm 6.x recovery.
Then I wiped data and flashed my PA rom again, and this time I had a black screen [yes I know it's hard to see a black screen on SAMOLED screens, but it was dark and I could see the screen coming on and off] bootloop. No SAMSUNG logo, just the screen turning off and on again.
Download mode didn't work until I took out the battery, so I'm gonna try Odin. only thing is I have to reboot into windows since I use linux, but I'm wondering if anyone knows what happened here?
lucky I have a recent TiBa..
If you booted into recovery you should have odined instead of trying too reflash cwm that's just gonna srew it more because its the kernel messing it up not the recovery. Any way get the full stock files for your device put them in Odin get the Atlas pit put it in there and check repartician and when its done flash it in Odin again with repartician not checked hope it works
Sent from my SCH-I500 using Xparent Skyblue Tapatalk 2
bbrad said:
If you booted into recovery you should have odined instead of trying too reflash cwm that's just gonna srew it more because its the kernel messing it up not the recovery. Any way get the full stock files for your device put them in Odin get the Atlas pit put it in there and check repartician and when its done flash it in Odin again with repartician not checked hope it works
Sent from my SCH-I500 using Xparent Skyblue Tapatalk 2
Click to expand...
Click to collapse
Yeah I got it fixed by odining eh03 then CWM and flashing jb ROM..
The problem was I didn't have access to Odin right away so I was trying to fix it with cwm.
Related
Well, I was previously running Comm rom, and i decided to switch to CM7 7/13
This didn't go so well. I Odin'd DL09 with atlas and repartitioned then installed Cmw and still Status 7 when I try to install. Then I tried installing 7/4 and it would just say something like "Checking BML" Or something, i forgot... and it would just reboot into cwm. I was running JT's cwm fix, and i tried with cwm all... I don't know what to do. Now my fascinate won't install comm rom, and every rom install just leads up to booting up in cwm.. no samsung logo.. Help??
Edit: Phone is now in "Manual mode"
i guess samsung recovery? but it wont boot. It just reboots into the same recovery after i press "reboot system now"
please? :'(
Just do this
after fighting with my phone yesterday trying to get it running this is what i did
Step one may be unnecessary but this is what i did.
1) Odined ED01 image let it boot. then Odind CWM3 3 finger salute. Flashed CommRom 2.0 when that was done i booted into CWM and disabled the VooDoo rebooted when the conversion was done.... i did step 2
2) in the OP of cm7 flash or odin the cwm
then flash the 07/04...
once that is up use the shutdown menu to access the Orange [cwm 4.0] cwm.
if you do a three finger salute it takes you to the RED [CWM 3.0] cwm.
Then flash the updates.
And suspect there was an issue with the Voodoo even though it said it was disabled. Good Luck
xwhofarted said:
Just do this
after fighting with my phone yesterday trying to get it running this is what i did
Step one may be unnecessary but this is what i did.
1) Odined ED01 image let it boot. then Odind CWM3 3 finger salute. Flashed CommRom 2.0 when that was done i booted into CWM and disabled the VooDoo rebooted when the conversion was done.... i did step 2
2) in the OP of cm7 flash or odin the cwm
then flash the 07/04...
once that is up use the shutdown menu to access the Orange [cwm 4.0] cwm.
if you do a three finger salute it takes you to the RED [CWM 3.0] cwm.
Then flash the updates.
And suspect there was an issue with the Voodoo even though it said it was disabled. Good Luck
Click to expand...
Click to collapse
That's the thing... It wont boot to anything i install on it.. But it sure as hell boots to ANY cwm i install... and it also boots to normal recovery in the absence of a cwm....
Can you get back to stock using odin? If you can try flashing a custom kernel after you flash the cwm recovery.
Sent from my SCH-I500 using XDA App
garywojdan81 said:
Can you get back to stock using odin? If you can try flashing a custom kernel after you flash the cwm recovery.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
I can flash the DL09 with odin... but ive been there... 20 times. I havent tried a kernel but it probably wouldnt work seeing as it only boots back into cwm. I'm desperate...
EDIT: flashed EB01 voodoo... still boots into CWM... omg.
jamespweb1503 said:
I can flash the DL09 with odin... but ive been there... 20 times. I havent tried a kernel but it probably wouldnt work seeing as it only boots back into cwm. I'm desperate...
EDIT: flashed EB01 voodoo... still boots into CWM... omg.
Click to expand...
Click to collapse
Have you tried flashing the official vzw eb01..(not dl09 and not eb01voodoo) file with pit and repartition checked? If not do that and let it boot completely. You need to do this to make sure your ext4 partition is formatted to remove voodoo.
After you odin official vzw eb01 with the pit file and repartition checked let it boot fully.then odin 3-30 recovery and immediately boot to cwr...if it boots up fully you will have to re odin recovery.
At this point wipe everything and flash com rom 2.0 that will give you root, recovery and the rom....from there you can go to com rom 2.1or whatever your want but your phone should be up and running
Sent from my SCH-I500 using XDA App
efan450 said:
Have you tried flashing the official vzw eb01..(not dl09 and not eb01voodoo) file with pit and repartition checked? If not do that and let it boot completely. You need to do this to make sure your ext4 partition is formatted to remove voodoo.
After you odin official vzw eb01 with the pit file and repartition checked let it boot fully.then odin 3-30 recovery and immediately boot to cwr...if it boots up fully you will have to re odin recovery.
At this point wipe everything and flash com rom 2.0 that will give you root, recovery and the rom....from there you can go to com rom 2.1or whatever your want but your phone should be up and running
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
I love you <3
My phone crashed this morning after running the daily OMFGB from the 31st for a few days. I tried to restart, it won't go past the Glitch Kernel screen. When I go into recovery, I am greeted with this message:
ClockwordMod Recovery v4.0.1.0
E: can't mount /cache/recovery/command
E: can't mount /cache/recovery/log
E: can't open /cache/recovery/log
E: can't mount /cache/recovery/last_log
E: can't open /cache/recovery/last_log
wiping data, did not help. reflashing the rom and kernel did not help. I still can't start the phone. What are the steps I need to take to fix this as I am currently not able to use my phone at all.
alemondemon said:
My phone crashed this morning after running the daily OMFGB from the 31st for a few days. I tried to restart, it won't go past the Glitch Kernel screen. When I go into recovery, I am greeted with this message:
ClockwordMod Recovery v4.0.1.0
E: can't mount /cache/recovery/command
E: can't mount /cache/recovery/log
E: can't open /cache/recovery/log
E: can't mount /cache/recovery/last_log
E: can't open /cache/recovery/last_log
wiping data, did not help. reflashing the rom and kernel did not help. I still can't start the phone. What are the steps I need to take to fix this as I am currently not able to use my phone at all.
Click to expand...
Click to collapse
Same thing happened to me yesterday..the only way I got my phone working again was to odin eb01 with the atlas 2.2..reboot fully...I then tried to go back to cm7 and got the same message and the only way I was about to fix it was to flash the com rom 2.0 obviously wipe everything before..let that boot and tried to flash cm7 with the recovery from com rom....still same message...i had to odin otb3.x.x.recovery... Download times infinity's recovery zip and flash that in otb recovery, then reboot recovery so I had ti's purple recovery...wipe everything and flash cm7...and success! I used the 7/17 build cause I didn't want nightly then rebooted from power button menu and flashed glitch and gapps.
Sent from my SCH-I500 using XDA App
Oh my goodness, sounds like something is really busted. Do you think it is OMFGB related? Yikes.
I have same thing, but I cant get the phone to show in download mode to odin anything
Same here. I'm now stuck in a boot loop. I can't even restore a backup.
Edit: Just tried to do a restore and the MD5 Sums don't match. I've had to do Odin reset three times today.
I think I might do Vodoo and try to restore that way. I will report back.
alemondemon said:
Oh my goodness, sounds like something is really busted. Do you think it is OMFGB related? Yikes.
Click to expand...
Click to collapse
No I don't think its omfgb related cause I've never ran that rom but I do think it has something to do with all the different recoveries we have floating around and so many different builds with different formats things are bound to get screwed up...my problem came from forgetting to wipe before flashing a different kernel and got me stuck in a boot loop.
Sent from my SCH-I500 using XDA App
I've had this problem ever since I got my Fascinate and tried to get CM7 on it. (2 days ago) I was always able to flash new builds just fine if I managed to get into the orange recovery and not the CM7 one. I believe the one I used was the one on ROM Manager.
This is kinda upsetting...
Hyphnx said:
Same here. I'm now stuck in a boot loop. I can't even restore a backup.
Click to expand...
Click to collapse
Its not the quickest but it should get you back...odin eb01 with the atlas 2.2pit...and reboot. Then odin recovery boot immediately to recovery via 3 finger salute...wipe everything and flash the rom you want...I've had good luck with cwm 3-30 fix all or otb 3x.x.x....if you want to go to cm7 odin the fixed recovery in jt's post and flash cm7 from that recovery....the sticky in the dev section...going from cm7/miui/gb to any other rom should give you some good info and instructions
Sent from my SCH-I500 using XDA App
efan450 said:
Its not the quickest but it should get you back...odin eb01 with the atlas 2.2pit...and reboot. Then odin recovery boot immediately to recovery via 3 finger salute...wipe everything and flash the rom you want...I've had good luck with cwm 3-30 fix all or otb 3x.x.x....if you want to go to cm7 odin the fixed recovery in jt's post and flash cm7 from that recovery....the sticky in the dev section...going from cm7/miui/gb to any other rom should give you some good info and instructions
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
We are having problems with the recovery he posted in his post.
Tried CWM-Recovery-All, turned my phone into muffed up phone. UGH!
Sorry for the double post. I've had to Odin 2 more times which makes it a total of 5 today. I used all the recoveries that are available. One at a time and they all end in the same way.
Hyphnx said:
Sorry for the double post. I've had to Odin 2 more times which makes it a total of 5 today. I used all the recoveries that are available. One at a time and they all end in the same way.
Click to expand...
Click to collapse
So what rom are you running now?
Sent from my SCH-I500 using XDA App
efan450 said:
Same thing happened to me yesterday..the only way I got my phone working again was to odin eb01 with the atlas 2.2..reboot fully...I then tried to go back to cm7 and got the same message and the only way I was about to fix it was to flash the com rom 2.0 obviously wipe everything before..let that boot and tried to flash cm7 with the recovery from com rom....still same message...i had to odin otb3.x.x.recovery... Download times infinity's recovery zip and flash that in otb recovery, then reboot recovery so I had ti's purple recovery...wipe everything and flash cm7...and success! I used the 7/17 build cause I didn't want nightly then rebooted from power button menu and flashed glitch and gapps.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
".i had to odin otb3.x.x.recovery... Download times infinity's recovery zip and flash that in otb recovery"
can you link to that? Is it the voodoo one form here:
http://forum.xda-developers.com/showthread.php?t=1046905
and which is the recovery zip that u flashed from otb recovery? can you link to them, i don't wanna screw this up any more than i already have.
alemondemon said:
".i had to odin otb3.x.x.recovery... Download times infinity's recovery zip and flash that in otb recovery"
can you link to that? Is it the voodoo one form here:
http://forum.xda-developers.com/showthread.php?t=1046905
and which is the recovery zip that u flashed from otb recovery? can you link to them, i don't wanna screw this up any more than i already have.
Click to expand...
Click to collapse
Yup...boot into the otb 3x.x.x recovery and flash the times infinity.zip and then select reboot recovery while in cwm and it should go from the otb one to the times infinity one...at that point wipe everything and flash cm7 build 7/17..not the nightly....once your on the mtd build you can flash the nightly if you wanted
From the power button menu
Sent from my SCH-I500 using XDA App
Edit: I suppose you could just odin times infinity's recovery...I just happened to have the zip on my sd handy so thats why I did it that way...it was that recovery that worked so you could odin it if you wanted it's in the link you posted try flashing it from ti's recovery..I just got there a little differently
Any suggestions if you cant get odin to recognize the phone? Ive tried three Win7 machines both x86 and x64 and three different cables...ALL of them say unknown device. Ive tried pointing to both the Sammy drivers and the nexus ones with no luck.
My phone was revived by simply doing the atlas odin method. I then flashed a fully rooted image...and from there on it's child's play. With that said, I can't get into download mode now, to odin things. What could be causing that? Not, very urgent, because at the moment the phone is running like it should
Thanks so much!
OK so I copied infinity times cwm red to phone and applied that. I still got message about cache. I ran the cwm4 from recovery and now Im back to square one again. I can try to install a ROM, but it boot loops everytime. Can my phone be revived w/o odin? Do I need an updated update.zip file?
humblewarfare said:
OK so I copied infinity times cwm red to phone and applied that. I still got message about cache. I ran the cwm4 from recovery and now Im back to square one again. I can try to install a ROM, but it boot loops everytime. Can my phone be revived w/o odin? Do I need an updated update.zip file?
Click to expand...
Click to collapse
unfortunately a boot loop normally requires odin...use the eb01 tar and the atlas 2.2pit and your phone will be back up and running
From there I would flash com rom and reboot then if you wanna take a stab at cm7...try and flash it with the com rom recovery...if it doesn't work you can just try odin'ing different recoveries as long as you don't let the phone boot fully you can simply pull the battery and try to odin a different recovery.try the one from com rom, the 3-30 fix all, ti's recovery, or jt's fixed recovery...I don't know where I got the file but I also have a recovery named fixed 3 x.x for cm7 but I came remember where I got it.it is important that you let eb01 sit for a few minutes after booting and also let com rom sit for a few minutes after flashing also...I just skipped all the setup stuff to get the main screen and then pulled the battery and started flashing
Sent from my SCH-I500 using XDA App
humblewarfare said:
Any suggestions if you cant get odin to recognize the phone? Ive tried three Win7 machines both x86 and x64 and three different cables...ALL of them say unknown device. Ive tried pointing to both the Sammy drivers and the nexus ones with no luck.
Click to expand...
Click to collapse
I'm running vista home edition...if it matters and I'm using odin v.1.7 try the samsung generic drivers also.but once I'm on cm7 my pc says it doesn't recognize my phone but if I put it in download mode and hook up odin recognizes it...so I'm not sure on that one
Sent from my SCH-I500 using XDA App
alemondemon said:
My phone was revived by simply doing the atlas odin method. I then flashed a fully rooted image...and from there on it's child's play. With that said, I can't get into download mode now, to odin things. What could be causing that? Not, very urgent, because at the moment the phone is running like it should
Thanks so much!
Click to expand...
Click to collapse
Try holding the down button while you plug into your wall charger then just move it to your pc...if that doesn't work...clean the contacts with rubbing alcohol...with the phone off.at worse case there is a jig you can manually force download mode...you can buy or make them
Sent from my SCH-I500 using XDA App
I can't escape TWRP!
My setup is this:
ROM: THS build 10
Kernel: ICYGlitch v14
Recovery: TWRP (included with ICYGlitch)
Recently, I wanted to flash ParanoidAndroid. I rebooted into TWRP via the power menu, made a backup, and tried to flash. It gave the error E: signature verification failed. Later, I tried turning off signature verification, but then it gave me another error. I then tried to flash cwm4_fixed_for_cm7, but it gave me the same error. Then I tried flashing the recovery through ODIN. It said it succeeded, but it still loads TWRP as the recovery. Help! I can't escape!
P.S. I know my way around the Fascinate, I'm not a complete noob.
try flashing cm7, then back to ICS, ...if all else fails odin back to stock start over.
Maybe
That would work, but I'd rather keep the Glitch kernel and stay on THS than start over. And there must be a way to change the recovery included with Glitch?
Let us know how that turns out for you. Good luck.
Sent from my SCH-I500 using Tapatalk
MultipleMonomials said:
That would work, but I'd rather keep the Glitch kernel and stay on THS than start over. And there must be a way to change the recovery included with Glitch?
Click to expand...
Click to collapse
flash a older version of glitch that still utilizes cwm recovery. check my kernels section of the guide.
That would work except for the fact that I cannot flash anything from TWRP.
MultipleMonomials said:
That would work except for the fact that I cannot flash anything from TWRP.
Click to expand...
Click to collapse
odin cwm4 fixed for cm7, then three finger and flash away.
Wait. Doesn't three-fingering on a MTD filesystem bootloop you?
at this point just odin back to stock and start over
shelby04861 said:
Let us know how that turns out for you. Good luck.
Sent from my SCH-I500 using Tapatalk
Click to expand...
Click to collapse
Sent from my SCH-I500 using Tapatalk
I figured it out. I was able to flash an older version of Glitch with CWM recovery.
How did you flash an older version of glitch in cwm if you were stuck in twrp? I though you couldnt flash anything. I am confused???
Sent from my SCH-I500 using Tapatalk
Sorry. I meant TWRP. Here is the procedure that I used. I don't know if it is necessary, but it worked.
1. make a nandroid
2. restore to stock
3. ODIN cwm
4. install THS build 1
5. install THS 10 (substitute whatever ROM you're using)
6. install newest Glitch (with TWRP)
7. restore nandroid
8. install older, CWM glitch
I think this works because nandroids don't restore the recovery partition.
I was having instability with the older Glitch version, so I flashed the newer version again, and I can still flash stuff.
Okay. I got it now. I thought the whole reason you didn't want to start over was because you didn't have a backup of your current setup. That is why people were saying that you were going to have to start over.
Glad it worked out.
Sent from my SCH-I500 using Tapatalk
I've tried flashing recovery via Odin and CWM Recovery and it will reboot into recovery just fine. However, when I let it reboot into android, turn it off, and then go back into recovery, CWM is gone. The phone, however, stays rooted.
Any idea what could be wrong or how to fix this?
Secondly, if I can get into CWM immediately after flashing, is it safe to flash a new ROM at that point or do I need to get CWM to stick first?
Anyone? Any suggestions at all will be appreciated
No1ustad said:
I've tried flashing recovery via Odin and CWM Recovery and it will reboot into recovery just fine. However, when I let it reboot into android, turn it off, and then go back into recovery, CWM is gone. The phone, however, stays rooted.
Any idea what could be wrong or how to fix this?
Secondly, if I can get into CWM immediately after flashing, is it safe to flash a new ROM at that point or do I need to get CWM to stick first?
Click to expand...
Click to collapse
Sure... You can flash a rom immediately following the flash of cwm.... Did you also install busy box?
Which cwm are you trying to use? 5.8.4.7 seems to do me good....?
Sent from my SPH-L710 using xda premium
Before your phone boots after installing cwm in Odin do a battery pull then boot into recovery （Volume Up+Home+power) then flash your superuser/root package. It will stick then.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
Naddict said:
Sure... You can flash a rom immediately following the flash of cwm.... Did you also install busy box?
Which cwm are you trying to use? 5.8.4.7 seems to do me good....?
Sent from my SPH-L710 using xda premium
Click to expand...
Click to collapse
I tried using that CWM version as well as an older one. Both work and I can get busy box and superuser installed once it boots up. But when I power down and try to go back into recovery, CWM is gone. I do get to keep root though.
iiApotheosis said:
Before your phone boots after installing cwm in Odin do a battery pull then boot into recovery （Volume Up+Home+power) then flash your superuser/root package. It will stick then.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
Click to expand...
Click to collapse
I tried unchecking the auto-reboot button on Odin 4 and 7, and going that route. Both allow me to get into CWM, where I try to flash the recovery v5.zip. Still doesn't stick unfortunately.
My flash counter is up to about 10 now, trying to get CWM to stick..
No1ustad said:
I've tried flashing recovery via Odin and CWM Recovery and it will reboot into recovery just fine. However, when I let it reboot into android, turn it off, and then go back into recovery, CWM is gone. The phone, however, stays rooted.
Any idea what could be wrong or how to fix this?
Secondly, if I can get into CWM immediately after flashing, is it safe to flash a new ROM at that point or do I need to get CWM to stick first?
Click to expand...
Click to collapse
Flashing 5.8.4.7 after renaming it to recovery.img with mobile odin did the trick for me and it stuck.
I used this guide below
http://forum.xda-developers.com/showthread.php?p=28687877
Sent from a Third Galaxy
cbond007 said:
Flashing 5.8.4.7 after renaming it to recovery.img with mobile odin did the trick for me and it stuck.
I used this guide below
http://forum.xda-developers.com/showthread.php?p=28687877
Sent from a Third Galaxy
Click to expand...
Click to collapse
Thanks everyone. I used CWM toolkit, reflashed the stock recovery, then used odin 3.07 to re-flash CWM 5.5.0.4 and it stuck.
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