Here are the steps I've taken and the results:
1. Odin - EB01/PIT/Repartition
2. Remove Cable/Battery Pull
3. Tried to boot but only got to the old CWM blue. Wouldn't let me do 3 button to anything else.
4. Flashed Recovery ALL
5. Booted to CWM Red
6. Full wipe
7. Attempt flash of CM7 7/4 (no go); 7/11 (no go); 7/17 (no go)
8. Flashed recovery included in JTs OP
9. Booted to new recovery (blue)
10. Repeated Step 7: got "Checking state of BML/MTD..." and then recovery just reset itself.
That's all I got over there.
Thoughts?
Oddly enough it actually worked this time around, I've spent way too much time on this!
Going to flash up to 7/17, enjoy the good times and get to the kernels later.
Thanks!
Related
Just tried to install GSB 2.8 on my stock 2.1 Eris (first custom rom) but it seems to be stuck in the Cynogen7 boot animation (it's been a good 20 minutes now.)
Steps I took:
1. root
2. format sd
3. wipe dalvik
4. flash gsb
5. flash gapps
6. reboot
7. where I am now
Should I just reboot it?
EDIT - fixed
Gigamaster89 said:
Just tried to install GSB 2.8 on my stock 2.1 Eris (first custom rom) but it seems to be stuck in the Cynogen7 boot animation (it's been a good 20 minutes now.)
Steps I took:
1. root
2. format sd
3. wipe dalvik
4. flash gsb
5. flash gapps
6. reboot
7. where I am now
Should I just reboot it?
EDIT - fixed
Click to expand...
Click to collapse
Was the fix wiping data, since you didn't mention that?
Had the same problem so I just went back to xtrROM 5. I'd like to hear how you fixed it.
I battery pulled, rewiped the dalvik then rebooted. 10 minutes later it booted.
Hello all,
I need some advice. I originally followed this page http://wiki.cyanogenmod.com/wiki/Sam...l_Update_Guide to flash and everything was fine for 3 or 4 days and then the fc's came. So i odin'd to stock and when getting ready to reflash i see that you need to be on 2.2 to use his guide. So another member kwkslvr (who has been very helpful and patient btw) told me his method for flashing CM7 so i attempted to straight from 2.1 with no root to the following...
(kwkslvr's method) You definitely don't need to be on Froyo. You don't need root either. What has worked best for me is to Odin to 2.1, reboot into stock recovery and flash update.zip. Since you've flashed before, update.zip will probably already be in your internal sdcard unless you removed it. You'll have to flash it twice in a row without rebooting and that will load ClockworkMod Recovery.
Once you're in CMW Recovery (probably green recovery), wipe data/factory reset then format/system. These two steps are CRUCIAL! Flash your CM7 Nightly twice. The first time you flash it, it installs blue recovery. The second time it installs CM7. After that, again without rebooting, install gapps.
From that point, wipe data/factory reset again and reboot into the OS.
So i tried that and got to where the phone restarts after the flash and it has galaxy and cyanogen below it for a few seconds and then immediately script with font like from recovery mode races down the screen for a few seconds, then back to galaxy/cyanogen in a loop. So i odin'd again and as of now am stock 2.1 with the options of kies n it to 2.2 and then follow cyan page again or trying kwkslvr's method again. I did notice he mentioned nightlies but i am attempting to flash the stable on page 1 of this thread but don't think that would make much difference. I love the way this ROM looks and performed before it went off the tracks. Any suggestions are welcomed. Thanks alot
EDIT: At the boot loop sequence i 3 buttoned to recovery and reflashed and it seems to have worked. I notice the battery gauge no longer has the # %. And the horizontal line next to it is gone too. On my market page under "not installed" i have adobe flash showcase (Reads this item is not available at top), google search which just has a open tab (Already is installed), magic 8 ball by dennis bond (Reads this not available in your country?? it was the first time i installed it) Any ideas on how to get these 3 items off the not installed section. It's mainly a minor annoyance. I have cleared cache in market with no luck. Thanks.
About a month ago I wanted to try out CM7 and see what it's worth.
I went to this thread: http://forum.xda-developers.com/showthread.php?t=1176411
I was using a stock GB ROM and rooted with CF-root kernel.
I downloaded the stable build and followed these instructions:
Install via ClockworkMod (do not use ROMManager for initial install):
1.Make sure you're running a rooted device.
2.Root your device and install ClockworkMod Recovery (http://forum.xda-developers.com/show....php?t=1118693)
3.Do a Nandroid backup!
4.WIPE (wipe data/factory reset + wipe cache partition) - do it for real.
5.Install the ROM from internal sdcard using ClockworkMod Recovery.
6.Do not reboot! We mean it - do nothing except choose zip and continue next step (if you come back to us with permission issues in install, we will know you did not read the directions and will call you an idiot). If it just plain hangs, reboot directly back into ClockworkMod recovery and continue at the next step.
7.Install the ROM from internal sdcard using ClockworkMod Recovery, again (due to a bug in the install).
8.Reboot
9.Install the Google Addon through ROMManager which is easiest, but you can
download the gapps.zip and install via ClockworkMod recovery instead.
Click to expand...
Click to collapse
When My phone booted it got into a bootloop.
I could not boot into recovery, I could only boot into download mode.
I searched the web and on one forum website I saw that someone encountered the same problem and after he encountered the bootloop he booted into download mode and flashed Siyah Kernel via Odin and his phone booted successfully.
I followed what he did and my phone booted into CM7.
After that I went on to other ROMs.
Two days ago I was running CM9 and I wanted to flash to CM7, so I downloaded CM7 nightly build #115 and did the following:
1) My phone was rooted with CWM. (CM9)
2) Wiped data, cache and dalvik.
3) Flashed the ROM twice.
4) Flashed GAPPS.
5) Rebooted.
6) "Samsung Galaxy S II with !" Screen.
7) "Kernel Panic" screen.
8) Took battery out.
*Tried booting into CWM with no success.
9) Booted.
10) Stages 6, 7 & 8.
11) Booted into download mode.
12) Flashed siyah kernel via odin.
13) CM7 working!
So there is my story!
I have also seen other people with the same problem, so it is not just me.
And here are my questions:
1) Why did these problems happen (kernel panic or bootloop)?
2) Why does Siyah Kernel fix these problems?
3) How can I prevent the bootloop/kernel panic from happening in the future (without flashing Siyah)?
Seconding the question as well as noting that it also occurs with Arif-Ali's nightly compiles.
did you wipe cache and dalvik cache after flashing cm7?
golcheck said:
did you wipe cache and dalvik cache after flashing cm7?
Click to expand...
Click to collapse
No, you dont need.
golcheck said:
did you wipe cache and dalvik cache after flashing cm7?
Click to expand...
Click to collapse
I did. I tried "messing" with CWM any which way and even flashed a stock rom in odin (and appropriate CF root). Nothing short of flashing Siyah (and probably any other kernel that supports CM7 except the one in the update zip) lets CM7 boot.
Net.silb said:
About a month ago I wanted to try out CM7 and see what it's worth.
I went to this thread: http://forum.xda-developers.com/showthread.php?t=1176411
I was using a stock GB ROM and rooted with CF-root kernel.
I downloaded the stable build and followed these instructions:
When My phone booted it got into a bootloop.
I could not boot into recovery, I could only boot into download mode.
I searched the web and on one forum website I saw that someone encountered the same problem and after he encountered the bootloop he booted into download mode and flashed Siyah Kernel via Odin and his phone booted successfully.
I followed what he did and my phone booted into CM7.
After that I went on to other ROMs.
Two days ago I was running CM9 and I wanted to flash to CM7, so I downloaded CM7 nightly build #115 and did the following:
1) My phone was rooted with CWM. (CM9)
2) Wiped data, cache and dalvik.
3) Flashed the ROM twice.
4) Flashed GAPPS.
5) Rebooted.
6) "Samsung Galaxy S II with !" Screen.
7) "Kernel Panic" screen.
8) Took battery out.
*Tried booting into CWM with no success.
9) Booted.
10) Stages 6, 7 & 8.
11) Booted into download mode.
12) Flashed siyah kernel via odin.
13) CM7 working!
So there is my story!
I have also seen other people with the same problem, so it is not just me.
And here are my questions:
1) Why did these problems happen (kernel panic or bootloop)?
2) Why does Siyah Kernel fix these problems?
3) How can I prevent the bootloop/kernel panic from happening in the future (without flashing Siyah)?
Click to expand...
Click to collapse
I fixed it.
This is how:
1. Make a CWM Backup.
2. Use Odin to flash I9100XXKI3, including the PIT (re-partition)
3. Flash this kernel (PDA section) and the old Bootloader (Bootloader section) with Odin.
4. Boot into CWM recovery and flash cm7+gapps.
5. Use Advance Restore in CWM to restore your /data partition if you want to.
I'm 90% certain that the problem was ICS's partition layout (PIT file).
I was having trouble with my CM9 [THS] rom, I was on build 13 so I thought I'd update to build 15. So every app was crashing and what-not, so I reboot it and put it in my pocket. 30 minutes later I take it out and it's warm, it was on the boot screen the whole time.
So I remember I can't use 3-finger recovery for ICS.. but at this point I didn't know what else to do [I was trying to get it done in a hurry]. So I did 3 finger recovery.
Then as I expected, it would not boot normally, it kept booting into recovery.
So I tried to flash CM9 build 15, but at "checking state of bml/mtd" it immediately rebooted and was in what seemed a bootloop.
So I heimdall a old recovery.bin, back from a Gingerbread ROM, hoping it would fix it like it did last time I had the bootloop.
It did, and it tried to boot up the CM9 now. I let it alone for a few minutes and realized it wasn't gonna finish booting, so I booted into windows [primary OS is Ubuntu] and did a complete ODIN, back to verizon Gingerbread firmware. I used atlas2.2.pit or something.
So I left it and came back and it said "PASS!" and it was now stock Gingerbread ROM.
So I heimdall'ed recovery.bin as stated on this page: http://wiki.cyanogenmod.com/wiki/Samsung_Fascinate:_Full_Update_Guide
And I did 3-finger recovery [because it says to if you are on stock GB], and so I did a full Wipe, and then I installed from .zip, and chose CM9 THS build 15 [ http://rootzwiki.com/topic/16630-romicsimm76d-teamhacksungs-ics-port-for-fascinate-build-15-071012/ ]....and it started to install but when it came to "Checking state of BML/MTD" it immediately rebooted, and looks like it's bootlooping now.
What's wrong? How do I get CM9 installed again?
I'm going to the dentist and I hope when I get back someone has posted the solution..
Thanks!
1) odin to stock and let boot then odin cwm fixed for cm7
2) 3 finger to recovery
3) wipe data, cache, and dalvik
4) install THS build 2 and let it fully boot
5) reboot recovery using power menu
6) wipe data, cache, and dalvik
7) flash build 15 + gapps
8) enjoy
Thanks.. That worked.
I had forgotten that you have to flash specific roms in order to bridge the gap from GB to ICS.
I'm not entirely sure why THS build 2 is so magical.. but whatever.
The thread on rootzwiki did not have build 2 linked, so I found it on another forum.
I am going to upload it to mediafire so if anyone wants THS build 2 mirror, they won't have to hunt!
Here is a dropbox mirror: teamhacksung-ota-eng.BUILD2.zip
I am trying to mirror it on mediafire but it quits uploading after the first MB.. :S
So... I'm trying to update to the current AOKP release, but seem to have an issue where the phone gets stuck on first boot.
Currently the process I'm using to flash is below:
1) Factory reset+wipe everything from recovery and reboot to bootloader
2) Flash boot.img, go to hwboot and reboot back in to recovery.
3) Push rom to sdcard, install rom/wipe cache and reboot
4) Watch that little X glow for 10-20 minutes.
This isn't the first time I've reinstalled the rom, however (I think) it is the first time I've wiped absolutely everything on the phone first. Is there some extra step I need to go through as a result? Or does first boot really take more than half an hour if I wipe all internal memory prior to reinstalling the OS?
Using TWRP 2.6 and hwboot 1.3(?) I think. Will check next time I'm in fastboot (leaving it on boot screen at the moment to see if it does anything).