I have rooted my phone and granted root access to root explorer, but i still can't paste anything into system/media folder and I can't rename the bootanimation.zip file. It says rename failed and then "root explorer was granted superuser rights" pops up on my screen. Am I doing something wrong?
You must to make changes inside twrp
Our phones are a bit different there.
system, or rather system_root, is read only. Think of it like a CD-ROM. You can only read from it, not write to it.
You have to use a kitchen of some sort, extract system.img from the ROM you are running, and edit the ROM from there. Once you have, you have to create the system.img from your files again. Then flash that system.img on your phone.
And then you are good to go!
It's that simple!
Related
I was messing around with root explorer and noticed that i was able to delete my boot animation with it when i was mounted as R/W so i thought i would try to copy one and it also works... so no need to push with adb shell.. here are the steps
1. take the boot animation make sure it is named bootanimation.zip and copy it to your SD card
2. then open root explore and mount R/W and then navigate to the file and press on file till the menu comes up and select copy
3. then navigate to data/local and paste the file in the local directory
and you are done, this can be done with the android_audio.mp3 file as well just paste it to the same place.
just thought this would make it easier for people instead of using adb shell
credit goes to yojoe600
Exactly what I was looking for, I'll give it a try, thanks.
The Animation worked but the Audio didn't, do you also need to put the Audio in a zip file?
I didn't think that you needed root to access /data/
So in that case, would need Root Explorer? Wouldn't any file manager do?
Yeah, you dont need root access at all for this.
just adb push bootanimation.zip /data/local/
palomosan said:
Exactly what I was looking for, I'll give it a try, thanks.
The Animation worked but the Audio didn't, do you also need to put the Audio in a zip file?
Click to expand...
Click to collapse
need to look at the text file in your bootanimations.zip and add the words android to the front of the text in that file
Hello, I have searched everywhere and cant find the answer to my question. I wanted to replace a file using CWM .zip how in the heck do I do that? Most of all I just wanted to learn how to do it as well...
Thanks,
Chad
Well to begin with you can take an existing zip with the file path you need, delete everything in the folders not touching the META-inf folder at all, those are the install instructions, and put the file you want to flash in the correct folder. I think thats how everyone starts out.
studacris said:
Well to begin with you can take an existing zip with the file path you need, delete everything in the folders not touching the META-inf folder at all, those are the install instructions, and put the file you want to flash in the correct folder. I think thats how everyone starts out.
Click to expand...
Click to collapse
but your update-script has to match what you are flashing via cwm. if you take a rom zip and just pop in a few files in place of the whole rom structures, your flash will fail because your update-script is looking for specific structures.
Oxicottin said:
Hello, I have searched everywhere and cant find the answer to my question. I wanted to replace a file using CWM .zip how in the heck do I do that? Most of all I just wanted to learn how to do it as well...
Thanks,
Chad
Click to expand...
Click to collapse
One way would be to use: Update Zip creator/modifier (Requires Windows)
yeah it would be bad mojo if you used a wipe rom zips META INFO to make an update zip.....
Thanks a million everyone......
Sorry for being late to the party again.. Here goes my attempt at an explanation though:
Essentially, a CWM flashable zip is just a zip file with the file system replicated in it. So for example, if you wanted to add swype, and you know Swype.apk would regularly go in /system/app, then you would create a blank folder called 'system', and another folder inside system called 'app', and put your Swype.apk inside that. (/system/app/Swype.apk)
After that, all that's left is to build an update script. So, from your root directory (where your system folder is), you would make another directory called META-INF, with a folder inside called 'com', another one inside that called 'google', and finally one called 'android' inside that (/META-INF/com/google/android), you put a text file in there called 'update-script' that tells recovery what you want to do (in this case, copy swype over to the corresponding directory on the file system).
http://forum.xda-developers.com/showthread.php?t=641223
^There's a guide for how to make those. You can also pick apart any rom you find in the dev section and check out the update script for reference.
After that, it's just a matter of zipping up all the contents in your root directory, then signing the zip with testsign.jar
modest_mandroid said:
Sorry for being late to the party again.. Here goes my attempt at an explanation though:
Essentially, a CWM flashable zip is just a zip file with the file system replicated in it. So for example, if you wanted to add swype, and you know Swype.apk would regularly go in /system/app, then you would create a blank folder called 'system', and another folder inside system called 'app', and put your Swype.apk inside that. (/system/app/Swype.apk)
After that, all that's left is to build an update script. So, from your root directory (where your system folder is), you would make another directory called META-INF, with a folder inside called 'com', another one inside that called 'google', and finally one called 'android' inside that (/META-INF/com/google/android), you put a text file in there called 'update-script' that tells recovery what you want to do (in this case, copy swype over to the corresponding directory on the file system).
http://forum.xda-developers.com/showthread.php?t=641223
^There's a guide for how to make those. You can also pick apart any rom you find in the dev section and check out the update script for reference.
After that, it's just a matter of zipping up all the contents in your root directory, then signing the zip with testsign.jar
Click to expand...
Click to collapse
Is there a way from the CWM interface to do the same with a backup you create? I noticed backups are not in the same format, they are usually .img, .tar, and an md5 file?
I cant go to recovery through Rom Manager for some reason. It works manualy( power+volume) but when I click it from the app it freezes, and shows an exclamation point triangle
have you tried to reinstall the app?
Wich CWM do you have?
thy the above post; if that doesn't work, go into recovery manually and fix permissions
that must be why
I was following this video http://www.youtube.com/watch?v=PVyGw6vycFo
and it said I had to wipe my data which I did, and maybe CWM was removed?
Ill try to flash CWM and see what happens.
Worked! thanks
In wich way?
Have you reinstall Rom manager App or reflah CWM Recovery?
actually, theres been a trend going on here....
I went on recovery to check if its working after I flashed it and it worked, after turning it off and removing the usb out of my computer I tried again and it didnt work.
Any ideas why?
Edit: when I had ROM manager I already tried to Flash CWM there if you're wondering.
Rename /etc/install-recovery.sh to something else with your preferred file explorer with root capability. Now reflash cwm and it will stick. What you are seeing now is stock recovery.
Harbb said:
Rename /etc/install-recovery.sh to something else with your preferred file explorer with root capability. Now reflash cwm and it will stick. What you are seeing now is stock recovery.
Click to expand...
Click to collapse
where can I find /etc/install-recovery.sh and what do you mean by file explorer with root capability?
Root explorer, ES File Explorer or something of the sort. This will let you directly modify files on the /system partition. Just enable root functionality in the settings, allow root when the popup comes up and rename/delete the /system/etc/install-recovery.sh file (this is the correct path, /etc is a link to /system/etc - ignore the other one).
Directories work pretty much the same as windows except it doesn't use "drives" (ie, C:\, D:\, etc), everything is found within the root directory (which is /).
Harbb said:
Root explorer, ES File Explorer or something of the sort. This will let you directly modify files on the /system partition. Just enable root functionality in the settings, allow root when the popup comes up and rename/delete the /system/etc/install-recovery.sh file (this is the correct path, /etc is a link to /system/etc - ignore the other one).
Directories work pretty much the same as windows except it doesn't use "drives" (ie, C:\, D:\, etc), everything is found within the root directory (which is /).
Click to expand...
Click to collapse
fairly new to android so I have no clue what you are talking about sorry... can you give me some steps on how to do that. again I apologize, Im still new
Download this from the market, i'm sure you'll figure it out
quick unrelated question: I tried to apply the ROM and it didnt continue, it said it was aborted or something
I recently Wiped my Phone completely and decided to Re-Flash Viper 1.2.1.
I noticed a problem prior to re-installing but thought nothing of if since it wasn't crucial at the time.
In Root explorer, I am able to delete [i normally delete boot animations] system files but not add where I need to add. Example, I wanted to add a ringtone to my system/media/ringtones folder. I normally [for the last six years] could just copy and paste such files using a root file manager.
However, when I any these files to for example /system/customize/resource/ it doesnt add it. BUT IT DOES rename the file and save it under a dif folder.
Example. Tried copying-copy to-moving to "androidtwirp.mp3" from sdcard to /system/media/notifications and a message pops up saying"notificationsandroidtwirp.mp3 successfully copied-moved to" and it saves notificationsandroidtwirp.mp3 to /system/media/ and it stays there. retrying from that location only results in "notificationsnotificationsandroidtwirp.mp3".
So not only does it rename the file but it saves it in the wrong location. I am at a loss for word. I tried the basics to tryand fix this but i cant seem to hit it on the head.
Thanks!
Edit: Not updating Super SU app, file explorer seems to have worked. Will attempt to duplicate problem to see what actually caused.it.
FOUND IT!
Updating my ES File explorer broke my system writing ability. DO NOT UPDATE is because when you do...
Any file you move, copy/paste to the system will not work properly.
This first happened when I tried to copy and paste a boot animation after I updated ES root explorer. It would rename whatever file i was trying to paste/move/copy over and save it under a sub folder.
example.
copying a ringtone [i.e. androidtwirp.mp3] from SDCard to System folder, the path is /system/media/audio/ringtones/ and it would rename it "ringtonesandroidtwirp.mp3" and save it under /system/media/audio/.
So basically not only was it renamed [which i didnt want it to be] but it would save it to the folder before the actual folder i needed it to be in, plus it would corrupt the file deeming it useless.
moving "ringtonesandroidtwirp.mp3" into the correct folder would only result in "ringtonesringtonesandroidtwirp.mp3"
this happened across the board with all files being moved around
The ES File Explorer version 1.2.1 comes with works flawlessly so don't update it.
I uninstalled ES [also any folders in SDcard related to it] and downloaded JRummy's root explorer and everything is back to normal except i have to reboot the phone to see files [like ringtones and notifications] that i added to the system.
I think it has something to do with our devices having an unlocked bootloaader, but still S-ON. There's S-OFF in the Dev section now if you really need to write to the system folder a lot.
I came from the Vibrant so I know what you're going through
Yeah, im on a low hboot so s-off might not be in my plans since I can practically flash what I want but it was ES file explorer, when I updated the apk the root permissions broke when writting to the system. I emailed the dev and they said they'd have it fixed on the next update.
echo en Android
After trying and trying and failing, I have finally figured out a way to port a rom to the Cube T7.
This has proven the only method (in my experience) to work. All the standard methods have failed
each time.
WARNING!!!!! THIS COULD BRICK OR DAMAGE YOUR PHONE
YOU ARE TRYING THIS AT YOUR OWN RISK. I WILL NOT BE HELD RESPONSIBLE
FOR WHAT HAPPENS TO YOUR DEVICE!!!!
Things you need.
latest Spftool
and the Rom package
NOTE:You need to know that you can't just flash the package I put together. You will
need to use the TWRP recovery that comes in the package to transfer file from your external sd to
the system folder and so forth. Also the proper permission to set.
Step 1: Flashing the images.
I've already pulled the correct img from each folder and put it together for you.
The only thing that you will need to do is extract the folder and use the spf tool to
install the firmware.
Note** In order to keep the 3.97 app storage, I've had to make sure to use the
Spf tool to do a full format except for the bootloader.
Step 2: Repairing the Rom
In the rar package, I included all the files need to fix the rom so
it will work smoothly on your phone. The files can be located in
the "system" folder which will need to be copied to your external sdcard
At this point you will already have flash the images and turn on the phone.
You will notice that the after you turn it on, you will get a warning that says "Cpu overheating"
or at least to that affect. This is not true by the way, this is from the fact the tp settings are off
from the original rom. Either way the warning will force boot your phone which again is fine.
Once this happens you will need to go to recovery.
Once in recovery make sure that you go ahead and mount your
system partition.
With this done you will be able to go to /system/etc/.tp
This folder contains the files that control the thermal manager for
the rom. You want to delete this folder. YES DETELE IT!!!
Once deleted, go to the system folder that you should have copied to your
external Sdcard. You need to copy /system/etc/tp to the exact location that you
just deleted the original.
Once you've done this you will need to set the permissions for the folder and the
files contained. The folder needs to be set to 0755 and the files inside need to be set to 0644.
Once done its best to go ahead and use the recovery to flash UPDATE-SuperSU-v2.46.zip to root your device before
restarting. Once restarted you will need to use root explorer or es explorer root function to
copy all the files to there correct locations and set their permissions. Each file is in its corresponding
folder as it should be in the system partition. All you will need to do is copy and past from the folder on the external and
paste to the same folder in the system partition. For those that may not know, all files will be set to 0644/rw--r--r-- and folders that you copy over will be 0755/rwxr-xr-x (if your using root explorer, just un check the group and others on the "Write" permissions.
Whats not working?
I can't figure out how to get the camera to working.
I've used standard tuts to try and copy the right files or libs
but not luck as of yet. If anyone figures out a way please share!!!
Also, if you have the fold case, the screen does not come on when you
open the fold. Also when double tapping the screen, this does not take it out of sleep
mode. From what I've seen those are the only things that dont work. If you see something
else, please report it to this thread.
Also in the package you will find the Carliv 3.3 recovery version for our phone.
Thanks to kushyree from needrom.com for building it for us.
He also has been assisting me in trying to port other roms to our phone. We owe him a lot of thanks.
Let me know if you guys need any help with this. I will do the best I can to try and help out. Enjoy.