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!
Hi guys! I have an Xperia Z3 D6603 running on official Android version 6.0.1 with build number 23.5.a.0.575, not rooted. I am not a tech guru and know very little of all these devices. My problem is that almost 5.0 GB of my internal storage is consumed by ".thumbnails" folder which I want to delete. I have searched some solutions and found out that normally people get some free space till these files reappear and in the mean time they can make this space useful but the case is different here. I have tried to delete this folder and all the containing files but even though the folder disappears for some time, I still don't get any free space even for a short time and the files start to reappear after some time. I don't have any Gallery other than the Album app and as it cannot be deleted, I have tried disabling but the problem still remains. I have also tried creating a new folder with the same name but the system would rename it to ".thumbnails 1" and another folder with the name ".thumbnails" would reappear . I had the same problem also with Lollipop on this device. I use FILE KOMMANDER, it is the system app.
Any help is highly appreciated.
The .thumbnails folder contain the preview of photo, image, an app generate that folder and it will be generate when deleted
hi guys,
something is very strange:
i flashed LP slim 5.0 from @Wajk (great rom so far) clean and fresh.
Now i discovered in the root directory a folder called d (and it refers to /sys/kernel/debug) with dozens of folders and hundreds/thousends of 0byte files.
Does anybody know what they are /where they came from and can i delete this d folder with all this folders/files???
Thx
The folder "/sys" contains information about the hardware and the linux system itself much like "/proc", which contains information about processes.
Those files you are seeing are part of the system, they are not really files i.e. they don't really exist on the phone, they are "virtual" and provide a way to read/write the mentioned information.
For more information just search for "procfs" and "sysfs" on the web.
Hope I could bring some clarification,
Sigi
Im still expirmenting with different ways of possibly, hopefully, someday over the rainbow, getting my S7 successfully downgraded. Ive taken so much time waiting for things to copy and paste, and convert, and made a custom firmware hours later, only for odin to either freeze or straight up shut down after reaching file analysis... so im exploring other ways. im not sure if its a good idea to flash only parts of the firmware? like just the AP files?
I wish samsung would allow us to say "I dont care if my phone isnt as secure" and then their butts are covered cuz we consented and we can still downgrade the bootloader and android version as desired.
i cant find any information on how to make a disk image into an lz4 file (as in oreo) since that one system file from the marshmallow stock is simply a disk image, so i went about it the other way and removed the lz4 from all of the oreo files, making them all either plain .bin or plain .img files except leaving the pit file and the meta data folder alone, and then repackaged them back into the same categorized tar.md5 files. odin checks them as legit, but just wont actually *DO* anything with them... so i got looking into my old s5 neo rom and saw that it was a 1 file version and wondered.... maybe i can make a 1 file version with a combination of the files i need/want, all into one custom tar.md5 and then maybe *that* will at least attempt a flash..... has anyone else tried this? or has already been thought about and failed?.... I only want that oreo rom with the marshmallow system image... is it really so impossible??
So glad I have an Appsung device... theyre locking their stuff down just as hardcore so... why not merge the names. Sampple is another option. heh.