Develop Bugs

Cyanogen boot loop

i have googled this and tried multiple ways of installing it but i always get a boot loop. Whats going on?

Hey if you just want to get your phone back again, just flash another firmware from the one you used. Should start up just fine.

have done already but i actually want to install cyn mod. I managed to get as far as the main screen buit then immediately reboots. I cant find wifi modules for latest doom kernel either they arent in his thread.

FLASH KERNEL FIRST (from cyanogenMOD or doomkernel for CM7 etc)
Than flash cyanogenMOD
any other way will make your phone bootloop.

I think you have to unlock BL via SE in order to flash CM..
of course you would likely broke your warranty.
this based on my experience (I'm a newbie too in the android's world). this is what I've done :
1. unlock BL via SE (not all carriers allowed this!)..
2. flash .42 fw
3. follow the instructions given on CM thread by fxp.
it's worked for me.
goodluck.

I've had this problem before. Did you wipe the delvic cache, wipe data/factory reset and wipe cache partition in CWM before you flashed the update.zip?

It would seem it was a specific version of cm that was making it bootloop the one from dooms thread 7.2.0 works fine and also the one before the latest stable release also worked fine. I however found a problem with the spacebar on the keyboard when using the phone in landscape so am now going to try arconium and doom kernel its a shame really because cm from what i used of it looked really nice.

Try 7.1.0.1.
I got bootloop too with 7.1.0.2

Kuroyukii said:
Try 7.1.0.1.
I got bootloop too with 7.1.0.2
Click to expand...
Click to collapse
Aye thats the one i used but ended up having a problem with the spacebar not working in landscape so am on acronium now which is all good but superuser keeps crashing meh always something eh.

at first im also having the same problem,just follow the instruction by FXP : flash bb56,flash fw.42,flash FXP kernel via fastboot,flash update via recovery,wipe dalvik cache,reboot..
Sent from my LT18i using Tapatalk

I have this exact same problem
I've done everything I was supposed to, I think, and still doesn't work. It boots, shows me the little Android "Welcome!" screen, and before I have time to press anything or begin setting up my device, it reboots into the Cyanogenmod loading screen. I've tried different kernels, different basebands, every time wiping Dalvik cache, etc. and it REFUSES to work. I'm pretty desperate by now because I really wanted to use this ROM so any help is greatly appreciated.
I also followed precisely rashid.fairus' instructions and it still does the exact same thing.

You need to Wipe Data, Cache and Dalvik ----- BEFORE AND AFTER FLASH
I do this here, and positive feedback

Velcis Ribeiro said:
You need to Wipe Data, Cache and Dalvik ----- BEFORE AND AFTER FLASH
I do this here, and positive feedback
Click to expand...
Click to collapse
Sometimes you DON'T WIPE ANYTHING AT ALL. Just flash CM and Google.
Works for me on Xperia Acro S.

gabantarung said:
Sometimes you DON'T WIPE ANYTHING AT ALL. Just flash CM and Google.
Works for me on Xperia Acro S.
Click to expand...
Click to collapse
Only when you upgrade to a later version of the same ROM.
Sent from my Xperia Arc S using xda premium

Velcis Ribeiro said:
You need to Wipe Data, Cache and Dalvik ----- BEFORE AND AFTER FLASH
I do this here, and positive feedback
Click to expand...
Click to collapse
Wipe dalvik and cache when upgrading to later version, wiping data will reset phone to factory settings and you lose all personal data.
僕のLT18iから送られてきた

HELP!;Wifi problem with cm9 rc1

I am currently running cm9 rc1 with the original kernel(the one dat comes in the folder)
heres my problem wifi turns on but wont scan or detect a network
This is what i didi in cwm;
wipe data
wipe cache
wipe dalvik cache
wipe battery stats
any sugesstions? if any one has cm9 rc 1 how did the set it up?

xperiaplayicsuser2013 said:
I am currently running cm9 rc1 with the original kernel(the one dat comes in the folder)
heres my problem wifi turns on but wont scan or detect a network
This is what i didi in cwm;
wipe data
wipe cache
wipe dalvik cache
wipe battery stats
any sugesstions? if any one has cm9 rc 1 how did the set it up?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=27535011&postcount=1801 This is a workaround, I'd use a different kernel to be honest. My signature has the kernel I currently use for cm9 if you want to try it out

agraceful said:
http://forum.xda-developers.com/showpost.php?p=27535011&postcount=1801 This is a workaround, I'd use a different kernel to be honest. My signature has the kernel I currently use for cm9 if you want to try it out
Click to expand...
Click to collapse
Thanks for the reply:laugh
but the roblem is it cant see networks
and if i were to use mjolnir kernel do i need to flash his modules or just flash and wipe everything

xperiaplayicsuser2013 said:
Thanks for the reply:laugh
but the roblem is it cant see networks
and if i were to use mjolnir kernel do i need to flash his modules or just flash and wipe everything
Click to expand...
Click to collapse
Doh! I read that part too haha my bad. Are you 100% sure it's not a problem with your network? If it's not then yes, flash the wifi modules through cwm and wipe cache. If that doesn't work then you may need to wipe everything and start fresh

agraceful said:
Doh! I read that part too haha my bad. Are you 100% sure it's not a problem with your network? If it's not then yes, flash the wifi modules through cwm and wipe cache. If that doesn't work then you may need to wipe everything and start fresh
Click to expand...
Click to collapse
Im sure its with the network beacuse it worked fine on gb and ill try and tell you
thanks

agraceful said:
Doh! I read that part too haha my bad. Are you 100% sure it's not a problem with your network? If it's not then yes, flash the wifi modules through cwm and wipe cache. If that doesn't work then you may need to wipe everything and start fresh
Click to expand...
Click to collapse
Still not recognizing how did you do it?

xperiaplayicsuser2013 said:
Still not recognizing how did you do it?
Click to expand...
Click to collapse
Well when I installed cm9 I flashed back to stock then went to cm9 and flashed everything, wiped everything about three times (better safe then sorry) and booted up. Have you tried fxp 129 with the Mjolnir kernel? It may be that the cm release is giving the issues..The bots on cyanogenmod go crazy sometimes.. You can also try re-downloading the ROM in case it's a corrupt download

agraceful said:
Well when I installed cm9 I flashed back to stock then went to cm9 and flashed everything, wiped everything about three times (better safe then sorry) and booted up. Have you tried fxp 129 with the Mjolnir kernel? It may be that the cm release is giving the issues..The bots on cyanogenmod go crazy sometimes.. You can also try re-downloading the ROM in case it's a corrupt download
Click to expand...
Click to collapse
thanks so much
wiping everything three times worked

[Q] Pacman 19.1a not booting

Hello,
I'm having issues to get the Pacman 19.1a (GSM) to start. It's stuck at boot. I've tried flashing 19.1, which is booting fine, however this is not allowing me to enter a PIN code. This issue was reported fixed in 19.1a which is why I tried.
I'm using the following kernel: boot-HELLBOY-CM10-201212251747.img
Is anyone else experiencing this issue?
Thanks!

Did u do factory reset n cache wipe
Sent from my One V using Tapatalk 2

bahubali67 said:
Did u do factory reset n cache wipe
Click to expand...
Click to collapse
Sorry forgot to mention that; yes I did and I wiped Dalvik as well.

flash the latest kernel then in recovery do a wipe data/factory reset then try to install

FTMC said:
Sorry forgot to mention that; yes I did and I wiped Dalvik as well.
Click to expand...
Click to collapse
The same experience, also fully wiped. Stuck on Pacman logo.

gulsher said:
flash the latest kernel then in recovery do a wipe data/factory reset then try to install
Click to expand...
Click to collapse
As far as I know, I'm using the latest hellboy kernel. I've tried CM9 and CM10, but they both have the same effect. Should I be mistaken, could you provide me with a download link or version number I should get?
@brusell: So it seems I'm not the only one? I would have reported it in the ROM's topic, however my current postcount does not allow me to...

Resolved in Verdion 19.3
Just wanted to post the "solution"; the issue has been resolved in version 19.3.

Ok so I did a factory reset wiped cache and wiped dalvic, installed pacman 19.3 using twrp and then flashed hellboy kernel and rebooted, but I've been stuck at the pacman logo for 2 hours!! Did I do anything wrong? Can you tell me how u got out of it on 19.1?Do i just wait for the battery to die?
nvr mind got it

swhatevers said:
Ok so I did a factory reset wiped cache and wiped dalvic, installed pacman 19.3 using twrp and then flashed hellboy kernel and rebooted, but I've been stuck at the pacman logo for 2 hours!! Did I do anything wrong? Can you tell me how u got out of it on 19.1?Do i just wait for the battery to die?
nvr mind got it
Click to expand...
Click to collapse
Hey mate, i'm having the same problem as you did. Could you post the solution? Thanks in advance!

[Q] Boot Loop, Need help!

i have been running the kiss kernel for a while now, last night i tried to flash the hellboy kernel and retern to my pacman rom. but it still boots, i have cleared all my caches formated everything but my sd card, have tried flashing all kiss kernels and multipul hellboy kernels, but never gets passed the boot screen.. any ideas?

i managed to get it to the android is upgrading.. starting apps thing, but it gets stuck there.

Did you wipe anything when you flashed the kernel? If the kernel was for jellybean it shouldn't hang like that... not sure?

lilrob1213 said:
Did you wipe anything when you flashed the kernel? If the kernel was for jellybean it shouldn't hang like that... not sure?
Click to expand...
Click to collapse
yeah i wiped the cache, devlink cache, data, system, and a factory reset, been trying to figure it out all day but have not made much improvement

JARR3DF15CH3R said:
yeah i wiped the cache, devlink cache, data, system, and a factory reset, been trying to figure it out all day but have not made much improvement
Click to expand...
Click to collapse
and you installed a rom after wiping those things right? I'm assuming... but just wondering. What rom did you flash and are you CDMA virgin mobile?

lilrob1213 said:
and you installed a rom after wiping those things right? I'm assuming... but just wondering. What rom did you flash and are you CDMA virgin mobile?
Click to expand...
Click to collapse
yeah i installed it after, pacman http://forum.xda-developers.com/showthread.php?t=1948770&page=12
im with telus gsm. the rom was working fine, but i went to change the kernel to hellboy cause i herd it was a bit better and now im in this bootloop

also not running the newest version of that rom, i am running v15a

Oh okay wellllll I'm on virgin mobile and I don't know much about the primou phones and rom and kernel compatibility so I'm afraid I'll have to leave this to someone who knows more... good luck to you though... maybe try booting into bootloader from the recovery and flash the boot.img you had before then flash the rom again?

lilrob1213 said:
Oh okay wellllll I'm on virgin mobile and I don't know much about the primou phones and rom and kernel compatibility so I'm afraid I'll have to leave this to someone who knows more... good luck to you though... maybe try booting into bootloader from the recovery and flash the boot.img you had before then flash the rom again?
Click to expand...
Click to collapse
thanks anyways, ill be sure to give that a try:silly:

Did u wait Little longer time while first boot???? Choose latest kernel n flash. .
Hit thanks if I helped u!!!

bahubali67 said:
Did u wait Little longer time while first boot???? Choose latest kernel n flash. .
Hit thanks if I helped u!!!
Click to expand...
Click to collapse
yeah i always wait a little while, i have chosen latest kernel, has not made a difference, i have gotten better results using an older one of the titanium kiss, hellboy doesnt seem to work with my phone for some reason

Did you use the command
fastboot flash boot boot.img or just
fastboot boot boot.img?
Also,after flashing it,does the terminal say something like this?
Okay.
Okay.
Finished.
Edit:also,see that you are flashing the kernel in the fastboot screen(where it says 'fastboot usb'),and not in the Hboot(bootloader) screen.

mihirengg19 said:
Did you use the command
fastboot flash boot boot.img or just
fastboot boot boot.img?
Also,after flashing it,does the terminal say something like this?
Okay.
Okay.
Finished.
Edit:also,see that you are flashing the kernel in the fastboot screen(where it says 'fastboot usb'),and not in the Hboot(bootloader) screen.
Click to expand...
Click to collapse
i am using the all in one tool kit to flash my kernel, yes i am in fastboot, a window pops up runs through code and my phone reboots, i have changed the kernel on it before, but for some reason this time it wont boot properly at all, the phone is currently at the " android is upgrading" screen, it was the starting apps box with the spinning circle

if you say that it is stuck at android is upgrading - that's because the dalvik works and it is deodexing your gapps.
so i suppose you flashed kernel, flashed rom and gapps and rebooted. well this works from time to time but you have to reboot between flashing rom and gapps.
1. download this kernel: hellboy
2. go to bootloader and flash the kernel.
3. go to recovery and: do a factory reset + wipe system - no need for wiping dalvik or cache cause factory reset does them both.
4. flash your rom
5. reboot.
6. if it boots properly, reboot to recovery and now flash GAPPS package.

1ceb0x said:
if you say that it is stuck at android is upgrading - that's because the dalvik works and it is deodexing your gapps.
so i suppose you flashed kernel, flashed rom and gapps and rebooted. well this works from time to time but you have to reboot between flashing rom and gapps.
1. download this kernel: hellboy
2. go to bootloader and flash the kernel.
3. go to recovery and: do a factory reset + wipe system - no need for wiping dalvik or cache cause factory reset does them both.
4. flash your rom
5. reboot.
6. if it boots properly, reboot to recovery and now flash GAPPS package.
Click to expand...
Click to collapse
thank you so much 1ceb0x! my phone has been in this bootloop for an entire 24 hours,

1ceb0x said:
if you say that it is stuck at android is upgrading - that's because the dalvik works and it is deodexing your gapps.
so i suppose you flashed kernel, flashed rom and gapps and rebooted. well this works from time to time but you have to reboot between flashing rom and gapps.
1. download this kernel:
2. go to bootloader and flash the kernel.
3. go to recovery and: do a factory reset + wipe system - no need for wiping dalvik or cache cause factory reset does them both.
4. flash your rom
5. reboot.
6. if it boots properly, reboot to recovery and now flash GAPPS package.
Click to expand...
Click to collapse
hey icebox, i have the same problem, stuck on pacman logo
can you tell me which hellboy kernel should i use?
i've flashed the 1st one on the mediafire list. thanks!

chikuera said:
hey icebox, i have the same problem, stuck on pacman logo
can you tell me which hellboy kernel should i use?
i've flashed the 1st one on the mediafire list. thanks!
Click to expand...
Click to collapse
Thats the old version.... See the changelog code and flash dat in future..... Right now.... Here u go....
http://www.mediafire.com/?waggdha1ir1lxz0

new cm nightly causing "com.android.phone" force close with custom kernels

so i just got the october 23 nightly for cm 10.2,flash fine,no issues,then i flashed the latest stable lean kernel and got the "com.android.phone" force close error,anyone else having this issue?

First of all have you cleared both your cache, and dalvik cache in recovery?

pattyboi:) said:
so i just got the october 23 nightly for cm 10.2,flash fine,no issues,then i flashed the latest stable lean kernel and got the "com.android.phone" force close error,anyone else having this issue?
Click to expand...
Click to collapse
i can confirm this error for you as i am experiencing the same issue

russell664 said:
First of all have you cleared both your cache, and dalvik cache in recovery?
Click to expand...
Click to collapse
yes i have,im not new to flashing kernels (dont take that as sarcasm please,was not inteded to be) i tried multiple kernels,all give the error except stock cm one

No problem bro, I have no clue of your experience so its always better to start and explain the basics
Have you checked the MD5 sums of the kernel images your flashing? To make sure they are intact and not corrupt?

i actually found this out through it happening on Carbon rom, due to something being modified with the com.android.phone, if you use a kernel with a custom ramdisk, you will have that problem. You need to either use stock kernel or find one that uses the stock ramdisk.

there is an updated version of Mpokang v10 that will work with the latest CM10.2 nightlies if you want to give it a try. It's posted on the last page or two.

Fix Force Close Error
pattyboi:) said:
so i just got the october 23 nightly for cm 10.2,flash fine,no issues,then i flashed the latest stable lean kernel and got the "com.android.phone" force close error,anyone else having this issue?
Click to expand...
Click to collapse
I have fixed this error with the following steps given below.
Solutions:-
- Update you App
- Clear Gmail Storage Data
- Clear App Cache and Data
- Reset App Preferences
- Reset Smartphone Factory Settings
I found these steps with the help of YouTube.
Here is that link:-
youtube.com/watch?v=fx8Fv8RXag8

ChristinaDavid said:
I have fixed this error with the following steps given below.
Solutions:-
- Update you App
- Clear Gmail Storage Data
- Clear App Cache and Data
- Reset App Preferences
- Reset Smartphone Factory Settings
I found these steps with the help of YouTube.
Here is that link:-
youtube.com/watch?v=fx8Fv8RXag8
Click to expand...
Click to collapse
the problem was ramdisk issue with the new cm nightlies....some kernels have been updated already.