yashsingh1/xdaforums huggingface dataset:
[8125, K-JAM, P4300, MDA Vario General] heyitsaj:
I had the same problem with my 2 gig corsair... What i did for mine to work for me is I deleted everything on the card than instead of just puting files on the card i made folders(my music, my videos, programs)... Sounds crazy but i haven't had problems ever since.
[8125, K-JAM, P4300, MDA Vario General] shkaff:
go http://www.eggheadcafe.com/software/aspnet/28840468/wmp11-and-windows-mobile.aspx and you'll be satisfied.

It works for me and I am quite sure it will work for all of you.

THT, Alexey
[8125, K-JAM, P4300, MDA Vario General] lala2u:
OMG! Thank you so very much Leblan. This worked for me too. I had to delete my music folder, so I lost all my sync music. But who cares, now wmp is reading my storage card again!

thank you
[8125, K-JAM, P4300, MDA Vario General] blu97ram:
I have an 8525 that did the same thing. Here is what worked for me.

Remove the Micro-SD card. Open Media player and click on menu. Then click on Library. Click on menu again and select the "update Library". Let it run and find the updates. After it completes close Media Player and insert the SD card in the slot. Now open Media player again and click on Menu. Click on Library, click on menu again, click on "Update Library" and let it run. It should see the card files and add them to the library. After it completes open the menu again open the library and look for the Storage card. It should now show up with all of your songs. (mine has 346 songs and it found them all).
[8125, K-JAM, P4300, MDA Vario General] lex dalebout:
how to fix this problem.

On the storage card, delete the following file Storage Card\MSMETADATA\XMEMediaLibrary.mlb You may have to tap & hold in the File Manager window on a blank area and choose "Show All Files" in order to see this folder. If this XMEMedialibrary.mlb isnt in that folder, just delete the whole folder, that worked for me. Also delete the file: Mobile Device\Application Data\Microsoft\Media Player\XMEMediaLibrary.mlb
[Nexus 7 (2013) Q&A] Hero746:
What is the best way to create a Nandroid back up? I'm currently using Online Nandroid Backup and have TWRP installed.

What would happen if I kept my Nandroid back up on my computer/an external hard drive? Is there a way to transfer it to my tablet when it's in recovery? Should I keep a back up on my internal storage just in case?

I'm planning to flash the Franco kernel and I hear that Nandroid doesn't back up kernels. How do I back up my stock kernel?

Since I'm new to creating Nandroid back ups, what exactly should I back up?
[Nexus 7 (2013) Q&A] Aerowinder:
Always keep at least one nandroid on your device.

Kernel is labelled as "boot" in TWRP backup list.
[HTC Desire S] asm0diel:
Hey guys!

I'm quite sure I have bricked my phone. It's a HTC Desire S.

It has HBOOT-2-00.0002 installed, along with 4ext.

In an attempt to root the phone and to install a new ROM, I followed all the steps of http://xdaforums.com/showthread.php?t=1525100 yet in the last one ( flash boot boot.img ) I think I have chosen the wrong boot.img file thus flashing the boot sector of the phone with something weird.

The phone shows the HTC logo, then shows a black screen. The screen is lit.

When I try to access the bootloader ( volume down + power ), nothing happens, only sometimes a blue (or pink) screen (empty) appears.

Is there anything I could do?

Please help.
[HTC Desire S] paulie-uk:
boot.img is the kernel and is loaded after hboot, so you should still be able to boot into the bootloader and re-flash over it.

Are you sure that you flashed

to

boot and not a different partition by mistake? Keep trying to enter the bootloader; remove battery, wait a few seconds, put battery back in, hold volume down, press power, release power, wait.... release volume down when something happens.
[Other Tools & General Discussion] kl3:
Hey,

since I'm flashing nightlies on a regular basis and also want to use my own custom /system/build.prop file, there are a few ways to accomplish both things as easy as possible:

Backing up /system/build.prop through a script in /system/addon.d

Flashing my own file using a zip after every update

Restoring previous build.prop using a Editor app and reboot

Manually change or add every desired entry and reboot

For most of you one of these ways should absolutely do the trick, but my problem was either things like build version, date, etc. got stuck at my custom file's one or I had to reboot after manually updating it, which got really annoying after several times.

So I decided to create my own flashable zip which works as follows:

Somewhere on the device is a simple text file in which are all those entries that shall be changed,added to or removed from /system/build.prop (In my case it's /sdcard/tweak.prop)

After mounting /system and /data (not if they are already) and setting write permissions to /system/build.prop the zip extracts a shell script to /tmp/tweakprop.sh

It This script scans the text file (aborts if not found) and looks for changed, new or unwanted entries in /system/build.prop in order to apply them. Changed entries will be overridden, new ones will be added, unwanted get removed and entries existing in /system/build.prop but not in your personal file will be ignored

When tweaking is done, it just removes /tmp/tweakprop.sh and unmounts /system and /data (only if they weren't mounted before) and reverts /system/build.prop's permissions to rw-r--r--

-> (See content of example.txt for more detailed examples and syntax!)

Using this method, you can not only forget about manually updating versions and/or lame reboots after updates for changes to take effect, but also edit your personal text file at any time without root rights beeing required. Once set up to be flashed after every update, your /system/build.prop is always tweaked as you wish and looks like a stock one (ROM version, etc. under About Phone).

The zip flashes well on all recoveries. Make sure your tweak.prop file ends with an empty line, otherwise the last line will be ignored!

I hope some of you can use this zip, it's free to modify. If you have any suggestions, let me know.

This project has been moved to a git repo at https://notabug.org/kl3/tweakprop. Please refer to it in the future to get updates as this is much easier for me to maintain. Upcoming changelog can be found here.
[Other Tools & General Discussion] kl3:
Changelog

Changelog
[Other Tools & General Discussion] TheEdgeOfRage:
Such Awesome, much appreciate :D i wanted to make one too, but never got the time to.
[Other Tools & General Discussion] jonwgee:
What should my text file look like if I just want to add one line of text at the end of my build.prop? For example,

qemu.hw.mainkeys=0

to activate softkeys on a device with capacitive buttons?

Thanks
[Other Tools & General Discussion] the_pirate_predator:
Need some information

I need explanation for the following lines of code.

## your personal file with tweaks and custom entries/values
tweak=/sdcard/0/tweak.prop
## abort execution if $tweaks not found
if [ ! -e $tweaks ]
then
ui_print "ERROR: Personal file not found. No changes were made."
ui_print "Script aborted. Check file path and flash again."
exit 0
fi

## read only lines matching any valid entry pattern (someVAR=someVAL), e.g.
## net.bt.name=Android, omni.device=n7100, url.legal=http://www ...
sed '/.*=.*/!d' $tweak > /tmp/tweak.prop
tweaks=/tmp/tweak.prop

You are giving a condition loop without even declaring the variable "tweaks" at first. You have declared only after the loop ends. Then that means, the code in the loop never executes. I think this is a small mistake you did with the code. Make sure you correct those.

But else, a great work!! :good: :good:
[Other Tools & General Discussion] thewisenerd:
Sorry, but stick to one variable, "tweak", or "tweaks".

Otherwise, its a very simple, yet efficient algorithm. :good:
[Other Tools & General Discussion] kl3:
Just a simple text file containing your mentioned line. Any other empty or non-entry lines will be ignored by my script anyway.

You're right. It's a typo, I'm correcting it now. Thanks for your advice.

I use a second buffer file that is a cleaned version of the original one. If I find a smarter way, I will.
[Other Tools & General Discussion] oguh:
I was searching for something like this for ages.

But i have a nob question! lol

I need to create a text file with all the lines i want to add to my built.prop file, so where I put the text file? And i have to give a certain name to that file or any name will do?

Hugo
[Other Tools & General Discussion] kl3:
My script searches for a file called tweak.prop located at your internal storage (storage/emulated/0/tweak.prop or sdcard/tweak.prop or sdcard/0/tweak.prop), but you can freely change the line

tweak=/sdcard/0/tweak.prop

to any path you want your personal file to be.
[Other Tools & General Discussion] oguh:
Thx for the quick response, and for your great work.

hugo
[Other Tools & General Discussion] bnbagiz:
Sorry but i don't get it.

i need to create a txt file called tweak.prop and place it where i want, for example /sdcard/tweak.prop

after extracting the tweakprop-0.3.zip for editing the line /tmp/tweakprop.sh

## your personal file with tweaks and custom entries/values
tweak=/sdcard/tweak.prop

zipping meta-inf and tmp folder and finally flashing this zip.. am i doing something wrong ?

because it takes no changes.

got this line in tweak.prop at /sdcard/tweak.prop

ro.sf.lcd_density=400

sorry, i really dont get it.
[Other Tools & General Discussion] kl3:
As my script already shows, changing the path to /sdcard/0/tweak.prop again should do the trick.
[Other Tools & General Discussion] sauron82:
I just want to change my DPI with this. What do I need to change in your default tweak.prop to be able to do that?

Click thanks if I helped you.
[Other Tools & General Discussion] bnbagiz:
did not work ! :/ you mean changing the path for the tweak.prop in the unzipped tweakprop.sh in /tmp/, aren't you ?

build=/system/build.prop
## your personal file with tweaks and custom entries/values
tweak=/sdcard/0/tweak.prop

---------- Post added at 02:41 PM ---------- Previous post was at 02:34 PM ----------

that is what i am trying to do

you need to change the line

ro.sf.lcd_density="value you like to have, i.e. 400"
[Other Tools & General Discussion] kl3:
Yes, that's what I meant. Then just try any other path. I guess the internal storage's path is a device specific thing. Which device do you? I would try locating your personal file at /system as this path exists on all devices/ROMs.
[Other Tools & General Discussion] bnbagiz:
I am using a LG G2 Intern. D802

PAC-Man ROM (but thing thats irrelevant)

so if i place my tweak.prop in /system/ i need to edit the path in tweakprop.sh right ?

edit:

personal file is in /system/tweak.prop

editting tweakprop.sh line to

/system/tweak.prop

does not work :( don't get it .. sounds so simple, actually it is, but i don't know what i am doing wrong :(
[Other Tools & General Discussion] sauron82:
I know that, but where do I put it in the provided tweak.prop? What do I remove from the provided tweak.prop so that's the only change? I really don't know what any of this code actually means. Thanks to the OP for providing this, but instructions aren't very clear.

Click thanks if I helped you.
[Other Tools & General Discussion] ottomanhero:
You're my hero.So tired of changing build.prop values every time I try a different ROM. :good:
[Other Tools & General Discussion] kl3:
Hm.. Which recovery? Maybe it's a problem with the updater-script doesn't get executed correctly. Sadly, I have no possibilities to test those scenarios.

I didn't provide any personal file. If you only want to change this line, create a file called tweak.prop containing only this line and place it right on your internal storage.
[Other Tools & General Discussion] my95z34:
If you put it in /system/ it'll get erased when you flash a new nightly anyways, as most .zip scripts wipe the /system partition... So... it would be best to keep it on the SD card.
[Other Tools & General Discussion] Lownita:
I want to achieve the following two tasks by flashing a .zip file in recovery:

1. Open the following file:

/system/etc/permissions/handheld_core_hardware.xml​

Add in the following lines right before the </permissions> closing tag at the end:

<feature name="android.software.vr.mode" />
<feature name="android.hardware.vr.high_performance" />

2. Open

/system/build.prop

Add this line:

ro.product.device=sailfish

So how can I do it? :)
[Other Tools & General Discussion] KrisM22:
Before doing this, backup your ROM in TWRP, since if anything goes wrong you won't be able to boot your ROM, and you'll have to boot to TWRP and restore that nandroid.

LineageOS ROM 5-18-2017, opengapps nano 5-18. Magisk(hide)

This is the result of many tests:

Huge thanks for this.

I made a tweak.prop and put copies on both internal storage and SDcard.

I flashed 5._MOD_build_prop.zip which was in a separate folder with nothing else, in internal storage.

I had to put a carriage return(enter) after BACKUP=n as well as the extra one at the end.

It puts the mod at the end of /system/build.prop

This is my tweak.prop

BACKUP=n

ro.build.fingerprint=motorola/osprey_retus_2gb/osprey_u2:6.0/MPI24.65-25/28:user/release-keys

remember to put an

EXTRA

line feed/carriage return after BACKUP=n, and at the end.

WORKED!

THANKS!
[Other Tools & General Discussion] KrisM22:
bad post.
[Other Tools & General Discussion] jerethi:
So... I know this is totally exactly what I have been looking for, as I have been flashing nightly builds of AICP for my 5X. However, I have absolutely no idea how to get this up and running. I understand this is a total noob question, but can someone take me through step by step how I would set this up?
[Other Tools & General Discussion] m0han:
i see you're using tweakprop

v0.5.9

zip file. please share the zip file here. thanks.
[Other Tools & General Discussion] HTalaia:
Help :)

Hi,

I was searching for a solution for a Vodafone Tablet that i have (known as Vodafone Tab Prime 7, or VDF 1400). I've been looking for a solution for a long time and i found that this one is very difficult to root or to change the recovery because it's very well locked by vodafone (and vodafone is no longer supporting this tablet).

This tablet is stuck on Android 6.0.1 (it's old, i know, but for the usage it is ok) and i would like to change the build.prop in order to change to userdebug to activate the multiwindow feature.

I have tried the zip file to change the build.prop but when i try to apply the zip on the recovery (stock) it returns the error "E: footer is wrong and E: signature verification failed".

Can anyone help me, please?

I am a noob in this subjects and i need help to solve this
[Other Tools & General Discussion] christian.arvin:
Its not meant to be flashed using the stock recovery.

You need a custom recovery to use this script, like TWRP.

Judging by your story, you wont be able to use it.
[Other Tools & General Discussion] HTalaia:
Thank you for your help.

Well, the next step is trying to install a custom recovery... but seams that it won't be possible... I will keep looking and trying to find solutions.

Thank you once again
[Other Tools & General Discussion] DumiJ58:
Can I add entries to /vendor/build.prop ?

And how can I do it, (what do I have to change in tweakprop.sh)
[Other Tools & General Discussion] christian.arvin:
You can, you need to modify OP's codes

Find the line pointing to

build=/system/build.prop

Change it to

build=/system/vendor/build.prop

Or

build=/vendor/build.prop
[Other Tools & General Discussion] DumiJ58:
Thanks, for the response...

It worked...:good:
[Other Tools & General Discussion] TraderJack:
Should this work on a Pixel 3 XL?

I'm running twrp but am unable to get this (or any other build.prop flashable I've tried) to work.

I don't get any errors, and in my various tests I'm pretty sure that the file is getting copied and executed, but my build.prop never gets modified.

I think there might be some issue with it mounting the partition to access the file, but I don't get any errors and not sure how to troubleshoot.

Also, no backup is created - yet another reason I think it can't even access the file.

I'm using the "a" version so my tweap.prop is inside the zip.
[Other Tools & General Discussion] Miustone:
I think this isn't working since system-as-root (or Treble) is a thing. Is anyone aware how we can mount the newer Android Systems the right way? My actual Script looks like that:

#!/sbin/sh
set -e

VER=V21

OUTFD=$2
ui_print() {
echo -n -e "ui_print $1\n" > /proc/self/fd/$OUTFD
echo -n -e "ui_print\n" > /proc/self/fd/$OUTFD
}

ui_print "M.A.R.S. PROP $VER"

ex() {
chmod 0644 "$build"
ui_print "-ERROR: $@, SCRIPT ABORTED"
exit 1
}

build=/system/build.prop
echo "" >> "$build"
name=mars.prop

for part in system data
do
ui_print "-MOUNTING /$part"
if mount | grep -q "/$part"
then
mount -o rw,remount "/$part" "/$part" && ui_print "-REMOUNTING /$part RW" || ex "-CAN'T WRITE ON /$part"
else
mount -o rw "/$part" && ui_print "-/$part MOUNTED RW" || ex "-CAN'T MOUNT /$part"
fi
done

ui_print "-SETTING PERMISSIONS FOR $build"
chmod 0666 "$build"

ui_print "-INJECTING PROP FILE"
prop=$(find /sdcard* /storage* /ext* /tmp* -name $name -type f -follow 2>/dev/null | sed 1q)

test -s "$prop" && ui_print "-$prop FOUND WITH CONTENT" || ex "-CUSTOM FILE $name NOT FOUND OR EMPTY"

answer=$(sed "s/BACKUP=//p;d" "$prop")

backup() {
echo "# BACKUP OF $build CREATED AT `date` MARS PROP PATCHER $ver" > "$1" || ex "-CAN'T WRITE BACKUP FILE $1" && \
(cat "$build" >> "$1" && ui_print "-$build BACKED UP AT $1.")
}

case "$answer" in
y|Y|yes|Yes|YES)
backup "${prop%/*}/${build##*/}.backup"
;;

n|N|no|No|NO)
;;

*)
[[ -z "$answer" || ! -d $(dirname "$answer") ]] && ex "Given path is empty or parent directory does not exist" || backup "$answer"
;;
esac

ui_print "-READING $prop"

sed -r '/(^#|^ *$|^BACKUP=)/d;/(.*=.*|^\!|^\@.*\|.*|^\$.*\|.*)/!d' "$prop" | while read line
do
if echo "$line" | grep -q '^\!'
then
entry=$(echo "${line#?}" | sed -e 's/[\/&]/\\&/g')
grep -q "$entry" "$build" && (sed "/$entry/d" -i "$build" && ui_print "-ALL LINES CONTAINING \"$entry\" REMOVED")

elif echo "$line" | grep -q '^\@'
then
entry=$(echo "${line#?}" | sed -e 's/[\/&]/\\&/g')
var=$(echo "$entry" | cut -d\| -f1)
app=$(echo "$entry" | cut -d\| -f2)
grep -q "$var" "$build" && (sed "s/^$var=.*$/&$app/" -i "$build" && ui_print "-\"$app\" APPENDED TO VALUE OF \"$var\"")

elif echo "$line" | grep -q '^\$'
then
entry=$(echo "${line#?}" | sed -e 's/[\/&]/\\&/g')
var=$(echo "$entry" | cut -d\| -f1)
new=$(echo "$entry" | cut -d\| -f2)
grep -q "$var=" "$build" && (sed "s/^$var=.*$/$var=$new/" -i "$build" && ui_print "-VALUE \"$var\" CHANGED TO \"$new\"")

else
var=$(echo "$line" | cut -d= -f1)
if grep -q "$var" "$build"
then
grep -q $(grep "$var" "$prop") "$build" || (sed "s/^$var=.*$/$line/" -i "$build" && ui_print "-VALUE \"$var\" OVERRIDDEN")
else
echo "$line" >> "$build" && ui_print "-ENTRY \"$line\" ADDED"
fi
fi
done

sed '/^ *$/d' -i "$build"

ui_print "-CLEANING"

chmod 0644 "$build" && ui_print "-ORIGINAL PERMISSION FOR $build RESTORED"

for part in system data
do
umount "/$part" && ui_print "-/$part UNMOUNTED"
done

ui_print "-DONE"

Thanks in advance for any Help with that!
[Other Tools & General Discussion] kl3:
Well, how dumb I was not to think of this - thanks for the hint :D
[Other Tools & General Discussion] my95z34:
No problem. =]
[Other Tools & General Discussion] Anisrael:
Worked Perfectly

I modified the sdcard/0/tweak.prop to say sdcard/tweak.prop and it worked perfectly for me on my HTC One. Thank you very much OP for such a useful script.
[Other Tools & General Discussion] Dude360:
Hi k,

I remember this was something me and Patrics were playing around with for ROMCleaner before life got in the way :(

Good work, I love little scripts like this and will be sure to play around with it on my next flash.

I have some suggestions if thats ok?

Does the answer file have to have the .prop extension?

We found it was a lot easier for users to use a standard .txt file rather than 'fiddle' with a different extension.

I know it sounds like a little thing but you'll be surprised at how many dont...

Can you make the script ignore anything in the file answer file preceded with a #?

If so you can make a sample file for complete novice users to use and also have the ability to quickly enable/disable edits.

Something like:

# !!!ALWAYS USE NOTEPAD++ WHEN EDITING THIS FILE!!!
#
# ===============================================
# | |
# | Dynamic build.prop Editor |
# | by |
# | klenamenis |
# | |
# ===============================================
#
# For help and support, please visit my thread:
#
#	http://xdaforums.com/showthread.php?t=2664332
#
# !!!ALWAYS USE NOTEPAD++ WHEN EDITING THIS FILE!!!
#
#
#==========================================================================================================================
#
#	Add your custom build.prop entries to this file to have them automatically
#	applied to your current build.prop when flashing a new ROM.
#
#	After flashing your ROM flash the tweakprop.zip and edits will be applied.
#
#	Eg:
#
#	To enable an edit:
#
#	ro.sf.lcd_density="400"
#
#	To disable an edit, precede the line with a hash symbol (#):
#
#	#ro.sf.lcd_density="400"
#
#==========================================================================================================================
#
#	!!! EDITS GO BELOW !!!
#
#==========================================================================================================================

You could also go more adanced and make the .sh dynamic by having some asserts in the updater-script look for the answer file in predefined locations etc

You can do a lot with scripts like these, just which I had more knowledge of nix scripting :(
[Other Tools & General Discussion] kl3:
Thanks for your tips!

Everyone can freely choose it's personal file name and path inside my script, the .prop extension is nothing but my own preference. Honestly, if users have to "fiddle" when (re)naming their personal files, they should really overthink what they're doing with my script.

Ignoring every comment line is no problem, I'll add this later. Did you know that my script only handles those lines matching the pattern

variable

=

value

? I wanted to strengthen the conditions for a personal file's line being a valid build.prop entry anyway, so thanks for the hint.

If users request an example tweak.prop, they'll get it - just hang on a minute! But I highly recommend to read some other threads or wiki pages about some build.prop stuff, my example will be no tutorial!
[Other Tools & General Discussion] Dude360:
Thats wicked, I stuck mine all nice and tidy named as BUILDPROPCleaner.txt in with my ROMCleaner stuff :)

Thats great. I can read some of the scripting to get the gist of it but dont know enough to follow it all.

Hehe there is no rush from me :) I do love scripts like this combined with edify and queuing systems in recoveries. They make the flashing process SO much faster! I remember when I went through a phase of nightlies and having to edit stuff left and right to get it how I wanted it.

Scripts like these are also a good way of learning by seeing what and how they do things without having to dredge through mountains of code :)

As for a tutorial...just dont lol The simplest thing can turn into pages of explanations (I know it well) lol

Keep it up mate, another awesome tool to add to my kit :)
[Other Tools & General Discussion] kl3:
Version 0.4, fixing the problem with internal storage's path, just got uploaded. For example, you can now easily put your file at /sdcard/some/folder/tweak.prop, flash my zip, move the file to /sdcard/tweak.prop and flash again without modifying the zip!

Have fun and please report your (non)working constellations of device, recovery and ROM so I can fix those having any issues.

Don't forget to subscribe this thread so you won't miss an update.
[Other Tools & General Discussion] oguh:
I still can't make this to work.

I'm on omnirom with TWRP recovery and my device is S3.

I create a tweak.prop file with only one line:

qemu.hw.mainkeys=0