I have been creating themes for all types of ROMs for a while now and for some reason about half of Hero ROMs I am not able to edit. When I download the .zip file and make changes when I go to close it I get memory errors and things of that nature that happen on multiple computers so I know it isnt my hardware.
So I decided to extract the Hero ROMs side by side, the one I can edit and the one I cant to see the difference. Well the one I cant edit always crashes when extracting, so I went folder by folder to find the issue. Well the problem is in the system > lib folder and there are 2 files with the same name but different capitalizations, liba2dp.so and libA2DP.so and it causes the error.
It appears I can remove the capitalized version of the file (aka the smaller one) and then everything goes back to normal and I can edit the ROM like usual. Can anyone confirm any of this?
this is microgays fault - ntfs doesn't support this - switch to linux.
maxisma said:
this is microgays fault - ntfs doesn't support this - switch to linux.
Click to expand...
Click to collapse
I have a virtual Mint installation I use for much of my theming which is why it was never really a problem, but I know other people have run into the issue and never bothered to ask and I just wanted to understand it instead of avoiding it.
So removing the file will work or am I breaking something else in exchange? I noticed your Hero roms dont have this issue and its your ROMs that helped me figure this out.
Related
i was just wondering what the deal is with trying to change the color of the letters and numbers on the taskbar.. i remember reading somewhere that it causes a bootloop but has there been any progress on that?
thanks!
Not sure about the boot loop rumor, but its almost near impossible to change. you have to deodex .odex files to get to the actual file to make the change. The problem is the .odex files can be deodexed, but reassembling them is more difficult. Trust me, im still trying to find a way to get this done.
obannvi said:
Not sure about the boot loop rumor, but its almost near impossible to change. you have to deodex .odex files to get to the actual file to make the change. The problem is the .odex files can be deodexed, but reassembling them is more difficult. Trust me, im still trying to find a way to get this done.
Click to expand...
Click to collapse
I was able to un-odex the file and see the code I needed to change. The problem fo rme was re-odexing the file. I un-odexed the file on the phone and then used utilities to re-odex on my PC. I wonder if I need to re-odex directly on the phone to create a valid file. Has anyone tried this yet?
daryelv said:
I was able to un-odex the file and see the code I needed to change. The problem fo rme was re-odexing the file. I un-odexed the file on the phone and then used utilities to re-odex on my PC. I wonder if I need to re-odex directly on the phone to create a valid file. Has anyone tried this yet?
Click to expand...
Click to collapse
i dont know..
if i had enough skills and knowledge about that stuff i would try but i'm still learning :]
is anyone up for the challenge?
Hello, since I'm new here and tried a lot of ROMs now, I just can't figure out how to install Dandiest DL Desire builds. I can't post in the threads too, because I don't have 10 posts yet. Hope to hear an explanation.
Sincere regards
Steven
Boek one?
Sent from my HTC HD2 using XDA App
I had the same problem. You might try using one of the lower versions. The thread organization was hard to follow, but with V2.0, if you copy the Desire DL folder and rename the config file (remove the SD from the end), AND place a data.img file (look for the 1GB file on the front page) in that folder, it should work. Be patient on the first couple of starts/restarts, it takes awhile. The one problem I'm trying to overcome is a data connection problem. I'm going to apply the "fix" file tonight and cross my fingers that it fixes it - other than that, I found it to be a nice stable build.
kdelisle said:
I had the same problem. You might try using one of the lower versions. The thread organization was hard to follow, but with V2.0, if you copy the Desire DL folder and rename the config file (remove the SD from the end), AND place a data.img file (look for the 1GB file on the front page) in that folder, it should work. Be patient on the first couple of starts/restarts, it takes awhile. The one problem I'm trying to overcome is a data connection problem. I'm going to apply the "fix" file tonight and cross my fingers that it fixes it - other than that, I found it to be a nice stable build.
Click to expand...
Click to collapse
Got it to work on Magldr now and renamed the config. Now my HD2 just keeps saying memory almost full... Did I forget to do something now?
I believe the memory full message is coming because of a data.img file which is too small. The ROM build thread has advice on either loading a 1GB data.img file, or repartitioning. I think if you search the ROM thread on memory or data.img, you'll find the helpful replies for that issue.
kdelisle said:
I believe the memory full message is coming because of a data.img file which is too small. The ROM build thread has advice on either loading a 1GB data.img file, or repartitioning. I think if you search the ROM thread on memory or data.img, you'll find the helpful replies for that issue.
Click to expand...
Click to collapse
Still having issues, and I don't get the partitioning thing.
My SD card has two partitions (I can't remember if that happened the first time I tried to install a build, or if I actually did that...). I have not done anything involving the ext partitions. Initially when I installed the Desire build from Dandiest (trying to install 3.4) I got the memory error. I researched and looked at Colossus's posts, and that's what caused me to download the 1Gb data.img compressed file (which is on the bottom of the first page). When I extracted that file from the compressed file, and copied it into the Desire_DL folder, I no longer got the memory space errors. I had other problems with the 3.4 build, so I tried the V2 build. After applying the data fix (I got those files from another post in that thread), I have been able to make the data connection work, and in general I like the build. I get some initial lag, but it's very stable, which I appreciate. When I have a little more time, I may try the 4.0/4.1 build, but several experienced users seem to be having trouble with that build, so it doesn't seem ready just yet. The file's name is literally "data.img" and should be 1GB and you should copy it directly into the Desire_DL folder (or whatever folder name you are using to boot into that version of Android!). Your config file should likely have the line data.img=1, to make sure it uses that and doesn't try to use or create one of the ext partitions. Good luck!
Hey everyone!
On the rom I currently use there are about 20 apk's I have no need for. What I do is download the rom, and individually delete the apk's before flashing the rom. The thing is I flash quite often (cheeky, I know ) and this is getting quite frustrating.
Ideally I want a script that does this all for me. I found one but it seems be for running on the phone, after the apk's have been installed. Does anyone know how I can create a script for the PC that does this before I even install the rom?
Thank you for any suggestions.
Oh and here's the thread I found that looked relevant...
http://forum.xda-developers.com/showthread.php?t=674357
edcoppen said:
Hey everyone!
On the rom I currently use there are about 20 apk's I have no need for. What I do is download the rom, and individually delete the apk's before flashing the rom. The thing is I flash quite often (cheeky, I know ) and this is getting quite frustrating.
Ideally I want a script that does this all for me. I found one but it seems be for running on the phone, after the apk's have been installed. Does anyone know how I can create a script for the PC that does this before I even install the rom?
Thank you for any suggestions.
Oh and here's the thread I found that looked relevant...
http://forum.xda-developers.com/showthread.php?t=674357
Click to expand...
Click to collapse
Over what OS?
If in Windows (or any M$ OS, incl. DOS) you can make a batch file.
My file is adjunted as example (modify as you like, put in the root dir -obviously to the unzipped ROM- and run. Rezip and maybe re-sign)
salu2
Thank you. This is exactly the kind of thing I am after. If I had of been born just a few years earlier I would probably know all about batch scripts. Fortunately, I just missed the DOS days!
Anyway, I puzzled out / looked up the commands in the script you posted. Based on that I extracted the rom, then placed the batch file within it, so that the cd (current directory) command runs correctly.
Unfortunately this mucks up the signing on the rom. Do you re-sign your CM7 roms every time you do this or is there an easier way?
Edit: My PC is Win 7, 64bit, soon to be Win 8 Consumer Preview.
Edit: The roms do not need resigning.
I don't re-sign the ROM, simply flash again over Clockworkmod Recovery.. and work.
But, you can:
1) sign using Auto-Sign....
2) Click [Thanks]...
Salu2
__________________________________________________________________
I know, I know.... my english is ****ty... but my spanish is much better... ;-)
Big thank you. That's solved that one nicely for me!
You're welcome.
Updated zip in my first Post.
Salu2
Hey again. I was hoping to build on the script you kindly provided. At the moment I am using various alpha roms where the exact apk's present changes fairly often. It would be great if I could see the outcome of each action. This way I would know if the apk has had it's name changed or been removed. How would I enable this?
I am using a couple of really old programs called recmod and reversmod and I am having trouble getting them to work. When I use the recmod tool, I do get a .dll file out of it, but the file is always 1kb and if I open a bunch of them in hex edit, they are nearly identical and each mentions that "this file cannot be run in DOS mode". Other than that, the rest of the file is almost entirely zeroes, so the code is null. Also the reversmode crashes when I try to use it on the .dll files I created, most likely because the files are busted.
In this thread: http://forum.xda-developers.com/showthread.php?t=1251237 OndraSter mentions something about recmod/reversmode using type 5 and 7 instead of just type 3. I don't really know what to make of this and Google leads me only to things that don't pertain to recmod at all.
Does anyone know how to make recmod work nowadays? Thanks in advance for any help provided!
ckv said:
I am using a couple of really old programs called recmod and reversmod and I am having trouble getting them to work. When I use the recmod tool, I do get a .dll file out of it, but the file is always 1kb and if I open a bunch of them in hex edit, they are nearly identical and each mentions that "this file cannot be run in DOS mode". Other than that, the rest of the file is almost entirely zeroes, so the code is null. Also the reversmode crashes when I try to use it on the .dll files I created, most likely because the files are busted.
In this thread: http://forum.xda-developers.com/showthread.php?t=1251237 OndraSter mentions something about recmod/reversmode using type 5 and 7 instead of just type 3. I don't really know what to make of this and Google leads me only to things that don't pertain to recmod at all.
Does anyone know how to make recmod work nowadays? Thanks in advance for any help provided!
Click to expand...
Click to collapse
The only thing i could find on it was ... http://forum.xda-developers.com/showthread.php?t=576027 and it hasnt been updated in awhile.
Diablo67 said:
The only thing i could find on it was ... http://forum.xda-developers.com/showthread.php?t=576027 and it hasnt been updated in awhile.
Click to expand...
Click to collapse
Yeah, that's the thread that first got me into the recmod tool. Great thread, just out of date. /:
Thanks for the reply though.
This may help
This may help someone help me a little. When I use recmod through the command line, I get an error saying "Error! ProcessCase0: bit 5 is zero!"
and this is the .dll file that I get out of it:
View attachment a.zip
I renamed the file name to a so it would be shorter to type because I was trying a lot of different command prompt things. It was originally k.senscmdd.dll, not that it really matters. All of the modules I tried came out almost exactly like this.
Hello guys.
I am wondering if there's any option/programme/app that can detect changes in apk files.
For example:
A dev releases a mod for something, let's say swaps a .png files to a custom .png and shares the mod in a thread.
And i want the same mod but in a different .png.
Now i can ofcourse ask the dev to do it, which is easy but i wont learn anything.
So i decide to try to make it for myself, but having no past experience with android i don't know how to do it.
And here's where the app/programme comes in (if there is one, ofc). A software that can detect any kinds of changes after decompiling apk files. Now many of you know that apk files have several folders inside, and inside those folder are various files.
So this software (if it exists) could be able to detect changes in the modded apk compared to my unmodded apk, and tell me where exactly the change(s) have been made.
In this way i don't need to bother a dev, and i maybe start to learn how to mod special areas of my phones UI.
Thanks for any reply!
Good day!