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.
Related
I have flashed several time and after reboot it stays stuck on the droids on skate boards,which i think is called boot loop.I have done a wipe and nanodroid back up.what am I doing wrong?
deanwards said:
I have flashed several time and after reboot it stays stuck on the droids on skate boards,which i think is called boot loop.I have done a wipe and nanodroid back up.what am I doing wrong?
Click to expand...
Click to collapse
The flash procedure should be:
- download and copy to SD the GSB and Google apps zip files
- restart in Recovery
- [optional] Nandroid backup, if you want to save what you have now
- wipe data/factory reset
- wipe Dalvik cache
- flash GSB
- flash Google apps
- restart
try rebooting into recovery and wiping the dalvik cache (assumung you are using RA_eris recovery) and rebooting again. That's solved most of my bootloop issues.
yeah, real talk i would completely do a full wipe
-data/dalvik
-format your sd card
then
-move GSB 2.8 and gapps to your sdcard and flash.
if it still won't boot i would try and flash kaosfroyo or something and see if that works
hope you figure it out
Hi guys, I was on cherry blur for a long while before finally decide to update.
I use the ROMRACER's Recovery from here:
http://forum.xda-developers.com/showthread.php?t=1204500
I update w/ the following manner:
1. Factory Reset/Wipe
2. Cache Partition Wipe
3. Dalvik Wipe
4. Install the ROM
ROMS i Tried:
Darkside 2.2
PureBlur 1.1
CherrynCrust .8
w/ DarkSide things freeze at M logo after reboot never got pass
w/ PureBlur the phone freeze up at random then reboot.
w/ CherrynCrust the phone freeze up at random then reboot.
I am not sure if there is anything else I should try, plz provide input if you have any experience. Thank you.
Update: I think i may have solve the problem
It seem that the phone does not like faux kernel and it seem to be the root of all the issue.
1. Fastboot -w
2. Fastboot reboot
3. Recovery > Factory Reset > Wipe Cache > Wipe Dalvik
4. Install PureBlur v1.1
5. Install PureBlur v1.2
6. Install ATT Stock Kernel
7. Reboot
---seem to work ok for an hour so far w/out crashing finger cross
I had problems when I used custom launchers, though I was on stock 2.2 atm, maybe that is your problem too?
Yeah i tried multiple launcher all produce the same thing, I thought it could be the overclocking so I use setcpu to set it back to 1ghz and still the same
Try wiping with fastboot -w and then flashing your ROM.
I think i may have solved my problem - updated my post
I just came from owning a vibrant (original galaxy s) and i've read multiple rom development threads but was surprised to see that there weren't any precautions listed when flashing a rom. i remember when we flashed roms on the vibrant, we had to:
- flash back to stock between roms
- wait at least 10 minutes after the roms were flashed for the dalvik cache to be rebuilt
- something else im forgetting at the moment (sorry it's almost 4 in the morning here).
do we not have to do this anymore with the sgs 2? is it ok to flash a gingerbread rom over cm7 and start using the phone right away after flashing? Thanks.
I follow my own procedure when I flash new ROMs, most are unnecessary, but I like keeping my phone clean of old stuff.
*IN CUSTOM ROM*
1. Wipe Data
2. Wipe Cache
3. Wipe Dalvik
4. Flash Stock ROM
*STOCK ROM*
5. Install ROM manager from Market
6. Flash CWM Recovery
7. Place .zip of a Custom Rom in internal SD memory
8. Reboot to Recovery
*PROCEDURE*
9. Wipe Data
10. Wipe Cache
11. Wipe Dalvik
12. For CM7.1, flash ROM TWICE, since it uses a new CWM Recovery. For a normal ROM, I install them twice too, just to be sure.
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 tried to install cwm in my s2 following this link: http://www.ibtimes.co.uk/install-an...ible-cwm-recovery-galaxy-s2-i9100-how-1434170
i stayed in the 11 step "PASS", after that, appears the samsung text and screen turns off.
Cwm works, i wipe cache but nothing happend.
Please help
NeguitO said:
i tried to install cwm in my s2 following this link: http://www.ibtimes.co.uk/install-an...ible-cwm-recovery-galaxy-s2-i9100-how-1434170
i stayed in the 11 step "PASS", after that, appears the samsung text and screen turns off.
Cwm works, i wipe cache but nothing happend.
Please help
Click to expand...
Click to collapse
Try this first.
If your device is stuck at boot animation or facing boot loop issues then try the following steps:
Disconnect your phone from computer, close Odin and remove phone's battery. Reinsert it back within 3 to 4 seconds, re-launch Odin and then repeat the tutorial from step 4.
Click to expand...
Click to collapse
Otherwise, just go into your recovery and flash a custom KitKat or a Lollipop ROM. This method would remove all the data present on the phone, so I am assuming that you took a backup before handling odin. To flash a ROM, do this:
1. Download ROM and GApps and put them in your storage(MOUNT SDCARD FROM THE RECOVERY ITSELF)
2. Wipe Data/Factory Reset
3. Wipe Cache Partition
4. Advanced>Wipe Dalvik Cache
5. Flash ROM AND GApps
6. Reboot system.
Then you're good to go.
Regards.
warrior1208 said:
Try this first.
Otherwise, just go into your recovery and flash a custom KitKat or a Lollipop ROM. This method would remove all the data present on the phone, so I am assuming that you took a backup before handling odin. To flash a ROM, do this:
1. Download ROM and GApps and put them in your storage(MOUNT SDCARD FROM THE RECOVERY ITSELF)
2. Wipe Data/Factory Reset
3. Wipe Cache Partition
4. Advanced>Wipe Dalvik Cache
5. Flash ROM AND GApps
6. Reboot system.
Then you're good to go.
Regards.
Click to expand...
Click to collapse
Thanks you! my S II is ok now.