Database Develop

[Q] do i need to perform full wipe if i flash XXLSA over XXLS7?

or can i just dirty wipe and wipe dalvik cache and im good to go?
thanks

Jamal Ahmed said:
or can i just dirty wipe and wipe dalvik cache and im good to go?
thanks
Click to expand...
Click to collapse
Not sure about this particular case, but I'll tell you my approach is to *always* do a full wipe + format partitions and internal sdcard before flashing *any* ROM. This way I'm sure there's nothing old left (app data, config etc.). Using this approach I've been running many ROMs without most of the bugs users report (using XXLSA now), I think it's worth the time to reinstall and reconfig everything. If you don't need to keep old data and config:
1) Wipe data & cache
2) Wipe dalvik cache
3) Format /system & /preload
4) Format internal sdcard (make sure you save anything you need before)
5) Flash ROM
6) Wipe cache again
7) Wipe dalvik cache again
8) Reboot
(Not sure if 6 and 7 are needed, but I prefer to be a bit paranoid in this case.)

Jamal Ahmed said:
or can i just dirty wipe and wipe dalvik cache and im good to go?
thanks
Click to expand...
Click to collapse
I think it depends on which custom rom u r currently on & which one you are gonna flash..for ex: flashing Ultimate v5 XXLSA over Alliance v1 XXLS7 may not work..

dbolivar said:
Using this approach I've been running many ROMs without most of the bugs users report (using XXLSA now))
Click to expand...
Click to collapse
I agree with you. If you perform a full wipe before to install a new rom, the probabilities of occur in some rom's issue (like FC or just a "simple" weird lag) are low. Tested personally.
It always better/advised to perform a full wipe.
In the end, you could do a nandroid backup of your last used rom, wipe everything, install the new rom, and then try to restore the data partition only. If you get some errors or general issue, you can easily full wipe everything again, and reinstall the new rom again... at least, you tried

Jamal Ahmed said:
or can i just dirty wipe and wipe dalvik cache and im good to go?
thanks
Click to expand...
Click to collapse
What does the OP states? Flashing ROMs is STILL a dangerous business.

Read the OP for the ROM you are installing

Jamal Ahmed said:
or can i just dirty wipe and wipe dalvik cache and im good to go?
thanks
Click to expand...
Click to collapse
leaks always require full wipe for it to function properly.

[Q] cm10.1 Nightlies not booting, kinda

I'm want get the current cm10.1 nightlies to run on my n7000. I'm using cm-10.1-20130511-NIGHTLY-n7000.zip with 20130301 gapps package but the furthest I can get is the welcome screen. Selecting my language will freeze the phone. I've tried re-installing wipe cache, wipe data etc.. even retried to whole install a few times but nothing works. Any ideas? Sucks cos I just finished a mod on my p7510 to display now playing in status bar and want to port it over.

that is an unclean install,
on cm kernel on its recovery format system, data,preload cache an dalvik and reinstall. also make sure you have latest gapps for that version

baz77 said:
that is an unclean install,
on cm kernel on its recovery format system, data,preload cache an dalvik and reinstall. also make sure you have latest gapps for that version
Click to expand...
Click to collapse
Heres what I'm doing:
Flash abyss kernell (I have emmc bug and have had to recover from it twice now),
factory reset,
Flash cm10.1 in order to install kernel and recovery a reboot recovery,
Now in cyanogen mod recovery:
wipe cache,
wipe dalvik cache,
wipe system
wipe date,
wipe preload,
re-install cm10.1
install gapps 20130301 (the latest gapps)
what can be going wrong?

thats pretty thorought. I would recommend not abys but cm kernel instead.

tried it with both

Then I dont know. What gapps version are you flashing?
I havent read it being an issue with latest cm, maybe bad download? md5 matches download?
Also try on stock gb rom (for your phones csc), if none of above, if with emmc brick check app some sectors are damaged. Thats what I would do. If damaged, or still weird lags check warranty.

Using the 201301 gapps from goo.im. Downloaded a few times now same issue, its probably my phone as partitions are a little strange from emmc recovery.

[Q] Endless Boot & Gapps issue

Received this phone a month ago, just got around to rooting it yesterday. Root with motochopper went fine. Unlocked the handset with motopocalypse, everything went fine. Installed latest CM10.2 nightly and everything ran fine, even restarted phone and it worked fine. I then realized I forgot to install Gapps, So i went to CWM and installed the Gapps through "install zip from sd card". Now phone will not progress past the bootloader unlocked warning screen. I can restart and put phone into recovery or fastboot no problem but I don't know where to go from here. I tried a factory reset and reinstallation of CM but to no success. I am a bit of a newb when it comes to external programs like RSD Lite and haven't used it. Is there something obvious I'm missing in my progress of trying to fix my phone?

clear cache and dalvik cache under advanced then restart.
if you still loop do the above steps plus data reinstall cm10.2.
if you still loop do all above steps but also format system under mounts be re-install.
if you loop after all that then try a different ROM.
PS what version of gapps did you use.

frog1982 said:
clear cache and dalvik cache under advanced then restart.
if you still loop do the above steps plus data reinstall cm10.2.
if you still loop do all above steps but also format system under mounts be re-install.
if you loop after all that then try a different ROM.
PS what version of gapps did you use.
Click to expand...
Click to collapse
i can't post outside links yet but on the wiki.cyanogen site in the Gapps section I used the 10.2 20130813 1f51b5cc6370c1f45dc951109b6ce6ed release. I will attempt those steps once i can find a legitimate charger in my house. Phone doesn't accept power unless its on and i need just a bit of juice to boot it up

frog1982 said:
clear cache and dalvik cache under advanced then restart.
if you still loop do the above steps plus data reinstall cm10.2.
if you still loop do all above steps but also format system under mounts be re-install.
if you loop after all that then try a different ROM.
PS what version of gapps did you use.
Click to expand...
Click to collapse
Here's the official name. Installed cm-10.2-2-130814-NIGHTLY-mb886.zip for the cm and gapps-jb-20130813-signed.zip for the GApps, both latest versions I believe

frog1982 said:
clear cache and dalvik cache under advanced then restart.
if you still loop do the above steps plus data reinstall cm10.2.
if you still loop do all above steps but also format system under mounts be re-install.
if you loop after all that then try a different ROM.
PS what version of gapps did you use.
Click to expand...
Click to collapse
none of the above steps worked unfortunately. Is there a set order of certain things to be mounted and unmounted in the mount section? Such as the system or sd card?

yodelyfish said:
none of the above steps worked unfortunately. Is there a set order of certain things to be mounted and unmounted in the mount section? Such as the system or sd card?
Click to expand...
Click to collapse
try changing the mount status of the cache
also are you getting any funny messages in cwm
PS are you flashing gapps before first boot up

frog1982 said:
try changing the mount status of the cache
also are you getting any funny messages in cwm
PS are you flashing gapps before first boot up
Click to expand...
Click to collapse
i got Cyanogen up and working. And no I was not flashing gaps Before first boot. i will try doing that before everything else

I got both GApps and cyanogenmod to install properly and the phone boots normally, but now I don't see any of the GApps actually present on the phone. Did I F somethin over again?

yodelyfish said:
I got both GApps and cyanogenmod to install properly and the phone boots normally, but now I don't see any of the GApps actually present on the phone. Did I F somethin over again?
Click to expand...
Click to collapse
did you flash gapps before flashing the ROM because the ROM flash will overwrite the gapps.
PS I suggest using zgapps http://forum.xda-developers.com/showthread.php?t=2240652 because they are stripped down which tends to prevent a lot of issues and if you want a 4.3 ROM try skeevydudes PAC ROM it is more stable plus has more features.

frog1982 said:
did you flash gapps before flashing the ROM because the ROM flash will overwrite the gapps.
PS I suggest using zgapps http://forum.xda-developers.com/showthread.php?t=2240652 because they are stripped down which tends to prevent a lot of issues and if you want a 4.3 ROM try skeevydudes PAC ROM it is more stable plus has more features.[/Q]
Awesome. Pac-Rom already looks better on review. I get to the dl page tho and have a monster list of choices. Which one do I go for?
Click to expand...
Click to collapse

frog1982 said:
did you flash gapps before flashing the ROM because the ROM flash will overwrite the gapps.
PS I suggest using zgapps http://forum.xda-developers.com/showthread.php?t=2240652 because they are stripped down which tends to prevent a lot of issues and if you want a 4.3 ROM try skeevydudes PAC ROM it is more stable plus has more features.
Click to expand...
Click to collapse
Thank you for all the help. PACROM is up and running swimmingly, all of the features are there and it is definitely better than CM by itself. Thanks again

[Q] Miui 4.2.2 has no gapps?

I recently started using the Miui 4.2.2 version by deepss1 , and I noticed that gapps wasn't there but had a chinese alternate play-store.
Will it be okay if I just flashed a normal 4.2.2 gapps zip for it instead?

Hey
Normal 4.2.2 gapps will be fine.
Make sure u boot once after flashing miui 4.2.2 and then flash gapps 4.2.2...
Sent from my Amazing Galaxy S III..!

tchindalia said:
Hey
Normal 4.2.2 gapps will be fine.
Make sure u boot once after flashing miui 4.2.2 and then flash gapps 4.2.2...
Sent from my Amazing Galaxy S III..!
Click to expand...
Click to collapse
Wow, that's it? thanks!

dandrake47 said:
Wow, that's it? thanks!
Click to expand...
Click to collapse
In CWM recovery: wipe all (data, cache, dalvik cache), install ZIP of Gapps for 4.2x and reboot.
Wiping cache might spare you a bootloop experience. It could work fine also without wiping but wiping can't do any harm

tetakpatak said:
In CWM recovery: wipe all (data, cache, dalvik cache), install ZIP of Gapps for 4.2x and reboot.
Wiping cache might spare you a bootloop experience. It could work fine also without wiping but wiping can't do any harm
Click to expand...
Click to collapse
I always do a full wipe before installing a new rom anyway
And as for Miui, it rocks! Not a day goes by without me checking for new updates

Same for me ,but with CM 10.2 :good::laugh::laugh:
dandrake47 said:
I
And as for Miui, it rocks! Not a day goes by without me checking for new updates
Click to expand...
Click to collapse

Random reboots after installing Gapps in Kitkat

Hi
I'm trying to install Kitkat 4.4 with Maclaws cm11. Also tried the carbon rom. All seems to work fine until I flash G apps. Then I get random reboots shortly after boot. Tried both micro and aroma Gapps from Mclaw. Am I alone with this problem? Any suggestions?
I'm using CWM for flashing and wrong cache etc. Baseband I8190XXANA2 in stock 4.1.2 (rooted) which works fine.
After more research it seems like reboots happens also without Gapps. Also happening in 4.3. There was recently a firmware update early this week. Maybe something has changed, breaking custom ROMs.

larscn said:
Hi
I'm trying to install Kitkat 4.4 with Maclaws cm11. Also tried the carbon rom. All seems to work fine until I flash G apps. Then I get random reboots shortly after boot. Tried both micro and aroma Gapps from Mclaw. Am I alone with this problem? Any suggestions?
I'm using CWM for flashing and wrong cache etc. Baseband I8190XXANA2 in stock 4.1.2 (rooted) which works fine.
After more research it seems like reboots happens also without Gapps. Also happening in 4.3. There was recently a firmware update early this week. Maybe something has changed, breaking custom ROMs.
Click to expand...
Click to collapse
Bud,
If you're on stock just do that:
1-Reboot in recovery
2-Choose Wipe data/factory reset
3-Flash cm rom
4-Flash gapps
5-Reboot
Done, that's it. Not complicate.
If you want to update cm roms:
1-Reboot in recovery
2-Flash cm update
3-Choose Wipe cache & dalvik cache
4-Reboot
Done.
You don't need to mess up with anything more. Read my FAQ here for gapps & for more doubts. Have fun

thanks...
mauam said:
Bud,
If you're on stock just do that:
1-Reboot in recovery
2-Choose Wipe data/factory reset
3-Flash cm rom
4-Flash gapps
5-Reboot
Done, that's it. Not complicate.
If you want to update cm roms:
1-Reboot in recovery
2-Flash cm update
3-Choose Wipe cache & dalvik cache
4-Reboot
Done.
You don't need to mess up with anything more. Read my FAQ here for gapps & for more doubts. Have fun
Click to expand...
Click to collapse
Thanks for the advice. I've read the faq's and followed that, but the problem is that my phone just reboots randomly a minute or so after it's booted up. Was suspecting this to be the latest firmware update, but if so the forum would probably been flooded with more with the same problem.
It might be my battery, which is bad. Just got a new one. Charging it now, and will try CM11 again tomorrow. If it still reboots I'll see if I'm able to access the logs to get an idea of whats going on. It works fine on stock, so I'm a bit puzzled... .

Solved
...and after changing battery CM11 runs smooth without reboots .
The reboots happened with the original charger plugged in. Why that didn't happen to the stock ROM I can't explain.
The original Samsung battery scares me a bit. It has become 1-2 mm thicker. Looks like an accident waiting to happen. Have to dispose of safely somehow...quick...