Hi all,
I would like to gain a bit deeper understanding of how LOS is working in terms of actual phone function. I'm pretty sure that the following is only the tip of the iceberg, but with the stock ROM, for example on a Sony Z5C, there is a folder
/system/etc/customization/modem
that contains .mbn files for various providers and a folder
/system/priv-app/CarrierConfig
that contains a corresponding .apk file.
Now for example in LOS17.1, the first folder (or similar files) do not exist and the second one is called CarrierSetup with a corresponding .apk file. I assume the latter .apk is responsible for some sort of generic carrier configuration, but how does that work? Is it hard coded in the .apk, or is there some generic configuration file somewhere? And: How can I find out, what configuration is currently used and what bands are available?
Any helpful answers or references to further info are welcome!
Cheers,
r.
Related
I can't copy or move files stored in device ROM.
I've tried with Resco Explorer and Total Commander, but without success.
I didn't understand if there's a registry hack that allows these operations.
I've notice (or so it seemed to me) that I was able to substitute/copy/move some files having the ROM attribute, but many others not (eg: I've tried to copy the nleddrvr_sec.dll, obviously without success, otherwise I'd post this here!).
Surfing in many forums, I read many others asking for the same thing, unfortunately I haven't seen answers to their question about this.
Hope someone explains to me how to do or why is impossible to do.
Mersì bo q.
Gubbài.
You can not copy / move / delete files in ROM. Thats the point of "Read Only Memory"
These files are not stored as individual files but are in fact packed in a special way as part of the device image which can only be written (flashed) by special tools.
If you want to extract OS files you need to use a ROM dump tool.
I suggest you look in the WiKi.
What you can do is overwrite one or more "ROM files". What will happen in reality is that a copy of the file with the same name will be placed in storage memory and the system will go there. If you hard reset your device or rename the file it will go back to the original file.
levenum said:
You can not copy / move / delete files in ROM. Thats the point of "Read Only Memory"
These files are not stored as individual files but are in fact packed in a special way as part of the device image which can only be written (flashed) by special tools.
If you want to extract OS files you need to use a ROM dump tool.
I suggest you look in the WiKi.
What you can do is overwrite one or more "ROM files". What will happen in reality is that a copy of the file with the same name will be placed in storage memory and the system will go there. If you hard reset your device or rename the file it will go back to the original file.
Click to expand...
Click to collapse
As you said here and here (Changing Files in Windows Dir )
it's impossible to move/copy ROM files, just overwrite 'em.
Doing so the system looking for these overwritten copies.
So now the question are:
- there's a registry entry that points to this substitute ROM files?
- to modify an existent file resident in ROM I MUST dump my ROM or another one same or similar?
Mersì bo q, anyway.
Gubbài.
Hi,
Following this thread: http://forum.xda-developers.com/showthread.php?t=310287 I created a dump directory for a WM6 image. Inside the SYS directories are a number of subdirectories. Some of these subdirectories have familiar names (e.g. calendar.exe). Using calendar.exe as an example, there are 5 files: imageinfo.bin, imageinfo.txt, S000, S001, and S002. Here are my questions:
1. What are these 5 files?
2. What tool would I use to put the folder together to create a single executable?
Sorry for the noob questions but I can't find the answer on the forums!!
OK, after trying out all of the tools in one of the bundles, I found the answer to the second question:
2. Within someone's kitchen tools (I don't remember which one I downloaded) was a file called recmod.exe. Run it with the folder as a parameter and it will put the exe together.
I still don't have the answer as to what those 5 files are though.
My terms may be off base but I'll try to explain what these files are as I understand it (and hopefully not look stupid in the meantime as I'm also trying to explain it in layman's terms).
Many core files are constructed like this so that they are optimized in the Rom to make them run more efficiently on our devices.
Is there a file repository on this site, and if not, why not?
It would make things much easier if we had a place to put these files complete with a description. I had been looking for modem files and finally found a collection of them in some thread, but it was a pain.
I've been searching for months and I haven't found a way to debrand the Lumia 1020 from ATT.
The company locks features (like internet sharing, for example) , event if you unlock the phone...
Is it the lack of interest from hackers and developers, or is ATT really that strong at keeping us from debranding it?
spaceOpia1 said:
I've been searching for months and I haven't found a way to debrand the Lumia 1020 from ATT.
The company locks features (like internet sharing, for example) , event if you unlock the phone...
Is it the lack of interest from hackers and developers, or is ATT really that strong at keeping us from debranding it?
Click to expand...
Click to collapse
See from page #54 with the assembly (DLL) modified if you are unable to flash, maybe this can help you (RM-877 > RM-877 or RM-875).
anaheiim said:
See from page #54 with the assembly (DLL) modified if you are unable to flash, maybe this can help you (RM-877 > RM-877 or RM-875).
Click to expand...
Click to collapse
Thanks for the info Anaheim.
I downloaded your dll files, but from the edits on your post, you mention that the first modified dll (Nokia.CareSuite.PlugIns.MurzimRecovery.dll) caused problems, but did you revert back the first modified dll before replaceing the second (Nokia.Packages.VariantPackage.DataPackage20.dll) ?
also, your thread (on page 54) mentions modifying the vpl file. What is required to modify exactly?
I read around the thread and other forums as well and there are many ways poeple do it. Some even change two other files (the dcp and the bin file), while some only people change file names, and some people chage the content of the files
any help will be greatly appreciated
thanks
spaceOpia1 said:
Thanks for the info Anaheim.
I downloaded your dll files, but from the edits on your post, you mention that the first modified dll (Nokia.CareSuite.PlugIns.MurzimRecovery.dll) caused problems, but did you revert back the first modified dll before replaceing the second (Nokia.Packages.VariantPackage.DataPackage20.dll) ?
also, your thread (on page 54) mentions modifying the vpl file. What is required to modify exactly?
I read around the thread and other forums as well and there are many ways poeple do it. Some even change two other files (the dcp and the bin file), while some only people change file names, and some people chage the content of the files
any help will be greatly appreciated
thanks
Click to expand...
Click to collapse
I tried with both DLLs at the same time, it did not work.
The flash procedure is performed from the VPL file (VPL file contains all the file names, for then flashed this files). It is a sort of "guide". VPL file is "signed by" the signature.bin file that contains his signature. It is useful to modified the VPL if you change / replace / etc some files.
I have not tried changing some file, because I have not had time.
anaheiim said:
I tried with both DLLs at the same time, it did not work.
The flash procedure is performed from the VPL file (VPL file contains all the file names, for then flashed this files). It is a sort of "guide". VPL file is "signed by" the signature.bin file that contains his signature. It is useful to modified the VPL if you change / replace / etc some files.
I have not tried changing some file, because I have not had time.
Click to expand...
Click to collapse
Ok thx,
so I keep the original Nokia.CareSuite.PlugIns.MurzimRecovery.dll and only change Nokia.Packages.VariantPackage.DataPackage20.dll with the one you supplied.
I tried flashing the ROM with a country variant RM-875 from GB (with only Nokia.Packages.VariantPackage.DataPackage20.dll modified) but I still got the ffu error.
I will continue to work on it and keep you updated
thanks again
spaceOpia1 said:
Ok thx,
so I keep the original Nokia.CareSuite.PlugIns.MurzimRecovery.dll and only change Nokia.Packages.VariantPackage.DataPackage20.dll with the one you supplied.
I tried flashing the ROM with a country variant RM-875 from GB (with only Nokia.Packages.VariantPackage.DataPackage20.dll modified) but I still got the ffu error.
I will continue to work on it and keep you updated
thanks again
Click to expand...
Click to collapse
Any updates on this? Where you able to successfully flash the Lumia 1020 att model?
blackbo said:
Any updates on this? Where you able to successfully flash the Lumia 1020 att model?
Click to expand...
Click to collapse
No, no news.
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