Hello!
Just a short question, what's the difference of those two ROM.zip files you get at the end ? One file is named with version number, date, official/unofficial etc. and the other one is just named "device-ota-eng.name.zip". Both are the same size and I can't see any differences.
For example, after building a PureNexusRom I got:
"purenexus_hydrogen-7.1.2-20170716-UNOFFICIAL.zip" and "hydrogen-ota-eng.dave.zip"
Related
I am continuing on my little cooking adventure but need some informtation that despite lots of searching I cannot find - perhaps someone could enlighten me on a coupls of issues.
1. I wish to assign different icons to my folders within programs - as others seem to do. How on earth do I do this? Yes, I can download .dlls, unsign them extract icons edit them and put them back and then resign them, but I cannot find my answer apart from the games folder.
I thought I would take a look at NRGs 2.0 ROM and see how he did it but I cannot locate his folder icons and so am confused even more.
2. Could someone explain how/what this autoshortcut things is and works as I keep seeing references to it when trying to rearrange shortcuts in the ROM.
Thanks for your time,
C.
For folder icons do the following if you have your dll already created. It sounds like you know how to do that part...
Create a new txt file
in the text file enter 50#"\Windows\yourdll -X" -X is the icon location. Rename the folder icon.lnk and place it in the folder. The 50 needs to be changed to something else and the first number should be something different and unique.
If you are cooking in a few icon.lnk files they need to be named like game folder icon and then with XML coding you need to rename them to icon.lnk
or what I do...
I place them all in a cab file and have the cab file run during customization.
Aaaaaaah (Moment of enlightenment)
Thank you so much, that answers a lot of questions for me. Time to get cracking I think.
Am I right in thinking I can add multiple files with the same name n the cab and simply install them to different directories - hence not bother with the renaming business?
Cheers
crazyC said:
Aaaaaaah (Moment of enlightenment)
Thank you so much, that answers a lot of questions for me. Time to get cracking I think.
Am I right in thinking I can add multiple files with the same name n the cab and simply install them to different directories - hence not bother with the renaming business?
Cheers
Click to expand...
Click to collapse
Yes you can...thats what I did before learning how to do it in XML or using the initflashfiles.txt files. An example of the txt file
Directory("\Windows\Start Menu\Programs\Tools\Rhodium Manila Tweak\"):-File("Icon.lnk","\Windows\Rhodium Manila Tweak Folder.lnk")
Oh, I assumed that I could not do this via the initflashfiles for some reason (assumed I would have a build problem due to multiple icon.lnk)
So, I could create a package with multiple *.lnks which then are renamed and put in the correct folders via the initflashfiles and then also include a custom dll in that package as well?
Thnaks again for the explanations.
crazyC said:
Oh, I assumed that I could not do this via the initflashfiles for some reason (assumed I would have a build problem due to multiple icon.lnk)
So, I could create a package with multiple *.lnks which then are renamed and put in the correct folders via the initflashfiles and then also include a custom dll in that package as well?
Thnaks again for the explanations.
Click to expand...
Click to collapse
Yes you can.
At0mAng said:
For folder icons do the following if you have your dll already created. It sounds like you know how to do that part...
Create a new txt file
in the text file enter 50#"\Windows\yourdll -X" -X is the icon location. Rename the folder icon.lnk and place it in the folder. The 50 needs to be changed to something else and the first number should be something different and unique.
Click to expand...
Click to collapse
While looking for something else I came across this thread and, while it's fairly old, I thought I should clarify two things, in case anyone else reads this.
First off, the <space> after "yourdll" should be a comma:yourdll.dll,-X(N.B. I have to admit that I've never actually TRIED using a space instead of a comma, so a space might actually work. That said, the standard for .lnk files in Windows, whether mobile or desktop, is to use a comma.)
Secondly, the "<number>#" at the beginning of the icon.lnk file (or any .lnk file, for that matter) isn't arbitrary.
The number represents the number of characters following the "#". So, for example, the example string above, "50#"\Windows\yourdll,-X", should really be: 21#"\Windows\yourdll,-X".
Assuming that "-X" is "-32", the file should contain:22#"\Windows\yourdll,-32"Another way to determine this is to look at the size of the file. Just subtract the characters of the number and the '#' itself from the size of the file. E.g., the above file would be 25 bytes.
(Once again, however, I have to include a caveat. The number doesn't actually matter. If the number before the '#' is wrong, the link will still work. I just wanted to explain what it's SUPPOSED to be.)
-geo
Just out of curiosity, is there ANY difference between the 4 or 5 different posts of the new .627 radio? Each author based them off the same file so the only difference could be what was done once they were pulled from the full OTA? I imagine there isn't but is there?
I downloaded a couple of them when they first came out and one later to see what the difference was because of the md5 concerns. All (of the ones I saw) have the same exact radio images that get flashed. One had an extra file added by the tool that was used to compress it. The others just used different compression tools to zip them.
If you are really concerned about mismatches, you can probably extract the actual .img's out and verify the md5's are all the same which they should be since they all came from the same OTA leak.
Not concerned - just curious
Hi Everyone!
I'm posting this here since I don't have posting privileges in the development area.
I have converted my Korean Galaxy Tab 10.1 as explained in the development section in this thread:
http://forum.xda-developers.com/showthread.php?t=1360588&page=5
to a 7510.
Everything worked fine.
Just one tiny problem I am experiencing:
My Wifi reception has greatly decreased after the conversion.
I noticed this imediately after the conversion but hoped it would "go away" once I had rooted the Tab an installed a modded ROM.
Unfortunately this was not the case.
Does anyone of you other "converters" have any experience with this problem or am I the only one?
best regards an looking forward to your answers
Krügge
Happy new year to everyone!
Well, since noone seems to have my problem I looked into the files myself.
The wifi drivers and their configuration files are located in /etc/wifi of the system image.
I flashed the korean shw-m380w original version and did a backup using CWM. I then did the same with the original gt-p7510 version.
When I compared the filesizes I noticed differences and the content of the configuration files were different as well.
So I just replaced the contents of the european wifi folder with the contents of the korean one. I had to use a linux shell, since the file permissions need to be saved.
I copied the newly created system tar file into the CWM backup directory of the european version, adapted the the md5 hash in the same directory for the new system tar file and went into CWM and did a restore.
Worked like charm. I'm back to my old, much better, wifi reception performance.
I don't know if this is the fastest an easiest method but it worked....
best regards
kruegge99
kruegge99 said:
Happy new year to everyone!
Well, since noone seems to have my problem I looked into the files myself.
The wifi drivers and their configuration files are located in /etc/wifi of the system image.
I flashed the korean shw-m380w original version and did a backup using CWM. I then did the same with the original gt-p7510 version.
When I compared the filesizes I noticed differences and the content of the configuration files were different as well.
So I just replaced the contents of the european wifi folder with the contents of the korean one. I had to use a linux shell, since the file permissions need to be saved.
I copied the newly created system tar file into the CWM backup directory of the european version, adapted the the md5 hash in the same directory for the new system tar file and went into CWM and did a restore.
Worked like charm. I'm back to my old, much better, wifi reception performance.
I don't know if this is the fastest an easiest method but it worked....
best regards
kruegge99
Click to expand...
Click to collapse
i have same problem with you. can you please explain to me step by step how to fix the wifi like you did?
Hi Everyone!
I have done some more experimenting.
Since I wanted to install different Android Versions and different Kernels and the fact that the Kernel Drivers are always compiled to work with only one particualer Kernel, I needed to find a way to improve Wifi reception without having the korean drivers.
I acomplished this by just pasting the config file nvram_net.txt from the korean Android into the directory /system/etc/wifi.
I renamed the original file to nvram_net.txt.orig and pasted, Afterwards I adjusted the permissions to be the same as the ones of the original file and rebooted.
This has worked with every Android Version I installed so far.
I have attached a Screenshot of the directory and the nvram_net.txt file of the korean tab.
I hope I can help somone with this.
To me it seems that the korean tab has just a slightly different Wifi Hardware than the P7510.
best regards
Krügge
Hi guys im a noob to the forums and to rom customisation in general so im hoping someone can help me.
I have a generic MX dual core, and have been supplied a flash firmware and image from the supplier. This image is basic and does not contain all of the repos that i want, nor the apps that I require.
The image supplied is a zipfile and contains:
factory_update_param.aml
hd18d_mx4.zip
recovery.img
I am able to successfully restore my box with this image (so I know that the image is working fine).
Within the hd18d_mx4.zip there is:
Directotories: data, META-INF, recovery, system
files: boot.img, bootloaded.img, logo.img
I can see the all the system APK files within the system/app folder. The problem is when i try to add another APK file into this directory within the archive (in this case videomix.apk), I am not able to restore the image to the MX device.
Can anyone help me with a noobies guide to do this. I have read that the apk file has to be signed, and the zip file has to be signed also?? But im not quite sure what this means, nor how I go about doing it.
Any help or tutorials will be much appreciate. I have downloaded the APK-multi-tool but dont have a clue what I need to do
Look forward to your replies.
P.S. Im using a windows 64 bit machine and not Linux (if that makes any difference).
I'm facing the same thing, did you end up having luck with this?
If not is there anyone that can assist?
Hi,
when i download some roms, release after release, i saw that, sometimes, only some files are changed.
if i make a little zip with only the differencies comparing two zip, and if i change updater-script
(deleting "delete system" process , deleting flashing kernel lines, generaly, at end of script and managing other things)
can someone confirm that if my updater-script never delete /system/ , i have no risk to "kill" my device ?
i have an idea about the reply but its good to have a thread about this question, no ?
i have test this following when i run a 2nd rom with dorimanx kernel.
- I search about differencies on two spirit releases rom. (using 7zip , good interface to compare and you have the total size of each folder in zip)
- On a structured folder, i keep only the new files from new release.
(apk, binary,priv-app,framework..., comparing them using size files essentialy because using the date as comparison filter never help in this way)
- i run my 2nd rom
1 - Remember us, with dorimanx kernel, when we are dualbooting roms, no matter the position rom you are run at a moment (1rst or 2nd), you will be able to see /system/ and /data/ partitions from the other rom which generaly sleep
2 - On PC, i generaly use WINSCP soft to acces easily on all structured folders of my device. (just let you know)
So,
- i launch WINSCP on PC, then i can log-in as root on my device, 2nd rom runing.
- in the interface gui of WINSCP, on left side, i see my extracted differencies structured with all files and in right side, i can see all folders from my device.
- with the interface gui from WINSCP, i can copy all that i need in /system_pri_rom/ and /data_pri_rom/ , which are the auto-mounted partitons from 1rst rom
- if DEV have moving some apks from /system/app/ to /system/priv-app/ , i move the files too. If DEV have delete some files, i delete too.
- when i reboot my 1rst rom, it booted without any trouble.
result :
the +
i dont flash anything
i dont change kernel
the -
looking for differencies between 2 zip take time
the +/-
i dont format/delete entire system and maybe with time, this can be corrupted.
If someone can help me this way by making a little script which can make the differencies with an output zip , it will be much appreciated
thanks.