Database Develop

[FIX] For 2.2 Market issues, use this mod - *Updated* with Stock Build.prop

For those of you having trouble seeing protected apps, I modified our fingerprint in the build.prop. What this does is spoofs the market into thinking its seeing a Droid 2 (with Froyo) It worked for me, let me know if it does for you.
1. Put build.prop into your AndroidSDK\TOOLS folder
2. Connect via USB.
3. CD (Navigate) in CMD to your tools folder
Mount your /system (adb remount) works for me
Copy and paste this
4. adb remount
5. adb push build.prop /system/build.prop
6. adb reboot
To test if you need this before you push the build.prop fix, search the market for Us Bank. If only 2 or 3 show up, you are not getting the full market. After this fix, you should see 10 items listed when you search for Us Bank.
Hope this helps.
2.2 Market Fix Build.Prop -- WITH STAGEFRIGHT=TRUE
This can also be done via Root Explorer.
Edit: Here is a "clean" build.prop for those of you who do not want the stagefright fix (which breaks video playback) Sorry, I was not aware it did that. Thank you.
Non Stagefright Build.prop -- WITH STAGEFRIGHT=FALSE
For everyone flipping out about Birdmans tweet and you want the stock build.prop, here ya go
Stock Build.prop -- WITH NOTHING! STOCK!
You only need the stock one if you ever plan on doing a factory reset. But, you also cant do a factory reset if you have removed or renamed apps so I feel that should be mentioned. If you've done any modding and you are planning on upgrading, your best bet is to always use the SBF anyway. I dont think birdman realizes the panic he sets in with one little tweet. Factory resets suck anyway. But then again... "you decide..."
Thanks to Jcase for giving me the original idea way back when. I just basically applied his Eris Market Fix to work with our phones.

This created several problems for me.
First, the build.prop file is a read-only system file and doing a push did not work for me.
I had to copy it to my sdcard and then in shell:
su
mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
cp /sdcard/build.prop /system/build.prop
mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
reboot
This created some really fubar'd effects on my network as I couldn't access the market from 3g. It more or less disabled my 3g network.
When I activated wi-fi, it worked fine, and did let me into the market.
I'm trying to put my original build.prop file back on, but I still have no 3g connectivity.
Update:
restored my build.prop and still no go.
update2:
tried clearing the 'cache' from reboot mode and even did a factory reset ... still no go.
I'm starting over with SBF, update, FROYO, etc.
I don't know for certain that this file hosed me, but I had not yet done any other system file issues. Either way, I would not recommend you follow my above instructions

Found a fix
I must say I take no responsibility if this causes problems but this worked for me. Do a search in the market for "Eris Market Fix." It was designed for the Eris but works just fine on my Droid X. I can see all the apps that didn't show up before. I haven't noticed any issues since applying this fix. You must be rooted for this to work, but I assume most everyone on Froyo already is rooted.

Zaphod-Beeblebrox said:
This created several problems for me.
First, the build.prop file is a read-only system file and doing a push did not work for me.
I had to copy it to my sdcard and then in shell:
su
mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
cp /sdcard/build.prop /system/build.prop
mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
reboot
This created some really fubar'd effects on my network as I couldn't access the market from 3g. It more or less disabled my 3g network.
When I activated wi-fi, it worked fine, and did let me into the market.
I'm trying to put my original build.prop file back on, but I still have no 3g connectivity.
Update:
restored my build.prop and still no go.
update2:
tried clearing the 'cache' from reboot mode and even did a factory reset ... still no go.
I'm starting over with SBF, update, FROYO, etc.
I don't know for certain that this file hosed me, but I had not yet done any other system file issues. Either way, I would not recommend you follow my above instructions
Click to expand...
Click to collapse
Firstly, I figured ppl would know how to use adb.
if you cant push the file, use "adb remount" and it will work.
Secondly,
Hmm... Sorry to hear that but I HIGHLY doubt it was the build.prop that did this.
I posted over at another thread, and it worked for everyone.
Check it.
http://www.droidxforums.com/forum/droid-x-hacks/4318-2-2-market-issues-use-mod.html

elkniwcire said:
i must say i take no responsibility if this causes problems but this worked for me. Do a search in the market for "eris market fix." it was designed for the eris but works just fine on my droid x. I can see all the apps that didn't show up before. I haven't noticed any issues since applying this fix. You must be rooted for this to work, but i assume most everyone on froyo already is rooted.
Click to expand...
Click to collapse
yes this worked for me aswell thank you

Yes this method definitely works. I have market working now and can search for protected apps etc.

elkniwcire said:
I must say I take no responsibility if this causes problems but this worked for me. Do a search in the market for "Eris Market Fix." It was designed for the Eris but works just fine on my Droid X. I can see all the apps that didn't show up before. I haven't noticed any issues since applying this fix. You must be rooted for this to work, but I assume most everyone on Froyo already is rooted.
Click to expand...
Click to collapse
I would not recommend this. I have talked to 2 people so far who said their phone have gone in to bootloops using the Eris Market Fix. After all, it is for an Eris. Read the comments on the app in market. Lots of people are using it on the wrong phone and having problems.
Do yourself a favor and just use the build.prop in this post as it has already been tested in numerous forums with no problems whatsoever, if done correctly.

he was just explaining where the idea comes from i think... You'd have to be crazy to use the eris market fix app on a droidx, just simply edit the build.prop fingerprint line.

I just used the root explorer meathod and now it wont boot.
I downloaded the file.
renamed my build.prob to build.prob/bak
placed the new build.prob in the system folder
rebooted and now after the M screen it just goes to a black screen with the backlight lit. Wont boot up. Im learning adb so this may be a noob question but can I access adb if the phone wont boot all the way up. That way I could change the build.prob back
Edit Delete Post: Im just retarted haha .prop not .prob :/

Could you plz give us some details on doing this with root explorer. Thanks
Prolly simple but I did try moving current build file then renaming and pasting yours without success doing us bank search. Also rebooted cleared cache and market history prior to search. Appreciate any help with doing this via root explorer.

LexusBrian400 said:
Firstly, I figured ppl would know how to use adb.
if you cant push the file, use "adb remount" and it will work.
Secondly,
Hmm... Sorry to hear that but I HIGHLY doubt it was the build.prop that did this.
I posted over at another thread, and it worked for everyone.
Check it.
http://www.droidxforums.com/forum/droid-x-hacks/4318-2-2-market-issues-use-mod.html
Click to expand...
Click to collapse
LexusBrian400 said:
I would not recommend this. I have talked to 2 people so far who said their phone have gone in to bootloops using the Eris Market Fix. After all, it is for an Eris. Read the comments on the app in market. Lots of people are using it on the wrong phone and having problems.
Do yourself a favor and just use the build.prop in this post as it has already been tested in numerous forums with no problems whatsoever, if done correctly.
Click to expand...
Click to collapse
I took a brief look at each file and I really don't understand how I got into trouble. As I said, I had not yet started doing any mods, just trying to install a few apps.
While I'm no computer or phone neophyte, I don't profess to be up to speed on Android yet. I do typically read through instructions pretty well, and search out multiple sources/explanations so I have a better 'understanding' of what I'm doing, rather than just "parrotting" the steps.
Having said that, I would like to know the difference between using 'adb remount' and the instructions I used in my first post. Is that just the difference in doing this via a shell command and not? ie, they perform the same action, just from a different starting point?
As for the Eris file, I did download that and all seems to be OK right now.

Sorry ahead of time for a possibly stupid question but I just wanted to be sure. Do you have to be rooted to do this fix?

Yes, it requires an edit to a file that you can only be edited when rooted

elkniwcire said:
I must say I take no responsibility if this causes problems but this worked for me. Do a search in the market for "Eris Market Fix." It was designed for the Eris but works just fine on my Droid X. I can see all the apps that didn't show up before. I haven't noticed any issues since applying this fix. You must be rooted for this to work, but I assume most everyone on Froyo already is rooted.
Click to expand...
Click to collapse
This works for me...thanks!

OP has been updated with original build.prop

Silly question but is the Non Stagefright file edit like the first one so the Market is fixed if you use either of the first 2 posted files. I realize the last file is just the stock build.prop but am a little confused on wah tis in the first 2 files. Obviously the first fixes the Market issue, so I guess I'm more question wha tis in the non stagefright file. TIA for any help/input

will2live said:
Silly question but is the Non Stagefright file edit like the first one so the Market is fixed if you use either of the first 2 posted files. I realize the last file is just the stock build.prop but am a little confused on wah tis in the first 2 files. Obviously the first fixes the Market issue, so I guess I'm more question wha tis in the non stagefright file. TIA for any help/input
Click to expand...
Click to collapse
Just use the non-stagefright one.
Just like the post says, stagefright breaks HD video playback for SOME people. However some people dont care and just want higher quadrant scores, so they use the stagefright=true build.prop
Use the =false version for better stability.

Thanks for the reply.

[Q] Reviewing Android Security - MUST be root?

So as a little side project I've tasked myself to review the security features and potential risks to data being stored within the Android OS and I've been using my Captivate as the test rat. Since pretty much everyone with an android device uses Gmail I wanted to focus first on the Gmail app. I know that information for many apps are stored under the /data/data/[app package]/databases directory structure in an SQL Lite *.db file.
That being said, I wanted to inquire with everyone here about being able to access the /data/data directory and all info there-in WITHOUT having to root the device. Im sure there might be some on that but Im just trying to be thorough in my review...any potential thief would obviously just instantly root and delve right in afterward the data but what other potential ways are there to get into that directory, if there are any?
I've been playing around with ADB and from what I can tell that is not a viable path. The only thing I could think of is somehow tricking the ADB daemon into thinking my phone is a development phone which would allow ADB to run as root but haven't found that to be possible.
So in any case, just looking for insight from the more experienced folk as to other avenues of attack against the user data beyond the obvious root method. Thanks very much for any help!

You can run adb shell as root if the phone is in clockworkmod recovery - but if someones going to the trouble of dropping a clockwork update.zip could just as well and as easy drop a root update.zip on the phone.
If someone physically gets a hold of your phone anything tied the google account/s on the phone would have to be considered compromised - as these phones are so easy to root anyway.

I just thought of another thing, if someone were to get a hold of your phone and have access to a computer with odin they could pretty quickly do a system dump (grab every file off your phone) return where you could find it without you ever knowing they got it.

dayv said:
I just thought of another thing, if someone were to get a hold of your phone and have access to a computer with odin they could pretty quickly do a system dump (grab every file off your phone) return where you could find it without you ever knowing they got it.
Click to expand...
Click to collapse
you dont need odin. adb will do it too

Pirateghost said:
you dont need odin. adb will do it too
Click to expand...
Click to collapse
Can you do a system dump in adb without root?

dayv said:
Can you do a system dump in adb without root?
Click to expand...
Click to collapse
yes
adb pull /system

Pirateghost said:
yes
adb pull /system
Click to expand...
Click to collapse
Learn new things every day.
I like this phone allot, but there just is no way to secure it against someone physically gets their hands on it.

Pirateghost said:
yes
adb pull /system
Click to expand...
Click to collapse
Yep thats actually very easy to do however it doesn't contain any critical private data really. I looked through the directories and while there is some interesting information that can be gleaned (e.g. the generic APN configs and other hardware information) there isn't any actual private stuff such as Gmail data, authentication info for apps, etc. That is all contained within the /data/data directory from what I understand.
You CAN get a list of all the packages on the device through /SYSTEM as well as all the APK's of the installed apps but otherwise not much I've found to be worrisome.
I'll have to check out Odin and see what that can offer from a non-root perspective.

Pirateghost said:
yes
adb pull /system
Click to expand...
Click to collapse
But, that is why you don't leave USB debug on all the time - and why there is a warning when you do turn it on.
PIN or pattern lock keep prying eyes out, and protect your phone from ADB, but not if you leave USB debug on. But, like other hardware, if someone has physical access and enough time, they can get to your data.

So now that Im rooted, is there an easy way to write up a script to copy all files in the /data/data and whatever other folders I decide onto my PC?

The potential joys of Nvflash (Dead in the water?)

Interestingly enough (I don't know the reasons), it looks like Motorola left a copy of Nvflash and Atrix-specific bootloader.bin for it on the Atrix. What's interesting about Nvflash is that it allows for targeted backup and restore of partitions (i.e. something along the lines of what Nandroid allows for, except at a lower level), which decreases recovery time when developers do something that ends up soft-bricking their phone. It should also break us free of our dependence on SBFs because we'll be able to create our own backups.
Anyways, the Nvflash on the phone is the Linux i386 binary. The bootloader.bin isn't platform specific, as it's meant for the target, rather than the host. THe archive is available in /usr/local/share/motorola/fireboxmake/OSH_tools.tgz.
Unfortunately, this is where we get stuck, because we don't currently know how to get a connection to the phone. And that's where all of you come in! Can you get further? I've gotten this far:
Code:
Nvflash started
rcm version 0X4
Command send failed (usb write failed)
I imagine that some of the functionality may end up requiring the --sbk flag (and we don't know the SBK right now), but I'm hoping that we can at least backup and restore /system, /data, and /osh.
Update: Information I've obtained indicates that this is the error you get when the SBK you pass in doesn't match the SBK on the system. So, no luck until we get that SBK.
Update 2: Additional links from dasmoover:
Tegra crypto engine source snapshot
/osh/usr/local/share/motorola/fireboxmake
Credit to dasmoover for the find.

Correct me if I'm wrong but isn't this the same thing as which apparently folks are trying to get taken down in the name of keeping the info under wraps?

I would like to excuse myself for earlier. I am glad that you have turned this in to something positive.
Sent from my MB860 using XDA Premium App

JdeFalconr said:
Correct me if I'm wrong but isn't this the same thing as some other thread, which apparently folks are trying to get taken down in the name of keeping the info under wraps?
Click to expand...
Click to collapse
It's related, but it's not quite the same thing. If nothing else, you have the binaries for this right now on your phone (dasmoover posted a link on the IRC channel 12 hours ago or so). I'm at this mostly for the backup/restore capabilities of Nvflash rather than bootloader hacking. Even if we only ever had that much, I'd be thrilled, because I hate having to re-SBF and set everything up again every time I soft brick my phone.
Also: I've been planning on posting this for a few hours now, before that other post even went up. I'm... disappointed to see that other post, but these two things aren't after the same thing.

http://gititbit.ch/fbm1 - /osh/usr/local/share/motorola/fireboxmake
also contains OSH_tools.tgz.
Firebox is the development name for the Webtop system. This contains the tools to prep the partition image for flashing. There are also some files IDA generated.
May be of use: http://gititbit.ch/tces1 - Tegra Crypto Engine Source Snapshot

do you mind me asking but.. what was that other thread about that it warranted getting deleted.

seven2099 said:
do you mind me asking but.. what was that other thread about that it warranted getting deleted.
Click to expand...
Click to collapse
it got deleted for a reason - let it be

I think we are getting warmer now .......... this calls for some investigation.

minooch said:
it got deleted for a reason - let it be
Click to expand...
Click to collapse
Wow he was just asking a questing...If you feel that even just telling him/us what the thread was about is so bad/dangerous then i think there is a bigger problem here. This should be a place to share information, ideas and if we start cracking down on that then we lose so much (yes if it is copyrighted or under nda then take it down)

http://forum.tegratab.com/viewtopic.php?f=13&t=18
They've been using nvflash to flash their tablet.

Perhaps someone can pull their SBK right out of the phone
sys/fuse/SecureBootKey
I doubt it is of any use because once pulled from the phone it appears as 0 bytes.
Looking at it from the phone shows nothing.
my guess is, as the path describes, a fuse, once lit, makes the file blank.

I navigated to nvflash with root explorer and executived the file. All get is executing file and nothing. I figured this would be.the case. Where would this need to run? A recovery state?
Sent from my MB860 using XDA App

sifon187 said:
I navigated to nvflash with root explorer and executived the file. All get is executing file and nothing. I figured this would be.the case. Where would this need to run? A recovery state?
Click to expand...
Click to collapse
The recovery state would be similar to the RSD recovery state (set on boot by pressing Volume Down) except that there's a specific Nvflash one. But, that's the one I can't get to respond properly.

LOOK HERE
LOOK HERE
http://forum.xda-developers.com/showthread.php?p=13145274#post13145274

blackax said:
Wow he was just asking a questing...If you feel that even just telling him/us what the thread was about is so bad/dangerous then i think there is a bigger problem here. This should be a place to share information, ideas and if we start cracking down on that then we lose so much (yes if it is copyrighted or under nda then take it down)
Click to expand...
Click to collapse
there is a separate dev forum that we can't access for DEVs only that that information is being used on. it being in the open here might hurt our chances of being able to exploit anything as moto might find it and patch it before the devs have a chance to get at it.

Is the Dev forum on XDA or.somewhere else just curious
Sent From My Gibgerblurred Phone

it's on xda, but you have to be a recognized developer of xda to access it.

PAulyhoffman said:
Perhaps someone can pull their SBK right out of the phone
sys/fuse/SecureBootKey
I doubt it is of any use because once pulled from the phone it appears as 0 bytes.
Looking at it from the phone shows nothing.
my guess is, as the path describes, a fuse, once lit, makes the file blank.
Click to expand...
Click to collapse
I am a complete noob and not close to a dev but if pulling the file blanks it the why not view the file while still on the phone while using an external source or application? Again like I said noob so sorry if alreay tried
thats just my 2 cents
sent from XDA mobile

Wow give a dime at least...
Sent from my MB860 using XDA App

drock212 said:
I am a complete noob and not close to a dev but if pulling the file blanks it the why not view the file while still on the phone while using an external source or application? Again like I said noob so sorry if alreay tried
Click to expand...
Click to collapse
Ends up being the same thing. Running sudo cat on the file prints nothing. That was one of the first things tried, even before copying the file.

Unroot?

Is it possible to unroot after using the 1 Click Root? I'm coming from a rooted Droid Eris and I remember the first few people who rooted their Erises had lots of problems and I just wanna make sure we can go back and re-root if a better root process comes along later on...

magicelf said:
Is it possible to unroot after using the 1 Click Root? I'm coming from a rooted Droid Eris and I remember the first few people who rooted their Erises had lots of problems and I just wanna make sure we can go back and re-root if a better root process comes along later on...
Click to expand...
Click to collapse
Yes, but you'd have to do it manually at this point.
You'd delete busybox and su, uninstall superuser.apk, and there may be a symlink you need to undo, but I think the latest one-click cleans that up. I'd have to go back and check.
And any bloat you froze needs to be unfrozen, or bloat removed needs to be restored.

Okay, first version of this tool, be kind and let me know if there are any problems with it.
Also: NO GUARANTEES. If it does something that breaks your phone, I am not liable. Use at your own risk. Etc., etc.
http://www.psouza4.com/Droid3/PetesMotorolaRootTools_v1.03.zip
UPDATE 9/1/2011: version 1.03

I'm trying the one touch unroot and keep getting an error about the /sdcard/d3unroot folder missing files.
I extracted all of the APKs from your link to my /sdcard/d3unroot directory, but for some reason one touch unroot will not work.
The root worked great

same error here...

Get that error as well

Same here.
Why does it even need that to un-root @ that point?

I'm getting the same error.

Is it really a one-click method?
I'm a dummy so I think I'm gonna wait for some clarity.
Thanks for doing this, man!

Fully re-written and should un-root and restore /system/app for both v5.5.959 and v5.6.890. Enjoy!
http://www.psouza4.com/Droid3/PetesMotorolaRootTools_v1.03.zip
This program is for Windows only and can:
root your device (most Motorola Gingerbread devices)
unroot your device
restore your /system/app, even if you deleted files
And a bit more, such as un-freezing apps if you un-root just like Titanium Backup can.

So how do I do this. Is it the same as the one click root meaning unzip the file and put my phone into charging mode and let it do its thing
Sent from my DROID3 using XDA App

spacecasespiff said:
So how do I do this. Is it the same as the one click root meaning unzip the file and put my phone into charging mode and let it do its thing
Sent from my DROID3 using XDA App
Click to expand...
Click to collapse
Pretty much -- this is an all-in-one. It'll tell you where to download files and where to put them when you begin.

I guess I'm just retarded I can't get this to work. I give up. Looks like I'm gonna have to get VZ to mail me a new D3

Yonnor said:
I guess I'm just retarded I can't get this to work. I give up. Looks like I'm gonna have to get VZ to mail me a new D3
Click to expand...
Click to collapse
Why can't you? More than willing to help, but have to tell me what the problem is. And bear in mind that I put out a new version less than 2 hours ago that fixes a LOT (it's a full rewrite).

ok ive downloaded the file to my computer.

Keep getting the error for the Restore data not being in the right place. I've extracted the files to the right spot (I think)
is the restore folder supposed to be located in the Root Tools folder, and then all the apk's placed that Restore folder?

Yonnor said:
Keep getting the error for the Restore data not being in the right place. I've extracted the files to the right spot (I think)
is the restore folder supposed to be located in the Root Tools folder, and then all the apk's placed that Restore folder?
Click to expand...
Click to collapse
Basically, yes.
I'll use your desktop as an example, so if you have:
Desktop\New Folder\Pete's Motorola Root Tools.exe
Then you'll want to extract all the files for the /system/app fix to:
Desktop\New Folder\restore
So that you have:
Desktop\New Folder\restore\AccountAndSyncSettings.apk
Desktop\New Folder\restore\AccountAndSyncSettings.odex
Desktop\New Folder\restore\AdminFeedNotifier.apk
etc.
This assumes you are using my new version 1.03.

psouza4 said:
Basically, yes.
I'll use your desktop as an example, so if you have:
Desktop\New Folder\Pete's Motorola Root Tools.exe
Then you'll want to extract all the files for the /system/app fix to:
Desktop\New Folder\restore
So that you have:
Desktop\New Folder\restore\AccountAndSyncSettings.apk
Desktop\New Folder\restore\AccountAndSyncSettings.odex
Desktop\New Folder\restore\AdminFeedNotifier.apk
etc.
This assumes you are using my new version 1.03.
Click to expand...
Click to collapse
Ok thank you, I'll give this a shot again.
EDIT: I have it set up as:
Desktop/PetesMotorolaRootTools_v1.03/restore/(all the apk's)
And I'm still getting the:
ERROR: /restore/ backup doesn't exist or is incomplete! etc etc

ok i just unrooted and all is good now im rooting agian. so thank you for this on click unroot meathod. its good to know that if i want to unroot i can. You should put this on every forum that you can. I will aslo tell people about it. You did a good thing for the people on this one. I think a lot of new people will whant to root now that they have a way to undo it.

Lol well like 8th try and I got it to work. Sorry for pestering you so much.

[Q] Absolutely any files that I move into /system gets deleted immediately.

I've been racking my brain trying to figure out what the cause of this is and it is extremely frustrating at this point. I've written a few scripts to automate some things that I would like to do on my phone and moved them into /system/bin. They would all instantly be deleted. I've just about given up on the issue of actually using scripts because of this, but now even moving a simple .mp3 file to use as a ringtone won't work.
I moved my .mp3 file into the /system/audio/media/ringtones folder. It copies over successfully and then it is instantly deleted. What gives, and how do I fix this?

/system is protected, so anything moved to it will get wiped. I believe if you flash a zip in recovery it can get around this though.

KiraYahiroz said:
/system is protected, so anything moved to it will get wiped. I believe if you flash a zip in recovery it can get around this though.
Click to expand...
Click to collapse
Strange, I distinctly remember not flashing any kind of .zip on my Nexus 7. All I did was root it and I was able to read/write to system as long as I granted permissions through SuperUser. Is that not the case with this phone?
If not, where else can I move script files and ringtones in order to use them?

Usually rooting and moving files works, but HTC has done something that doesn't allow this.
Not sure about the scripts, but for ringtones, you can just leave it anywhere you like. In the sound settings, you can choose what ringtone you want, just click "+" on the top right when choosing sound. Notification tone is a tad more tricky though...
EDIT: Ok worked it out, usually in most android phones you can paste them at sdcard/media/audio/ringtones and sdcard/media/audio/notifications, but for the One it's just sdcard/Ringtones and sdcard/Notifications. .ogg files don't work as well (which is weird since that's what AOSP uses...), you need to convert them to mp3/m4a.

Just drop your ringtones, notifications or alarms in the corresponding folders on the sd card. No need to put in system anymore.
Sent from my HTC One using xda app-developers app

I'm pretty sure changing your kernel removes the system protection.
Sent from my HTC One using xda app-developers app

KiraYahiroz said:
Usually rooting and moving files works, but HTC has done something that doesn't allow this.
Not sure about the scripts, but for ringtones, you can just leave it anywhere you like. In the sound settings, you can choose what ringtone you want, just click "+" on the top right when choosing sound. Notification tone is a tad more tricky though...
EDIT: Ok worked it out, usually in most android phones you can paste them at sdcard/media/audio/ringtones and sdcard/media/audio/notifications, but for the One it's just sdcard/Ringtones and sdcard/Notifications. .ogg files don't work as well (which is weird since that's what AOSP uses...), you need to convert them to mp3/m4a.
Click to expand...
Click to collapse
Thanks, that takes care of the ringtones and notifications. Now if only I could figure out where to store my scripts so that they'll run from any location.
lampel said:
I'm pretty sure changing your kernel removes the system protection.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Is flashing a kernel the only way to make system writable? I'm hesitant to do so because I have no issues with the stock kernel at the moment and all I really want is to be able to run scripts. That said, what's the best kernel available for the One right now?

raphytaffy said:
Thanks, that takes care of the ringtones and notifications. Now if only I could figure out where to store my scripts so that they'll run from any location.
Is flashing a kernel the only way to make system writable? I'm hesitant to do so because I have no issues with the stock kernel at the moment and all I really want is to be able to run scripts. That said, what's the best kernel available for the One right now?
Click to expand...
Click to collapse
I do not believe flashing a kernel will give you system write capabilities. HTC has a security implementation known as S-ON which prohibits write access to the system partition. Until S-OFF has been obtained (not out yet) the only way to write to the system partition is via a flashable zip or adb.
Sent from my HTC One using xda app-developers app

RPelham said:
I do not believe flashing a kernel will give you system write capabilities. HTC has a security implementation known as S-ON which prohibits write access to the system partition. Until S-OFF has been obtained (not out yet) the only way to write to the system partition is via a flashable zip or adb.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Sorry, I should have mentioned that I have the HTC One Developer Edition, which I believe comes with an unlocked bootloader and S-OFF. I am able to write to /system through adb after mounting it, but my files are immediately deleted after writing to it.

There are kernels and fixes available to fix writing to /system but I'm not sure they apply to the dev edition so I'm not posting links - I don't want to suggest something that gives you a bootloop or worse... And I think a few S-OFF units have shipped but I don't think all the dev editions are S-OFF although they are all bootloader unlocked.
raphytaffy said:
Sorry, I should have mentioned that I have the HTC One Developer Edition, which I believe comes with an unlocked bootloader and S-OFF. I am able to write to /system through adb after mounting it, but my files are immediately deleted after writing to it.
Click to expand...
Click to collapse
S-ON is a security measure that does prevent writing to certain areas but I don't think it will affect writing to /system on this phone as long as the kernel allows it.
RPelham said:
I do not believe flashing a kernel will give you system write capabilities. HTC has a security implementation known as S-ON which prohibits write access to the system partition. Until S-OFF has been obtained (not out yet) the only way to write to the system partition is via a flashable zip or adb.
Click to expand...
Click to collapse

lampel said:
There are kernels and fixes available to fix writing to /system but I'm not sure they apply to the dev edition so I'm not posting links - I don't want to suggest something that gives you a bootloop or worse... And I think a few S-OFF units have shipped but I don't think all the dev editions are S-OFF although they are all bootloader unlocked.
Click to expand...
Click to collapse
No worries, I found a thread for the kernel module that will allow system writes. If anyone else is looking for the same solution, the thread is here: http://forum.xda-developers.com/showthread.php?t=2230341.
Thanks for the help everyone!