Database Info

[Q] problem installing a modded rom

I am having hard time to install a ROM after I modded it a bit.
The ROM itself had been installed already and works perfectly.
I was trying to change a few things like icons, bootanimation, default launcher and other stuff but the phone keep giving me an error and fail to install the file.
my phone is HTC HD2 t-mobile version, the ROM is android 2.3.4 with CM7, I am installing ROMs using MAGLDR 1.13 + clk 3.1.0.1.
I modified the zip file using 2 methods - both led to the error
1. unpack the zip file, replace the files, repack the folders back together into zip
2. swapping the files without extracting the folders out of the zip file
in both cases I used winrar (my computer runs 64bit win7).
am I missing something?
any help will be much appreciated

This is strange... I basically use the same method to mod minor stuff (like icons)... And it works for me without problems.
Are you sure your repackaged file has the same structure? Maybe unpack both original package and your modified one and compare folders and files using WinDiff or something?

I ran a check with "Beyond Compare 3" and it appeared to be the same except the files I've replaced.
What archiving software are you using?
There is no need to sign the zip or anything like it, right?

I'm using Total Commander which has zip functionality built-in.
No, I don't need to sign anything either (although I don't know, maybe it requires setting development options in android's settings).

[Q] Editing zip before flashing a ROM

I know I have done this before and this is a noob question, but lately I've been having trouble with this.
If I make changes to the zip file of a ROM (eg replace a few existing files, and remove some unwanted system APKs, but not add anything new), do I need to sign the zip before flashing or just flash straight after editing? Also what's the best tool to use to replace the files within the zip? I trust WinRAR will do the trick...

djsubtronic said:
I know I have done this before and this is a noob question, but lately I've been having trouble with this.
If I make changes to the zip file of a ROM (eg replace a few existing files, and remove some unwanted system APKs, but not add anything new), do I need to sign the zip before flashing or just flash straight after editing? Also what's the best tool to use to replace the files within the zip? I trust WinRAR will do the trick...
Click to expand...
Click to collapse
I've never added anything (yet!), just deleted un-wanted APK's and altered some system files (ie build,prop etc). I've never signed anything and I used IZArc although only as that's what's installed on my XP system.
This is something that I too would like to do more so that I can further personalize and tweak some of these already great ROMS, so I'm also curious for some pointers from more the experienced.

Check the portal, there's an app to create flashable zips there.
PS - POST QUESTIONS IN THE GENERAL SECTION !!!!!!!!

You can set a flag in recovery to check for signatures or not. When it is not set you can flash any zip file
Sent from my HTC Desire S using XDA App

jorgen2009 said:
You can set a flag in recovery to check for signatures or not. When it is not set you can flash any zip file
Sent from my HTC Desire S using XDA App
Click to expand...
Click to collapse
I tried this once, and then I flashed the zip. It was a CM7 zip which would normally take at least 20-30 seconds to complete, but this modified zip flashed in less than ten seconds. It said successfully flashed but when I rebooted nothing had actually happened. Hence I was wondering what went wrong?

[GUIDE][INFO] How to Unbrick your Softbricked device without any CWM/TWRP restores

Sick of taking huge sized nandroid backups before applying any tiny tweak/MOD and then undergo the long painful procedure of restoring ??
Through this guide , I will tell you about some really simple yet effective ways to unbrick your soft-bricked phone/get out of boot loops.
Our Unbricking Weapon
Android Commander - http://forum.xda-developers.com/showthread.php?t=628138
About Android Commander - Android Commander is windows application to keep control on your android apps and files from PC.
It detects your device even when it is in a bootloop!
Click to expand...
Click to collapse
TIP : You need a kernel/ROM with root enabled for ADB otherwise the AndroidCommander program will give NO root access ( since it is operated via ADB)
Ok so below are some of the most common reasons of bootloops :
1. Incorrect/Incompatible Build.prop Tweaks - SomeBuild.prop tweaks which you add to your Build.prop file located in /system folder might not be compatible with your device's hardware or firmware and this causes bootloops .
For eg - Over Sized heap limit , changing rendering methods to those which are not supported etc.
Solution - Have a backup of your Build.prop file before adding/removing/changing any build.prop tweak (its doesnt even take 2 minutes ) and if you face a bootloop, simply replace your current build.prop file with your backed up one.
2. A corrupt/incompatible System application / jar file (for eg - a wrong framework-res.apk) - Most of the time when theming or modifying, we might replace a system app with a modified app which might not be made for our device/hardware. This can lead to both bootlooping and/or crashing of the app
Solution - Have a backup of the original apk or download it from anywhere and simply replace( delete the apk and push your downloaded apk ) it via AndroidCommander.
3-An incompatible bootanimation - a bootanimation which either has a wrong desc.txt file with wrong resolution or wrongly sized images can lead to bootlooping
Solution - simply replace the bootanimation.zip file located in /system/media folder with any compatible bootanimation.
4An incorrect/corrupt Dalvik Cache - This can be simply solved by wiping the dalvik cache in recovery. Btw, clearing cache and dalvik cache can solve most of the bootloops which are not caused by incompatible mods/tweaks.
5.An incorrect init.d script and/or a system file like a lib/configuration/property/firmware etc( like efg.cfg file missing )
Solution Delete if its an addition , correct it or simply replace it with an original one
Click to expand...
Click to collapse
Note
There are many other ways to get out of a boot loop like flashing a CWM zip to replace your corrupt file / mounting as USB storage via Recovery but personally i feel that this is the easiest and fastest way to recover from a soft-brick.
These are only a few which i remember, i will post more in the future. As you can see that i didnt go into details of each and every category since there are endless problems and solutions which are obviously very specific. My main motive was to spread this idea since it has really saved me the hassles of restoring a backup for every small tweak i apply. All of the above problems have occurred to my device for once at least. This method has saved me a lot of times , Hope this guide helped you :angel: No more getting scaredof Soft-Bricks :laugh:
Press Thanks:good: if this helped you

But i tried it got some data corruption errors. could not find proper guidance / help on that , after few days sold the device.

[GUIDE][TUTORIAL] Create small flashable zips to restore before applying MODs/Fonts

GUIDE: CREATING SMALL FLASHABLE ZIPs TO RESTORE FILES OR SETTINGS WITHOUT HAVING TO DO FULL NANDROID RESTORE
This will enable you to apply MODs without having to do a FULL NANDROID restore to recover if the MOD fails or if you don't like it
This brief guide will teach you how to create a flashable ZIP file that you can use to restore your phone to pre-MOD settings if you want to revert back or if the MOD simply does not work
WITHOUT having to do a full restore of your phone.​
It is a very good idea to create these backup flashable ZIPs and keep them safe to recover from mishaps or when creating/testing MODs/themes.​
*************************************************************************************************************************************************
As usual: Disclaimer: I am not responsible for any loss of data or functionality on your phone. To be 100% sure, always make a NANDROID backup if you are not 100% certain you can recover.
*************************************************************************************************************************************************​
There are many reasons you might want to do this, for example when testing a MOD for another ROM that is similar to yours but not exactly the same (eg: Optimus G3 vs Cloudy G3) or when upgrading your ROM to a new version and wanting to re-apply old MODs.
There are many ways to get into boot loops or fail to boot, the biggest culprit being fonts installations, but include also bootanimations and others.
INSTRUCTIONS:
Part 1: general
1. Install ZIPme app from playstore
2. Find out which files are being modified by the MOD you are trying to apply, this is usually framework-res.apk, LGSystemUI.apk, lge-res.apk, but be aware that some MODs affect a lot of files. See part 2 for more details on how to do this.
3. If you are applying a font, don't worry, the FONTs section (see part 2) should cover all Fonts.
4. If you are applying a bootanimation, don't worry, the bootanimation section (see part 4) should cover all Bootanimations.
5. For every flashable ZIP you create you can test it straight away by booting into recovery and applying the zip file. There is no reason why it should not work.
Part 2: FONTS
1. In ZIPme select the following:
- ADD FOLDER: /system/fonts
- ADD FILE: /system/etc/system_fonts.xml
2. Create the flashable zip in an /sdcard location you can access from recovery
Part 3: MODs that affect framework-res.apk, LGSystemUI.apk or any other app
1. Find out which apks are being modified:
- You should of course read the OP (instructions for the MOD)
- The easiest way to find out modified apks is to download the MOD and open it: the zip file will contain either the apk files themselves or have directories with the names of the apks being modified.
- You can always ask the developer to make sure
2. Once you have a full list of files being affected you can create the flashable zip:
- in ZIPme, simply select "ADD -> File" for every file being affected
- If you have an ODEX ROM (.odex files are present) make sure you pick those too!
- save the flashable zip in an /sdcard location you can access from recovery
Part 4: Bootanimations
1. In ZIPme select the following:
- ADD FILE: /bin/bootnimation
- ADD FILE: /system/media/bootanimation.zip
- ADD FILE: /system/media/shutdownanimation.zip
2. Create the flashable zip in an /sdcard location you can access from recovery
Part 5: Other flashable files you should always keep handy
1. Always keep with you the following files for good measure: they don't take much space but can help recover from problems without having to fully restore from NANDROID backup
- original kernel from your ROM
- flashable bootloader (if you do not know what I am talking about then DON'T do it)
- flashable baseband (if you do not know what I am talking about then DON'T do it)
- flashable recovery image (TWRP, etc)
- "Xposed-Disabler-Recovery.zip": this is created by Xposed when you install it. It is located in the root folder of your sdcard. Copy it and put it somewhere safe.
- SuperSU: keep a flashable latest SuperSU with you to recover root
Any comments, suggestions, feedback are welcome

reserved

bloof said:
Any comments, suggestions, feedback are welcome
Click to expand...
Click to collapse
good work mate, i'm out of Thanks for today.

Just tried, nice and easy to use. Thank u

does it save paired bluetooth and wifi devices?

deleted

Can you use this to make a zip of boot.img and libs? Not finding how to do that. Thanks for any information.

matusala said:
does it save paired bluetooth and wifi devices?
Click to expand...
Click to collapse
Nope. It saves what you tell it to save.
The guide as it is only saves files, was meant for modding restore, not other stuff.
If you try mods a lot and don't like a certain theme or icon set you don't need to do a full nandroid backup and full restore because you changed 3 files in your mod.

countryfolk07 said:
Can you use this to make a zip of boot.img and libs? Not finding how to do that. Thanks for any information.
Click to expand...
Click to collapse
Not with what I wrote.
The app ZIPme can do a lot more than simple file recovery, but I am not an expert at flashable zips so can't comment on more advanced uses like buildprop etc.
I would certainly not write anything about boot images, way too likely to cause someone to screw up their phone....
Pick a flashable boot/libs zip file from somewhere and try to reproduce at your own risk.

Edit CSC others.xml

HI there,
I want to edit the file others.xml in system\csc\ to add in VoLTE activation for my Galaxy note 3.
Now, I know that most people say you need root, but I don't wat to root, have done it before, but I do not want to lose access to certain apps such as SKY Go, which need orginal stock.
My question, can we use a low level edit from say CWM recovery or any other piece of software that allows you one of two things:
1. Edit file others.xml before android is booted
2. If edit not possible, copy into that directory a previously prepared file and rename
I'd like to understand where CWM recovery or TWRP (or any other) sit within Android structure and what abilities do they have (e.g. edit, copy, rename etc.)
Many thanks everyone