Develop Bugs

[Q] Quick question

Say I want to flash a new version of the rom i'm using do I need to wipe everthing again?

After multiple updates it's usually a good idea for a full wipe. However just one update you'll be fine wiping cache and dalvik only. If you've flashed a custom kernel then you'll need to reflash that, along with any other mods you've made to the system.
Read the thread for the rom and double check that it isn't recommended to do a full wipe for this particular update. Also make a nandroid backup just in case you encounter any problems.
I only flash updates of the same rom, usually only wiping dalvik and cache. I do make sure to do a full wipe about once a month though. It keeps the phone running smoothly and helps weed out apps that I don't really use when I go to restore.
Supersonic Evo 4G | MIUI | Tapatalk

It's always recomended to do a full wipe unless the op says otherwise. Some ops will make patches that do not require full wipe. If you don't full wipe, don't complain about problems. It's the first thing you will be asked. Use Titanium Backup for your apps and wipe away. Always nandroid first just in case you make a mistake.

thanks for the great answers guys appreciate it

You're welcome, just trying to be helpful.

[Q] How to get rid of having to do a battery pull

Hey guys,
I always have to pull my battery out multiple times on reboots, or after flashing a rom.
When I change roms, I do a fact. reset and wipe cache/dalvik, on updates of same rom I only do a wipe of cache/dalvik. I tried fixing permissions.
How is this caused ? It eventually boot up every time, just very annoying.
Does wiping system help ? I've read that most rom dev's include it anyway in flashing rom.
Phone: Samsung Galaxy Nexus
Rom: AOSP Paranoid Android 2.99 beta 5
Recovery: TWRP 2.3.2.1
Thnx for your help!

Firewalker1980 said:
Hey guys,
I always have to pull my battery out multiple times on reboots, or after flashing a rom.
When I change roms, I do a fact. reset and wipe cache/dalvik, on updates of same rom I only do a wipe of cache/dalvik. I tried fixing permissions.
How is this caused ? It eventually boot up every time, just very annoying.
Does wiping system help ? I've read that most rom dev's include it anyway in flashing rom.
Phone: Samsung Galaxy Nexus
Rom: AOSP Paranoid Android 2.99 beta 5
Recovery: TWRP 2.3.2.1
Thnx for your help!
Click to expand...
Click to collapse
I haven't encountered this but I sometimes get bootloop when I flash Gapps without wiping cache and dalvik. Whenever I flash a new ROM, I do factory reset, wipe system, cache, and dalvik. So you may try wiping all of them and make a fresh install of the ROM then see if this problem keeps affecting you. Just make a nandroid backup in case this does not help so you restore your whole data easily

ahmadallica said:
I haven't encountered this but I sometimes get bootloop when I flash Gapps without wiping cache and dalvik. Whenever I flash a new ROM, I do factory reset, wipe system, cache, and dalvik. So you may try wiping all of them and make a fresh install of the ROM then see if this problem keeps affecting you. Just make a nandroid backup in case this does not help so you restore your whole data easily
Click to expand...
Click to collapse
Hey thx for your suggestions!
I always flash a "new" rom that way though. But an update of the same rom, I "dirty" flash, which should be fine according to everyone.
No matter what Rom/Kernel I use, I still frequently have to pull the battery out.
It's never from locking up within Android. It just freezes/loops on the Google bootlogo.
I once wiped everything, even the storage space, and it helped for a little while, but did not make it go away for good.
Could it be related to certain apps ? Maybe PGM or Seeder or smth ?
All input welcome
---------------------------------------------------------------
Phone: Samsung Galaxy Nexus Maguro
Rom: AOSPA 2.99 latest
Kernel: AK Purity v20
Recovery: TWRP 2.3.3.0

[Q] nightly rom from cm 10.1

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.

[Q] Why does ota update work without data wipe?

I'm just wondering why Sprint's ota updates don't require a data wipe, but flashing the stock ROM in a custom recovery needs the wipe? I installed cnexus's rooted stock on my phone and initially tried a dirty flash, but had problems, so I wiped and did a clean install and all is good. My wife's phone is being prompted for the ota and I want to update her but I'd prefer not to have the Knox bootloader. I would simply update her phone as I did mine, but she'll kill me if I wiped her data. So, why can the ota install without the data wipe but the (essentially) same ROM installed manually can't? Anybody know?

An OTA just adds new file, a rom overwrites the entire system, that's why a full wipe is always recommended. I think there is a thread somewhere here that has flashable OTAs though. It sounds like she is rooted, so why don't you use a backup app like titanium?

Titanium is great and you will never have to worry about losing data. Plus its good to clear out the phone every once and awhile to keep it running fresh.

Root / SuperSU Failing to complete? ( Help)

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