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から送られてきた

[Q]Why do i have problems with installing custom roms

I have locked bootloader, and rooted Arc S. ICS .587. Whenever i try to install custom rom, usually it demands cache and dalvik to be wiped and i do it. But when iinstall it, (i tried 2 roms on with aroma instaler and one without) and on both i got bootloop. Whenever i tried to install mod that also required wiping cache and dalvik i also always got bootloop. When i dont wipe it phone can boot, but features that i wanted to install dont work properly.
I am really intrested in installing custom rom, can anyone help me??? :crying:
Thanx in advance!

Re-read the instructions of whatever you're flashing and keep trying.

Very useful...

DjDexter5GHz said:
Very useful...
Click to expand...
Click to collapse
Not a lot more to suggest when People make such vague posts.

Usually you should make factory reset and format /system
Have you?

DjDexter5GHz said:
I have locked bootloader, and rooted Arc S. ICS .587. Whenever i try to install custom rom, usually it demands cache and dalvik to be wiped and i do it. But when iinstall it, (i tried 2 roms on with aroma instaler and one without) and on both i got bootloop. Whenever i tried to install mod that also required wiping cache and dalvik i also always got bootloop. When i dont wipe it phone can boot, but features that i wanted to install dont work properly.
I am really intrested in installing custom rom, can anyone help me??? :crying:
Thanx in advance!
Click to expand...
Click to collapse
Pls specify which custom rom you wanna install we can help you more. Check out the link at the bottom of my signature if you're new here. Do some reading.
Sent from my LT15i using xda app-developers app

[Q] Need assistance, please

Hello! I am new to the Xda community, and I have a Xperia S. I went throw a lot of Rom threads and read all, even video tutorial and because of that I got confused. Can anyone spare some time (aprox. 10 mins) to answer me some questions, by chatting or here. Please do not make a fool out of me like some other guys around here.
1. if i go into bootloop after flashing CM10, can i restart the phone and go into CWM without flashing again boot.img, and flash the rom again?
2. if i go into bootloop after flashing CM10, do i have to flash the stock rom using flashtool?
3. tell me a simple way to get out of bootloop.
4. flashing the CM10 on my SXS with built number *.2.55 will work?
If I have made anymistakes by posting this here, i would like someone to take it down. Thank you for your time.

chossen said:
Hello! I am new to the Xda community, and I have a Xperia S. I went throw a lot of Rom threads and read all, even video tutorial and because of that I got confused. Can anyone spare some time (aprox. 10 mins) to answer me some questions, by chatting or here. Please do not make a fool out of me like some other guys around here.
1. if i go into bootloop after flashing CM10, can i restart the phone and go into CWM without flashing again boot.img, and flash the rom again?
2. if i go into bootloop after flashing CM10, do i have to flash the stock rom using flashtool?
3. tell me a simple way to get out of bootloop.
If I have made anymistakes by posting this here, i would like someone to take it down. Thank you for your time.
Click to expand...
Click to collapse
I dont have an Xperia yet, but from reading and experience from other phone ...
1) did you wipe data, cache and dalvik cache? if not, try to do it and check again for bootloops. If not possible then reflash the firmware and try to wipe these things directly after flashing the firmware.
2) if you wiped, try to restart with flashing the firmware again and wiping everything.
3) if nothing working reflash stock, boot stock once to see if it is working without bootloops and then restart from scratch.
4) if also not working .... is it the correct firmware? did you forget something?
There are good instructions for the firmwares, if you do everything as explained, you shouldnt get bootloops. But ... no howto is perfekt.
Its mostly trying as much as possible, till you have the correct way to flash a firmware. Bootloop isnt that bad ...
If you have a way which works for you, keep the steps for later flashing and tell the community what you had to do differently or if you missunderstood some points, even then tell it, because that can make these instructions better.
---------- Post added at 04:36 PM ---------- Previous post was at 04:31 PM ----------
chossen said:
4. flashing the CM10 on my SXS with built number *.2.55 will work?
Click to expand...
Click to collapse
I would say that it doesnt matter which firmware is on the phone, as long as you unlock the bootloader and the fastboot or flashtool is working.
The custom firmwares use the same methods but might have added recovery for easier flashing later.
You should even be able to downgrade to older firmware with unlocked bootloader and flashing the ftf file.
Its only important to wipe the data, cache and dalvik cache that the firmware is working.

thank you very much but still to solve all of my problems:
You said "1) did you wipe data, cache and dalvik cache? if not, try to do it and check again for bootloops. If not possible then reflash the firmware and try to wipe these things directly after flashing the firmware."
what do you mean by that? which firmware to reflash CM10? how by restarting the phone? and will i be able to go into CWM without the boot.img?

chossen said:
thank you very much but still to solve all of my problems:
You said "1) did you wipe data, cache and dalvik cache? if not, try to do it and check again for bootloops. If not possible then reflash the firmware and try to wipe these things directly after flashing the firmware."
what do you mean by that? which firmware to reflash CM10? how by restarting the phone? and will i be able to go into CWM without the boot.img?
Click to expand...
Click to collapse
With different phone and different firmware i had some issues with recovery, specially if i didnt wipe directly after flashing the new firmware without reboot and without reboot into recovery ...
I hope i dont mix anything up. CWM is the recovery (?)
The recovery function is part of the kernel image which is exactly the boot.img.
You can see at the freexperia project page howto install CM10, i cant post links at the moment.
3rd point is flashing the CM kernel (boot.img)
4th point is booting into recovery
From that recovery you can flash the custom rom as described in point 5.
Point 6 is wiping the device, which is neccessary for first custom rom or if you change version (eg. CM9 to CM10) or if you change to a different ROM.
Most bootloops happen if you forget to wipe the device. I am not sure, but most important is dalvik cache, if that one is wiped the next boot takes longer, as it will be rebuilt during boot.
If you get into a bootloop after flashing kernel and custom rom, go into recovery and wipe the device, try rebooting.
If still in bootloop, try to reflash the custom ROM as in point 5 (starting at 4th point) and wipe device after flashing
If it didnt help, try reflashing the kernel and ROM, starting at point 3 and include the wiping the device.
If that didnt help, try to go back to full stock (kernel and rom) and repeat.
But check if you got the correkt ROM for your device.
Play a bit around with the steps, you can even reflash the kernel and leave the rom. I had once a bad situation with bootloops, but they are easy to fix. More important is the part with the kernel, i think there you can brick your device.
But when you follow the instructions you shouldnt have too many problems, just dont jump over a step at the first flashing. But as allways sayd, every custom rom, every kernel flashing can harm your device and you're responsible on your own.
But if you get into problems, write down what you did and you will get help here.
Edit:
"if not possible then reflash the firmware ..." There i had once a problem with a different device. I forgot to wipe after flashing a new version and got into a bootloop. In recovery i couldnt wipe the device fully, something got bugged, but reflashing helped. Reflashed wiped and i could reboot into system. As it was longer time ago i dont remember what exaclty happend, but i think the problem was about forgetting to wipe the device.

Wow Thank you soo much, you lost allot of time explaining this to me, I really appreciate it i understood everything I owe you really
ooh and what do you mean by wipping - all: factory reset, cache and dalvik or just cache?
Sent from my LT26i using xda premium

chossen said:
Wow Thank you soo much, you lost allot of time explaining this to me, I really appreciate it i understood everything I owe you really
ooh and what do you mean by wipping - all: factory reset, cache and dalvik or just cache?
Sent from my LT26i using xda premium
Click to expand...
Click to collapse
didnt take too much time
in case of first custom rom, changing custom rom version (e.g. CM9 -> CM10) or changing to a different custom rom: all: factory reset, cache and dalvik
in case of updating (e.g. CM10->CM10): dalvik should be enough, maybe cache and dalvik.
If something not working, do a complete wipe.

As I understand from what I read, you flashed cm10 and are now stuck at boot, did you fastboot the kernel? On my xperia s I always need to fastboot the kernel after flashing a ROM, especially when changing from an ICS to a jb ROM.
Sent from my Xperia S using xda app-developers app

daddyc00l said:
As I understand from what I read, you flashed cm10 and are now stuck at boot, did you fastboot the kernel? On my xperia s I always need to fastboot the kernel after flashing a ROM, especially when changing from an ICS to a jb ROM.
Sent from my Xperia S using xda app-developers app
Click to expand...
Click to collapse
No, he has no bootloops, from what i understood he is scared to get into bootloops and doesnt know what to do if it happens.
Hmm, kernel flashing after upgrading from ICS to JB? or all the time?
By kernel flashing you mean the boot.img flashing with fastboot, and its the same file as flashed before?

I've only ever fastboot'd my first kernel, advanced stock kernel. Any others have always been in recovery and never had any issues
Sent from my Android 4.2.2 Xperia S

It seems that you got the wrong Kernel. I'm not sure, of course.
But I had that issue some time ago, and a fix it flashing the right kernel that I found on xda forum. Ohh, dont forget to do the proper wipes.
I hope u solve this as soon as possible.

For some good info on recovering a phone read through the recovery thread in my signature.
Even if you don't have any issues now, you can see what others have done wrong & right.
From Jaramie's LT28at
2012Xperia SOFT-BRICK Recovery Thread

[Solved] Bootloop after flashing any Touchwiz based rom

Hi,
For about a few days, I can't flash any touchwiz based rom, even the ones I could flash without any problem before. After I flash any touchwiz rom, my phone goes into a bootloop cycle. Though I can boot into recovery and download mode with key combinations. I don't know when this happened for the first time but as far as I can remember, it would be after I flashed some 4.4 AOSP rom (could be Omnirom, I'm not sure though)
What I did to recover from boot loop:
- Wipe cache, wipe dalvik cache and reboot, no joy.
- Wipe cache, wipe dalvik cache, wipe data, reboot, no joy.
- Wipe cache, wipe dalvik cache, wipe data, wipe data/media, reboot, no joy.
- Pulled out the battery between these steps too.
At first, I thought something was wrong about the aroma installer itself because the phone was getting frozen during aroma installer setup screen, then I came up that it was caused due to my older CWM version, so I updated the recovery and it didn't freze again during installation.
And by the way, I've lost my efs partition during these processes, thankfully I've had a nandroid backup from a couple of months before.
Now I'm stuck with AOSP roms and the only way I can use a touchwiz rom is to flash the stock rom via odin. But I want to use the new leaked version based Note3 featured roms.
I've seen similar topics at S4 section but I couldn't be sure if I can do the exact steps for an N7100 international device.
I'm pretty familiar with linux system and I can use adb so I can provide any kind of information you need to diagnose this issue. Thanks in advance. Best regards.
HOW I SOLVED THIS PROBLEM
- Wiped everything (system, data, sdcard, of course internal sdcard)
- Flashed n7100 16GB pit file via odin
- Flashed stock rom via odin
- During these steps, I realized that my CSC code had been changed, I've corrected it acording to my country code
- Rooted my phone again
- Flashed CWM 6.0.4.3 recovery
- Flashed DN3 V3.1 rom
- Bingo, I successifully booted into DN3 rom but had no WIFI
- Flashed MJ5 bootloader
- Rebooted, then WIFI worked without a problem
- Setup my phone and did some restore
It's all good now. Thanks for everything, I hope these steps can help someone facing the same problem.

Guys, I really need some help.. Any idea about what might the problem be?
Sent from my GT-N7100 using XDA Premium 4 mobile app

Download HD wipe script,flash the script zip via cwm/philz then try installing the rom of your choice.
I found the script from tamirda's phoenix rom thread and is very useful:http://d-h.st/fWr

Full wipe cache and reset in recovery menu, clear everything, you should be up and running.

akp.ajinkya said:
Download HD wipe script,flash the script zip via cwm/philz then try installing the rom of your choice.
I found the script from tamirda's phoenix rom thread and is very useful..
Click to expand...
Click to collapse
Thanks for the reply. I flashed this superwipe script, then flashed DN3 rom but still I got stuck at Samsung Galaxy Note II screen boot loop. I really don't understand this. What am I missing? What would happen if I wipe the entire internal memory block, I mean the whole things, even the root partition too.. I'm thinking that maybe there's some file inside the root partition that prevents me to flash touchwiz roms or perhaps something wrong about touchwiz based roms' bootloaders.. I'm truely pissed..
(InsertNameHere) said:
Full wipe cache and reset in recovery menu, clear everything, you should be up and running.
Click to expand...
Click to collapse
Have you read my first message? I remember that I've mentioned I've done already what you ask me to do.. Believe me I wouldn't shoot a new thread if I could've solved my problem with such easy steps. I've already done so many wipes, including internal SD and whatsoever.. I'm really confused and NEED help. Thanks anyway..

I think you can go for the method you mentioned.But also give a try to start fresh i.e pit file flashing...wiping everything n installing stock rom then rooting,flashing custom recovery n then installing any TW custom rom.
Also give other TW based roms a try too.

Im having the same problem but after flashing kernels (e.i. saber & perseus).
Im currently running on Tigra rom. Is this a compatibility issue or im just missing something here too?
I came across flashing bootimg but this thread http://forum.xda-developers.com/showthread.php?t=1752270
is for One S, im not sure if will work on Note 2 & haven't tried it yet.
Any suggestions? help pls...

akp.ajinkya said:
I think you can go for the method you mentioned.But also give a try to start fresh i.e pit file flashing...wiping everything n installing stock rom then rooting,flashing custom recovery n then installing any TW custom rom.
Also give other TW based roms a try too.
Click to expand...
Click to collapse
Well, the problem is gone.
What I did was the things you said.
- Wiped everything (system, data, sdcard, of course internal sdcard)
- Flashed n7100 16GB pit file via odin
- Flashed stock rom via odin
- During these steps, I realized that my CSC code had been changed, I've corrected it acording to my country code
- Rooted my phone again
- Flashed CWM 6.0.4.3 recovery
- Flashed DN3 V3.1 rom
- Bingo, I successifully booted into DN3 rom but had no WIFI
- Flashed MJ5 bootloader
- Rebooted, then WIFI worked without a problem
- Setup my phone and did some restore
It's all good now. Thanks for everything, I hope these steps can help someone facing the same problem.

Happy to help you bro

[Q] [need help] every ROM get's stuck on boot animation

I tried:
different recoveries ( 2 versions of TWRP and 1 other ) , flashing different kernels, wiping cache/dalvik cache/factory reset like 100 times, 3 ROMS that used to work in the past
I didn't try flashing a rom with adb because I can't get it to work, but I don't know if it would help.
The only thing that works is stock ROM with stock kernel and stock recovery. ( ROM from EN MIUI forum )
Everything else just gets stuck on the boot animation ( the cyanogenmod/mokee/... logo )
btw: already tried googling, but all I found is how to fix the problem by installing stock everything but the problem is I hate the stock rom/recovery and If I flash a custom recovery and ROM after fixing it, it just gets stuck again.
Thanks in advance

As you already tried TWRP and not working, here is something u can try...
1)Flash Original miui for redmi 1s
2)then flash philz touch through stock recovery
3)then try to install CM 11 or other ROM
Not sure if it will work for you but you can try
BANG that THANKS button

lanadekat said:
I tried:
different recoveries ( 2 versions of TWRP and 1 other ) , flashing different kernels, wiping cache/dalvik cache/factory reset like 100 times, 3 ROMS that used to work in the past
I didn't try flashing a rom with adb because I can't get it to work, but I don't know if it would help.
The only thing that works is stock ROM with stock kernel and stock recovery. ( ROM from EN MIUI forum )
Everything else just gets stuck on the boot animation ( the cyanogenmod/mokee/... logo )
btw: already tried googling, but all I found is how to fix the problem by installing stock everything but the problem is I hate the stock rom/recovery and If I flash a custom recovery and ROM after fixing it, it just gets stuck again.
Thanks in advance
Click to expand...
Click to collapse
Had you tried to wipe cache, dalvik, data, and system before? I had my problem solved with custom rom
See here, focus what written at Edit section, ignore else. Just curios thou.. Need to be confirmed by others. Thanks

presetz said:
Had you tried to wipe cache, dalvik, data, and system before? I had my problem solved with custom rom
See here, focus what written at Edit section, ignore else. Just curios thou.. Need to be confirmed by others. Thanks
Click to expand...
Click to collapse
Could be the problem I asked the guy/girl who posted it how he fixed the problem. I'll also look for another non-CM based ROM and see if it works.

lanadekat said:
Could be the problem I asked the guy/girl who posted it how he fixed the problem. I'll also look for another non-CM based ROM and see if it works.
Click to expand...
Click to collapse
Just try what i said, wipe cache, dalvik, data, system,
As i recalled (i used twrp) reflash twrp. Leave it without OS
After reboot update twrp to 2.8.6.0 allow to install root, reboot.
And after you enter twrp recovery once again, do clean install as custom rom "how to install" instructed. Hope that help, might have to try other than cm, just for testing it.
Hit thanks if it work, else dont curse on me

presetz said:
Just try what i said, wipe cache, dalvik, data, system,
As i recalled (i used twrp) reflash twrp. Leave it without OS
After reboot update twrp to 2.8.6.0 allow to install root, reboot.
And after you enter twrp recovery once again, do clean install as custom rom "how to install" instructed. Hope that help, might have to try other than cm, just for testing it.
Hit thanks if it work, else dont curse on me
Click to expand...
Click to collapse
oh haha I didn't notice you were the same guyI thought you linked me to someone else's post xD I'll try it, I hope it works!
edit: thanks! reflashing the kernel, wiping everything, then fixing the permissions ( but not the SElinux permissions ) fixed the problem for me I'm back to android 12.1
I'll see if I can close the thread.