ok i have Avatar rom for verizon.
everything works great.
but noticed some apk's crashing after updating to most recent version of avatar
i did not wipe / factory reset
so it was a dirty flash over same rom and same android version.... most apk's work fine and some dont.
is that normal, or should i not complain because i did dirty flash my updated rom ?
Well, dirty flash isn't recommended, but with that said, I always update my rom like that. I'm sure that a clean install would solve the issue, but bbefore you do it, definitely try fixing permissions in recovery.
Related
Generally whenever I install a new rom (update or not) I will use the following steps:
download rom / put on sd
Wipe data / factory reset
Wipe dalvik and cache partition
Format System
flash rom
flash gapps
Reboot
This has always worked without fail and in this case it seems to have worked again.
However, I noticed in my settings menu that I no longer have "launcher options" under interface. Has this option been removed from the newest nightly? or has something gone wrong during my flash?
Used:
clockwork-6.0.1.2-d2att
cm-10-20121111-NIGHTLY-d2att
JB-4.2-Gapps-signed.zip
Phone:
Samsung Galaxy S3 SGH 1747
Carrier: Bell
EDIT: Also receiving: Android is upgrading, starting apps on every single reboot. Still loads fine but minor annoyance.
EDIT2: Figured it out, installing the 4.2 gapps was causing all problems. Reverted back to the 4.1.2 gapps and everything is fine. Thread can be closed.
SOLVED!
Could I ask: Did you have to reflash the ROM to fix this? Or just flash an older version of the gapps?
I have the same problem and just got all my apps back ... would rather not have reflash the ROM and then restore everything if I don't have to.
Jalopy
djjohnnyblaze said:
Generally whenever I install a new rom (update or not) I will use the following steps:
download rom / put on sd
Wipe data / factory reset
Wipe dalvik and cache partition
Format System
flash rom
flash gapps
Reboot
This has always worked without fail and in this case it seems to have worked again.
However, I noticed in my settings menu that I no longer have "launcher options" under interface. Has this option been removed from the newest nightly? or has something gone wrong during my flash?
Used:
clockwork-6.0.1.2-d2att
cm-10-20121111-NIGHTLY-d2att
JB-4.2-Gapps-signed.zip
Phone:
Samsung Galaxy S3 SGH 1747
Carrier: Bell
EDIT: Also receiving: Android is upgrading, starting apps on every single reboot. Still loads fine but minor annoyance.
EDIT2: Figured it out, installing the 4.2 gapps was causing all problems. Reverted back to the 4.1.2 gapps and everything is fine. Thread can be closed.
SOLVED!
Click to expand...
Click to collapse
JalopyPilot said:
Could I ask: Did you have to reflash the ROM to fix this? Or just flash an older version of the gapps?
I have the same problem and just got all my apps back ... would rather not have reflash the ROM and then restore everything if I don't have to.
Jalopy
Click to expand...
Click to collapse
You do not have to wipe data if the rom is the same. Just wipe cache/dalvik and then reflash rom/gapps 4.1.2.
Installing home2launcher will also wipe away your option of launcher under settings. Which is unfortunate.
Sent from my SGH-I747 using xda app-developers app
I have a Galaxy s3 rooted So I was ble to flash the newest nightly cb 10.1 before the one that came out today. I want to try out the one that came out today however I am confused about something. I know i have to flash the rom and delete data and cache during recovery mode and what not. What step do i need to take so that when i do flash thi snew rom i dont have to manually re install all my apps and configure my phones layout again?/
You can try dirty flashing by just clearing cache and dalvike cache after you flash the new nightly. This method won't affect any of your apps or settings. If you get any weird bugs from dirty flashing, try clean flashing (which wipes pretty much everything) before reporting any bugs. If you have to clean flash then you can backup your apps with Titanium Backup.
Hello,
i have a Problem regarding KitKat in combination with GApps,
yesterday i installed some KK ROMs, to find the one that suits my needs (AOKP, PA, CM, Carbon and Omni), and all of them worked really great.
But as soon as i flash a GApps package (PA, AOKP or BaNkS' GApps), the phone becomes literally unusable. Every press of a button takes like 5 secs with shuttering animations and the device bootloops every minute.
Before flashing the KK ROMs i upgraded vrom an oldish CWM 6.0.0.x or sth in that timeframe (Android 4.1) to the latest TWRP.
Before every flash i wiped Dalvik, System, Cache and Data.
Any suggestions?
Infi<3 said:
Hello,
i have a Problem regarding KitKat in combination with GApps,
yesterday i installed some KK ROMs, to find the one that suits my needs (AOKP, PA, CM, Carbon and Omni), and all of them worked really great.
But as soon as i flash a GApps package (PA, AOKP or BaNkS' GApps), the phone becomes literally unusable. Every press of a button takes like 5 secs with shuttering animations and the device bootloops every minute.
Before flashing the KK ROMs i upgraded vrom an oldish CWM 6.0.0.x or sth in that timeframe (Android 4.1) to the latest TWRP.
Before every flash i wiped Dalvik, System, Cache and Data.
Any suggestions?
Click to expand...
Click to collapse
Have you tried frashing a rom and gapps immediately after (I mean before rebooting to see if the rom "works really great" ).
I've never tried using a rom without gapps myself, so I don't really know if that helps or not...
evilnoxx said:
Have you tried frashing a rom and gapps immediately after (I mean before rebooting to see if the rom "works really great" ).
I've never tried using a rom without gapps myself, so I don't really know if that helps or not...
Click to expand...
Click to collapse
Yes, that was on the first KK Rom i tried, because thats how i usually install as well (Jelly Bean), and it was unusable as well. First i thought it was the ROM, but since the other ones behaved the same way i tried one without GApps and it was fine. Same with the others without GApps.
Edit:
Retried now with Carbon ROM + GApps Core, seems that yesterday evening i forgot to wipe Cache and Dalvik after flashing GApps, now everything seems to run smooth.
Which CWM version are you using right now? And are you 100% sure you use the right gapps? And in which order do you wipe? (That shouldnt make a really big diffrence)
Edit: didnt saw your edit.
Sent from my Galaxy Nexus using XDA Premium HD app
Infi<3 said:
Yes, that was on the first KK Rom i tried, because thats how i usually install as well (Jelly Bean), and it was unusable as well. First i thought it was the ROM, but since the other ones behaved the same way i tried one without GApps and it was fine. Same with the others without GApps.
Edit:
Retried now with Carbon ROM + GApps Core, seems that yesterday evening i forgot to wipe Cache and Dalvik after flashing GApps, now everything seems to run smooth.
Click to expand...
Click to collapse
Wiping the caches is really important. It forces android to "optimize" all the apps. I believe it actually recompiles some of the code in order for the apps to work better, and in your case to actually work at all.
When I try to flash SuperSU it fails and just aborts.
I have tried flashing stable and all the beta builds same results. I'll attach a screenshot of it.
Originally I had root with everything working fine but decided to try and update through the update app when I was rooted. This was when I was on 3.2.4 trying to get to 3.2.7. All the update process seemed to do was revert my phone to unrooted and did not update to 3.2.7. Ever since then flashing SuperSU didn't seem to work. I waiting for a full zip. Of 3.2.8 to come out thinking flashing full update would fix it. It didn't.
Everything is running fine on 3.2.8. Just any attempt at flashing SuperSU fails.
These were all dirty flashes.
I have not tried a complete restore to stock yet. Would like to avoid this if possible.
I have no active modifications to my system.
savvymatthew said:
When I try to flash SuperSU it fails and just aborts.
I have tried flashing stable and all the beta builds same results. I'll attach a screenshot of it.
Originally I had root with everything working fine but decided to try and update through the update app when I was rooted. This was when I was on 3.2.4 trying to get to 3.2.7. All the update process seemed to do was revert my phone to unrooted and did not update to 3.2.7. Ever since then flashing SuperSU didn't seem to work. I waiting for a full zip. Of 3.2.8 to come out thinking flashing full update would fix it. It didn't.
Everything is running fine on 3.2.8. Just any attempt at flashing SuperSU fails.
These were all dirty flashes.
I have not tried a complete restore to stock yet. Would like to avoid this if possible.
I have no active modifications to my system.
Click to expand...
Click to collapse
Clean installation will probably fix it and has less risk of potentially bugs compared to dirty flashes.
LS.xD said:
Clean installation will probably fix it and has less risk of potentially bugs compared to dirty flashes.
Click to expand...
Click to collapse
Yeah kinda figured that. How exactly do you force a fresh install and? Sorry for the noob question.
savvymatthew said:
Yeah kinda figured that. How exactly do you force a fresh install and? Sorry for the noob question.
Click to expand...
Click to collapse
OnePlus.net offers the rom files as download:
OOS 3.2.6 (capable for OTA 3.2.8)
Open Beta 7
I'm using the Open Beta at the moment and it runs without any issues
OOS roms can be flashed with custom TWRP
For a clean installation just wipe partitions (System; Data; Cache; Int. Storage) with TWRP before flashing the new rom
Just don't be surprised if you wipe your int. storage, you will lose all of your roms and things you've downloaded to your phone. I never wipe int. storage, just Cache, Dalvik, Data, and System.
Hw4ng3r said:
Just don't be surprised if you wipe your int. storage, you will lose all of your roms and things you've downloaded to your phone. I never wipe int. storage, just Cache, Dalvik, Data, and System.
Click to expand...
Click to collapse
Thank you for pointing on that I backup all my stuff on my computer once a week but others may not.
By never wiping your internal or manually deleting folders you will collect garbage over time when you change android installations.
I have a back up from when i first set it up, so its very old. After i Flash and set everything up again think im gonna start making weekly back ups, with all the roms and stuff for this phone probably be smart.
Thanks guys
Hello, I really need some help!
I have the GT i9195 and I've flashed it with CM13 and the proper GApps. I have TWRP Recovery and it's all 100% functional.
The problem here is, I flash the ROM, ok. I flash the GApps, ok. Then i wipe every cache and stuff and reboot. It takes a lots of time to reboot, but it's okay. After, maybe 1 hour, more or less, he finally starts.
Now here's what is wrong. ALL the GApps don't work. The phone is working fine, all sensors, cameras and even calling is fine, but the GApps don't work.
So, I've tried to downgrade to CM12.1 with the proper GApps, same. I've changed the ROM to another version of the CM13, nothing. I've downloaded all GApps, from Pico to Custom, nothing...
What can I do? Can anyone help me out?
Flash Opengapps select ARM Platform,use pico version. Wipe data,cache,dalvik cache then flash rom & gapps. OR flash separately, flash rom reboot system. Then wipe cache,dalvik cache flash gapps.
Leandro Avlis said:
Hello, I really need some help!
I have the GT i9195 and I've flashed it with CM13 and the proper GApps. I have TWRP Recovery and it's all 100% functional.
The problem here is, I flash the ROM, ok. I flash the GApps, ok. Then i wipe every cache and stuff and reboot. It takes a lots of time to reboot, but it's okay. After, maybe 1 hour, more or less, he finally starts.
Now here's what is wrong. ALL the GApps don't work. The phone is working fine, all sensors, cameras and even calling is fine, but the GApps don't work.
So, I've tried to downgrade to CM12.1 with the proper GApps, same. I've changed the ROM to another version of the CM13, nothing. I've downloaded all GApps, from Pico to Custom, nothing...
What can I do? Can anyone help me out?
Click to expand...
Click to collapse
Its hard to tell by your wording but you are flashing GAPPS and the ROM at the same time and not booting into rom first right?
I have had a lot of Play Services FC's lately and had to wipe data from play services and market to get them working after I was rooting and un-rooting back and forth.
civicsr2cool said:
Its hard to tell by your wording but you are flashing GAPPS and the ROM at the same time and not booting into rom first right?
I have had a lot of Play Services FC's lately and had to wipe data from play services and market to get them working after I was rooting and un-rooting back and forth.
Click to expand...
Click to collapse
I flashed all at same time (following some instructions I saw) then I only flashed the ROM and after the GApps. Even so, they are not working!
I've tried all GApps for this device, none are working.
My best solution so far was download the stock Firmware and Flash it trough Odin.
It's stock, but is working fine without any issues until now.
But I really really want to put CM13 or CM12.1 in this phone.
Leandro Avlis said:
I flashed all at same time (following some instructions I saw) then I only flashed the ROM and after the GApps. Even so, they are not working!
I've tried all GApps for this device, none are working.
My best solution so far was download the stock Firmware and Flash it trough Odin.
It's stock, but is working fine without any issues until now.
But I really really want to put CM13 or CM12.1 in this phone.
Click to expand...
Click to collapse
you're doing something wrong. Im running an old official cm13 build on my LTE, give that a shot?
civicsr2cool said:
you're doing something wrong. Im running an old official cm13 build on my LTE, give that a shot?
Click to expand...
Click to collapse
The problem here is the GApps. The ROM is working fine! CM13, CM12.1... etc. They're all working 100%, the GApps aren't working with non official Firmware.
Leandro Avlis said:
The problem here is the GApps. The ROM is working fine! CM13, CM12.1... etc. They're all working 100%, the GApps aren't working with non official Firmware.
Click to expand...
Click to collapse
Something in your process is wrong regardless if its rom or gapps. try this Gapps, its running right now on my official cm13.
https://drive.google.com/open?id=0Bx5gPVuLapkKZVl1N3o5RzlqcFk
This is the latest stable release that Im runnning as well
https://download.cyanogenmod.org/get/serranoltexx-snapshot.zip