yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S (4G Model)] jeffsf:
Backup, for me, means recovery backups and Titanium Backup backups, both copied to another device (in case I wipe my microSD). Not so bad.

USB drives are a PITA under Windows. There isn't a sure-fire way to get the right one installed for Odin / heimdall, which is different than the one for adb on this build, which is different than the one for that build,... I try them out until I get one that works when I have to, but do everything I can on Linux or Mac.

Vibrant ROMs are basically not compatible with the T959V. The hardware is different enough in key places.

---

Posted from whatever phone booted today
[Samsung Galaxy S (4G Model)] sveris:
I think I'm almost ready to root and upgrade FROYO.VUVKD1 to stock GB 2.3.6, using Superoneclick, but I'm wondering about two things.

One guide method suggests using:

1) Kies mini to first upgrade to stock GB 2.3.6, then,

2) Supermanager to make a backup copy of the EFS folder, and finally,

3) Superoneclick to root the phone.

Another method begins by rooting the phone, then upgrading to stock GB 2.3.6 and offers more than one method to do the upgrade.

Seems I recall reading about disadvantages to using the Samsung Kies mini software, but I don't recall the specifics. So, should I avoid using Kies mini and should I upgrade first or root first? Thanks in advance for any input.
[Samsung Galaxy S (4G Model)] sveris:
I appreciate the caution re: using Vibrant ROMs. I was a bit surprised to see posts in the T959V specific forum about it sometimes being okay to use them. I guess it's like Caveat Emptor, eh? Sometimes they work, but not necessarily on every T959V - even when starting from scratch with a stock ROM backup.
[Samsung Galaxy S (4G Model)] FBis251:
If you're going to upgrade to Gingerbread 2.3.6, you should give lumin's guide a shot since that's the best method to use in case you soft-brick your phone.

http://xdaforums.com/showthread.php?t=1470716

That will get you a completely stock 2.3.6 rom. I don't recall if you can successfully root 2.3.6 with superone click though, but there are a lot more rooted gingerbread kernels out there that will be useful to you.

I recommend the blastoff kernel by [MENTION=1949378]bhundven[/MENTION] since he knows his stuff. I'm not biased 'cause we were both in Team Acid ;)

http://xdaforums.com/showthread.php?t=1828171
[Samsung Galaxy S (4G Model)] sveris:
Actually, lumin's guide is the one I was referencing when I posted those instructions. But, he didn't mention any issue about using Kies mini or that its use might limit future modding. I guess I'll keep searching the forums for more advice or a definitive answer. And I'll take a look at the description of the blastoff kernel you recommended.

Thanks again for taking the time.
[Samsung Galaxy S (4G Model)] champ1919:
Heimdall (the one clicks) and odin (kies) drivers will clash. You'll need to decide which method you will want to use (or use different usb ports for each method). Being new, I would suggest the one clicks for you.

Unless you wish to have the official, official release, there isn't really a need to go kies route imo. The one clicks are the same.
[Samsung Galaxy S (4G Model)] sveris:
Thanks for reminding me about the clash potential. But now I'm getting confused again. Lumin's guide suggested the following:

1) Kies mini to first upgrade to stock GB 2.3.6, then,

2) Supermanager to make a backup copy of the EFS folder, and finally,

3) Superoneclick to root the phone.

Would this be mixing and matching like you said, or am I missing something?
[Samsung Galaxy S (4G Model)] jeffsf:
The "problem" is that you want Froyo. You'll be stuck with basically three-year old tools. Froyo was incredibly painful to use, even compared with Gingerbread. There wasn't much of a demand to "go back to Froyo" once the stock Gingerbread upgrades hit people's phones. Edit -- Looks like there is a heimdall one-click for Froyo, thanks to [MENTION=3833556]FBis251[/MENTION] http://xdaforums.com/showpost.php?p=50931923&postcount=10

In my opinion, just go straight to stock Gingerbread. It shipped that way or OTA upgraded to it for most of the phone's life (until Apple sued Samsung and got it pulled from retail).

This is the thread you should be following for Gingerbread or later: http://xdaforums.com/showpost.php?p=21953878&postcount=2
[Samsung Galaxy S (4G Model)] sveris:
Well, you may have convinced me to upgrade directly to GB 2.6.3. Just a couple more questions and I'll be ready to take the plunge.

Will the upgrade lock my unlocked phone - back to T-Mobile? I'm on another carrier now. Other than that, I think I'm prepared.

I installed Supermanager and made a backup copy of the efs folder on my T959V, then copied it to the SD card and also to my PC. But, just when I decided to upgrade using Kies mini, I believe I found another contradiction.

In lumin’s guide, he says to do the following:

•	- Download Kies mini if you do not already have it. When you follow this link you will see two tabs - 'Manuals' and 'Software ' - click [Software] and download.

•	- Make sure your phone is charged.

•	- Double check that USB Debugging is not enabled. Go to [Settings] > [Applications] > [Development] and UN-Check [USB debugging].

•	- Start Kies mini on the computer.

•	- Make sure phone is not connected to computer yet.

•	- In USB Settings on my phone I select [Kies (Firmware update)] if it is not set to ask every time.

•	- Plugged in phone, let device drivers install on computer. You will see a notification on your computer when complete.

•	- Then Kies mini will recognize the phone.

•	- Hit [upgrade] and wait.

•	- Phone will eventually reboot. Check your IMEI.

I interpret that to mean – according to lumin’s guide - that USB debugging should NOT be enabled.

However, from the T-Mobile Support website, this link, http://support.t-mobile.com/docs/DOC-1810 it says:

Prepare the Samsung Galaxy S 4G

1.	From the Android home screen, press the Menu key and tap Settings.

2.	Tap Applications.

3.	Tap USB settings.

4.	Tap Ask on connection.

5.	Tap the Escape key once to go back to the Applications menu.

6.	Tap Development.

7.	Tap USB Debugging.

8.	Tap the Home key to exit the settings menu.

9.	Insert the USB data cable into the phone and then into an available port on the computer.

10.	Select Samsung Kies at the phone prompt. The PC should recognize several devices and begin installation. This is normal and may take a few minutes. Unplug the data cable when completed.

I interpret that to mean – at least according to T-Mobile Support for the T959V - that USB debugging SHOULD be enabled.

So, which is correc: enable or disable USB debugging modet? Do I need a remedial reading course? Or, is lumin saying the same thing as T-Mobile, but in a different order? After reviewing both sets of instructions several times, this is what I think is the situation. Lumin first turns off USB debugging and instead of selecting Ask on connect for basic USB settings, he then selects the Kies firmware update option. However, T-Mobile Support instructs the user to select the Ask on connection option, first, followed by ENABLING the USB debugging function.

Does that mean either method works, just getting from point A to point B by taking different paths?
[Samsung Galaxy S (4G Model)] jeffsf:
OK, heimdall will basically reset your phone to stock if you mess up.

Once a phone is carrier unlocked, it is carried unlocked (unless you restore a pre-unlock efs, which isn't something that is likely to happen inadvertently).

That said, you either should try something or decide that you are too risk-adverse for flashing and especially rooting a phone.

Again, heimdall one-click is probably the most robust way to get there

---

Posted from whatever phone booted today
[Samsung Galaxy S (4G Model)] sveris:
Decided to follow the instructions in lumin's guide to do the GB upgrade - rather than the ones from T-Mobile Support. It worked like a charm. All is well for now. Will check everything for a few days before rooting and removing bloatware. Thanks again to all for advice, recommendations, links, and guidance.
[Samsung Galaxy S (4G Model)] jeffsf:
Glad you're able to enjoy an upgraded phone!

---

Posted from whatever phone booted today
[Samsung Galaxy S (4G Model)] FBis251:
If you'd like to debloat your phone, I made a site that lets you download a zip file that will do the debloating for you. All you need to do is pick which apps you'd like removed, then flash the zip.

http://teamacid.sourceforge.net/debloater/

Enjoy!

PS: You'll need a custom kernel and recovery to flash the zip.
[Samsung Galaxy S (4G Model)] sveris:
I'll keep that in mind. Still want to check out everything for a few days, since I've noticed a few minor differences after the upgrade.

I just made another backup copy of the efs folder, and noticed something I did not expect. The copy I made when the phone was on Froyo looks empty, while the one for GB 2.6.3 is definitely

not

empty.

Froyo efs - 0 files - folders

GB 2.6.3 efs - updated file system plus 3 folders - root, .android, and imei

Did I do something wrong the first time I backed up the efs folder while running Froyo? Does it matter, now that the phone is running GB 2.6.3?
[Samsung Galaxy S (4G Model)] sveris:
Everything checked out okay, so I decided to root using Superoneclick. Seems like it's taking a long time: how long should I wait? Her's what it says on the Superoneclick program screen that is displayed:

Killing ADB Server...

OK

Starting ADB Server...

* daemon not running. starting it now on port 5037 *

* daemon started successfully *

OK

Waiting for device...

OK

Pushing rageagainstthecage...

1815 KB/s (585731 bytes in 0.315s)

OK

chmod rageagainstthecage...

OK

Running rageagainstthecage...

It's been running for 30 minutes and no progress at all. The screen on my phone shows no indication of anything other than the normal background picture. Should I close Superoneclick and try again, or .... ???
[Samsung Galaxy S (4G Model)] FBis251:
You got your one-clicks working right?

bhundven made a one-click jar of AntonX's basic with a twitst kernel which will root your phone after you flash it.

http://sourceforge.net/projects/tea...sic_with_a_twist-v1.1.0-NO_OC_UV.jar/download

AntonX's kernel is fairly old though and you should only install it to get root + recovery working. Afterward I recommend you install bhundven's blastoff kernel:

http://xdaforums.com/showthread.php?t=1828171

You can get the download link from that thread.
[Samsung Galaxy S (4G Model)] sveris:
I stupidly forgot to check the version of Superoneclick that I downloaded - that was the problem. Downloaded the 2.3.3 version and rooting proceeded without incident, and it only took a few minutes. I'll probably give your debloating app a try next week. Tiny steps for me!
[Samsung Galaxy S (4G Model)] champ1919:
To free up some more memory (and since we'll never get another firmware update), you could download "fota fix" from the play store and get 70 megs back.
[Samsung Galaxy S (4G Model)] sveris:
That sounds like a good start to free up some memory. Can I just download

any

free version of busybox to use the fota fix app - since I don't really know much of anything about busybox? I seem to recall that Superoneclick needed did a temporary install of busybox to root my phone. Or, should I learn more about busybox before proceeding with the fota fix app?
[Samsung Galaxy S (4G Model)] champ1919:
I don't recall it needing busybox.
[Samsung Galaxy S (4G Model)] sveris:
First search on android market stated fota fix app requires busybox. I'll do some more research.
[Samsung Galaxy S (4G Model)] sveris:
Clicked too fast - sorry. Here's what I found:

Fota Fix

Matt Henry

- May 25, 2011

Tools

Description

DO NOT DOWNLOAD THIS APP UNLESS YOU ARE COMFORTABLE FLASHING BACK TO STOCK USING ODIN

**APP REQUIRES ROOT + BUSYBOX**

**SAMSUNG GALAXY S 4G ONLY!!**

This app removes the placeholder used to save space for the over the air update, freeing up more room for system files and apps. I got pretty sick of that annoying "Internal Storage Full" message and the fota fix was a perfect fix!

Credits:

Stericson (Root Tools)

Credits:

Stericson (Root Tools)

But, something just occurred to me. If later I screw up installing a custom ROM and/or kernel and have to go back to GB 2.6.3, will these missing fota files be an obstacle?
[Samsung Galaxy S (4G Model)] champ1919:
Nah, not a problem as the one click will restore them.
[Samsung Galaxy S (4G Model)] jeffsf:
You should be able to remove them manually over adb as it should have the basic commands available without installing "busybox" on the phone. My very, very vague recollection is that the two files you need to remove are /data/fota/fota_delta_dp1 and /data/fota/fota/delta_dp2 -- you'll need to cat /dev/null into each of them, then set them unwritable (or they get regenerated).

Ah -- here's an old thread on it: http://xdaforums.com/showthread.php?t=1025610
[Samsung Galaxy S (4G Model)] sveris:
Well, since I used Samsung Kies to upgrade, and Superoneclick to root, I don't have any hands on experience with the one click you mention. I'm still a real noob with this stuff, haven't used CWM, probably messed up my Froyo efs backup copy because it was empty, etc. But I do have a copy of the GB efs folder - on my SD card and my PC. :o

I'll keep reading.
[Samsung Galaxy S (4G Model)] sveris:
Good memory re: those file names, and thanks for the link to the guide. It looks pretty straightforward - even for me. I'll read through it again and give it a whirl later this week.
[Samsung Galaxy S (4G Model)] sveris:
Okay, here's the part of the guide I'm trying to follow, but I'm havng problems.

How to Delete Fota files

Step 1: Download all three files in your computer and send them to your email and open them from your phone.

Alternative method: Download them directly to your phone.

Step 2: Install File Expert

Step 3: Install Super Manager

Step 4: Open File Expert and navigate to the directory aka folder that you downloaded the files to.

Step 5: Press and Hold the fota.zip file and select Unzip files

Note: File Expert will unzip files by default in same folder.

It will create a Fota folder with two files fota_delta_dp1 and fota_delta_dp2

Step 6: Open Super Manager and then open setup and check the "Enable ROOT function" then press menu on your phone and switch to r/w (stands for read and write)

Step 7: Navigate to the folder where you have the 2 Unzipped fota files (fota_delta_dp1 and fota_delta_dp2)

Step 8: Select both and cut them

Step 9: Navigate to /data/fota and paste the 2 files in this folder

Step 10:Reboot phone and WAWAWIWA! between 150mb-300mb of free space

At Step 6. it says to press menu on your phone and switch to r/w (stands for read and write). I can't find any r/w option anywhere. Press menu on my phone? Does that mean the Menu button with 2 horizontal bars at the lower LH corner of the touchscreen? I certainly can't find any r/w option there or within any of the Supermanager menus.

Also, I cannot locate the /data/fota target directory either. I can find the source directory and 2 files created earlier, to cut and paste, but not the target directory.

What the heck am I doing wrong? I guess I have trouble reading between the lines in some of these guides.
[Samsung Galaxy S (4G Model)] champ1919:
Matt's app from the play store does it with just 2 clicks.
[Samsung Galaxy S (4G Model)] jeffsf:
My guess is that either or both your phone is not rooted or busybox is not installed.

---

Posted from whatever phone booted today
[Samsung Galaxy S (4G Model)] sveris:
Agreed. But I'm trying to learn about flashing as I proceed. I need to start learning more about the basics.
[Samsung Galaxy S (4G Model)] sveris:
Thanks, jeffsf. I did not see any reference in the guide instructions to install busybox. And, I'm too much of a noob to know that is would be required. FYI, my phone is rooted and verified with Root Checker Basic. Also, I have been able to manually remove one or two bloatware apps with no apparent problems.

I'll install busybox and try again.
[Samsung Galaxy S (4G Model)] sveris:
Busybox installed today, and I gave things another try. I followed the guide instructions, again, and got hung up at Step 6. Eventually, I stumbled onto a successful solution and here's what I found.

I could

not

select the R/W function in Supermanager - unless I first navigated to the Fota folder and selected the 2 files created when I used File Expert to unzip the fota.zip file. In other words, the

order

of Steps 6 and 7 in the guide made a difference for me.

Did others have the same experience I did? If so, would it be better to interchange Steps 6 and 7 to help future users of this guide?

In any event, thanks again to the author for freeing up a lot of extra memory for me! 323 Mb available after rebooting.
[AT&T HTC One (M7)] leandrocamoezi:
hello i have a "one att htc unlocked" and because of it being unlocked I can not receive updates via OTA.

I wonder if anything I can do?
[AT&T HTC One (M7)] mb_guy:
ac

Look in the Q&A thread some others experiencing this as well. There is procedure from [MENTION=2895182]clsA[/MENTION] to update manually.

It is not because of the unlocked.
[AT&T HTC One (M7)] kiory01:
Link please
[AT&T HTC One (M7)] clsA:
here you go

http://xdaforums.com/showthread.php?t=2659374
[Sony Xperia L] kcitizenerased:
Hello

My first "mod" Xperia ZU Kit Kat the charging animation.

Requirement:- Root

Instruction:-

1. Download the attachment

2. Extract the .zip and copy it to your mobile storage

3. Copy the images and paste it to "/system/etc/chgicon" by Root Explorer and set all images permission to "rw-r-r"

4. Swtich off your phone plug charger and see effect

enjoy :good:

thanks to DavidMKD http://xdaforums.com/member.php?u=4694376 for the post http://xdaforums.com/showthread.php?p=50933432
[JAMin, XDA Neo, S200 General] bigal82:
hey

is there a spanish rom to download ??

byby alex
[Sony Xperia P, U, Sola, Go] victorcqueirozg:
Well, I discovered that the Sony update to ICS it is not so good as GB, but and what about JB? Worth it? What I am losting staying on GB? Actually when I FINALLY root the Xperia U 2.3.7 and install CWM, my celphone gain some little lags that was anoying me (Even without CWM if you guys think that maybe it could be the problem), nothing is going as I really want, how could I change this? How could I solve that?

I was trying to enable Developer Options (That came with the STOCK FIRMWARE .184 but now all I got is "USB Debugging and stuff) but nothing works for me, and I don't want to change to ICS. What i'm trying to say here it is just "Change the GB for JB worth it?" and I'm justing explaning what i'm passing through...

Someone could advice me? Thank you for all. Sorry for any english error. :fingers-crossed:
[Sony Xperia P, U, Sola, Go] Ryccardo:
I tried CM10 and Slim JB, but while the increased app compatibility is clear and you can repartition them for even more space than stock... I just prefer GB, not to mention the camera sucks compared to Sony's.
[Sony Xperia P, U, Sola, Go] mannu420:
plzzz help me bro

plzzz help me bro how you root xperia u running on 2.3.7 , i want to root my xperia u too running on 2.3.7 plzzz help mee plzzz mail me or reply me hair xda my email add is=mannu.sandhu421@gmail.com plzzzz plzzz plzzzz help
[Sony Xperia P, U, Sola, Go] victorcqueirozg:
Flash firmware .184.

Flash this kernel: http://xdaforums.com/showthread.php?t=1766892.

Turn on your phone with USB Debugging on, and root with FlashTool, using Superuser (I recommend).

Done.

For more information, read: http://xdaforums.com/xperia-u/issues/video-guide-xperia-how-to-unlock-root-t1897826.
[HTC Droid DNA] redadz:
I'm running LiquidSmooth v3.0 Beta (LS-KK-v3.0-2014-02-13-dlx) on my Verizon DNA and I'm pretty happy with it. Big thanks to deadman96385, santod040, and anyone else who contributed to this project!

This is the first custom ROM I've run as a "daily driver" on my DNA after ~16 months on the stock ROM, so most of my impressions are in comparison with the most recent stock HTC software. I briefly tried CyanFox but switched back to stock. I also tried the "HTC One *STOCK* ROM Port" (DLX_WL_K442_SENSE55_MR_4.19.401.8) but couldn't get it to boot; actually flashing it messed up my recovery as well. I suspect maybe my download was corrupted since other people reported success with that ROM.

Back to LiquidSmooth:

- Perceived performance is generally pretty solid. It's mostly very smooth, living up to its name.

- I do get the occasional app crash (FC); haven't noticed a pattern yet. It's not frequent enough to bother me much.

- A few times I have had the phone become unresponsive when opening the recent apps view or when trying to unlock from the lock screen. But this hasn't happened in a few days. Could be the freezing was related to one of the features I tried and later disabled (see below), or just due to the ROM "settling in" (populating caches, etc.)

- Love KitKat and the add-on features:

- I'm using the "pie control" for quick access to apps, quick screen off, menu access, etc.

- I tried HALO and couldn't really figure it out / didn't find it useful.

- I like the idea of Active Display but it didn't work that well in combination with the way I use the lock screen, so I turned it off and use the lock screen's built-in active display features instead.

- I'm using the default Google Now launcher for the moment. I like the easy access to voice search and google now. Don't like that it doesn't have multi-touch for dragging icons between home screens.

I think the battery is draining faster than with the stock ROM, though it's hard to say because I've also been using the phone a lot more actively while I get it set up and configured the way I want. It may be that the active display feature of the lockscreen is using more power?

People in the development forum mention an over-the-air (OTA) update mechanism; I haven't been able to find that yet.

There's a new version posted called 03-05-14; I haven't tried that version yet.

Anyway, I'm quite happy with this ROM and imagine I'll stick with it for a while. I would recommend it to anyone looking for a clean, fast, stable ROM, and in particular to anyone freshly rooted and looking for a solid ROM to try out KitKat and get a lot of great new features.

(note—maybe it would have made more sense to put this directly in the existing LiquidSmooth development thread, but I don't have permission to post there. And I'm not developing the ROM, just using it.)

Thanks again! Great ROM.
[HTC Droid DNA] Yehudah:
How much did they pay you? LOL :D

I tried it as well as all of the other KK AOSP ROMS. I really like AOSP.

I was on stock until viperDNA 2.0 came out, then I decided to S=OFF/ROOT/etc... and plugged Viperware in. It was awesome. Not an issue ever. So I wanted to give 3.0 a try, after trying every ROM out there (actually it kinda became like crack to me LOL).

So far after several days, it's 5x5, not an issue at all. On my phone, only the Viperware works as advertised.

That's not to say that Viperware doesn't have its issues, but I just haven't seen any yet. As I said I really like AOSP, but because Viperware uses Aroma installer, I can delete almost everything - which gives it a kind of AOSPishy look/feel.

My sig hits it; these developers (ALL of them) are amazing and do all of this for US on their own time for FREE. If I were a kagillionaire, I'd employ you ALL.
[HTC Droid DNA] redadz:
Hah! :) Thanks Yehuda. I started this thread because I wish there were more ROM reviews here on xda, since I don't really have time to try out every ROM. I appreciate your review of ViperDNA; maybe I'll try that next.

Update on LiquidSmooth: after a week or so I found that it wasn't as clean as I originally thought and went back to (rooted) stock for a while.
[Windows Phone 8 Q&A, Help & Troubleshooting] raybands:
Hi guys im new here and i dont know if i posted this in right section but anyways, i wonder you guy noticed on nokia lumia when you set lock screen image then you lock your phone it tend to tint the image (make it dark? and the image lost shapness) anyone of you guys have the same problem if it a problem. Its quite annoying tbh.

Best regards Dom