Hello,
I'm using Calkulin+Clemsyn 1.5ghz Froyo Combo VERSION 8 final (bootloader 1.2 only)
I did this steps to flash it, I'm 1.2 bootloader.
1. Download Calkulin's Format all zip and use CWM to install it.
2. Go to Advance, and Clear Dalvik-cache
3. Then wipe data/cache
4. Install from zip
It install fine and I boot up, but if I restart my g tab I get stuck on the two birds.
Any help is greatly appreciated! thanks
I would like to update this thread that I successfully fixed it!
How how how?
So I'm in the exact same boat as you. I have tried multiple ROMs thiking they were to blame. But I'm now in the same predicament.
What did you do to fix this problem?
Don't use CWM ICS, use the old version.
Related
To begin with, I am a complete noob with any and all phone mods. I'll run down what I've done and whats happening when I do it.
I used the adb method to root my tbolt. Once that was done, I installed Superuser, and Rom Manager and flashed with the latest CWR, after clearing the download manager and turning on the erase option in settings. I have done this (flash cwr) before each attempt to flash a rom.
I have tried 3 roms: Das Bamf 1.3.2 themed (tried twice), The Perfect Storm 1.2 and VirusROM RC1b3. I used identical steps to flash them:
1. Booted to CWR
2. made a nandroid backup
3. wiped data
4. wiped cache
5. wiped Davlik (sp?)
6. wiped battery
7. install zip from sd, choose zip from sd
8. after installation, reboot
When I reboot, the white boot screen with green htc logo appears, disappears, appears, disappears, and so on. I assume this is what people are referring to as a boot loop. It happened with both Roms, and luckily I am still able to get back to recovery and restore the stock rooted rom.
I've asked for help in the android forums, and a couple of people there have been trying to help, but the only real suggestion I've received is bad dl's. I haven't been able to find the md5's for the .zips to compare to what I generate, but I can't believe 3 straight dl's are corrupt.
Anyone have any suggestions as to what I'm doing wrong? Any help is greatly appreciated.
hootinani said:
To begin with, I am a complete noob with any and all phone mods. I'll run down what I've done and whats happening when I do it.
I used the adb method to root my tbolt. Once that was done, I installed Superuser, and Rom Manager and flashed with the latest CWR, after clearing the download manager and turning on the erase option in settings. I have done this (flash cwr) before each attempt to flash a rom.
I have tried 3 roms: Das Bamf 1.3.2 themed (tried twice), The Perfect Storm 1.2 and VirusROM RC1b3. I used identical steps to flash them:
1. Booted to CWR
2. made a nandroid backup
3. wiped data
4. wiped cache
5. wiped Davlik (sp?)
6. wiped battery
7. install zip from sd, choose zip from sd
8. after installation, reboot
When I reboot, the white boot screen with green htc logo appears, disappears, appears, disappears, and so on. I assume this is what people are referring to as a boot loop. It happened with both Roms, and luckily I am still able to get back to recovery and restore the stock rooted rom.
I've asked for help in the android forums, and a couple of people there have been trying to help, but the only real suggestion I've received is bad dl's. I haven't been able to find the md5's for the .zips to compare to what I generate, but I can't believe 3 straight dl's are corrupt.
Anyone have any suggestions as to what I'm doing wrong? Any help is greatly appreciated.
Click to expand...
Click to collapse
Did you try hitting install ROM from SD card in ROM manager and just flashing it through the app? Not sure that will change your result but it flashes it for you and you can choose the options to make a backup and wipe. Can't hurt to try it.
I did try it with Das Bamf, but got the same result. Thats when I read that using rom manager to install the roms could cause problems and started doing it manually.
After uninstalling/reinstalling rom manager and flashing cwr again, I got TPS 1.1 to flash, and its working great. I then tried to flash 1.2 thru cwr, both with a data wipe and without, but both times it boot looped.
I've dl'd TPS 1.2 from a different source, and I'll try to install it when I get home. But any other suggestions are very appreciated. I'm just glad I finally got something to flash.
I'm stumped. I tried new dl's of TPS 1.2 and Das Bamf 1.3.2te, and both of them failed. I even tried turning off my antivirus while dl'ing and moving the file to my sdcard, but it didn't make a difference.
Every ROM I have tried (I have 1.2) fails signature verification. When I turn off verification, it exits with code 7. The only ROM that installs is Clem's Ultimate which results in an endless boot loop. What am I doing wrong?
ClockworkMod Recovery v3.0.2.8 (GTAB 1.2 and NI Adam rev5)
RileyB said:
ClockworkMod Recovery v3.0.2.8 (GTAB 1.2 and NI Adam rev5)
Click to expand...
Click to collapse
riley,
what are you trying to do? - from where to where?
I had a 3.0 ROM and am trying to take it to a Froyo ROM. Sorry for failing to include that info!
RileyB said:
I had a 3.0 ROM and am trying to take it to a Froyo ROM. Sorry for failing to include that info!
Click to expand...
Click to collapse
You are trying to go from HC to a froyo or GB?
edit: let me know what ROM and BL that you are on...then what ROM you are trying to get to
On Flashback 10.3
Want to use Clem's Froyo (Ultimate)
One of two things happens.
1. Endless boot loop
2. Auto boots into recovery after wiping Dal and cache, installing and rebooting and will not go to system
RileyB said:
On Flashback 10.3
Want to use Clem's Froyo (Ultimate)
One of two things happens.
1. Endless boot loop
2. Auto boots into recovery after wiping Dal and cache, installing and rebooting and will not go to system
Click to expand...
Click to collapse
If you are trying to end up in Beasty/Clemsyn Ultimate 1.2 BL,
I think you should start with a clean stock base.
Save your pak's with titanium backup. save what you want on your pc.
NVflash (APX - power and vol -) and nvflash back to a 4349 stock.
after, boot in cwm
factory reset and wipe and partition to 4096/0 then 2048/0
mount usb.
copy over the ROM and then flash
wipe after.
http://forum.xda-developers.com/showthread.php?t=1392761 - this flashback OP has all the specific instructions on how to wipe and restart..instead of using FB ROM, you would use the BEASTY/CLEM ULTIMATE - or what ever else - make sure you stay on 1.2BL base
This worked flawlessly! Thank you! The nvflash step with formatting the SD was what was missing!
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).
Hello All,
I am able to flash my phone to any other rom so I was looking for some help to get ICM up and running.
If I flash my phone with beta 0.4.3 or 0.4.4 cwm flashable i reboot my phone and it sits in the "unlocked" Motorola Dual Core Technology screen and won't boot. Any ideas or can I get you information off my phone to assist?
Thanks,
Olsookie
olsookie said:
Hello All,
I am able to flash my phone to any other rom so I was looking for some help to get ICM up and running.
If I flash my phone with beta 0.4.3 or 0.4.4 cwm flashable i reboot my phone and it sits in the "unlocked" Motorola Dual Core Technology screen and won't boot. Any ideas or can I get you information off my phone to assist?
Thanks,
Olsookie
Click to expand...
Click to collapse
Make sure to use Joker's Clockworkmod recovery, named cwm-v3, here.
Thanks gollyzila, I am using the Jokersax CWMv3 recovery image at this time. I meant to mention that earlier in my first post.
Thanks,
Olsookie
olsookie said:
Hello All,
I am able to flash my phone to any other rom so I was looking for some help to get ICM up and running.
If I flash my phone with beta 0.4.3 or 0.4.4 cwm flashable i reboot my phone and it sits in the "unlocked" Motorola Dual Core Technology screen and won't boot. Any ideas or can I get you information off my phone to assist?
Thanks,
Olsookie
Click to expand...
Click to collapse
I would recommend flashing 0.4.0 first, then Gapps if you want it, then boot up. Then wipe cache and flash to 0.4.4 and re-flash Gapps. This method has been posted for the previous couple versions to avoid problems and seems to resolve a lot of issues. Might give it a shot and at least see if 0.4.0 will boot. Also check to make sure your download is the correct size and not corrupted.
try pulling the battery and then booting again. if that doesn't work flash 0.4.0 first like ccallahan suggested
CCallahan said:
I would recommend flashing 0.4.0 first, then Gapps if you want it, then boot up. Then wipe cache and flash to 0.4.4 and re-flash Gapps. This method has been posted for the previous couple versions to avoid problems and seems to resolve a lot of issues. Might give it a shot and at least see if 0.4.0 will boot. Also check to make sure your download is the correct size and not corrupted.
Click to expand...
Click to collapse
wala! that worked. thank you very much CCallahan. much appreciated.
i was having the same problem heres what i did i factory reset cleared cache/dalvic installed 3.1 then reboot wipe cache/dalvic then i flashed 4.4 over it
when you first flash any cm9 fresh, not over a backup, you must flash twice. Joker has mentioned this many times that the scripts he has for the install have to run twice in order to fully install.
1. Flash cm9 (whatever beta you want)
2. Reboot recovery (in advanced in cwm)
3. Flash rom again
4. Flash gapps
5. Boot to system
You should be good to go now
sent from my Kick Ass MIUI MoPho using XDA premium
I have a sch-i500 that is rooted with cwm working.
I am very interested in running liquid smooth v 2.9 found here: http://forum.xda-developers.com/showthread.php?t=2245120
so I did a format, wiped the cache and davlik. when I installed the zip from external sd card the phone immediately gave me a screen for CWM v 6.0.3.3.
I can still navigate and restore old back ups but the phone does not go past the Samsung logo on the boot screen. Any advice is appreciated.
I was previously running stock 2.3.5 E09 if that helps
http://forum.xda-developers.com/showthread.php?t=1026746
seems to be the best way for me to recover from this (looks like I flashed a non voodoo rom without removing voodoo) but I am unable to get the phone into download mode with or without the battery in the phone.
please help......(update) Alright, I am a moron. needed to have a powered usb port. on my way to recovery. thanks for having all this great info in one place.
aircooledbusses said:
so I did a format, wiped the cache and davlik. when I installed the zip from external sd card the phone immediately gave me a screen for CWM v 6.0.3.3.
I can still navigate and restore old back ups but the phone does not go past the Samsung logo on the boot screen. Any advice is appreciated.
I was previously running stock 2.3.5 E09 if that helps
Click to expand...
Click to collapse
Oh so close.
When coming from 2.3.x ROM you will need to flash the rom (liquid: or other 4.2.x) you will need to flash 2 more times...
The 1st flash get you into the new recovery only,,, as you found out.
2nd flash will pop up with an error message about incompatible partition and telling you to re-flash again,,,
So 3rd flash actually installs your new ROM
Then install a current/compatible Google gapps
.
Enjoy
.
Thank you, I am getting closer.
still on the second and third flash of the rom I get a satus 7 error which I think is a bootloader issue.
I have flashed the GBbootloader.tar through odid to no avail and am following Section:4 How to flash any ICS 4.0.x & 4.x.x JellyBean based rom
http://forum.xda-developers.com/showthread.php?t=1238070
anythoughts?
aircooledbusses said:
Thank you, I am getting closer.
still on the second and third flash of the rom I get a satus 7 error which I think is a bootloader issue.
I have flashed the GBbootloader.tar through odid to no avail and am following Section:4 How to flash any ICS 4.0.x & 4.x.x JellyBean based rom
http://forum.xda-developers.com/showthread.php?t=1238070
anythoughts?
Click to expand...
Click to collapse
what does the error say besides status 7?
did you odin the CWM4 fixed for cm7 then install the ROM 3 times?
can you get a pic up for us to see?
just to be sure......using odin, I repartitioned with the pit, and flashed a E03 rom. rebooted the phone fine.
flashed the CWM4 fix for 7 and redid the GB bootloaders as well.
went into recovery and factory reset, wiped cache, and dalvik.
installed liquid-JB-v2.7-Official-fascinatemtd.zip this time first time took me directly to clockwork where I flashed again. prompted with install from sdcard complete. repeated and got same message.
factory reset, wipe, wipe and flashed gapps. Everything seems to have worked this time with the v2.7Official instead of 2.9. I will play with this for just a bit and probably try it again tonight with a fresh downloaded copy of v2.9. I really do appreciate your assistance and help and I would not have gotten this far without the forum.
update:
flawless installation of v2.9 since 2.7 was already installed. (installed via cloclwork mod recovery)
It was most likely an operator error that prevented me from installing 2.9 after E03. But I don't see the benefit of going back to recreate why it didn't work. Thanks again all is good and right.