I have an Alcatel onetouch pixi 4 and I rooted it, I wanted to mod my build.prop so I can get multi window mode, so I nodded the build.prop found in /system and I rebooted and wondered why it did not work but I found out that Alcatel phones have this folder named custpack in the system directory which also has a build.prop inside it
I read online and the build.prop found inside the custpack folder is the original so I modded it and saved it but FX file manager said about the file is truncated so I went back into it and then this happened... (Look at the screenshot) how do I edit the build.prop to take effect permantly
P.S: I shouldn't delete the custpack folder because my phone will not boot anymore
Related
Dears
i have replaced build.pop file under system by invalid one and when i restarted the tab it doesn't start at all. it give Samsung logo then nothing.
i have a backup from the original file i just want to know how to access the system folder to restore the original one.
there's something new, i used Droid Explorer to access the system folder and i have restored the original file successfully. but the tab is still not working i don't know what happened
please help
i'm sorry, when i connected the tab again with Droid Explorer i can the files has been renamed
i want to rename build.prop to build.prop.wrong
and rename build.prop.org to build.prop
but it doesn't work
I have rooted my HTC One aka M7 and all is well except when I try to edit my keyboard layout which is located in:
/system/usr/keylayout
I can edit the file but when rebooting to test it, my changes have reverted back to stock.
I am familiar with editing the files as I have done this before on many phones and tablets.
I usually just use ES File Explorer with R/W (Read / Write) permissions turned on for the /system directory.
Very easy to do and have never had a problem before.
As a test, I have tried renaming the original file by adding a number 1 to the end of the file and then replacing the stock file with my edited version.
This has always worked but when I try this on the HTC One upon reboot the original file that has been renamed with a 1 at the end is now gone from the /system/usr/keylayout folder and the stock file is back and the edited version of the file is gone.
I know 'file permissions' are correct as I have set the file to what it was before any changes and I know I have R/W permisions for the /system folder set correctly because without it I can not even rename the stock file (adding the 1 on to the end of the file's name is not allowed unless R/W is set for the /system folder).
It is almost like there is a backup that is being replaced upon reboot to the /system/usr/keylayout folder.
If there is a backup, I can not find where the backup file is to edit/change it also.
I am trying to change the AVRCP.kl file but it its the same no matter which file I edit or rename, it always reverts back to stock file (both the name and the contents) after a reboot.
Anyone have any ideas? Anyone edited there keylayout on the HTC One aka M7 yet?
Thanks
Come on people, no one can answer this question?
I have the exact same problem except I have an M8. Something somewhere keeps reverting the kl file/folder on reboot.
Howdy.
I'm trying to modify a .so file (libflashplayer.so), but have run into a few problems:
I first tried editing the file after it was installed from an .apk. This appears to work at first, but the edited file is quickly replaced with the original.
I then tried editing the file in the .apk package. This causes the package to fail to install (I'm guessing because the md5 in the certificates no longer matches)
Aldo tried moving a folder with the .so files from the .apk (com.adobe.flashplayer-1 which is what is created when the .apk installs correctly) directly into /data/app-lib/.The directory was created successfully but appears to be immediately deleted.
Is there a way to accomplish what I'm trying to do? If so how?
Other possibly relevant info:
My device is rooted
I did not write the code for anything in the .apk, I got it from a link on xda (pretty dubious i know but I couldn't find another option)
I'm using cyanogenmod 10.2 (based on android 4.2 I believe).
I'm editing the file with a hex editor to change a a few characters ("AND" to "WIN")
Hey xdadevelopers, I got this phone called cherry mobile me vibe and today cherry mobile released an update for my phone but I got a problem, the update.zip is trying to rename a system app which I already deleted earlier and now I can't update.
I got this idea to delete the line in updater-script which corresponds to the renaming part, but I don't have any idea how to do it.
I attached an image that shows the updater script and the line which I think should be deleted
asdads0909 said:
Hey xdadevelopers, I got this phone called cherry mobile me vibe and today cherry mobile released an update for my phone but I got a problem, the update.zip is trying to rename a system app which I already deleted earlier and now I can't update.
I got this idea to delete the line in updater-script which corresponds to the renaming part, but I don't have any idea how to do it.
I attached an image that shows the updater script and the line which I think should be deleted
Click to expand...
Click to collapse
Don't know if deleting that line is going to fix your issue but to edit the updater-script first open (do not unzip) the zip file, copy/move extract the script to another folder, delete the line and then reinsert the updater script back into the zip file. Doing it this way instead of unzipping then rezipping everything you may be able avoid having to sign the zip.
Hello,
I bought a Umi Diamond X and i just found out that it came with adware.
Since i could not find any custom roms for it, i tried editing the recovery image. Manged to remove some APK files, but SystemUI is giving me some problems.
What I did until now:
1) Used simg2img to convert system.img to a mountable image
2) mounted the previously generated image and deleted suspicious folders from system/app and system/priv-app.
3) Use SPFT to flash the edited image to the device.
However, I found that SystemUI.apk is also making dubious requests in the background, so I need to replace it with a stock version. I tried taking SystemUI.apk from different roms of similar phones, with a similar SoC, and copy-paste it into my edited system.img. However, everytime i do this, SystemUI crashes when the phone starts up.
Going into the stock recovery, i have the option to "check root integraty". This appears to scan (among others) all APK files in system/app and system/priv-app. I see it detects the deleted APKs and the 1 modified APK. Could the installer have a signature of the expected APKs and not install if the file doesn't match that signature?
Is there any way I can replace SystemUI.apk with a known good version?
Bump..
Bump again..