yashsingh1/xdaforums huggingface dataset:
[Tilt, TyTN II, MDA Vario III General] Snowreaper:
What trials and tribulations did you have to go through? What was your end result and were you happy with that end result? Here's a brief outline of what i went through.

I recently bricked my phone and had to spend almost 2hrs at an ATT store making arrangements to get it replaced under warranty. Since i bought my Tilt on Amazon (got a deal w/a new line of service for $50 usd.) Amazon told me to talk to ATT, ATT said talk to Amazon, ATT told me to go talk to the local repair shop. They were closed, and i had no phone cept the paperweight that was my Tilt. Since all this was on a Sunday everything closed early and i ended up buying a cheapo "Go" phone to use.

Called ATT warranty support from work, they said they never even saw the Tilt on my plan but they did see that damn Go phone. Thats when i was told to go to the store and show some ID and what not. Everyone was really helpfull at the store and after waiting on the phone at the store, we eventually got to the people that can replace the phone.

The only thing that sucks now is that i'm getting a refurb as a replacement, but beggars can't be choosers.

I do have a few questions now though. Right now the phone doesn't start up at all, should i worry about ATT spotting what i did wrong? If so should i find a large and powerful magnet in the hopes of corrupting or erasing the data on the phone? I'm just curious what other's went through having to replace their phones and am only partially kidding in regards to magnet thing.

I'd also like to stress that i'm not asking for any criminal malfiesence, just the story you have and how hard/easy was it for you to get your phone replaced. It doesn't have to be an ATT phone either. :)
[Tilt, TyTN II, MDA Vario III General] luvmy356:
I also bought my Tilt through Amazon on their $50 deal last month, and mine experienced the Red Light of Death RLOD within 2 weeks. Took it to the local ATT store, they said I needed to deal with Amazon since the phone was less than 30 days old.

Went to Amazon.com, filled out the forms to return/exchange the device and within two days, I had a new Tilt. I can't believe how easy it was. During those two days, I went back to my old Symbian powered Nokia 6670.

Before I packed up the old Tilt in the box to return, I tested it with the new battery, and it booted up (which allowed me to reset the device)....so for grins, inserted the old battery into the new Tilt and experienced the RLOD, so in my case, my dead Tilt was due to a defective battery.

Lessons that I learned...1. if my new Tilt dies, make sure the guys at the ATT store give me a new battery to try. 2. Keep a spare charged GSM phone in my cars in case if my Tilt dies while I'm out (I was a T-Mobile/Voicestream customer for 10 years before switching so I have a box full of GSM phones). 3. Amazon.com is really easy to deal with.
[Tilt, TyTN II, MDA Vario III General] Nate731:
And because you broke it, it's AT&T's responsibility to replace it?

That being said, when I first got my 8525 after my Wizard died, I bought it from ebay and it developed a problem. Call up AT&T on the hardware line and tell them that your Tilt won't turn on anymore. If they give you static, ask for a supervisor. You'd be very surprised how well the "supervisor game" works is all situations.
[Tilt, TyTN II, MDA Vario III General] DaPutster:
I bought mine from NewEgg & around 30 days in "up" on the d-pad stopped working 90% of the time. I took it to an AT&T store, showed a rep the problem & he gave me the number for the warranty exchange. I called them up, explained the issue & 2 days later I had my newly refurbished phone (verified with ~1 hour inbound & outbound usage each). The new one seems to be working without issue so far.

Overall I'm satisfied with the AT&T support on this considering they don't offer any paid extended coverage on the phone anymore.
[Android Q&A, Help & Troubleshooting] Tahsinalam:
Hey Guys,

I use a htc e9 plus.Recently it started acting really weird.Very slow and Sluggish Ui.Crashing apps,unable to open play store, taking 15 secs to make a call after pressing the dial button,the syncing process never ends and Syncs nothing,not being able to remove the Google account like I press on remove and It says processing but nothing happens.The big thing is I can't even factory reset my phone.Pressing on wipe data does nothing.

So I managed to perform the reset from bootloader.Then it was working just fine.1 day later it said My Google play services isn't up to date and started the same problem.can't even open the app store how am I supposed to fix this?

This phone is now completely useless to me.
[Android Q&A, Help & Troubleshooting] dustojnikhummer:
I have enountered quite a lot of people with different phones (Huawei, Xiaomi, Lenovo) with simmilar issues, all problems with GApps. I guess Google ****ed up something. Again. I don't have the problem yet, Redmi Note 4 on AEX.
[General Topics] _OldSalt_:
Root Device with Chainfire

Warning: If you have a KNOX enabled device, rooting it will trip the KNOX warranty flag, voiding your warranty. This flag cannot be reset, and will prevent some applications from working.

Warning: Rooting improperly can “Hard Brick” your device, turning it into a source of spare parts.

There are numerous rooting tools out there. I use Chainfire whenever possible. The current website firmware.mobi will generate an easy to use package including Odin for supported devices. Download and extract the package to a new folder on your PC. Start Odin using the root.bat file. Read the warnings. Next:

Ensure Developer Options are enabled on your device. On the SM-G903W, go to Settings/About Phone/Software information/Build number seven times. Other devices may use a different method. Consult your manual.

In Settings / Developer Options ensure OEM Unlock is on and turn on USB Debugging

Note: I also turn “Auto update system” off

Turn the device off, then re-boot into the download mode (Volume Down + Home + Power, and then press Volume Up on my device)

Plug the device into a USB port of your PC

Select AP in Odin, then select the image.tar.md5 file downloaded with your package.

Ensure one of the COM ports is highlighted.

This is your last chance to abort. DO NOT CONTINE if you have any doubts.

Click Start

When your device is rooted successfully you’ll see a green pass in Odin. Congratulations! Your device will re-boot into recovery mode to root the device, and then re-boot normally. Well, that’s how it was supposed to work. When I used the CF Autoroot file for the SM-G903W, I got the error message “Recovery is NOT seandroid enforcing”, and was unable to boot into the recovery mode. I used Odin to re-flash the recovery partition which allowed me to enter the recovery mode again. A little searching on this forum, led me to this post by Neoony. I used the link for the SM-G903F and succeeded in rooting the device.

Now you need a root manager. My preference is Super SU. Install it from Google Play. Run Super SU. It will let you know if you were not successful by reporting that your device is not rooted.
[General Topics] _OldSalt_:
Install Backup/Recovery (TWRP)

As we intend to modify the Android system itself, we need the ability to back it up and restore it. There are several options including Clockwork Mod (CWM), Team Win Recovery Project (TWRP) and Titanium Backup. My personal preference is TWRP.

Installation is as follows:

Install the “Official TWRP App” from Google Play

Run the App, agree to the Terms and Conditions, and enable “Run with root permissions,” then tap OK.

Tap “TWRP FLASH” on the next screen

Select your device from the drop down menu, you will need a network connection for this. You’ll be presented with a series of choices. Choose the latest and greatest. The image will be downloaded to your device.

Select “FLASH TO RECOVERY”, and confirm the image is correct. You will see the message “Flash Completed Successfully!” when installation is complete.

Exit the “Official TWRP App” and re-boot your device into the Download, followed by Recovery, and finally normally to confirm all is well.
[General Topics] _OldSalt_:
Install Applications

The applications to install are those you will use to customize your device. I suggest BusyBox, and Terminal Emulator from the Play Store. BusyBox requires root access for the expanded command set. Terminal Emulator will allow command line access on your device so you won’t need ADB on your computer. You will be able to gain root access through it to modify anything on your device anytime, anywhere.

Other Apps you may find useful are the Jota Text Editor, and Hex Editor. These are also available through the Play Store.
[General Topics] _OldSalt_:
NANDroid backup

Once the device is rooted, and your choice of applications are installed it’s a good idea to fully back up the device. This includes ALL partitions, so you have a baseline that you can re-flash. If your device has minimal memory, you may need an SD card or USB OTG drive to hold your backup. These backups will often be larger than 4GB.

Re-boot your device into the Recovery Mode. In TWRP, select ALL the partitions. Select the desired Storage location, and tap OK. Swipe to backup your device. Note the warning that “Backups of data do not include any files in internal storage such as pictures or downloads.” That is not the purpose of TWRP, and is best accomplished with the native backup utility. This backup will require several minutes.
[General Topics] _OldSalt_:
Wrap up

Everyone needs to start somewhere. My goal in starting this thread was to provide that starting point, and a path forward for those new to modifying an Android device. That is why I started with a stock not-too-old device, and showed how to take it to manually changing the boot animation and sound. Why manually, when there are apps for that? An App can only accomplish a single task, such as changing the boot animation. At the command line you can do almost anything. You won’t be stopped by the lack of an App.

Much of the material covered by this guide is specific for a device. Those with Samsung devices came out far ahead, and those with a Galaxy S5 neo may just have hit the jackpot. The general sequence for all devices is the same. You’ll just need to dig for those devilish details.

There are two things that should stick out:

1. Use a not too old device by the same manufacturer as your target when starting. It’s far cheaper than bricking a bleeding edge device.

2. Backup, backup, backup! This can’t be stressed enough. Losing hours or days of work is very depressing, and often leads to dropping a project.

Good luck modding your device. This forum is one of the best, if not THE best place for resolving those devilish details that you will encounter.
[General Topics] _OldSalt_:
The Next Step: Changing the Boot Logo

First, thanks to Near_07 for his post Galaxy S9 and S9+ Boot logo. I modified his package to make one for the Samsung Galaxy S5 neo. Note that his script is for the same exynos platform. This is critical for packages containing binaries.

I unpacked the pile to a new directory on my PC.

The first thing I did was to verify paths and filenames in the script "update-binary". I opened the file using WordPad on my PC for ease of reading. The file contains references to "/dev/block/platform/11120000.ufs/by-name/UP_PARAM", which does not exist on the S5 neo. I used Terminal Emulator to check for something close and found "/dev/block/platform/13540000.dwmmc0/by-name/PARAM ". I copied the file to the Download directory, and from there to my PC. Opening the archive, I found that it contained the file "logo.jpg". Bingo! I was in the right place. I copied the "update-binary" back to the Download directory on the S5 neo, and used Jota Text Editor to change ALL the references from 11120000.ufs to 13540000.dwmmc0; and UP_PARAM to PARAM. I then copied the modified "update-binary" back to replace the original on my PC. Why did I use Jota Text Editor on the S5 neo, instead of notepad on my PC? Unix, Linux, and Android use different end of line sequences than the PC. There are programs for the PC capable of generating Android compatible files, but I'm sticking with software already mentioned in this tutorial.

Choosing or Creating a New Boot Logo:

Choose or create a new .jpg image, the same size as your screen for your new boot logo. I've attached the original logo.jpg from my S5 neo to this post. I used that as a starting point, moving and adding elements to mate with my boot animation. I've included a demo copy in the zipped package. I've also attached a copy of the first image in my boot animation sequence. The powered by Android Nougat element fades in as the animation runs.

How to Change the Boot Logo:

You are rooted and have TWRP installed if you've been following along. These are pre-requisites. STOP NOW if they are not installed.

Download the file S5neo_Boot_Logo_Changer

Unzip the file to an empty directory

Replace logo.jpg with your desired logo. Note the name MUST be exactly the same.

Use 7-Zip to compress the contents of your working folder, with 'Store' as the compression method

Copy the resulting archive to the Download folder on your S5 neo

Re-boot your S5 neo into the Recovery mode

Install the package, re-boot, and enjoy!
[General Topics] _OldSalt_:
Removing Bloatware (or fun with scripts)

Bloatware consists of the unwanted apps generously added to your phone by Google, the manufacturer, and your carrier. There can literally be a hundred or more of these apps on your phone. So how do you get rid of them? You can use a package found on this site, but that can be problematical. You may have a different view of bloatware than the package’s author. You may not know what each APK deleted by the package does, and delete one you actually want on your phone. If this happens you’ll need to restore from backup, factory reset the phone, or even re-flash the firmware. My preference is to archive the APK on my desktop so that hopefully I can restore the APks with the package manager.

To start, grab one of the packages to delete bloatware for your version of Android, for as close to your phone as possible. I used this one by Windforce. The contents of updater-script may include a section that looks like this:

run_program("/sbin/rm", "-rf", "system/app/AASAservice");
run_program("/sbin/rm", "-rf", "system/app/BluetoothMidiService");
run_program("/sbin/rm", "-rf", "system/app/CloudGateway2017");
run_program("/sbin/rm", "-rf", "system/app/GooglePrintRecommendationService");

There are many tools such as word processors, and text editors that you can use to strip out the unwanted bits so that you end up with something like this:

AASAservice
BluetoothMidiService
CloudGateway2017
GooglePrintRecommendationService

Save it as a file, ensuring that you have an Android (Unix) end of line character. We end up with a list of folders containing the unwanted APKs. Next we need a script to archive the APKs.

The following script has been designed to run in the ‘Download’ folder, from the Terminal Emulator, or ADB (Android Debugging Bridge). It was written on my desktop using Notepad++, to ensure the proper end-of-line character was used. The script, and APK lists must be copied to the Download folder from the desktop. To access the Download folder from the Terminal Emulator or ADB, Super User or root permissions are required. File permissions allowing root to execute the script must be set. Finally the script must be run from within a shell.

mount -o rw,remount /system	# mount /system for read/write
tempdir=/system/app/app	# temporary folder for APKs to be archived
mkdir $tempdir
while read apkname	# loop parses file for APK names to archive
do
mv /system/app/$apkname $tempdir/$apkname
done < sysapp.txt	# supplied list of APKs to be archived
tar -czvf sysapp.tar.gz $tempdir	# archive APKs
rm -rf $tempdir	# remove temporary folder recursively
rm -rf /cache/*	# clear cache contents
rm -rf /data/dalvik-cache/*	# clear dalvik-cache contents
reboot
exit 0

After the script has executed, you’ll note the icons for the archived APKs remain on the apps screen, and are still listed under Apps. The must be manually removed. You’ll find that ‘Uninstall’ is now available in both places for the archived apps.

Attached is a .zip file containing the script, and data files I used on a Samsung Galaxy S5 neo (SM-G903W).
[Samsung Galaxy S9  Questions & Answers] samsungsandiego:
Hello all,

I recently downloaded the Good Lock 2018 package from Galaxy store, and was playing around with the new apps. Upon installing Edge Touch, I noticed my phones edges weren't registering touch. This makes it difficult to hit backspace on my keyboard app, along with other touches. I don't want ANY area blocked off, I want to use 100% of my screen. I tried creating a "profile" with zero pixel border, it works for 5 mins and then defaults back to "Optimized" which is about 30 pixel border no touch zone. I've also tried uninstalling the app, but it looks like it leaves the residual settings behind, blocking the border. Does anyone know why this is happening or how to reset so I can use 100% of my screen?

Thank you in advance, this is driving me nuts!
[Samsung Galaxy S9  Questions & Answers] *Detection*:
Open the actual Good Lock 2018 app and turn it off

Also clear data from the edge border app
[Samsung Galaxy S9  Questions & Answers] samsungsandiego:
This actually worked for about 6 hours, and then it has reset back to normal. There is no setting option in Good Lock to "turn it off". The best I can do is clear cache/data and uninstall.
[Samsung Galaxy S9  Questions & Answers] *Detection*:
I just installed it, set up the Edge Zones, made sure it worked then deleted my custom Zone, set it back to optimised before uninstalling as suggested by the app, then uninstalled it and my edges are working fine again
[Sony Xperia XA1 Questions & Answers] AlinPletea:
Hello, guys!All the time when i use 3G,hsdpa connetion on data mobile my phone is overheating(it reach 43C) unless i have full signal. I tried to repaired with xperia companion, hard reset but same problem. What would can be the problem?
[MX Player] arsenal3008:
Today I bought the MX Player Pro and he asks me again to buy

Operation code 4VW33438FK370554N

Account number RU00MO6ACG

Operation code return 70S15352GE696743L

There is no money on the account

View attachment 4549772
[MX Player] Thirumalai.K:
Hi,

Generally, Google Play won't ask you to purchase again if you have already purchased it. If it asks, Probably it's a Google Play Bug. Kindly remove your google account from the device. Clear the Google Play & Google Play services data. Then add it back after restarting. It should fix the issue. If the problem persists, Kindly contact us at support@j2apps.com along with the email id info which is used to purchase. We will be happy to assist you.
[Galaxy Grand 2 Original Android Development] Sudeep:
CENTER]Who's back? We're back.[/CENTER]

CarbonROM is an aftermarket firmware based on the Android Open Source Project. We are dedicated to fast, stable, and feature-filled roms, honesty and communication with our users, and openness with our code. We like frequent builds, with the very latest and greatest hardware support and fixes. We strive to not only provide you with the best rom we can build, but also to give back to the Android community and our fellow developers. For us, this is about creating something we can be proud of and hope you will enjoy.

Bugs:

Offline charging

Sim data doesn't work

Best for gamers

It's aosp-caf based rom.. which focus on performance.. PUBG experience in these rom is great I treid it👍🏻👍🏻 😊

Instruction to flash:

1)wipe everything expect sd and internal (TWRP)

2)FLASH ROM, GAPPS AND MAIN VENDOR N CAMERA PATCH(TO WORK CAMERA)

3) tht all. . Enjoy the rom

Download links -om link

Rom link-

https://drive.google.com/file/d/1n3UvWDYIsGmBxnjhbCw6HSFfWHghhPFy/view?usp=drivesdk​

Vendor link-https://drive.google.com/file/d/1k08gE0yjjq24MqNL2JenIGWD4l_9-bwi/view?usp=drivesdk

XDA:DevDB Information

Carbon rom V1.0, ROM for the Samsung Galaxy Grand 2

Contributors

Sudeep

Source Code: https://github.com/CarbonROM

ROM OS Version: 7.x Nougat

ROM Kernel: Linux 3.4.x

Based On: Aosp

Version Information

Status: Stable

Current Stable Version: 1.0

Stable Release Date: 2018-07-14

Created 2018-07-14

Last Updated 2018-07-14
[BLISS ROMS Discussion] Dwayne Dibley:
Hello,

Just installed the latest Bliss ROM (Bliss-v10.0-Stable-bullhead-OFFICIAL-20180627-0736) onto my Nexus 5X.

Pretty sure I flashed correctly through TWRP 3.2.2 :

*Flashed ROM

*Flashed GAPPS

*Flashed ROOT (magisk 16.4)

Seems to boot without issue - everything works fine - but I just have no Bliss sub menu in settings!

Any advice would be appreciated :)
[Galaxy Grand 2 Original Android Development] Sudeep:
Who's back? We're back.​

CarbonROM is an aftermarket firmware based on the Android Open Source Project. We are dedicated to fast, stable, and feature-filled roms, honesty and communication with our users, and openness with our code. We like frequent builds, with the very latest and greatest hardware support and fixes. We strive to not only provide you with the best rom we can build, but also to give back to the Android community and our fellow developers. For us, this is about creating something we can be proud of and hope you will enjoy.

Bugs:

Offline charging

Sim 1 data dozens work

Best for gamers..

It's is a aosp-caf based rom.. Focus on performance..

PUBG WORKS GREAT IN THESE ROM

Rom link-

https://drive.google.com/file/d/1n3UvWDYIsGmBxnjhbCw6HSFfWHghhPFy/view?usp=drivesdk

Vendor link- https://drive.google.com/file/d/1k08gE0yjjq24MqNL2JenIGWD4l_9-bwi/view?usp=drivesdk

XDA:DevDB Information

Carbon rom , ROM for the Samsung Galaxy Grand 2

Contributors

Sudeep, CREDITS AND THANKS: ·sachinbansal and prime 99 for supporting me everytime •carbon team •grand 2 telegram group( https://t.me/galaxygrand2) •Hash(for his tree, kernel, and vendor) •Adityaupreti for his huge contribution in g2

ROM OS Version: 7.x Nougat

ROM Kernel: Linux 3.4.x

Based On: Aosp

Version Information

Status: Stable

Current Stable Version: 1.0

Stable Release Date: 2018-07-14

Created 2018-07-14

Last Updated 2018-07-14
[8525, TyTN, MDA Vario II, JasJam Accessories] CocheseUGA:
Anyone taken one of the desk docks out there and made it work in a car?

I'd like to be able to get in my car and dock my Zune and my 8525, without having to search for the plugs, or any of that nonsense. And I don't want some Pep Boys universal vent mount, either.

Just looking for some ideas, maybe I might build one.