Database Develop

[Q] Corrupted /cache on CM7

Well, something interesting just happened with my CM7. I've beed running it for 4 days and it has been a completely different device (for the good). But 30min ago everything started force closing (3G Watchdog, Gmail, G+). I tried to reboot but then completely stuck. It couldn't move past the LG screen (just turned off). It wouldn't even boot into CWM. Then I realized if i kept the power button pressed, I can work my way through CWM. As soon as I released it, it will turn off. So I managed to wipe cache and dalvik from there and all of the sudden everything is back to normal.
At first I thought I lost EXT4 journaling, but just checked and it's still there. Did anyone face something similar? This was completely weird and freaky. I'm glad everything is OK.

never had such a problem or heard of it before. i know that when i flash a new build without wiping cache and dalvik my phone is very unstable. also a complete wipe and advanced restore data does wonders.
Sent from my Optimus 2X using XDA App

I wiped/factory restored before flashing CM (4 days ago). I noticed someone mentioned something similar (force closes and such) in the CM nightlies thread. I managed to check what was the reason of force closes (before I couldn't even boot) and every time it was because of SQLite error. Seems like apps weren't able to access their database files (which are in /data I suppose).
It really looks like a standard boot loop which happens sometimes after a installing a new build, but this was just out of the blue. Will see how it behaves in the next few days.

[Q] CM9 Reboot Issue

I just installed CM9 via the Novacom2 method. The tablet seems to reboot itself after a few minutes of being booted up for no apparent reason. I can start up the device, and not even touch one thing, and after a bit it will self reboot.
Anyone experiencing this? Should I do a reinstall? Novacom2 method, or a complete factory reset with CWM?
CM9 runs extremely smooth otherwise, but I can't have it up for more than 5 minutes with a self reboot. It's bizarre.
Thanks in advance people...

I meant ACMEInstaller2 where I wrote Novacom2 ....

The only time I got random reboot is if I try to overclock. I went to replace CWM with TWRP today, and checked in CPUspy something quick. I had 36 hours of up time (remember this only dropped 4 days ago). Initially I tried to OC, even only going one step up I got freezes, and reboots. But leaving it at stock frequencies I have zero stability issues.
I would say to start fresh. With a fresh downloaded copy. Go into CWM and wipe data / factory reset, wipe cache, advanced > wipe dalvik, mounts > format system, data, cache, then reinstall, and install the charge fix. Then don't restore anything, and see if that fixes it.
Sent from my Galaxy S II (i777)

that may be the route I go. After about 15 reboots it is currently holding steady I have not made any interventions.
As a side issue, I get email notifications but the email app crashes upon opening. Gmail works fine though....

quarlow said:
The only time I got random reboot is if I try to overclock. I went to replace CWM with TWRP today, and checked in CPUspy something quick. I had 36 hours of up time (remember this only dropped 4 days ago). Initially I tried to OC, even only going one step up I got freezes, and reboots. But leaving it at stock frequencies I have zero stability issues.
I would say to start fresh. With a fresh downloaded copy. Go into CWM and wipe data / factory reset, wipe cache, advanced > wipe dalvik, mounts > format system, data, cache, then reinstall, and install the charge fix. Then don't restore anything, and see if that fixes it.
Sent from my Galaxy S II (i777)
Click to expand...
Click to collapse
I did a fresh start as above and the CM9 from is running problem free and 10x better than before when I had done the acmeinstaller2 method. Thanks button hit.

gizmo2431 said:
I just installed CM9 via the Novacom2 method. The tablet seems to reboot itself after a few minutes of being booted up for no apparent reason. I can start up the device, and not even touch one thing, and after a bit it will self reboot.
Anyone experiencing this? Should I do a reinstall? Novacom2 method, or a complete factory reset with CWM?
CM9 runs extremely smooth otherwise, but I can't have it up for more than 5 minutes with a self reboot. It's bizarre.
Thanks in advance people...
Click to expand...
Click to collapse
Try fixing permissions and wiping up cache from CWM, that fixes the reboots after power-on for me.
It used to do it if I left the screen to go off, but is fine now

I too am having reboot issues, but it only happens when I'm doing something. So far trying to open the Photoshop PS Touch app will cause a reboot, clicking settings in boat browser, etc. It's strange as hell.

I as well get the stock android mail client crashing when opened but its notifacations and gmail all work. I just installed maildroid and disabled stock email and seems to work OK

gizmo2431 said:
I just installed CM9 via the Novacom2 method. The tablet seems to reboot itself after a few minutes of being booted up for no apparent reason. I can start up the device, and not even touch one thing, and after a bit it will self reboot.
Anyone experiencing this? Should I do a reinstall? Novacom2 method, or a complete factory reset with CWM?
CM9 runs extremely smooth otherwise, but I can't have it up for more than 5 minutes with a self reboot. It's bizarre.
Thanks in advance people...
Click to expand...
Click to collapse
I have the same issue, but normally when the screen is on, it always reboots when I try to connect to usb storage, I have a galaxy s2 running on stable(nightly had too many bugs). anyone has the same problem?

I usually get reboots when I let the screen turn off due to inactivity. I tried installing TWRP and doing a clean install from there but it rebooted at the setup screen for CM9. I've had reboot issues since I first installed CM9, but its improved a little bit. I did try uninstalling android completely then reinstalling, but still got reboots. Does anyone have any other suggestions?

I think the best thing to do is use ACMEUninstaller to complete remove Android from your TP, then reinstall from scratch. I had reboot issues after upgrading from CM7a2 until I did a complete wipe.

[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

[Q] Random reboots, bootloops, etc

Ok so I'm pretty sure my phone is done for, but I thought I'd see if anyone knew a solution before I go buy a new phone
Yesterday I dropped my phone (which was running Slimbean), but I popped the battery back in and it worked fine. Then about three hours later, it randomly shut off while I was using it, then started going into a bootloop. Occasionally it will start up all the way, but I'm lucky if its on for 10 minutes before turns back off and starts bootlooping again. I got it to boot into CWM, (the first time it shut off while I was in CWM) and wiped everything and reflashed Slimbeam, but it didn't change anything. Any ideas?

Go back in and do wipes on everything but external drive reflash wipe cache + dalvik cache + fix permissions then boot. Let sit 10 minutes before doing g any setup with Google or phone. This allows all drivers to load and configure prior to having more data to configure.
Sent from my CM10 Linero Odexed Powered by Evil

Unfortunately, (Multiple apps) has stopped issue - reboot

After using my 910t one night playing a game it suddenly froze up and I had to do battery pull. When it restarted I got the whole Unfortunately (multiple apps) has stopped and then it rebooted. Tried clearing cache - dalvik, reinstalling rom, using TWRP backup, and finally ODIN COG2 (firmware at the time) - and then thought maybe DOK2 would fix it so tried that as well. Same problem persisted. Wiped System - Internal - Data - Cache... I am able to get into TWRP, Stock Recovery, Download Mode, and ODIN finishes without any errors - but as soon as I get to the Samsung setup screen - it starts the whole Unfortunately ...... then reboots over and over. I did notice once ODIN firmware flash completed, the green android install bar after reboot would go almost halfway then reboot, wondering if thats a cause for concern as well. Any help would be greatly appreciated thanks!

After oden flash you should be back to normal. This is weird in deed.
@dannygoround