Database Info

[Q] CM7 with gapps built in?

Hi all,
on my very first flash of CM7, I had to install gapps. All worked well and I was happy.
Since then, every time I flash CM7, I get gapps already installed (yes I wiped all, yes I cleared dalvik cache, I even did the lock/unlock thing in order to clear all data).
I somehow get the feeling that my flashes are not a "clean" install.
did anyone else experience this as well?
thanks...

On your first time on CM7, wipe everything, flash cm7, flash gapps. When you want to update cm7, jus wipe cache and dalvik, then flash the updated cm7. No need to reflash gapps, no need to do a full wipe either.... unless you want to.
-Nexus S

So you mean that from now on. Gapps will always be installed? Even after full wipe/ factory settings?
Sent from my Nexus S using XDA Premium App

asafru said:
So you mean that from now on. Gapps will always be installed? Even after full wipe/ factory settings?
Sent from my Nexus S using XDA Premium App
Click to expand...
Click to collapse
That's not what he meant. He meant that if you are upgrading CM7, you do not need a full wipe at all.
But after a full wipe your Gapsps should be gone. It's weird that it is still there after a wipe. :S

It's still there after a wipe... is there a way to make sure I full wipe correctly?
Sent from my Nexus S using XDA Premium App

asafru said:
It's still there after a wipe... is there a way to make sure I full wipe correctly?
Sent from my Nexus S using XDA Premium App
Click to expand...
Click to collapse
Wipe Factory/Dalvik/Cache: Full Wipe
Wipe Factory: Removes Apps + Settings
Wipe Dalvik/Cache: Wipes the cache but your apps + settings remain.
Wiping factory will delete your Gapps.
Proper way to flash CM7:
1. Wipe Factory/Dalvik/Cache
2. Flash CM7
3. Flash Gapps
4. Flash Kernel (Optional)
5. Reboot
Proper way to upgrade
1. Wipe Dalvik/Cache (Optional)
2. Flash Kernel (Optional)
3. Flash CM7
3. Reboot

asafru said:
So you mean that from now on. Gapps will always be installed? Even after full wipe/ factory settings?
Sent from my Nexus S using XDA Premium App
Click to expand...
Click to collapse
Upgrading to newer versions will now keep all your data in tact, so gapps will be there etc.

great, I think it's all sorted out now.
just one question though, I've read that CWM dalvic cache wipe doesn't work. Is that true?
If so, what is the best way to wipe dalvic cache and do factory reset (fastboot/adb commands are also welcome..)

asafru said:
great, I think it's all sorted out now.
just one question though, I've read that CWM dalvic cache wipe doesn't work. Is that true?
If so, what is the best way to wipe dalvic cache and do factory reset (fastboot/adb commands are also welcome..)
Click to expand...
Click to collapse
It works. Somebody confirmed this, the error that pops up during CWR is SD EXT.
You can check for yourself, run a logcat (search the forum) while the phones booting.

[Q] Process system is not responding. Would you like to close it?

I got this while replying to a text message...
I've been getting quite alot of these, from even various applications. It's driving me nuts!!!!
Is there any (permanent) solution for this??
ROM: Gummy
Kernel version: 3.1.10_IcyGlitch_V14-BS_I896-I897 [email protected] #1
Baseband version: T959TLJL3
I'd be forever grateful if this problem could be solved... I really love this ROM

First I would reboot to recovery, then wipe cache, in advanced wipe dalvik cache, then fix permissions. If the problem comes back , I would back up your apps, msgs, that you want, then, wipe system,cache, wipe data/factory reset, and reflash. Maybe a newer rom.
Sent from my SGH-I897 using Tapatalk 2

This is a bug firmware, also sometimes a problem when using swap. I recommend flash newest ROM, they are much better.
Sent from my SGH-I897 using xda premium

simple man said:
First I would reboot to recovery, then wipe cache, in advanced wipe dalvik cache, then fix permissions. If the problem comes back , I would back up your apps, msgs, that you want, then, wipe system,cache, wipe data/factory reset, and reflash. Maybe a newer rom.
Sent from my SGH-I897 using Tapatalk 2
Click to expand...
Click to collapse
I did the first thing you reommended, it didn't work and to make matters worse, ma phone doesn't pass the boot screen....
I quickly rebooted in recovery and made a nandroid backup - followed your second suggestion but i never made a backup of ma msgs because you didn't say so in the 1st suggestion... i can load new roms but can restore from ma nandroid backup

When you wipe dalvik cache, your phone can and will take several minutes to reboot, because it's rebuilding the dalvik cache. Secondly, wiping dalvik cache and fixing permissions wouldn't cause your phone to not boot. Between my wife's and my phone, I've flashed Roms, updated, experimented, fixed, stuff, etc... hundreds of times, and never has a dalvik cache wipe / fix permissions caused the phone to not boot. Hesitant to try to help, because you seem to be blaming me..... But if you can't restore a nandroid, it could be you're on a kernel in which the nandroid backup/restore feature doesn't work, you are running an earlier ICS build.
Sent from my SGH-I897 using Tapatalk 2.

aduka said:
This is a bug firmware, also sometimes a problem when using swap. I recommend flash newest ROM, they are much better.
Sent from my SGH-I897 using xda premium
Click to expand...
Click to collapse
Please elaborate... btw i have a friend tht has the same ROM and doesn't face the same issues like me :/

aduka said:
This is a bug firmware, also sometimes a problem when using swap. I recommend flash newest ROM, they are much better.
Sent from my SGH-I897 using xda premium
Click to expand...
Click to collapse
simple man said:
When you wipe dalvik cache, your phone can and will take several minutes to reboot, because it's rebuilding the dalvik cache. Secondly, wiping dalvik cache and fixing permissions wouldn't cause your phone to not boot. Between my wife's and my phone, I've flashed Roms, updated, experimented, fixed, stuff, etc... hundreds of times, and never has a dalvik cache wipe / fix permissions caused the phone to not boot. Hesitant to try to help, because you seem to be blaming me.
Sent from my SGH-I897 using Tapatalk 2.
Click to expand...
Click to collapse
I'm sorry if i came across like that...
just that the phone is driving me nuts
ALSO.... it's the second time i am seeing where reboot take way longer than usual after restoring from a nandroid backup. I av done quite a few and reboot takes less than 10mins. I attempted one the other day and 2hrs 30mins later all i saw was the splash screen and boot animation, phone HOTT!!
This evening again, it looked as if it was going to do the same thing thing... it passed 20mins, i can't sit around waiting for that again

It sounds like a flash to stock KK4 (Full Reparation) would be your best bet. If you're already on G. B. bootloaders, I would recommend the NO BOOTLOADER version, no use flashing bootloader unnecessarily. After that, I would flash the rom of your choice, following the instructions in the O. P. line by line.
Maybe a lot more current rom.
http://forum.xda-developers.com/showthread.php?t=1300843
Sent from my SGH-I897 using Tapatalk 2

duwii said:
Please elaborate... btw i have a friend tht has the same ROM and doesn't face the same issues like me :/
Click to expand...
Click to collapse
Then I recommend re-flash the stock kk4 NO BOOTLOADER, format the internal sd, install the ROM again and install all the programs manually, not with the nandroid backup.
Sent from my SGH-I897 using xda premium

Dirty vs Clean Flash

A dirty flash is only wiping cache and davlik then flashing your ROM....
a Clean flash is at LEAST factory reset/data wipe + wiping davlik(factory wipe takes care of /cache also)... Maybe doing a format /system also.
SO let the games begin! Which is better?! FIGHT!!
...

Brian Gove said:
A dirty flash is only wiping cache and davlik then flashing your ROM....
a Clean flash is at LEAST factory reset/data wipe + wiping davlik(factory wipe takes care of /cache also)... Maybe doing a format /system also.
SO let the games begin! Which is better?! FIGHT!!
...
Click to expand...
Click to collapse
If I switch ROM's I factory reset then wipe cache and dalvik cache. If it's a theme for example I only wipe cache and dalvik cache since the theme is suppose to be made for your ROM right?....don't see the reason to reflash the ROM as well.

Wipe data? What's that for? Is THAT why my phone won't turn on..........
Nightlies: No data wipe (yes to cache/dakvik)
New rom, even if it's the same android build: always, full wipe
Themes: No wipe at all, flash right on, right after flashing rom's. Don't like to wait for two bootups!
Sent from my SCH-I535 using xda premium

Il throw a vote to whichever works.. I usually dirty wipe.. If I have issues then clean it and try again.. With nightlies I tend to be fine dirty a lot, but even still I will do a clean every couple weeks just because..

why do so many folks wipe cache and dalvik after they wipe data? A data wipe/factory reset wipes all three, there is no need to do anything else.
I always wipe data, flash rom, then advance restore data only from a nandroid...dirty flashing in its most elegant form

So we all agree that a dirty flash is just wipe cache/dalvik cache.
Do you wipe prior to re-flashing, or afterwards? Does it matter?
Sent from my SCH-I535 using xda app-developers app

What about flashing a new, updated kernel for a rom you're currently using? What steps should be taken for that? For example, cleanrom 2.1 comes with cleankernel 1.1, but the kernel has been updated to 1.2 and is out as a seperate download. How would you update just the kernel that's made specifically for the rom you use?

xxx420 said:
What about flashing a new, updated kernel for a rom you're currently using? What steps should be taken for that? For example, cleanrom 2.1 comes with cleankernel 1.1, but the kernel has been updated to 1.2 and is out as a seperate download. How would you update just the kernel that's made specifically for the rom you use?
Click to expand...
Click to collapse
Dirty wipe
Sent from a SYNERGIZED GalaxySIII

When I dirty flash, I wipe data cache n dalvik cache. Once I flash what I wanted, I wipe those two once again n select "fix permissions" just in case
Sent from my SCH-I535 using Tapatalk 2

apet8464 said:
So we all agree that a dirty flash is just wipe cache/dalvik cache.
Click to expand...
Click to collapse
I disagree. I believe a dirty flash also wipes system. If you are 100% certain that your ROM build effectively wipes system as part of it's install routine, then you could skip this step, however I always wipe system to be safe. This works for me and I rarely need to wipe data or sd card(s).
---------- Post added at 11:01 AM ---------- Previous post was at 10:57 AM ----------
xxx420 said:
What about flashing a new, updated kernel for a rom you're currently using? What steps should be taken for that?
Click to expand...
Click to collapse
When changing Kernels but not the ROM in a separate recovery session than a ROM flash, you don't need to "dirty wipe." Just wipe cache and dalvik. Dalvik wipe is key so that the dalvik virtual machine can be rebuilt by the new kernel.

Thanks for the info guys.

I usually dirty on nightlies until I have issues. Always clean when switching roms.
Sent from my SGH-I535 using xda app-developers app

It is always good to complete wipe when switching roms.
Sent from my SCH-I535 using xda premium

What if im just switching between stock rom nandroid backups? Can I just restore from one to one? I only have two backups anyways both for stock. Never flashed a rom before
Tap'n

grin0048 said:
This isn't meant to be rude or anything, I'm just honestly wondering if there's any logical reason to think this is substantively different than just not wiping data?
Click to expand...
Click to collapse
I find that this method works better than just wiping cache and dalvik, since im advance restoring data over a clean flash. both ways are considered dirty flashing tho.

I wipe dalvik, cache and battery stats. Works like a charm thus far. Wiping data is what blows out the IMEI correct?

coldhardtruth said:
I wipe dalvik, cache and battery stats. Works like a charm thus far. Wiping data is what blows out the IMEI correct?
Click to expand...
Click to collapse
Incorrect, flashing anything is what may lead to losing your IMEI. Backup using the appropriate tools in the development section. Btw stop wiping battery stats, it's not necessary.
Sent from my SCH-I535 using xda app-developers app

droidstyle said:
why do so many folks wipe cache and dalvik after they wipe data? A data wipe/factory reset wipes all three, there is no need to do anything else.
I always wipe data, flash rom, then advance restore data only from a nandroid...dirty flashing in its most elegant form
Click to expand...
Click to collapse
Factory reset doesn't touch the davlik(Which I speculate(Guess) has to do more with the kernel than anything)
apet8464 said:
So we all agree that a dirty flash is just wipe cache/dalvik cache.
Do you wipe prior to re-flashing, or afterwards? Does it matter?
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
This is what I meant as a dirty flash when I made the thread yes...
xxx420 said:
What about flashing a new, updated kernel for a rom you're currently using? What steps should be taken for that? For example, cleanrom 2.1 comes with cleankernel 1.1, but the kernel has been updated to 1.2 and is out as a seperate download. How would you update just the kernel that's made specifically for the rom you use?
Click to expand...
Click to collapse
Usually when I flash a new kernel, or a different kernel, I just wipe the davlik cache and I am fine. There was some reboots after the first boot on the AOSP ROMs but afterwards it ran fine.
SlimSnoopOS said:
Incorrect, flashing anything is what may lead to losing your IMEI. Backup using the appropriate tools in the development section. Btw stop wiping battery stats, it's not necessary.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
SlimSnoop is correct. According to one of the developers of a very prominent ROM the IMEI issue was because our phones got confused sometimes(Randomly phone to phone) and tried to reset during a flash. The data it tried to reset was bogus, therefor losing IMEI. He is also correct far as the wiping battery stats. It's only usefull when you have really strange results with battery. Google for the real reason to use them.
Far as backing up your IMEI so you will never run into the problem of losing it.... go into your terminal (almost every ROM has a Terminal emulator)
Type this:
su
then hit enter. Grant permissions
then type:
reboot nvbackup
then hit enter. This will make your phone do some shyt and reboot, but you really shouldn't need to worry about your IMEI after this. Regardless of how many ROMs you flash or what you do or who you date or who you kiss, etc... blah blah....
This really should be the end all for the IMEI...

annoyngduck said:
Wipe data? What's that for? Is THAT why my phone won't turn on..........
Nightlies: No data wipe (yes to cache/dakvik)
New rom, even if it's the same android build: always, full wipe
Themes: No wipe at all, flash right on, right after flashing rom's. Don't like to wait for two bootups!
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
New rom only when their bases are different , like going from ics to jb, or the dev says to do it (Even then Ill try it without a wipe because im lazy).
Themes I never wipe anything
Nightlies never wipe anything.
Edit: If I do have issues I then go back and wipe delvik and cache . That usually straightens out any issues and allows me to keep my setup.

tonu42 said:
Hey but you know I'm right
Click to expand...
Click to collapse
Actually you're not right.
Sent from my SCH-I535 using Tapatalk 2

Random reboots. Advice?

I have been having random reboots with my nexus s. I have tried factory resetting the device. I am rooted and I have had this problem on both CM10 and AOKP M1. I have not messed with the kernels or overclocked the device. Any help would be great thanks!

Justin967 said:
I have been having random reboots with my nexus s. I have tried factory resetting the device. I am rooted and I have had this problem on both CM10 and AOKP M1. I have not messed with the kernels or overclocked the device. Any help would be great thanks!
Click to expand...
Click to collapse
Have you tried full wipe and reflash the ROM?
S-Beamed from my GS3 via xda premium

[email protected] said:
Have you tried full wipe and reflash the ROM?
S-Beamed from my GS3 via xda premium
Click to expand...
Click to collapse
When it happened on aokp milestone 1 I wiped and installed cm10 after a day or two on cm10 the same thing has started.

Justin967 said:
When it happened on aokp milestone 1 I wiped and installed cm10 after a day or two on cm10 the same thing has started.
Click to expand...
Click to collapse
You can't flash between different ROMs without full wipe and expect it to work. Just factory reset is not enough.
S-Beamed from my GS3 via xda premium

[email protected] said:
You can't flash between different ROMs without full wipe and expect it to work. Just factory reset is not enough.
S-Beamed from my GS3 via xda premium
Click to expand...
Click to collapse
you mean doing a wipe/factory rest in recovery isn't enough? I have been doing that for over a year on many different devices without any problems.

Justin967 said:
you mean doing a wipe/factory rest in recovery isn't enough? I have been doing that for over a year on many different devices without any problems.
Click to expand...
Click to collapse
Hi,
Yeah the more wiping the better:
All done via recovery....
Factory reset, wipe cache, wipe dalvik....then I flash a zip file called "wipe all" this basically wipe everything under mounts and storage except the SD card.
Call me careful but I do the above twice b4 any new ROM and I've had zero issues.
Good luck
Vs Nexus S4G using tapatalk2

Justin967 said:
you mean doing a wipe/factory rest in recovery isn't enough? I have been doing that for over a year on many different devices without any problems.
Click to expand...
Click to collapse
What I usually do when switching ROMs: all done in recovery, wipe/factory reset, format /system, then flash the ROM, flash gapps, wipe cache and dalvik cache again, reboot. If you still have random reboot without installing many apps, you may have a defective hardware component or you have some apps eating up all the memory forcing the system to reboot.
If you could, do this after a random reboot in a terminal and post the last_kmsg file here.
su
cat /proc/last_kmsg > /mnt/sdcard/last_kmsg
S-Beamed from my GS3 via xda premium

Encrypted? Have tried mostly everything.

I want start by saying that I did not take the 4.3 OTA from Verizon. I flashed my phone from 4.2.1 to 4.4.1 cm11 and various KitKat Roms. My last being mastamoons version. I wanted to flash back to a 4.3 TW ROM for stability. KitKat has been wonderful the days it decided to be 100% stable. But the myriad of issues plaguing my daily apps, freezing or phone rebooting warranted a flash to TW 4.3. I made a forum post because I was not entirely sure how to flash from 4.4 AOSP back to 4.3 TW and the advice given to me on CleanROM 8.1 thread was to format data, cache, dalvik and flash the zip. I did so and everything was fine. No bootloop (yet, kinda. Will get to that). So my phone rebooted and the first try got me to the start screen. Here is where things go wrong. It asks me for my PIN or Password as if it is encrypted. I've never encrypted my phone so I was perplexed. I thought maybe I triggered KNOX? But CleanRom 8.1 is touchwiz. But it doesn't not include KNOX from what I've read. I've wiped system and tried multiple methods of formatting the phone and I always get back to the same problem .
Sent from my SCH-I535 using xda app-developers app

The bootloop I solved after
I formatted /system. I even restored my previous cm10.2.1 backup which was on 4.3 and I did a manual factory reset from settings. Then I formatted data, cache, dalvik and still nothing.
Sent from my SCH-I535 using xda app-developers app

ErikFry said:
The bootloop I solved after
I formatted /system. I even restored my previous cm10.2.1 backup which was on 4.3 and I did a manual factory reset from settings. Then I formatted data, cache, dalvik and still nothing.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Try doing a complete wipe. What recovery are you using?

I have wiped system, data and cache. Isn't that a full wipe? I'm running the latest clockwork mod recovery. Thank you for your response.
Sent from my SCH-I535 using xda app-developers app

ErikFry said:
I have wiped system, data and cache. Isn't that a full wipe? I'm running the latest clockwork mod recovery. Thank you for your response.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Try another recovery maybe? I did get your PM
Sent from my S3 on AOKP

ErikFry said:
I have wiped system, data and cache. Isn't that a full wipe? I'm running the latest clockwork mod recovery. Thank you for your response.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
You need to wipe your internal sdcard. Backup any important files to your external SD or a computer. Then wipe everything. System. Data. Internal SD card. Caches. Format system. Then flash the modem in the op if you haven't already. Should be in the op of the ROM you want to flash. Then flash the ROM. Might take up to 10-15 minutes for initial boot so be patient. You should be all good from there.
[email protected]'$ [email protected]@XY- eliminate white backgrounds and any form of ics/holo blue.

Thanks man. Will try tonight.
Sent from my SCH-I535 using xda app-developers app