[SOLVED] - Nandroid restore nerfs Kyocera splash screen. - Kyocera Zio M6000

Well, now that we can use clockwork recovery, we can start trying to figure out why a nandroid restore causes the Kyocera splash screen to be replaced by a whit horizontal bar.
Anyone have any suggestions?

My assumption would be that the Kyocera splash screen is hardcoded into the phones "hidden files" and when you flash Clock work and do the Nandroid restores it is probably overwritting them.

Been searching on the net for any instance of a similar issue, to no avail (yet).
Hidden files hmm? Mind elaborating?

Spz0 said:
Hidden files hmm? Mind elaborating?
Click to expand...
Click to collapse
lol I say this b/c we cant find these files anywhere and almost every OS whether it be a computer or a phone has "hidden files" that the user cannot access. These files usually hold important system information that if altered would likely result in unstable operation or even the lack of operation. These files are normally stored on a partitioned part of the "disc" that is not accessible. When I used to develop for the Jailbreak community on the iphone we ran into this a lot. Of course there is almost always a work around when it comes to modding/hacking.
I am trying to learn as much as I can about Android OS and so far I can say it is very, very different than the iphone OS.

I am pretty sure the image is in the boot loader.
There is a 4K header, but only the first 2K are used. Then after that the boot files start.
I can rip the boot loader with either doing a "cat /mtd > file.img" (or something like that, don't remember off hand), or with the dump_image program.
If I use the cat, I get a white bar, if I use dump_image, I get a black screen. dump_image removes empty sectors I believe. That's the difference so it must be in those sectors.
On top of that, if I flash the sprint boot loader, I get a Sanyo image. So basically, someone needs to go in there with a hex editor and manually copy whatever is needed into that useless space after the first 2K and the 4K. At least that's where I think it is. Someone could do a compare between the dump_image and the cat to be certain.
(That's all from what I remember from a few months ago)
But to know what needs to be copied, we need to somehow get a fresh copy of the raw 2.2 upgrade files. Not certain how to go about that. Since the OTA upgrade downloads them, we should be able to adb and copy them over before it installs them, depending on where it's being downloaded to.

phazei said:
But to know what needs to be copied, we need to somehow get a fresh copy of the raw 2.2 upgrade files. Not certain how to go about that. Since the OTA upgrade downloads them, we should be able to adb and copy them over before it installs them, depending on where it's being downloaded to.
Click to expand...
Click to collapse
Would any of the files from the zclusive pc update route be of any help? I still have those.

I'm not really sure if this is any help at all, but in normal linux distros the initrd.gz is stored in the boot partition. This archive contains scripts used to boot the computer. It has been known to contain image files. I do not have the necessary OS right now to gunzip and investigate. If you guys want to find out if that file exists on android and see what is inside, it might be a good lead. If nothing else, it may point to the correct image.

I hace CentOS Ubuntu and a few other live distros, Ill check the boot partition for the kyo logo.
Sent from my Zio using XDA Premium App

NO MORE WHITE BAR!
Mattix724 said:
So, I have dumped my boot.img finally because gregnotcraig and other devs restored with nandroid and lost the Kyocera splash. With this boot image below you can restore your Kyocera splash. NO MORE WHITE BAR.
http://db.tt/zisPRYH
Simply enter fastboot and place this boot image in your SDK folder where fastboot is located.
Run this command...
"fastboot flash boot boot.img"
"fastboot reboot"
And there you have it, the stock splash screen.
Sent from my Zio using XDA Premium App
Click to expand...
Click to collapse
Sent from my Zio using XDA Premium App

i said it in #openzio, but i'll say it here, too...
thank the dog you had that. you made several people in irc happy little campers!

Solved!
http://forum.xda-developers.com/showthread.php?t=994754

Mattix724 said:
NO MORE WHITE BAR!
Sent from my Zio using XDA Premium App
Click to expand...
Click to collapse
For those of us who would like to change up the Kyocera logo, would it be possible to flash the Sprint ZIO boot.img to a cricKet ZIO (and not lose functionality)?

No.
Sent from my Zio using XDA App.

We will be releasing a custom boot image soon. Source is available just need to recompile with new splash1
Sent from my Zio using XDA Premium App

Related

Bootup Screen For Kyocera Zio M6000

First and foremost i want to thank esk02k and his friend for the images. All Credit goes to him for the images check out his post on xda called the thc weed leaf (i would post the link to his page but it wont let me says out side links are not allowed by new users but yet its an internal link). I didnt use all of them as there was only 37 images that i had to replace and i couldnt find the file that links to the boot up animation png files to add in the extra files so i used most of them and all i did was make it to the right size and converted them from jpg to png.
I am using the stock rom and my phone is rooted using universal androot version 1.6.2 beta5 (search for 1-click root for N1 to find this it will work on this phone) you have to install super user then you need root explorer found in the market. Now on to how to install this.
1) Install universal androot and the root explorer run universal androot to get your phone rooted you may chose soft root which only lets you temporary root till you reboot (dont worry it will not void your warrenty)
2) Download kyocera zio m6000.zip at the bottom of this post and extract it to a folder on your pc
3) Copy the folder to the root of your sd card
4) Open up root explorer and click on /data/FLEX/bootanimation
5) Copy Startup_Sound_M6000.ogg from the folder you copied to your sd card to the /data/FLEX/bootanimation folder overwriting the one in there
6) Next goto /data/FLEX/bootanimation/assets folder and copy all the png files from the folder you copied to your sd card to the assets folder over writing the ones in there
7) Exit out of root explorer and reboot your phone to see your new boot up screen and enjoy the first mod for this phone. (Note im not sure why the android screen dont show up no more when none of the files that was replaced was the android png files only the cricket png files are replaced)
Well there you have it the very first mod for this phone i hope you all like it as this is my first attempt at making a boot up screen animation im not sure how to make it animate more so please give constructive critisim do not bash it please and please tell esk02k thank you for all the hard work he did with the images all i made was the start up sound and resized the images and converted them to png to work on this phone so in all it only took me bout 7 hours his work was a ton harder and probably took him days maybe weeks. So major props to esk02k
**edit** Wow i started this by making the first mod for the phone and showed you all where to replace the stuff and got the ball rolling and not one thank you. Wow it shows me how much im appreiated here.
Everytime I try to copy the files, it says I do not have enough space. What do I need to get rid of?
muttd said:
Everytime I try to copy the files, it says I do not have enough space. What do I need to get rid of?
Click to expand...
Click to collapse
Remove some unwanted apps or apps that came on the stock rom that are worthless to you i removed the demo games that the company put on it and that gave me enough free space you need 6.50 mega bytes free to use this i made it as small as i could with out making it look like crap. you can remove some of the apps from /data/app i would recomend to back up the files before u delete them in case u have to put them back.
I have tried to copy the new pngs to the assets folder, but every time. I do, the original files replace the new ones. The closest I got was when I rebooted and I saw the first png of the original cricket boot animation, then it skipped all but the very last one of the new png I attempted to install.
Can anybody help me?
Sent from my Zio using XDA App
I am a new user of Kyocera Zio M6000. I also want to install the boot up screen for it. You describe the installation process clearly. Thank you for it.
SnakeFist said:
First and foremost i want to thank esk02k and his friend for the images. All Credit goes to him for the images check out his post on xda called the thc weed leaf (i would post the link to his page but it wont let me says out side links are not allowed by new users but yet its an internal link). I didnt use all of them as there was only 37 images that i had to replace and i couldnt find the file that links to the boot up animation png files to add in the extra files so i used most of them and all i did was make it to the right size and converted them from jpg to png.
I am using the stock rom and my phone is rooted using universal androot version 1.6.2 beta5 (search for 1-click root for N1 to find this it will work on this phone) you have to install super user then you need root explorer found in the market. Now on to how to install this.
1) Install universal androot and the root explorer run universal androot to get your phone rooted you may chose soft root which only lets you temporary root till you reboot (dont worry it will not void your warrenty)
2) Download kyocera zio m6000.zip at the bottom of this post and extract it to a folder on your pc
3) Copy the folder to the root of your sd card
4) Open up root explorer and click on /data/FLEX/bootanimation
5) Copy Startup_Sound_M6000.ogg from the folder you copied to your sd card to the /data/FLEX/bootanimation folder overwriting the one in there
6) Next goto /data/FLEX/bootanimation/assets folder and copy all the png files from the folder you copied to your sd card to the assets folder over writing the ones in there
7) Exit out of root explorer and reboot your phone to see your new boot up screen and enjoy the first mod for this phone. (Note im not sure why the android screen dont show up no more when none of the files that was replaced was the android png files only the cricket png files are replaced)
Well there you have it the very first mod for this phone i hope you all like it as this is my first attempt at making a boot up screen animation im not sure how to make it animate more so please give constructive critisim do not bash it please and please tell esk02k thank you for all the hard work he did with the images all i made was the start up sound and resized the images and converted them to png to work on this phone so in all it only took me bout 7 hours his work was a ton harder and probably took him days maybe weeks. So major props to esk02k
Click to expand...
Click to collapse
Apparently, the same number of images as the original must be used?
I tried one of my own, using boot screen found elsewhere on XDA that had more images. Didn't work.
Going to play around w/ the images today, reduce the count to the same as the original and see if that's indeed the case.
Or maybe it was the size of the images. I dunno yet.
Doesn't do a thing to my Cricket Zio.
hey i figure since your so gutsy can you get me a recovery rom my phone is crashed and cant find crap online
aago1254 said:
hey i figure since your so gutsy can you get me a recovery rom my phone is crashed and cant find crap online
Click to expand...
Click to collapse
We need a good solid backup rom, any post?
If your phone is a brick check the other zip threads for the update and you'll be on your way to a working phone
Sent from my from my rooted 2.2 no bloat Zio using XDA App
Zip threads?
Where can I find these zip threads?
ZIO threads. Like the 2.2 in the development section
Sent from my from my rooted 2.2 no bloat Zio using XDA App
Zip threads
Well, the 2.2 thread appears to refer to the windows downloader, with which I have two problems:
1) I don't run windows but linux, and
2) To do this, it appears I need to get into USB debug mode. I'm stuck in fastboot.
What I think I really need is the stock ROM from the Sanyo Zio. Does somebody here have this?
I can see if I can use adb to pull the 2.2 rom and if I have any luck I will let you know
Sent from my from my rooted 2.2 no bloat Zio using XDA App
Thanks
I'd really appreciate it.
You can email me too - justin at justinholmes.com
You may want to see if you can use a windows machine to update. I think you can do a virtualbox but I'm not 100%
Sent from my from my rooted 2.2 no bloat Zio using XDA App
I'm wondering if ReactOS is far enough along to run the updater. Will have to give it a try, liveCD.
No go. Booted the live CD, couldn't access any of the media devices to access the update tool.
Hmm
but listen, I can't get the phone into USB debug mode, so how can I run the updater? At the moment I'm stuck with fastboot. Normal boot is black screen, no response of any kind, no adb.
Turn the phone off, hold volume up down and power and your phone will bopt into modem download mode. Then update.
Sent from my from my rooted 2.2 no bloat Zio using XDA App
Umm wrong thread.
Try the android 2.2 thread. Lot's more helpful info there friend
jMyles said:
but listen, I can't get the phone into USB debug mode, so how can I run the updater? At the moment I'm stuck with fastboot. Normal boot is black screen, no response of any kind, no adb.
Click to expand...
Click to collapse
Sent from my Zio using XDA App

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.

[SOLVED]Slow Nandroid backups on bootstrapper?

Hey, guys. Haven't used an android for months since I let my DROID X go. I could have sworn I came across a thread with a solution to slow backups on bootstrapper but can't find it. Anyone have the solution? Thanks.
To slow them down or speed them up? To speed them up flash the newest ClockworkMod Recovery from Rom Manager after flashing the Bionic Bootstrapper. Then go to the Clockworkmod folder where your backups are saved (either sD or sd-ext) and place a file named ".hidenandroidprogess" without the quotes in that root directory of ClockWorkMod. That is .hideNANDROIDprogress not Android. Nandroid. Should speed things up drastically.
Sent from my Xoom using xda premium
Thanks! Going to try that tomorrow. The backups take way too long.
Okay. I created a file in that backup folder like you told me but I'm still getting slow backups. ".hidenandroidprogress" without the quotes of course. And a period inserted before. I flashed the latest clockworkmod recovery as well. 5.0.2.5
Not the backup sub folder where the files are. It needs to be in the SD-EXT/CLOCKWORKMOD/ folder. Not sd-ext/clockwordmod/backup/ folder. Assuming thats where you write your backups. Sorry I didn't make that clear.
Sent from my Xoom using xda premium
Got it. That's exactly what I did. Backups are much faster. Thanks for that.
Make a folder, or a file? If its a file, just a text file and name it .hidenandroidprogress?
Sent from my DROID BIONIC using xda premium
Correct. Make a blank file, like a .nomedia file, and call it .hidenandroidprogress or just copy a .nomedia file in there and rename it to .hidenandroidprogress. CWM will then stop showing you progress of Nandroid backups and restores. You just get the four or five main steps listed (backing up system, data, sd-ext...etc) no file listings and proggess bar as it goes. DRASTICALLY speeds up the process
Sent from my Xoom using xda premium
Legato Bluesummers said:
Correct. Make a blank file, like a .nomedia file, and call it .hidenandroidprogress or just copy a .nomedia file in there and rename it to .hidenandroidprogress. CWM will then stop showing you progress of Nandroid backups and restores. You just get the four or five main steps listed (backing up system, data, sd-ext...etc) no file listings and proggess bar as it goes. DRASTICALLY speeds up the process
Click to expand...
Click to collapse
I didn't notice much difference at first, but I am now. This is EXTREMELY helpful.
Legato Bluesummers said:
You just get the four or five main steps listed (backing up system, data, sd-ext...etc) no file listings and proggess bar as it goes. DRASTICALLY speeds up the process
Click to expand...
Click to collapse
What's funny is that my nandroids have ALWAYS been like this on the Bionic. I've been using cvps bootstrap since I first rooted (day of bionic release).
I wasn't sure what people were talking about so I put a hidenandroidprogress file in that folder and it slowed my nandroids waaaaaay down since it was showing every step...
Not sure why mine was backwards, but I was just reminded of this so I just checked and I don't see the file in my sd-ext/clockworkmod folder... Guess I need to do another backup and see if it's fast or slow again...
Underwater Mike said:
I didn't notice much difference at first, but I am now. This is EXTREMELY helpful.
Click to expand...
Click to collapse
After I create the file in file manager, I can't see the new file that was created. Is the .hidenandroidprogress file a hidden file to begin with?
Yes. Anything beginning with a period denotes that the file is a hidden file.
Sent from a GlaDos Baked Potato
Anyone know if this technique works with TWRP used in Safestrap 3.x?
No idea. Only use TWRP on my Xoom. And I don't have a bionic anymore. Sorry
Sent from a GlaDos Baked Potato

[RecoveryFileManager]Manage Your Files from Recovery with AROMA File Manager

Aroma File Manager
"Have you ever rebooted your device into recovery, only to find that you forgot to do some basic file management before embarking on your flashing journey? Perhaps instead you shut down your device, but would like to delete or copy some files without having to fully boot your device into the Android OS. Whatever the case, there are dozens of use-cases for being able to manage your files from recovery, and now it is possible.
XDA Recognized Developer amarullz has created AROMA File Manager, which lets users on any standard recovery manage their files in full GUI glory. You may assume that installing a recovery-based file manager would be quite complicated. However, it is quite simple. To run AROMA File Manager, all you have to do is “install” the update.zip, as you would with any other update.zip. Rather than physically installing onto your device, AROMA will instead be launched and allow you to cater to your file management needs. According to the developer:
How To Use?
Copy the zip into your sdcard, then reboot your device into recovery mode. Choose install from sdcard, then select the AROMA Filemanager ZIP. The file manager will starting, and you are ready to managing your filesystem (copy, cut, delete, make new folder, etc) while you are in recovery.
Those looking to get started should head over to the original thread. If you’re lucky enough to be rocking the HTC One X, head over to the dedicated One X Thread instead."
XDA Page: http://www.xda-developers.com/android/manage-your-files-from-recovery-with-aroma-file-manager/
Cool.
Thanks for making us aware of this. This is great will test
Sent from my MB860 using XDA Premium App
Niiiiice!
sent from my Atrix
Good find bud, thanks for the upload =)
I couldnt get it to work. Had no touch response only volume keys.
Just bumpin this so people who haven't seen it can try it, since more and more roms are using aroma. Great little tool to have.
Sent from my MB860 using xda app-developers app
I would find this EXTREMELY useful!! I dunno how many times I've booted into recovery and than rebooted back into the OS because I forgot to do... something!
*EDIT*
I answered my own question by looking into things a little deeper. I must have misread the post because for whatever reason (like an idiot) I thought it was originally ONLY for the HTC One X and you had got it working on the Atrix! Now that I believe it should work, imma test it out and post it in the Photon 4G forums!
Thanks because if it wasn't for this particular thread, I wouldn't have discovered such an awesome and useful tool!
Sent from my MB855 using xda premium
Its saved my ass on a number of occasions
Sent from my A500 using XDA
ATRIXXIRTA said:
Its saved my ass on a number of occasions
Sent from my A500 using XDA
Click to expand...
Click to collapse
It definitely makes things THAT much easier!
I even gave it a test run on my new G-Tab 2 but the touch interface doesn't work. I had to use the alternate volume up/down, power to select option ha. But it still worked
Typed on my Samsung Galaxy Tab-2 7.0 running CM9-ICS_4.0.4 using T-talk 2.0
ATRIXXIRTA said:
Aroma File Manager
How To Use?
Copy the zip into your sdcard, then reboot your device into recovery mode. Choose install from sdcard, then select the AROMA Filemanager ZIP. The file manager will starting, and you are ready to managing your filesystem (copy, cut, delete, make new folder, etc) while you are in recovery.
Those looking to get started should head over to the original thread. If you’re lucky enough to be rocking the HTC One X, head over to the dedicated One X Thread instead."
XDA Page: http://www.xda-developers.com/android/manage-your-files-from-recovery-with-aroma-file-manager/
Click to expand...
Click to collapse
Doesn't install just sits in install widow with nothing happening. But it would be a good thing to have wgen it starts being able to instill. Using latesr twrp recovery.
silvagroup said:
Doesn't install just sits in install widow with nothing happening. But it would be a good thing to have wgen it starts being able to instill. Using latesr twrp recovery.
Click to expand...
Click to collapse
So your OnePlus One is the Atrix 4G all of a sudden? You see that there are issues about this in the thread, you see that this is from 2012. There are better things out there for your device than this. Furthermore, this thread and project is abandoned, so you set yourself up for failure to begin with. Us Atrix 4G members appreciate your spam post. Now, since you decided to not do your homework, here's the thread that you should have been looking at, which was referred to in post #1, which is still an active project http://forum.xda-developers.com/showthread.php?t=1646108
Will this work like a Root Explorer ? can we change system files ?
Um, duh.
It runs within the recovery. That obviously means you can do just about anything.

[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!

Categories

Resources