Database Develop

[CM9] Investigation on Bootloops

Hey folks,
being stuck in bootloops is one of the most annoying things for us powerusers.
Therefore I want to investigate a little bit deeper into this topic.
The normal procedure of "solving" the bootloops for me was flashing a base Gingerbread ROM by Ficeto (Mostly JVT) via ODIN, disabling Lagfix, entering CWM & flashing ICS again.
But one time (about 2 weeks ago) I had no time to go through this process, so I took the battery out of the phone (to abord the bootprocess & shut the phone down), placed it in again & putted the phone back in it's pocket.
About one hour later when I looked at it by accident (wanted to check the clock & forgot that it was bootlooping) the phone was fully booted & back to normal.
so the last 4 times my GT-i9000 (running nightlys of CM9) got stuck on the Bootscreen coming again & again, I took the battery out, placed it in again & let it bootloop for a while & after about 20 minutes baaam my SGS was properly booted?!
So my question/request is for you if you are stuck in bootloops:
[highlight]Please try the following:
1. Take the battery out & place it in again
2. Start the phone again
3. wait, wait, wait & be patient
4. Tell me if the problem solved itself or if after more than 2 hours of bootlooping nothing happened [/highlight]
if it didn't please tell me how long you've waited, what caused the looping & which nightly etc you where running!
just for clarification: with bootloops i mean being stuck on the Samsung Galaxy S / Cyanogenmod Screen where it is written in plain text which appears before you can enter recovery or the normal bootanimation appears. When my phone was/is bootlooping I also have no chance to enter Recovery. & I also know that it sounds strange that BL should solve themselves, but please try it!
[edit] I also read some time ago that there where other people with the same experience, this is why I opened a thread & I'm sure this is not a thing related to only my phone

I experienced something similar , also with CM9 . Phone working very hard , so i restarted it , but after the Galaxy S GT i9000 screen , the CM9 blue boot loaded for about 10 minutes and nothing , so I decided to enter in recovery ( I removed the battery , waited a minute , inserted it in the phone , and the recovery didn't work . Waited 10 minutes , and after that the recovery worked , and I reflashed CM9 , because it was the only rom I had in the internal SD card .

About two hours without any improve... CM9 build 12 working every time, build 15 and 16 without chance. Odin is my honey

Thomas. said:
About two hours without any improve... CM9 build 12 working every time, build 15 and 16 without chance. Odin is my honey
Click to expand...
Click to collapse
It would be nice if you could tell exactly what you did, if more people would do that we might be able to figure out why this thing happens to you and why it doesn't happen to me.
when i flash:
*phone not connected to pc or charger
*running stock kernel
*16 gb micro sdcard mounted
*all sorts of battery percentage, from 10 to 100 percent
*reboot recovery by terminal command "reboot recovery"
*format /cache
*flash the build from /mnt/sdcard/download
*flash gapps from same location
*run a script that wipes dalvic, removes several sounds and unwanted apps and fixes permission
*format /cache again
*reboot
I know this is a pretty weird procedure and it's in no way an advice to anyone, it is just an example of giving details that might lead to a common factor for bootloops.
Taptalked u see

Ok briefly (as I'm not home at moment) I have had bootlooploop on 2 separate occasions. Both times I left for 35 mins looping & then removed battery.
After 20 mins I put battery back & same thing - looping for around 30 mins.
No recovery available on both occasions. I tried taking out Sim card & external SD but this didn't make any difference.
So I just flashed CM7 kernel via Odin = problem fixed !

BLADESMAN1889 said:
Ok briefly (as I'm not home at moment) I have had bootlooploop on 2 separate occasions. Both times I left for 35 mins looping & then removed battery.
After 20 mins I put battery back & thing - looping for around 30 mins.
No recovery available on both occasions. I tried taking out Sim card & external SD but this didn't make any difference.
So I just flashed CM7 kernel via Odin = problem fixed !
Click to expand...
Click to collapse
Thanks for your post!
What caused the bootloops?

fipsib said:
Thanks for your post!
What caused the bootloops?
Click to expand...
Click to collapse
1st time I got bootlooploop was [15/Jan/2012] I was trying to boot into Recovery via power button so I could upgrade from Build 12 to Build 13.
2nd time [2/April/2012]I was on AOKP B28 & I had booted into Recovery to wipe cache & dalvik & after successfully wiping, the bootloop came when I hit the 'Reboot' option to start the phone.
(AGAINST better judgement - since first bll I had avoided wiping cache & dalvik)

jep. I also had bootloop problems by wiping cache and dalvik cache. I was on SlimICS flashed midnight kernel. Everything was working just right but CPU scaling had some bugs for me so i removed init.d scripts went into recovery wiped cache and dalvik cache...and boom....bootloop :/. Now I'm back on CM7 because this is a rather annoying problem....

BLADESMAN1889 said:
Ok briefly (as I'm not home at moment) I have had bootlooploop on 2 separate occasions. Both times I left for 35 mins looping & then removed battery.
After 20 mins I put battery back & same thing - looping for around 30 mins.
No recovery available on both occasions. I tried taking out Sim card & external SD but this didn't make any difference.
So I just flashed CM7 kernel via Odin = problem fixed !
Click to expand...
Click to collapse
Can you link me CM7 kernel for Odin? thanks

farid993 said:
Can you link me CM7 kernel for Odin? thanks
Click to expand...
Click to collapse
Yep, here it is,
View attachment 1012442
This worked for me both times
[remember to leave UNCHECKED
Ensure Reboot, Repart, F-Reset]
Then boot into Recovery and restore Nandroid - no need to be flashing gingerbread.

Ever since the first nightly, I have been plagued by bootloops. Usually formatting /system, /data and /cache helped. But not this time. I tried to install the 19/4 nightly, and had gotten into bootloops. Yes, I have used custom kernels before.
However, even clearing init.d, clearing NSTools, flashing from FixRecovery, the cm7 kernel, even flashing with Heimdall (flashing stock kernel and custom kernel) could not get me out of the loop. Note: I tried the method as described in the OP.
What I finally did was format everything, excluding ext-sd. Format internal SD as well, after backing up some files. And BAM! That was it! Something on the SD corrupted the install. No bootloops, can even install custom kernel, no problem.
So, that may be a tip for people not able to get out of the bootloop, or experiencing constant bootloops.

Hey it's under Devs investigation now:
http://forum.xda-developers.com/showthread.php?t=1627689

My galaxy with CM9 started to bootloop yesterday, no way to enter recovery
I'll make you know in a couple of hours if something change leaving it on ..
If nothing change, is there a place where I can find CM9 kernel to flash with odin ?
thanks

Read Bejda's post, one post above yours.
Taptalked u see

wooops didnt see the second page of the thread
anyway leaving it there to bootloop didnt solve the problem
flashing semaphore kernel seems yes

Device is stuck on boot logo

Hello, I have a problem with my Galaxy Note and I don't know what to do.
A few hours ago I tried to start the device as I usually do after I turn it off, but the device does not turn on and only stays stuck on this screen: "Samsung galaxy note n7000".
I'm running this Rom: "[ROM][4.1.2 JB]Ultimate N7000 XXLSC JellyBean 4.1.2 v5.1".
I have the ability to log into CWM by the combination of the known keys
I hope you guys can help me, thanks in advance.
(Note: The battery is charged and i also tried to remove it and put it back in.)

This problem happened to me before with the xxlsa leaked rom
Do a wipe from a safe kernel and flash the rom again

Try to boot into recovery and do a reboot recovery and then reboot.
Else you may do a backup and restore the same backup. It works most of the time. But a little time consuming.

Had same problem by loosing power. The device wont boot anymore. Fix per, reinstall without wipe did not work. Switch rom

i believe this problem comes to all jelly bean leak always Stuck on the first boot.
just got this problem again how i did it ？press power on Stuck on first boot next step straight away press 3 button go to recovery n hit reboot system n my phone bootup n back to normal.

terminator_5505 said:
This problem happened to me before with the xxlsa leaked rom
Do a wipe from a safe kernel and flash the rom again
Click to expand...
Click to collapse
How can i replace the kernel and reinstall the rom if I cannot see the device on my computer when it's connected?
nokiamodeln91 said:
Try to boot into recovery and do a reboot recovery and then reboot.
Else you may do a backup and restore the same backup. It works most of the time. But a little time consuming.
Click to expand...
Click to collapse
I've already tried both methods you have specified and none of them worked.
My attempt to make a Nandroid backup has failed and the CWM said something like "backup of /data failed".
alvinhaw said:
i believe this problem comes to all jelly bean leak always Stuck on the first boot.
just got this problem again how i did it ？press power on Stuck on first boot next step straight away press 3 button go to recovery n hit reboot system n my phone bootup n back to normal.
Click to expand...
Click to collapse
Hi, this is not the first time I try to boot the device after installing a new rom.
I'm with this rom for a few weeks now and the problem occurred only yesterday.

This is well known problem with xlsc rom. U have to wipe everything and to flash rom. There are some solutions with backup/restore but they didn't work for me.
So, complete WIPE, and than flash!!

Backup of data failed because of insufficient space. Make backup to internal if there is more space.

i have the same problem since i full wipe and flashed asylums 20130302 build. after doing a full wipe and clean install, i started downloading my regular apps from playstore and suddenly it turned off just like when you remove the battery.
i tried the following::
1. full wipe and installed the rom -- it boots up few minutes then shuts off and wont boot up without charger
2. restored from nandroid -- same as above
3. full wipe and installed previous builds -- same
4. full wipe + flashed latest build 20130303 + latest gaps for JB 4.2 -- same
5. check battery stat -- ok
whenever it shuts off, it wont turn back on unless without a charger. it just shuts off at random. this is the second day I'm experiencing it and its frustrating.
any help? thanks
edit:: btw it shuts off at boot animation

In the other thread where you asked this question too there are members who replaced their battery and solved it this way.
Maybe you should try this and replace the battery.
Good luck.

I got same issue and I'm for kill someone. Why these problems on a official rom?

[Q][GT-I9001] Ivendor CM10 plus CastagnaIT Kernel (from Softreboot to Hardbrick)

Hello everyone,
I just hardbricked my SGS+ and now I'm a bit curious how this could happen.
This is what I did:
I used to run CM9 RC5 from arco68 along with the Kernel for ICS from Christopher83 and CWM 6.0.1.2.
Because my phone always lost the wifi-connection and also had some freezes I decided to try out CM10 Beta 3 from ivendor.
I backuped my phone, downloaded the zips and even verified the MD5sums. Next I flashed CWM 6.0.1.9 as recommended in the thread from ivendor.
After exporting the nandroid backup and other stuff like photos to my computer I wiped everything as mentioned in the thread, flashed the two zips and rebooted. Everything went fine and I was almost ready with setting up my phone again when I got my first softreboot.
Suddenly it showed the CM-bootlogo and after maybe 10 seconds I was back on my homescreen. I got another two or three softreboots until I decided to flash the Kernel 3.x from CastagnaIT.
I rebooted into recovery, wiped cache and dalvik cache, flashed the zip and rebooted.
Now I wanted to reboot into recovery again to fix permissions but instead I got a softreboot and my phone stuck at the CM10 bootlogo.
I waited for around 5 minutes and then I just turned the phone off and booted into the recovery mode.
Because I wanted a clean install without any problems like softreboots I decided to wipe my phone again (data, cache, system) and just reflash the zip for CM10. And at this point everything went wrong.
I flashed CM10 but when I tried to flash gapps my phone just turned off. And no, the battery was not empty. In fact the battery was at around 50-60% and my phone was also connected to my computer.
I tried to turn on my phone but now it stuck at the Samsung bootlogo.
The next thing I did was probably a horrible mistake. I tried to un-brick my phone but I did not realize that I could boot into download mode without problems so I guess my phone wasn't softbricked at all.
Well, after that I still stuck at the Samsung bootlogo and couldn't enter recovery mode. I got into download mode somehow and maybe this was my second mistake. I tried to flash the "i9001Reset.zip" via Odin. Everything went fine but when Odin said "Close serial port and wait until rebooting" my phone was completely dead. I think it was while I tried to flash the reset-file when I got a message like "MBR: read failed". So somehow I managed to destroy my master boot record.
Now I can't turn on my phone or enter download nor recovery mode. I already removed the battery for about 45 minutes but this didn't work either.
My phone is dead but at least I saved the important data and maybe I'll get a new one through warranty. Or I just buy a Nexus 4.
My questions are:
What did I do wrong especially when I tried to save my phone?
How can I prevent such things from happening?
And at which point I should have got help here in the forum or elsewhere?
I would really appreciate some tips for the future because I already flashed and used a lot of different ROMs but this is the first time something really went wrong.
Thanks for reading and thanks for your help in advance.
(Please excuse my non-perfect englisch.)
Greetings,
Mangoniter

HELP xperia z problem-cant solve it

hi guys, yesterday i did some flashing of roms just like i do almost every day or so, and i didnt like the rom(flyme rom) i flashed so i just tried to restore the previous rom which was the existenz rom .... so using TWRP, i put that to restore and i went to eat something but after a couple of minutes, i went to my phone to see if it was completed and it was powered off by itself... ( the phone was not completely charged but it had at least 50% of battery so i dont think battery is the issue here).....so after that,i powered it on and it stuck in a bootloop so i realized that the restore wasnt successful.... so i went into the recovery and i did a factory reset and i tried to flash another rom cm11 based (that i had been using some days ago) and the flashing was successful ( with gapps and ssu...) so i rebooted but nothing.... my phone powered off as it should but when it powered on, sony logo appeared (as it should) and then it suddenly powered off again..... i couldnt even enter the recovery cause it immidiately turned off 2 seconds after sony logo appears.....so i went into fastboot mode and i flashed a kernel of cm11 just to be able to enter at least the recovery .... successfully flashed boot.img but again couldnt enter the recovery...the same as before.....then i realized that if i tried to power on my phone while it was charging ( wall charger) it could boot and even enter the rom but still after some seconds it immidiatly powered off by itself for no reason...then i didnt know what else to do so i had a last chance.to flash an ftf....so i flashed one successfully using flashtool and the same problem again..... then i flashed another one ( older ftf ) but nothing..... then i tried to charge my phone until full ( i could see in TWRP the percentage) and then i powered on but the same..... however it did open whithout charging ....but again after some seconds it powered off again.... so i went in TWRP and i left it there open all night to drain all the battery ...and i noticed that it drained until 1% and then it took it about 1 hour to power off ....i mean it was on 1% with screen on for more than an hour.... so i think that the battery has to be reseted or something..... i dont know what to do.... i have unlocked bootloader, i have no warranty , and i dont even know what is causing that so please if somebody knows something about that tell me....
(btw before all that happened, my battery was fine...i could spend many hours with screen on.... i had not noticed any damage to the battery or something)

Try to flash a stock ftf to your phone from flashtool

tjlm21 said:
Try to flash a stock ftf to your phone from flashtool
Click to expand...
Click to collapse
They already did. Read before posting.
Sent from my C6603 using Tapatalk

A partition or partitions could be corrupted, and formatting is the only way to fix that. Not sure if flashtool formats before writing images - so..
1. Fastboot a kernel (boot.img) .
2. Boot into recovery and format EVERYTHING, including /data/media.
3. Power off phone.
4. Flash an ftf.
Good luck:thumbup:

shoey63 said:
A partition or partitions could be corrupted, and formatting is the only way to fix that. Not sure if flashtool formats before writing images - so..
1. Fastboot a kernel (boot.img) .
2. Boot into recovery and format EVERYTHING, including /data/media.
3. Power off phone.
4. Flash an ftf.
Good luck:thumbup:
Click to expand...
Click to collapse
thanks for posting but i already did that.... i will buy a battery and i hope that solves the issue :/

[Q] Stuck on Welcome Screen... lenovo k3 note

(its my dad phone)
hi so yestarday i installed the "aosp-k3note-5.1.0" rom and it all went fine but worked slow and without bluetooth.
so today when i got home my dad told me he just installed a new rom from romnation(he dosent remember which rom but he said it was an offical rom)
BUT he downloaded it stright to the phone and installed it without erasing anything(date/cache/davlik)...
so when he tried to use the phone it will gives errors like gaps stoped working and all kind of stuff that made the phone useless...
so i downloaded "VIBEUI_V2.8_1526_7.80.1_DEV_K50-T5" rom and gapps64 and went to the CMW and this time i erased the date cach and davlik and installed the rom and after that the gapps
and now i cant get past the welcome screnn becuase as soon as i choose english or chinse it will give me "wlan has stopped" and return to the language menu...
so now im stuck becuase i cant use adb to root it and SP tools dosent work too(i tried to keep it pluged for an hour and it still wont do anything with ot without the battery)
what can i do? and thanks for any help...

Try this to get CWM back on.
rollcage0 said:
(its my dad phone)
hi so yestarday i installed the "aosp-k3note-5.1.0" rom and it all went fine but worked slow and without bluetooth.
so today when i got home my dad told me he just installed a new rom from romnation(he dosent remember which rom but he said it was an offical rom)
BUT he downloaded it stright to the phone and installed it without erasing anything(date/cache/davlik)...
so when he tried to use the phone it will gives errors like gaps stoped working and all kind of stuff that made the phone useless...
so i downloaded "VIBEUI_V2.8_1526_7.80.1_DEV_K50-T5" rom and gapps64 and went to the CMW and this time i erased the date cach and davlik and installed the rom and after that the gapps
and now i cant get past the welcome screnn becuase as soon as i choose english or chinse it will give me "wlan has stopped" and return to the language menu...
so now im stuck becuase i cant use adb to root it and SP tools dosent work too(i tried to keep it pluged for an hour and it still wont do anything with ot without the battery)
what can i do? and thanks for any help...
Click to expand...
Click to collapse
Try removing the battery and plugging the phone in to the PC.
Start SP Tools with CWM set in the scatter and only recovery ticked
Press Download in SP tools and then insert the battery
CWM should download to phone
If that fails repeat but plug the phone in once you press Download, then insert the battery.

rollcage0 said:
(its my dad phone)
hi so yestarday i installed the "aosp-k3note-5.1.0" rom and it all went fine but worked slow and without bluetooth.
so today when i got home my dad told me he just installed a new rom from romnation(he dosent remember which rom but he said it was an offical rom)
BUT he downloaded it stright to the phone and installed it without erasing anything(date/cache/davlik)...
so when he tried to use the phone it will gives errors like gaps stoped working and all kind of stuff that made the phone useless...
so i downloaded "VIBEUI_V2.8_1526_7.80.1_DEV_K50-T5" rom and gapps64 and went to the CMW and this time i erased the date cach and davlik and installed the rom and after that the gapps
and now i cant get past the welcome screnn becuase as soon as i choose english or chinse it will give me "wlan has stopped" and return to the language menu...
so now im stuck becuase i cant use adb to root it and SP tools dosent work too(i tried to keep it pluged for an hour and it still wont do anything with ot without the battery)
what can i do? and thanks for any help...
Click to expand...
Click to collapse
Omg..i have almost exactly the same problem and the solution that MrAAnderson suggested didn't work.Here's how i ended in this problem.I was running VIBEUI_V3.0_1602_7.407.1_DEV_K50-T5 ROM on TWRP recovery made By Pr1nc3V app Lenovo K3 Note Manager [v2.1].Since i had annoying bug with "R" (roaming icon) and "gapps stopped working" issue i wanted to re-flash same ROM.I entered into TWRP recowery,cleared dalvik+cache,rebooted into recovery again.Now i wanted to flash ROM,but it didn't flash it gave me an error,same thing happens if i try to flash stock recovery (i even tried naming ROM and recovery as "recovery.zip" and "update.zip").Rebooted the phone but i'm also stucked on welcome screen where i can't pass it because of "Unfortunately,WLAN stopped working".
Tried to flash ROM and stock recovery with SPFlashTool but the tool doesn't see phone at all,same as Lenovo K3 Note Manager by Pr1nc3V .Right now i'm running out of solutions for this mess i created,any advice will help.Help me please to restore my phone.
EDIT: i just realized that i actually made a "factory reset" in TWRP recovery..not just wipe data,cache and dalvik.....what are my options now folks?

Ok i'm happy to announce that i resolved my problem (after a panic mode on,lol).Here is what i did..
1. Obviously you have to get back on your stock (original,ugly chinese-english one) recovery (in case you already didn't..).To do that i used SP Flash tool.(i wouldn't go into details but if you need just ask).
After that we have following situation..stock recovery + dev ROM (which isn't working well).
2.If you try to flash any ROM in this state it will fail (based on my experience,i tried to flash exactly same ROM which is already installed..no way.).So now next step is to get a CUSTOM (TWRP or CM) recovery,again flashing it with SP Flash tools.
From this point you can choose wher would you go...STOCK rom ,MODDED one ...anything actually.I hope i clarified a bit.

sptools is not detecting my device