Flashed CM9 to experiment with it and see how it ran, prior to doing so made a backup of current setup (unnamed 2.2.1 w/ siyah kernel). After flashing to CM9 and playing around a bit i was going to revert back to my original setup. Tried flashing back and now I am unable to even get to CWM Recovery, or Download Mode. It will boot to the SGS2 screen and then just go black no matter what I do. It is still recognized in Odin so I was thinking I'm going to have to revert back to stock and just flash it back afterwards. Any ideas before I proceed?
AK40Nine said:
Flashed CM9 to experiment with it and see how it ran, prior to doing so made a backup of current setup (unnamed 2.2.1 w/ siyah kernel). After flashing to CM9 and playing around a bit i was going to revert back to my original setup. Tried flashing back and now I am unable to even get to CWM Recovery, or Download Mode. It will boot to the SGS2 screen and then just go black no matter what I do. It is still recognized in Odin so I was thinking I'm going to have to revert back to stock and just flash it back afterwards. Any ideas before I proceed?
Click to expand...
Click to collapse
Flash back to stock. Strange - you say you can't get into download mode, but Odin recognizes it?
Ok, finally got into DL mode and flashed a stock kernel from Entropy's post. Now i'm faced with it booting to the ATT splash screen and it just loops that screen infinitely. I'm still unable to access recovery mode to wipe data/cache or anything like that. This is becoming frustrating and I'm not quite able to wrap my head around why after flashing stock that I'm unable to boot into the phone beyond the splash screen. Am I using the wrong stock fw or something? Here's the link to the one i used.
http://forum.xda-developers.com/showthread.php?t=1286432
From my experience it's the wrong SPL/radio combo.
No matter what I do, I'm stuck up to that point.....I've tried a few different stock flash packages through Odin to no avail, same result every time. I know i'm probably doing something wrong or I'm missing something here, its not bricked I do know that so its not like i'm dead in the water here. Any ideas would be better than where I'm at currently.
BeenAndroidized said:
From my experience it's the wrong SPL/radio combo.
Click to expand...
Click to collapse
There is no SPL on the GSII, and a bad radio will only screw up calls/cell data.
To the OP - exactly how did you flash CM9? CWM or some kanged-up Odin build?
Through CWM, everything worked fine but when I was using CM9 my back button and serach button weren't working, probably erroneous to this situation. this is just messing me all up that I'm able to boot up til the splash and then it just loops it over and over, its making me think that the FW is having issues loading or something.
Problem solved finally. Something must have changed after this last flash attempt because now I was able to get into CWM of all things and recover my old backups. Nice little adventure that was. Thanks guys for the help!
Entropy512 said:
There is no SPL on the GSII, and a bad radio will only screw up calls/cell data.
To the OP - exactly how did you flash CM9? CWM or some kanged-up Odin build?
Click to expand...
Click to collapse
Understood. Coming from G1 I know it's different.
Sent from my SAMSUNG-SGH-I777 using XDA App
Related
This is my first time flashing a new ROM. I decided to go with the stock Froyo ROM. And that went pretty smoothly.
I did the Titantium Backup to restore some of the apps I wanted back. However some settings didn't seem to come over, even though I selected to backup app and system settings. Examples included my phone contacts and my WinAmp playlists (songs are still there).
Anyway, that isn't so much the reason for this topic though. I did a Nandroid backup before and decided to do a restore of that backup. I initiated it from the Rom Manager and got into the Clockwork Recovery and saw it restoring. All appeared fine.
But when the phone rebooted, it is now stuck at the "Vibrant" screen. Has been stuck there for 15-20 minutes now.
I've been looking around. Is the problem because I went from 2.2 back to a 2.1 backup?
Hahaha I had that problem a few days ago, just flash back to stock with odin. Best to try a different rom....
Sent from my SGH-T959 using XDA App
Starting to think the phone might be bricked. Can't get into recovery mode or download mode. Always immediately comes back to the Vibrant screen. Pulled the battery. Didn't help.
Did you try holding down the volume buttons while putting the battery back in? Had a bit of a brick yesterday and that put it straight into download mode without even showing the vibrant logo.
DPCerberusBlaze said:
Did you try holding down the volume buttons while putting the battery back in? Had a bit of a brick yesterday and that put it straight into download mode without even showing the vibrant logo.
Click to expand...
Click to collapse
Thank you! That did the trick. I put the stock Froyo back on via Odin now and am back up again. Whew, Christmas is saved! Thanks.
Try Eugene Ginger Clone is pretty face...I'm currently running Team Whiskey Nero Beta 3...noticed a couple bugs nothing major
Sent from my SGH-T959 using XDA App
Ravynmagi said:
This is my first time flashing a new ROM. I decided to go with the stock Froyo ROM. And that went pretty smoothly.
I did the Titantium Backup to restore some of the apps I wanted back. However some settings didn't seem to come over, even though I selected to backup app and system settings. Examples included my phone contacts and my WinAmp playlists (songs are still there).
Anyway, that isn't so much the reason for this topic though. I did a Nandroid backup before and decided to do a restore of that backup. I initiated it from the Rom Manager and got into the Clockwork Recovery and saw it restoring. All appeared fine.
But when the phone rebooted, it is now stuck at the "Vibrant" screen. Has been stuck there for 15-20 minutes now.
I've been looking around. Is the problem because I went from 2.2 back to a 2.1 backup?
Click to expand...
Click to collapse
You were trying to load a 2.1 nandroid restore onto a 2.2 kernal. Nandroid does not restore the kernal so you would have to install one separate from the nandoid if you want to try it again.
in order to restore your nandroid backup you would have to first flash a 2.1 ROM, preferably the one you are restoring from, whenever I am changing versions, 2.2 to 2.1, I always Odin back to JFD and build up from there.
Kernel flashing questions
I have flashed numerous roms but have never flashed just the kernel. Do you flash it just like you would any zip file? Can I use CWM to flash using the flash rom from sd card method? If I decide to not use the kernel I just flashed can I just flash the rom over it(assuming it has its own kernel)? Sorry for all of the questions I have researched it and still do not have a clear enough understanding to try to flash a kernel at this point in time. Any and all help is absolutely appreciated.
tenbeau said:
I have flashed numerous roms but have never flashed just the kernel. Do you flash it just like you would any zip file? Can I use CWM to flash using the flash rom from sd card method? If I decide to not use the kernel I just flashed can I just flash the rom over it(assuming it has its own kernel)? Sorry for all of the questions I have researched it and still do not have a clear enough understanding to try to flash a kernel at this point in time. Any and all help is absolutely appreciated.
Click to expand...
Click to collapse
Thanks button right next to the quote >.<
I'm used to the quote being on the left.
Anyway, you can flash just the kernel. Check the Development section. There are some out there (Eugene has a bunch as do others). Depending on how they packaged the kernel, you would either flash with CWM or through Odin. The different ROMs typically come with the kernel, so you could just flash a 2.1 ROM and then nandroid back to what you had, or flash just the kernel, then nandroid.
I was trying out CM7 nightlies but the bugs were overwhelming, and when I tried to restore my previous ROM through Clockworkmod it couldn't find the boot image. I rebooted and have been stuck on the Vibrant/Samsung startup screen ever since. Can anyone help?
Ur just gonna have to pull the battery and odin back to stock. Then root and flash cm 7 but dont forget to wipe
Sent from my SGH-T959 using XDA Premium App
I agree. What was the ROM you tried to restore? was it a 2.3 gingerbread ROM as well as CM7? or was it a 2.2 ROM that you tried to restore while still running 2.3 CM7?
jotophenic said:
I was trying out CM7 nightlies but the bugs were overwhelming, and when I tried to restore my previous ROM through Clockworkmod it couldn't find the boot image. I rebooted and have been stuck on the Vibrant/Samsung startup screen ever since. Can anyone help?
Click to expand...
Click to collapse
CM uses a different file system from other ROMs (MTD/yaffs2) which means your old ROM's kernel won' t be able to read the file systems on the phone. You need to Odin back to stock with a re-partition, re-root, re-install clockwork and re-flash.
There a sticky on how to use Odin, and how to get into download mode here:
http://forum.xda-developers.com/showthread.php?t=849028
Search for "HOW DO I USE ODIN?!?!?!?!"
no harm no foul!
as soon as i saw the word 'kernel' here i knew what i'd done. i did try restoring back to gingerclone 2.2 while still running cm7. wah wah. but no harm, it was my girlfriend's phone and she's already back from tmo with a brand new galaxy s 4g. thanks for the replies fellas
Hi all
I'm not new to flashing but I'm new to flashing cm7.
I odin back to stock jfd eclair. Root and Install CWM 2.xxx. I downloaded the stable cm7 and I started flashing. (after I wipe data/cache of course)
IN recovery, it said finding package, opening package, then my phone processed a series of lines and reboot automatically. On the startup, it says VIBRANT SAMSUNG, then GALAXY S CYANOGEN(mod) then the same recovery screen with many lines. It moved too fast into another reboot I couldn't read what was on the screen. And it kept doing this for quite 10 mins now.
Is it normal? if not, what did I do wrong? I can get into download mode and odin back to stock but I did it last night and I couldn't think what i did wrong.
Please help!
Hmmmm..... seems a bit wierd, try going into recovery and wiping and reinstalling with a new download.
Sent from my Nexus S 4G using XDA App
stumpyz9 said:
Hmmmm..... seems a bit wierd, try going into recovery and wiping and reinstalling with a new download.
Sent from my Nexus S 4G using XDA App
Click to expand...
Click to collapse
No i don't think its a bad dl. I checked md5. I'm odin back to stock again now.
wavestar92 said:
No i don't think its a bad dl. I checked md5. I'm odin back to stock again now.
Click to expand...
Click to collapse
Try reflashing cwm when your rooted, may have not flashed right
Sent from my Gewgle Phone via XDA App
This happened to me also, I went directly back to recovery, 3 button, and reflashed. Worked the second flash for some reason.
Thanks. I turn it off, get into recovery again, and re flash it successfully
Same exact thing happened. I have no idea how many time I odened back to stock trying to figure it out.
I did as you guys said, as soon as that loop began, pulled the battery and got back into recovery. flashed again and worked just fine!
same thing happened to me...i got back into recovery...i noticed cwm updated to 5.0.2.8 then i reflashed and all good...when i tried to flash at first. cwm was 2.5 ..maybe thats the issued it wont flash on that...has to be cwm 5.0
anyway getting ready enjoy some cm7 on my vibrant...
I was reflashing back to stock firmware gingerbread 2.3.6 from eryigits due to its massive slowdown from its initial install. But then after flashing the stock firmware it boot looped so i thought maybe there was something wrong with the partitions and loaded what I got from another thread. But then the progress bar in Odin wasn't moving at all so I terminated odin and opened another instance similarly it didn't progressed. I plugged off my ygp and rebooted only meet a cellphone logo and a computer logo with an exclamation mark unpleasantly called black screen of death. Is this what they call a brick? Should I follow the guide on hardbrick recovery ie http://forum.xda-developers.com/showthread.php?t=1496360?
Yeah use the unbrickable reserector
Sent from my YP-G70 using xda app-developers app
atcq28 said:
Yeah use the unbrickable reserector
Sent from my YP-G70 using xda app-developers app
Click to expand...
Click to collapse
I see thanks then.
avid_reader said:
I was reflashing back to stock firmware gingerbread 2.3.6 from eryigits due to its massive slowdown from its initial install. But then after flashing the stock firmware it boot looped so i thought maybe there was something wrong with the partitions and loaded what I got from another thread. But then the progress bar in Odin wasn't moving at all so I terminated odin and opened another instance similarly it didn't progressed. I plugged off my ygp and rebooted only meet a cellphone logo and a computer logo with an exclamation mark unpleasantly called black screen of death. Is this what they call a brick? Should I follow the guide on hardbrick recovery ie http://forum.xda-developers.com/showthread.php?t=1496360?
Click to expand...
Click to collapse
No, this screen is the forced download mode also called lucky brick. So while you are on this screen the player should be detected as it is in download mode. So you should be able to flash your rom.
Just flash the rom in odin again see post above me
if it bootloops again format the device in recovery mode
There is a way to fix this.
I was flashing STOCK GB 2.3.6, because i didn't like Erygit's rom, and i got the bootloop too.
The bootloop was caused by the fact i didnt do a Factory data reset, and when i did it, i rebooted from Recovery and the Stock ROM booted.
Just do a factory reset from recovery, it should work.
Thanks for the swift replies and sorry for my late reply as well! Thanks alot for your recommendations. I haven't been able to touch my ygp for awhile due to school. But I'll surely try out everything suggested. Btw I kind of already reflashed the stock gb rom it bootlooped after so I pretty much didn't have a cwm recovery. But I'll try flashing it in a while! Thanks again! ^_^
Here goes, hopefully someone can help!
Ive installed a fair few roms on my phone and never had any issue, maybe this explains the complacency.
After updating to CWM recovery -6.0.4.7 I get stuck on my bootscreen, only seeing "Samsung galaxy I9100P" , ive been putting I9100 roms on it and losing NFC functionality for a while.
I went to update to the newest CM-11 nightly and read I needed to update CWM-recovery first. So did that, rebooted phone as instructed after installing new CWMr and nothing. Just stuck on I9100 screen.
No way to get into recovery mode, the only bright side I have found is I can boot into ODIN download mode. So what would be my next steps anyone?
Flash stock rom. or flash a kernel to get a working recovery bk with odin.
Sent from my GT-I9300 using xda premium
andrewwright said:
Flash stock rom. or flash a kernel to get a working recovery bk with odin.
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
From a dig through the forums it sounds like NAND rw corruption?
I wouldn't be calling it that just yet. Unless you'd like to pay for a motherboard replacement ? Most of these are recoverable.
Used ODIN and flashed a new kernel, still on the boot screen, except now I have the yellow exclamation mark. Now to, Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again.. this day is not going well..
Fingers crossed, flashed 3 or 4 kernels before one worked and allowed me into recovery mode. Trying to restore back to my backup from this morning. Heres hoping! :good:
Worked perfectly, the first thing I did was retry the initial task which was what got me stuck, currently waiting on CM-11's initial boot up after a successful install Thanks for the calming responses!