Is there a way to modify cyanogenmod before I install it, so that after the installation, is already configured with my settings/preferences?
NucleusMS said:
Is there a way to modify cyanogenmod before I install it, so that after the installation, is already configured with my settings/preferences?
Click to expand...
Click to collapse
i dont think the same is posible before installing the same(Cynogenmod) for sure
Settings are stored at data partition in db files, so you can modify the zip, include those files into it and modify updater-script. After that, flash the zip, and your settings should be.
But I do not recommend to do this, because you can end with a bootloop.
Anyway, what's the problem to set the phone again? That's only 2 minutes.
Related
i asked in few threads but seems people are not willing to answer this question, and in threads with roms whom includes custom themes, do not have instructions how to install. So how to do that?
newestuser said:
i asked in few threads but seems people are not willing to answer this question, and in threads with roms whom includes custom themes, do not have instructions how to install. So how to do that?
Click to expand...
Click to collapse
Always search first post of specific thread for answers you will find your answer, or at least search your question before posting
you are not specific to your question
Q.1 Which Firmware are you using
Q.2 Is it Rooted
Q.3 what kind of theme is that (a CWM Flashable, xRecovery Flashable or Manual)
If you are using stock firmware then you will have to root, then you find a compatible theme and apply it according to the method provided by the theme maker
same applies to Custom ROM but they are already rooted and you might already have a recovery software installed
e.g
if its flashable by xRecovery you can go to xRecovery and flash it
if its flashable by CWM you can go to CWM and flash it
if you don't want to flash it go to Root Explorer copy that Framework-res.apk and replace it in system/framework directory and change permission to rw-r--r-- and reboot your device
and above all Backup your device before doing these because first time you might do it wrong and stuck up in boot loop
im using cm mini 7 v20 for rooted mini pro, i dont know if themes are flashable or not, they dont write that:
http://forum.xda-developers.com/showthread.php?t=1217611
not everyone are captain obvious to know what type they are
thanks for responding!
http://forum.xda-developers.com/showpost.php?p=18818162&postcount=35
newestuser said:
im using cm mini 7 v20 for rooted mini pro, i dont know if themes are flashable or not, they dont write that:
http://forum.xda-developers.com/showthread.php?t=1217611
Click to expand...
Click to collapse
its a Flashable zip, can be done via CWM
or you can manually copy & Replace those apks to their respective destination after extracting
and change permission to rw-r--r--
but be sure to backup first
ahub1988 said:
its a Flashable zip, can be done via CWM
or you can manually copy & Replace those apks to their respective destination after extracting
and change permission to rw-r--r--
but be sure to backup first
Click to expand...
Click to collapse
thanks, but can you tell step by step instruction ? because last time i did that via CWM... i got a bootloop :X
newestuser said:
thanks, but can you tell step by step instruction ? because last time i did that via CWM... i got a bootloop :X
Click to expand...
Click to collapse
so you want to do it manually.
first i must tell you as it is for older miniCM version it might cause problems
First extract your zip in SD card
copy apks from framework and apps folders
mount /system to rw and paste them to system folder
change permission of each apk to rw-r--r-- by press-holding and clicking permission in root explorer
make sure all apks have permission of rw-r--r--
move and replace framework-res.apk from /system to /system/farmework/
move and replace all other apks from /system to /system/apps/
Reboot
Thats it; if you done it correctly then it will go fine
or you can try themes from here by installing apks Here
The apks can be extracted and installed directly, no copying and setting permissions needed. However the core framework of cm7 must have changed since these were made as they don't render properly on newer cm7 based roms
I am trying to make a modified /system/app/NfcNci.apk , but when I load it on the device, I get the below error. What do I have to do to build to fix this? This is on a rooted stock Nexus 4. I built apk using standard google source, and pushed file over using adb. Thanks.
Code:
W/PackageManager( 529): Signature mismatch for shared user : SharedUserSetting{4182adf0 android.uid.nfc/1027}
E/PackageManager( 529): Package com.android.nfc has no signatures that match those in shared user android.uid.nfc; ignoring!
CptanPanic said:
I am trying to make a modified /system/app/NfcNci.apk , but when I load it on the device, I get the below error. What do I have to do to build to fix this? This is on a rooted stock Nexus 4. I built apk using standard google source, and pushed file over using adb. Thanks.
Code:
W/PackageManager( 529): Signature mismatch for shared user : SharedUserSetting{4182adf0 android.uid.nfc/1027}
E/PackageManager( 529): Package com.android.nfc has no signatures that match those in shared user android.uid.nfc; ignoring!
Click to expand...
Click to collapse
This thing comes when the target device contains apk/dex(odex) file with a different signature, which is normaly due to the fact that the app is build by some others, or some other adk. Or any other adk other than yours( i mean the one u used to create ur modified apk).
The solution goes like this,
Uninstall the apk, and remove its odex(dalvic cache ), if its a system apk, use root access to do it.
If its a critical app( which will turn of ur device if u delete it, like phone apk etc) create a recovery flashable zip of ur apk, go to recovery, wipe cache, dalvic cache, and flash ur zip.( remember to rename the apk exactly as it is in ur device, else it wont replace the original one, also set appropriate permissions). Reboot.
Dissable signature verification by patching core.jar ( lucky patcher application can do the trick for u). But its not recomended, unless u know what it is and what it can.
Sent from my HD2 using xda premium
Thanks I ended up fixing this by just copying the AndroidManifest.xml and the INF directory from the original apk into my modified one and it worked.
showlyshah said:
This thing comes when the target device contains apk/dex(odex) file with a different signature, which is normaly due to the fact that the app is build by some others, or some other adk. Or any other adk other than yours( i mean the one u used to create ur modified apk).
The solution goes like this,
Uninstall the apk, and remove its odex(dalvic cache ), if its a system apk, use root access to do it.
If its a critical app( which will turn of ur device if u delete it, like phone apk etc) create a recovery flashable zip of ur apk, go to recovery, wipe cache, dalvic cache, and flash ur zip.( remember to rename the apk exactly as it is in ur device, else it wont replace the original one, also set appropriate permissions). Reboot.
Dissable signature verification by patching core.jar ( lucky patcher application can do the trick for u). But its not recomended, unless u know what it is and what it can.
Sent from my HD2 using xda premium
Click to expand...
Click to collapse
I may have edited something wrong in build.prop and now my phone won't load after the SONY logo. I would push a stock build.prop if I had CWM but apparently I lost that after following steps to root JB with locked bootloader. All I have now is fastboot and flash mode.
Is there any way to push a file and set permissions using one of these modes? I can reflash ICS and do everything all over again but if I could just push a stock build.prop I think I can avoid the long way.
PS. Can I also get help putting CWM on this phone? I wanna keep bootlock 'coz I'm a purist like that. Lol! :silly:
do any of these modes support mounting \system and \data ??
XperiaMT27 said:
do any of these modes support mounting \system and \data ??
Click to expand...
Click to collapse
No, but fastboot can flash an update.zip according to a wiki. I don't think that's the same as a regular flashable zip is it?
Bump 'coz it's really getting tiring to reflash from zero when just one file needs editing.
androidmeda said:
Bump 'coz it's really getting tiring to reflash from zero when just one file needs editing.
Click to expand...
Click to collapse
Have you managed to solve this?
KOPRajs said:
Have you managed to solve this?
Click to expand...
Click to collapse
I ended up with reflashing only SYSTEM partition via Flashtool (don't forget to uncheck "Wipe DATA"). You are going to loose any modification of "/system" (e.g. root) but at least you won't loose your settings, apps and data.
Hi everyone,
I want to eventually create an edited ROM for an Android tablet. (Very simple stuff, really. Removing apks, adding build.prop mods)
I have a working update.zip file, which re-installs the image on the tablet, through stock recovery and the install from sdcard option.
But once I unzip it,
and then zip and even re-sign it (with the tool I found by searching the forum),
the recovery says 'installation aborted', when it is verifying the package.
1. How can I avoid this from happening? I get it that closing the update.zip is done wrong. How can I pass the verification section?
2. It IS possible to push such a .zip through stock recovery, right? I want to avoid CWM and TWRP and make it as simple as possible.
Thanks.
Have you tried making the changes without the unzip-rezip step? Editing the zip contents directly inside the zip (just drag n drop, delete, etc).
dxppxd said:
Have you tried making the changes without the unzip-rezip step? Editing the zip contents directly inside the zip (just drag n drop, delete, etc).
Click to expand...
Click to collapse
I tried this, too.
I only deleted one apk from system/app and later I tried again by deleting the apk and its odex file, too.
In both cases, instead of rejecting the update instanlty, it starts the process and then stops after a few seconds.
IS it possible that there is a filesize checker text inside the image?
(or maybe a propery inside the build.prop or updater-script ?)
Any ideas, anyone?
Still no progress.
I am trying to avoid custom recovery,
(I guess that would involve re-compiling it - which I do not know how to do - or ... just asking so from someone?)
is it possible to push the update.zip through stock recovery?
iraklisvel said:
Still no progress.
I am trying to avoid custom recovery,
(I guess that would involve re-compiling it - which I do not know how to do - or ... just asking so from someone?)
is it possible to push the update.zip through stock recovery?
Click to expand...
Click to collapse
No
Stock recovery doesn't flash custom roms
Get cwm from builder.recovery.com
Press thanks :good: I'd helped :highfive:
Hi!
I noticed that all change i made in system or vendor build.prop are ignored, or in some other xml files, even if i made a factory reset!
I try to add camera2 API and doesn´t work as example, APN changes to, etc...
The files i add, Change after boot still like stock but if i mount it on twrp it shows the changes i made!
Why?!
After some research i think there is no way to tweak system or vendor.
In some way i think vendor and system are writed in data when is flashed and stay in encriped data partition and when it boot only read data.
I read in some where that images only are use for fast update like dual images something problably the tweak image is not the one in use...
https://source.android.com/devices/tech/ota/ab/
Only customs ROMs will work maube because it have their own boot images and works in a diferent way.
I think it is the end of stock mods... :\
Thanks
Hello i had the same problem in android 10 miui 11.0.3 // you will need to reinstall your stock rom from https://xiaomifirmwareupdater.com/miui/platina/ fastboot rom using mi flash tool
After flash done flash twrp / magisc / install root explorer.
After that you should be able to edit again these files.
Or you can use twrp file manager to edit that .xml files // find a recovery that have the ability to edit those files.