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.
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!
http://forum.xda-developers.com/showpost.php?p=20107570&postcount=17
I posted in my thread my problem. Does anyone know what I have to do exactly at the last step I am currently at?
I downloaded the 5 driver files for our crespo. Then I ran the scripts. Now I got a folder 'vendor' with some files in it. And I wonder where I should put it.
Hi everybody,
Quite awhile ago while playing around with custom Roms and going from one version of android to another, something went wrong with my file system. I had a regular file system but upon one of the installs it ended up making sdcard/0/ then the rest of my file structure. What I mean to say is I have 2 sets of folders, one where the files were stored for app data and files from before (sdcard/Downloads) and now a new set of files where they are now saved (sdcard/0/downloads). This creates problems for apps that have specific file structures where it looks for files and doesn't specify the location like backup utilities.. Because now I can't find the old backup file because the /0/ version of it is empty and it doesn't mention where specifically its looking.
Anyways I'm planning on upgrading to 6.0 (currently on 4.4.3 or something very close). I want to rectify this situation even it means a 100% reset of my phone. Any tips?
Thanks
flash latest factory image will solve your issue. it is a common issue when you jump from LL to KK and viceversa.
I have been trying to make lineageOS 17.1 tree for SM-J737S.
I tried to imitate the existing ones and made a tree, and extracted the blob file from the stock rom.
The kernel is a file obtained from Samsung open source, but the defconfig file had to be renamed.
I renamed it from exynos7870-j7topltekor_defconfig to exynos7870-j7topltekor_defconfig.
(because I got an error saying that the file could not be found)
I tried a 32-bit build because the blob file did not include a 64-bit library.
it seems to build normally, but it doesn't go any further.
I left it alone for more than 1000 minutes, but it only increased time and didn't go any progress.
EDIT : I've looked up a lot of literature recently.
And my work was fundamentally wrong in many ways.
Of course it was a code that couldn't work.
I've also made some stupid mistakes, and I've only noticed recently.