Develop Bugs

[Q] Is it ok to reinstall a rom without clearing anything?

I flashed Sandvold's ICS 0.8.1 yesterday, but after reading a few threads today I saw that it's better to do the custom install instead of the typical one. I did a nandroid and decided to simply flash the rom again without clearing anything.
It seems fine so far, but I'm wondering if this can lead to any problems?
Also, do I need to reinstall a2sd after re-flashing?

I think that if you downgrade from ics to gb than you need to make a full wipe but if you upgrade than I think it's ok
Sent from my WT19i using xda premium

thedancingbear said:
I flashed Sandvold's ICS 0.8.1 yesterday, but after reading a few threads today I saw that it's better to do the custom install instead of the typical one. I did a nandroid and decided to simply flash the rom again without clearing anything.
It seems fine so far, but I'm wondering if this can lead to any problems?
Also, do I need to reinstall a2sd after re-flashing?
Click to expand...
Click to collapse
Yes, always wipe.
xdevilium said:
I think that if you downgrade from ics to gb than you need to make a full wipe but if you upgrade than I think it's ok
Sent from my WT19i using xda premium
Click to expand...
Click to collapse

If you are with the exact same rom then a wipe shouldn't be needed and a2sd should stay if you don't wipe.

Try it and if it doesn't work do a full wipe I've never seen anyone say you'll break your phone if you don't wipe. Someone on Sandvold's thread recommended app extractor from play store as an easy way to restore after a full wipe. Didn't work for me but I only tried it once so you could check that out. It just restores everything from your nandroid
Sent from my HTC Desire using xda premium

greenie25 said:
If you are with the exact same rom then a wipe shouldn't be needed and a2sd should stay if you don't wipe.
Click to expand...
Click to collapse
If u are flashing the same rom (newer version) u still have to wipe dalvik. Its better anyway just to do a backup then full wipe and flash the rom then restore
Sent from my HTC Desire

Always wipe Dalvik, sometimes, the rom setup menu does it automaticly.

Failed frosty JB OTA update...

Hi all,
First post on xda here. I was trying to update my frosty jelly bean v6 to v7 via OTA update, installed the package and it restarted itself in CWM mode but it said something alone the lines of "failed update... update file not found." I downloaded the v7 package from the developer's link and was thinking about just installing it from zip on sd card.
Why can't it update? If I install v7 from the zip and wipe cache will that work too or no?
Sent from my SGH-T999 using xda app-developers app

Install from CWM yourself, as you suggested.

Do I have to perform a full data wipe for that then? Or would just cache and dalvik cache be ok.
Not really sure why OTA update didn't work in CWM in the first place, if anyone can offer answers that'd be helpful. Thanks!
Sent from my SGH-T999 using xda app-developers app

timma1 said:
Do I have to perform a full data wipe for that then? Or would just cache and dalvik cache be ok.
Not really sure why OTA update didn't work in CWM in the first place, if anyone can offer answers that'd be helpful. Thanks!
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
This what you do after you put the zip in the scard...make sure your in recovery..
Wipe data/factory reset
Wipe cache & dalvik
Install Rom
Wipe cache and dalvik (again)
Fix Permissions
Reboot & let it sit for 5-10 mins (Don't touch anything!)
Reboot & enjoy!
*Please perform a full wipe for v7!
Hope this helps.

Thanks. Yeah I saw that on the dev thread... I followed those steps when i first flashed the frosty JB. But my question is do i really have to do a data wipe even for every version update? That seems to be a lot of hassle...
Sent from my SGH-T999 using xda app-developers app

Wipe Dalvik and dirty flash it. 4.1.1 > 4.1.2 = no clean flash necessary. I guess it's the devs' fault for spreading all of this clean flashing nonsense that's been more contagious than the bubonic plague. Like the IMEI loss rumors. It's only necesary if: going from ICS to JB, or vice versa. Or if you're having some major issue that no one else is having. Which is rare.

Thanks for the suggestion. I tried to dirty flash it but it said the signature verification failed?
Just to note the only tweak I made to my sd card previous to trying to update was deleting the original frosty JB v6 zip. That shouldn't matter right?
Sent from my SGH-T999 using xda app-developers app

timma1 said:
Thanks for the suggestion. I tried to dirty flash it but it said the signature verification failed?
Just to note the only tweak I made to my sd card previous to trying to update was deleting the original frosty JB v6 zip. That shouldn't matter right?
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
What is the version of your CWM? i think its need to be updated.

3.0.7
Sent from my SGH-T999 using xda app-developers app

Yup, update it, the latest version is 6.xxx. i encountered the same error when i tried to install cm10 with an outdated cwm.
For a noob, you can easily update cwm by downloading and installing ROM MANAGER using your phone from PLAYSTORE.
launch the rom manager app then you can see an option there to update cwm

Id like to make a quick point on the dirty vs clean flashing.
Usually, it is correct that dirty flashing is ok except when jumping between android versions. (Even then, when going forward in version, its still often ok to dirty flash).
However, in the cases we see here this is not necessarily true. I am of course referring to our jb leaks and roms based on them.
Dirty flashing these after an update can cause problems. Many people, myself and the devs themselves included, have seen where a number of bugs would be nonexistent if you just did a clean flash. These are experimental builds based on leaked firmware. I'm certain the devs you guys are referring to recommend a clean flash for two reasons. First, it simply makes their rom operate much better. Second, and most important from a dev standpoint, if you dirty flashed, and are experiencing bugs, there is nothing the dev can really do for you. In fact, unless you clean flashed the rom, you shouldn't even report on bugs unless you find a fix for it.
Another thing to consider is a couple if these roms are based not just on a leak, but on multiple leaks often from more than one carriers device! Due to this, if you dirty flash you are much more likely to have bugs show up. It really depends on what has been changed, updated and rebased, and no one can predict how uts going to act.
No one says you cannot dirty flash these roms. Many have done so with few to no issues. But, if you do, and you run into problems please do not blame the dev or expect him to fix the problem unless it is being reported by the majority of users.
Not trying to argue or say anyone is right or wrong. I'm just trying to clear up the reason for the dev suggestion to clean flash.
Hope it helps!
Sent from my SGH-T999 using xda app-developers app

Can you flash a higher base rom if you have an older base?

I'm just wondering if you have an older base like 4.0.4 and you want to flash an 4.1.1 rom is that possible or should i upgrade to 4.1.1 then flash?

It's totally possible.
However, this is a good time for a clean install. ie data wipe.
I hardly ever recommend one. But, this is one of the times.
I didn't, however. Last time was ice cream to jelly bean
Sent from my SGH-T999 using xda premium

Thank you
also do you know if flashing back to stock and then upgrading thourgh the kies to 4.1.1 and then flashing a custom rom be safer?

Fewer steps = better.

qwerty123z said:
Thank you
also do you know if flashing back to stock and then upgrading thourgh the kies to 4.1.1 and then flashing a custom rom be safer?
Click to expand...
Click to collapse
You sound like my brother in law. He does that every time he flashes a new ROM, makes no sense to me. When I flash a new ROM, I wipe data/cache and /system, then flash the ROM and restore my Titanium Backup.

Thetenthdr said:
You sound like my brother in law. He does that every time he flashes a new ROM, makes no sense to me. When I flash a new ROM, I wipe data/cache and /system, then flash the ROM and restore my Titanium Backup.
Click to expand...
Click to collapse
Same here... I never did an official update from ICS to Jellybean and so far so good. I know that it's best to install the latest drivers/partitions, but I was too lazy. Lol
Sent from my SGH-T999 using xda premium

[Q] regarding Google edition roms

My apologies if this has been asked before. But from my understanding the Google edition still has all the touch wiz framework. I was Wondering if you had to Odin back to stock in order to flash a modified stock Rom? I had to do this on my s3 because it always gave me problems. This is an issue for me now because my hard drive on my laptop is fried and have no access to Odin besides mobile Odin.
Sent from my SGH-M919 using Tapatalk 4 Beta

A modified stock ROM will be packaged to flash in recovery. Just be sure to properly wipe since you will be going back to TW.

So all I have to do is do a super wipe, system and all. And I should be good to go? Can I nandroid back to my current set up if I don't like the Google edition Rom? Or will that cause complicatIons that will require me to Odin back to stock?
I know it's a dumb question. But I want to Bork my Device
Sent from my SGH-M919 using Tapatalk 4 Beta

MacTheRipperr said:
So all I have to do is do a super wipe, system and all. And I should be good to go? Can I nandroid back to my current set up if I don't like the Google edition Rom? Or will that cause complicatIons that will require me to Odin back to stock?
I know it's a dumb question. But I want to Bork my Device
Sent from my SGH-M919 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Nandroid is fine, and doesn't need any wiping, it does it before the restore, but I wipe anyways.
If you just want to flash a different ROM, for going from ROM to different ROM, it's best to:
Factory Reset
Wipe both Caches
Format /system
Flash ROM or ROM and gapps if it's AOSP
To upgrade a current ROM to an updated version, if the base version of Android hasn't changed, you can dirty flash, which is the exact steps, minus the factory reset.

Okay thanks, I was just curious. Because I can't currently restore from Odin because I don't have a pc.
Sent from my SGH-M919 using Tapatalk 4 Beta

[Q] Upgrading data from 4.2 to 4.3

Using custom ROMs, CWM & TWIP, backup apps like Titanium and Reware MyBackup, etc. are not new to me. I've done my share of ROMs on various phones & tablets.
It's really easy to say wipe data for best results when upgrading to a new Android version or ROM. That's typically what I've done as recommended.
But, when a carrier like T-Mo finally pushes out their update, for example the MK2 to move to 4.3, the data gets upgraded automatically and reliably. Obviously no wiping of data.
I don't want the locked MK2 bootloader and KNOX. Other than that, I'm OK with mostly stock.
If I flash one of the MK2 modified stock ROMs on top of stock 4.2 (maybe just rooted), will it upgrade the data just as it would when you do a carrier upgrade? If necessary, I would also flash the latest KT kernel & modem, so Wi-Fi calling would work and the latest baseband would match. Again, as close as stock for now w/o locked bootloader & KNOX.
This would save me a lot of headache and hassles with having to use Titanium for apps & data. I can always also do a Nandroid to back up before an after this entire process.
Has anyone tried to upgrade to the latest modified stock MK2 ROM on top of a stock MDL ROM and keep their data?

If you flash the rom you have to use titanium but believe me it's 10 times better than doing the ota.. It's worth extra step.sit down watch TV and let titanium do its thing.
Sent from my SGH-M919 using Tapatalk 2

egren58 said:
If you flash the rom you have to use titanium but believe me it's 10 times better than doing the ota.. It's worth extra step.sit down watch TV and let titanium do its thing.
Sent from my SGH-M919 using Tapatalk 2
Click to expand...
Click to collapse
+1
Sent from my SGH-M919 using xda app-developers app

A little background... I've been a SW developer for 20 years. I want to understand how stuff works. I have no problem screwing around with my phone, Nandroid, wipe data, etc. and have already done so. My wife just wants a working phone and could care less. I want to upgrade her phone w/o locking her bootloader and w/o KNOX in case I want to use her phone later. She wants all here system and app data to remain identical, otherwise, I'll have to hear her *****ing & moaning until I fix it.
Technically, is there any difference between flashing a the modified 4.3 stock ROM w/o wiping data and doing a traditional carrier upgrade in how it handles the upgrade for any data partition? (ignoring bootloader & modem upgrades). Does the carrier upgrade do anything different after it formats and installs onto the system partition? I wouldn't think so. Please correct me if I'm wrong here.
Also, I think it can be sketchy restoring TB System Data from older OSes (4.2) onto newer OSes (4.3). I'm particularly referring to stuff like SMS/MMS/Call Logs/etc. Maybe I'm wrong here and a newer OS is always expected to be able to upgrade order system data if restored?
So, in order to retain all that stuff (for her phone), it would seem that simply flashing the modified 4.3. ROM onto a dirty 4.2 data partition would be exactly what the carriers do when they push the update form 4.2 to 4.3?

Here, go to this thread follow the directions in the OP carefully and your wife will be on the latest boot loader Knox free MK2. Once you've finished that then you can flash any type of 4.3 ROM or 4.4 and not have datadrops or any problems. Pretty much doing the 4.3 ota for the bootloader but Knox free.
http://forum.xda-developers.com/showthread.php?t=2544612
Sent from my GT-I9505G using XDA Premium 4 mobile app

Thank you for the response, but it doesn't address the specific question. Additionally, I don't want the latest bootloader because its locked
Sent from my SGH-M919 using Tapatalk

If you upgrade that way I suggested it gives you an unlocked updated boot loader
Sent from my GT-I9505G using XDA Premium 4 mobile app

CalPolyRock said:
A little background... I've been a SW developer for 20 years. I want to understand how stuff works. I have no problem screwing around with my phone, Nandroid, wipe data, etc. and have already done so. My wife just wants a working phone and could care less. I want to upgrade her phone w/o locking her bootloader and w/o KNOX in case I want to use her phone later. She wants all here system and app data to remain identical, otherwise, I'll have to hear her *****ing & moaning until I fix it.
Technically, is there any difference between flashing a the modified 4.3 stock ROM w/o wiping data and doing a traditional carrier upgrade in how it handles the upgrade for any data partition? (ignoring bootloader & modem upgrades). Does the carrier upgrade do anything different after it formats and installs onto the system partition? I wouldn't think so. Please correct me if I'm wrong here.
Also, I think it can be sketchy restoring TB System Data from older OSes (4.2) onto newer OSes (4.3). I'm particularly referring to stuff like SMS/MMS/Call Logs/etc. Maybe I'm wrong here and a newer OS is always expected to be able to upgrade order system data if restored?
So, in order to retain all that stuff (for her phone), it would seem that simply flashing the modified 4.3. ROM onto a dirty 4.2 data partition would be exactly what the carriers do when they push the update form 4.2 to 4.3?
Click to expand...
Click to collapse
Flashing roms without wiping is not always a great idea. If you do... atleast clear cache and dalvik cache. You won't lose your data but you may or may not have issues. YMMV. As far as transferring system data from different Android versions, that is a no no. Just backup your sms and what not using the various programs on the Play store, most of them do a good job. What I REALLY recommend is for you to make a Nandroid backup using Nandroid manager or through your recovery such as CWM or PhilZ. Once you have this backup safely stored on an EXTERNAL SD card or on your computer, you can experiment and flash away. I doubt you'll have problems since the upgrade is minor but just have your backup handy... it is critical in case you have problems after doing the dirty upgrade and to avoid getting your butt whooped by the wifey
Sent from my SGH-M919 using XDA Premium 4 mobile app