yashsingh1/xdaforums huggingface dataset:
[AT&T Samsung Galaxy Note I717] mlaws90:
How much was it on the site, just wondering?

The Tracking number they gave me starts with a 9 and it should start with 1Z usually for UPS, but they may use SurePost(a combo of UPS and USPS) which I dont know much about. Does anyone know what is going on with the shipping tracking?
[AT&T Samsung Galaxy Note I717] Slammin:
I received a similar number dorm my order last week and it took a few days (including the weekend) before i was able to track it.

I ordered last Wednesday and it should arrive thisThursday.
[AT&T Samsung Galaxy Note I717] mlaws90:
I had the EXACT same experience. I ordered on Wednesday got the tracking info on Friday(I think, not by email). I was only able to track it when I checked today after like 10 or 11 maybe not sure, but before that it said "Not available". It is a different type of shipping....It is 1 hr 10 min away from me RIGHT NOW, and I wont get it till Thurday either(estimated, possibly earlier I guess).

"UPS Mail Innovations" is who is shipping it, may not be that same.
[AT&T Samsung Galaxy Note I717] Theoriginalgiga:
I don't recall getting an email giving me a shipping number, but I checked the webpage and shows that I'll get mine Thursday. oh and mine is 104 miles away. Knowing UPS, it'll be here on Thursday they don't tend to like to get things to me early.
[AT&T Samsung Galaxy Note I717] Theoriginalgiga:
So I just got this in on the 20th and wanted to play with it a bit before I said anything about it. In a nutshell, I don't like it. I like it's premise with A2DP, the accelerometer and the cool integration things, but in the end I feel it was poorly executed.

First the rubber actually hurts my ear, which is a novel concept for me because I have big ears. Even with a big earpiece, I was hoping it would apply enough grip that I could wear it without the loop, but no such luck. The over the ear hook is cool, it disconnects easy enough but not so easy that i'll pop off while on your ear and it swivels for optimal positioning, but it's hard plastic and it's a small loop.

The audio is good, but not better than any of it's competition, but in the same breath it isn't worse than it's competition either. The noise assassin, is a cool idea, but no more effective than the competition's noise canceling.

The tap tap function is cool, but why not just use a button? It has a function called shake shake so you can answer your phone call while it isn't in your ear, my only question is why not just put it in your ear and answer it then? To pair, it uses a double shake shake, which is handy to quickly put the headset into pairing mode, but how often do you need to pair a headset?

The software. Oh how i wish I could say that all of that could be made up with the software. But all you can do with the software is tell it what you want the talk button to do when you press it and if you want it to speak your calender reminders.

Lastly is the webpage. First you have to install the updater software, which you would imagine to operate similar to like a logitech software bundle but all it does is provide an interface for your headset and the webpage which is fine. You can choose from 6 different voices which is cool AND you can specify what service you want to use when you do a press and hold action. Unfortunately the majority of the services, (all 7 of them) require accounts/payments. From the webpage you can access different functions like disabling the tap tap or shake shake feature or A2PD, but my question is, why can't the app handle these?

I guess I'm being just picky or maybe I'm jaded because I just got it in and it isn't working with my phone anymore (not sure if it's a ROM issue or a headset issue) but I don't like the headset. If anyone wants it, i'll give it up for a little less than I paid for it or else it'll probably end up in a drawer whilst I continue my search for the best bluetooth headset.

Oh and a bit on dailysteals, good company, the headset only came with the 1 ear cover, and the back was a little scratched up where it looked like someone couldn't figure out how to plug it in but I can accept that for a headset that's still going for $70 to $110 new.
[AT&T Samsung Galaxy Note I717] LittleRedDot:
I'll take it off your hands if you want.
[AT&T Samsung Galaxy Note I717] Theoriginalgiga:
PM sent
[HTC Desire S] Sengeh:
Is it possible to permanantly root my desire s with quick root which was just release?

S on.
[HTC Desire S] SimonTS:
Give it a try. It should work, but as most of us are already rooted we're not likely to flash an unrooted ROM just to test this.

If you, on the other hand, test it then you can post a new thread on how good it is with instructions and become a hero (well, almost) ;)
[HTC Desire S] thefunkydonkey:
I've just tried and it failed on my DS after the reboot to recovery :( .

A second attempt cannot be made as this is the output:

Checking Device Connection...Device Connected

Preparing Universal Explout... Failed!

Error: Universal Exploit method has been patched on this Firmware!

It detects my first attempt so I have to figure out to move further now...

The device shows no issue/wipe at the moment.

Can't post Quick Root device info as my number of posts is below 10.
[HTC Desire S] SimonTS:
I'd go back to the Dev with a PM and ask for advice - this is exactly the sort of feedback they need and want.
[HTC Desire S] thefunkydonkey:
Thanks Simon, I just wanted to read a bit more. Looks like somebody is experiencing the same here.

Beign lower than 10 posts I can't post write in the main thread at the moment..
[Verizon Samsung Galaxy S III] Brian Gove:
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!!

...
[Verizon Samsung Galaxy S III] galchristian:
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.

:cool:
[Verizon Samsung Galaxy S III] annoyingduck:
Wipe data? What's that for? Is THAT why my phone won't turn on.......... :p

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!
[Verizon Samsung Galaxy S III] wctaylor79:
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.. :)
[Verizon Samsung Galaxy S III] droidstyle:
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 ;)
[Verizon Samsung Galaxy S III] Byonik:
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?
[Verizon Samsung Galaxy S III] xxx420:
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?
[Verizon Samsung Galaxy S III] epagib:
Dirty wipe

Sent from a SYNERGIZED GalaxySIII
[Verizon Samsung Galaxy S III] xXJay_RXx:
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 :)
[Verizon Samsung Galaxy S III] Droosh:
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 ----------

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.
[Verizon Samsung Galaxy S III] xxx420:
Thanks for the info guys.
[Verizon Samsung Galaxy S III] johnwaco:
I usually dirty on nightlies until I have issues. Always clean when switching roms.
[Verizon Samsung Galaxy S III] flash_27:
It is always good to complete wipe when switching roms.
[Verizon Samsung Galaxy S III] techgov8:
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
[Verizon Samsung Galaxy S III] droidstyle:
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.
[Verizon Samsung Galaxy S III] coldhardtruth:
I wipe dalvik, cache and battery stats. Works like a charm thus far. Wiping data is what blows out the IMEI correct?
[Verizon Samsung Galaxy S III] SlimSnoopOS:
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.
[Verizon Samsung Galaxy S III] Brian Gove:
Factory reset doesn't touch the davlik(Which I speculate(Guess) has to do more with the kernel than anything)

This is what I meant as a dirty flash when I made the thread yes...

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.

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...
[Verizon Samsung Galaxy S III] piiman:
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.
[Verizon Samsung Galaxy S III] Addiso:
Actually you're not right.
[Verizon Samsung Galaxy S III] BiggyBoy1:
Yeah, like there is a lot of difference between in the op sys. between a galaxy S3 and note 2? :confused:

---------- Post added at 02:01 PM ---------- Previous post was at 01:56 PM ----------

Oh, but thanks for all your help finding the correct place to be, as well as making a new member feel welcome here. #rudemuch
[Verizon Samsung Galaxy S III] HypostaticOnion:
Not to mention it's not hard to find when looking at the devices large at XDA. I mean, there's even a device search... I'm so confused when people come to the wrong forum asking for help when it's so easy to find the right place.

Sent from my SCH-i535 with Tapatalk 2

If I've helped, please hit the thanks button
[Verizon Samsung Galaxy S III] jmxc23:
If you go to the note 2 thread you will get help from those with a note 2. Yet you go to a galaxy s3 thread and expect galaxy s3 owners to help you with your note 2. Then when someone says "wrong forum dude" you get an attitude about it. Next time post in a note 2 thread. FYI although both have a Touchwiz variant of android the note 2 version comes with added features so it is a different variation of the same OS. It is exactly like having different variations of Ubuntu.
[Verizon Samsung Galaxy S III] :
With every ROM I flash, I always do a complete wipe, even if its a nightly.

I've seen way to many issues with just doing dirty flashes, those cause the most issues,
[Verizon Samsung Galaxy S III] bbqsfire:
I completely agree. Dirty flashing is OK but I would rather wipe clean and flash new. To many times the dirty flash has messed me up.
[Verizon Samsung Galaxy S III] Surge1223:
Wait, I categorize flashing into three categories:

1.Dirty flash - wipe cache, then flash and reboot (I do this when flashing a theme or something that doesn't replace/affect a system apk)

2. Regular flash - wipe cache & dalvik, then flash nightly, etc. Reboot

3.Clean flash- format system, wipe cache/dalvik, flash Rom, gapps etc, factory data reset, Fix permissions, reboot

3a. ODIN

Have I had it wrong this whole time then?

Surge1223
[Verizon Samsung Galaxy S III] SlimSnoopOS:
Sarcasm? Lol cuz #'s 1 and 2 are the same, they are dirty flashes. As for #3, format data before flashing the rom but yes that's a clean flash.
[Verizon Samsung Galaxy S III] xs11e:
No fight here, I ALWAYS dirty flash a new ROM and, to me, dirty flash means no wipe of anything! If the flash doesn't work (and about 30% of the time it doesn't) I reboot into TWRP, do a full wipe and flash again.

Why? Because if it does work it saves time setting up the new ROM so it's a gamble.

I may be wrong but I see little chance of bricking the phone, just a couple of extra minutes to pull the battery, reboot into TWIRP, wipe and reflash. To me, it's worth the gamble, as always, YMMV!
[Verizon Samsung Galaxy S III] Naddict:
Thread cleaned,

Users are expected to be respectful in all posting.

And, let's keep this discussion on topic as well.

No more one upping each other in here.
[Verizon Samsung Galaxy S III] arathorn4:
Awesome thread. Maybe this vocabulary lesson will save me some unnecessary data wipes. Ugh such a downfall of my flash addiction
[Verizon Samsung Galaxy S III] tandeejay:
If you do a dirty (no wipe anything) flash, and it doesn't work, have you tried slipping in a wipe dalvic, cache before you do your clean wipe to see if that works? or do you just go straight to a clean flash if your dirty flash fails?

I like your idea of trying to reduce setup time :) If you reduce the setup time for 70% of your flashes, your ahead :D
[Verizon Samsung Galaxy S III] bigee1212:
Are system settings and ROM settings saved in the /system or /data folder? If the data folder is purely apps from the play store then I don't see why Dorty flashing wouldn't worm even from different ROMs... As long as its the same base etc. But if some system settings are saved in /data then dirty flashing can cause problems.
[Verizon Samsung Galaxy S III] DonMigs85:
Format/ Data isn't really needed? Just doing Format/ System is sufficient?
[Verizon Samsung Galaxy S III] FlashHappy78:
I used to dirty flash nightlies, and updates, but it seems every time I encounter bugs. And every time I encounter these bugs, a good wiping and clean flash seems to clear them up, that being said, dirty flashing to me seems like a waste of time considering every time I end up wiping and clean flashing.
[Verizon Samsung Galaxy S III] gdeangel:
The main reason I dirty flash nightlies is to save having to set up the system settings the way I like every time I flash.
[Verizon Samsung Galaxy S III] poppo101:
I tend to agree. I have one ROM that I have been trying and everytime I dirty flash I tend to have problems with it rebooting. Don't know if it may be an incompatible app or what since I have been flashing a JB 4.3 based ROM. If I wipe clean and flash, I have no problems.

Current Phone:

ATT Samsung Galaxy S III

Rom:PWNCAKES QUANTUM v1.20

Kernel:CM3.4.60

Baseband:I747UCMG2

Previous Phones:

ATT Samsung Captivate

Motorola Milestone Droid
[Verizon Samsung Galaxy S III] gdfrisco:
Working great here after doing a dirty flash upgrade from 1.5, so far everything is running smooth, no previous installed apps were affected at all. thanks man!
[Verizon Samsung Galaxy S III] xunholyx:
I'm the same way if it's an update or nightly, or an aosp ROM being flashed over another. I have no problems about 85% of the time, and if I do I clean flash. It saves a lot of time.
[Verizon Samsung Galaxy S III] jimwick:
Clean saves time

My partner in work and I got the S3 at the same time, he has done a dirty flash twice so far and supposedly has no issues, I started testing different ROMs the last 4 weeks and found I only had no problems when doing a clean install. My knowledge of the Android is a lot greater than his just because of the fact that I learned how to backup and restore every setting through clean installs. I believe if your "Tech Minded" then there is no way you would try a dirty flash. A clean install has always been the easiest way to go since Win95 and my first xv9500 for me :laugh: , just my cents........
[Verizon Samsung Galaxy S III] SymbioticGenius:
Please... do enlighten us.
[Verizon Samsung Galaxy S III] papadelogan:
I tried a dirty flash once, just to see.... and I won't bother with it again. I'll do it clean, every time. I have Nova Prime so my desktop icons, etc. are restored, plus I use MyBackupPro and that will restore System Setting and Android Home, so my setup time isn't too bad. Plus I know I'm reducing my likelihood of issues, and the extra setup time isn't really that much and it helps me find new things in the updated version.
[Verizon Samsung Galaxy S III] Entropy512:
If you're going for an update from the same project - even your definition of "dirty" is too much.

e.g. if you're going from one CM nightly to another, or one Omni build to another, etc - If you even have to wipe cache/dalvik, someone screwed up.
[Verizon Samsung Galaxy S III] optimusodd:
So the Clean Flash is :

Format system > Wipe Dalvik cache > Wipe data/factory reset > Flash Rom, Flash Gapps etc > Fix permissions > Reboot.........Right ?

Is "Fix permissions" necessary ?

What if we are taking nandroid backup ?

a)Of the current ROM

b)Of different ROM

Are we supposed to wipe or format anything ?AFAIK,Recovery automatically does it.But I have also heard that we need to wipe cache partition and dalvik cache after the nandroid backup is restored to make sure that the restored state can be recovered correctly and is not affected by cache issues :confused:
[Verizon Samsung Galaxy S III] Hans5849:
Fix permissions is unnecessary and not an option in some recoveries anymore. It was a carryover from the times before android supported moving apps to the external sd card.

Nandroid first to backup your current setup.

Personally if I'm restoring a old backup I'll wipe and format everything first then restore the backup.
[Verizon Samsung Galaxy S III] xs11e:
I never tried that, I just go straight to a clean flash if the "wipe-nothing" flash fails.

Sorry to be so long in answering, I've been away from my S3 for several months but I'm back, now.
[Verizon Samsung Galaxy S III] stu1811:
Huh. Learned something new. I've never wiped /System before.
[Verizon Samsung Galaxy S III] beepea206:
I only dirty flash (just a dalvik & cache wipe), unless I'm doing one of the following:

- Going from 4.3 to 4.4 (and vice versa)

- Going from AOSP to CM base (and vice versa).

You only need to wipe data (factory reset) when you're flashing different framework, like an upgraded version or a different base (CM/AOSP). I'll only wipe data if there are issues with the function of the rom and I use it for troubleshooting only. The data wipe only zaps apps, app data and system data associated with the framework, so if there's no substantive change to framework, you don't really need to wipe that partition. If you know what you're doing, you can wipe only when necessary.

You should ALWAYS wipe dalvik and cache... because you should allow the new rom to build up that dalvik cache, rather than carry over from a previous rom. Many bootloops are caused by old dalvik data. We should probably be clear you don't need to 'format' to flash a new rom, only 'factory reset' or 'wipe data', which clears the data partition, rather than wipe the internal memory.

HOWEVER... as someone that compiled and posted CM builds in the past, if you dirty flash, DO NOT go into a development thread and whine about a rom not working. Make sure you've wiped data and maybe even reflashed after a full wipe before you do so. People that dirty flash and complain about roms not working only piss off devs. :)
[Verizon Samsung Galaxy S III] :
Thanks to the useful posts! I tried to get SlimBean 4.3 on my Samsung Nexus S 4G (I know, I'm in the wrong forum). But when the phone booted up, it was stuck on the activation screen. I then cleaned flash everything to start over. This time, I put an AOSP ROM on first, then did a dirty flash (just a dalvik & cache wipe), before flashing the SlimBean 4.3 ROM on. This time, after reboot, I was easily able to get past the activation screen, and the ROM's been running smoothly so far. I never did a dirty flash before, always a clean flash. But, this experience has opened me up to doing dirty flashes, when needed, now. Thanks again guys!
[Verizon Samsung Galaxy S III] beepea206:
Yea, devs don't ever want you to dirty flash, especially if you're going to report issues, but if you're mindful of the framework/version you're going to/from, you can generally dirty flash and be fine.

FYI, you will most certainly have bootloops if you try to go from CM10/CM11 to an AOSP-based rom; I've tested and confirmed. Always full wipe if making a jump like that. :)
[Verizon Samsung Galaxy S III] caain:
Neither did I. Made me think it's time to quit the 3 year lurking streak and start posting to learn some more.
[Verizon Samsung Galaxy S III] twistedillutions:
All this time i thought I was doing clean flash

wipe catche dalvik then flash new version of rom (liquidsmooth)

i do factory reset /clean flash wen i got to a different rom

also learn that i had to clean flash wen i went from 4.3 to 4.4 on the same rom
[Verizon Samsung Galaxy S III] Brian Gove:
semantics, semantics..... gfys
[Verizon Samsung Galaxy S III] KanD93:
AFAIK, AOSP means pure android and all ROMs are based off AOSP. So that way CM = AOSP.

I think you should have rather compared going from CM to AOKP and not AOSP.
[Verizon Samsung Galaxy S III] dbus08:
I just dirty flash unless switching android versions. I throw an occasional clean flash in just because it helps me get rid of stuff I never use but never really noticed until I can't remember what went here.
[Verizon Samsung Galaxy S III] oopewan:
Always clean. Take your time and do it right the first time.
[Verizon Samsung Galaxy S III] wanerza77:
That mean if I'm from rom v1 to v2 I'm just wipe cache & flash the v2 rom without flash the gapps? Aren't Im right?
[Verizon Samsung Galaxy S III] Bramton1:
I usually play it safe and do a clean flash almost regardless. The only exception is nightlies. Even then, I won't sorry flash more than a few nightlies without a clean flash (this is probably why I shy away from ROMs with nightlies).

I just upgraded Bean Stalk from one version to a newer version a month and a half later. Did a clean flash.
[Verizon Samsung Galaxy S III] jdip:
I read this whole thread and am still confused...

Does restoring to factory settings in TWRP, then flashing a ROM count as a clean install? Or do I have to manually wipe cache and dalvik manually in addition to restoring to factory settings?