Related
Hi all,
let me start telling that reading through this frum gives me the feeling that this is a very nice place for information around htc-devices and I thank both creators and users of this site for such a good information-base.
Reading here convinces me that I am able to fulfill my wish to change the language of my VPA-IV (HTC Universal).
I am a Dutch person working in Russia. As I was living in Germany I optained the device there, hence the German language.
For me personally all computer stuff should be English, so I'd also like this device to be so. The fact that the keyboard is German does not disturb me too much.
As a Vodafone user, who has other provider cards as well, I immediately bought the unlock code, so the device is working with other GSM cards as well.
When I asked Vodafone (before I bought the device) if I could switch to English I was told that I should buy myself another Windows Software and they were not able to provide me with it. They were not able to provide any help, nor software for this purpose though.
When reading around the site here (as well as the ftp) I understood that Windows is not provided now. So my first question would be :
-Am I really set to go if I have downloaded the following files :
Jasjar_WWW_11353_137_10301.zip
MaUpgradeUt_noID.zip
Universal_Radinly_UPgrade_1.04.02.zip
Or do I need something more ?
Further I read about extracting the .exe file (f.e. Jasjar_WWW_11353_137_10301.exe) and put some files from there at certain places. I have WinRar but this program does not recognize the .exe file. Can I really extract files from this .exe ? How do I do this.
A lot of talking is here about a bootloader. If the device is in this stage, can I still access it ? (f.e. like seeing a harddrive in my PC's Windows Explorer or something the like)
As I will be stressed like hell (who does not, when he does this first time) when I see the bootloader screen, is there something I SHOULD or should NOT do to make sure all will be OK ?
Last but certainly not least I feel very eager to backup before I do this. Is there a posibility to backup my ROM in some way, save the files on some place for eventual return to the ROM and ExtRom I have now ?
I tried the Program TotalCommander. If I enter the Extended_Rom in the "directory" field of this program I see all files included in the Extended_Rom, same if I enter simply "Rom". Is a backup simply copying these files to my PC or is there more to be done ?
thanks for answering in advance,
Ruud
Hi,
I'm searching a german ROM...
if you have a little of your time to spend on it, i would be very thankful.
but first:
- about extracting the .exe files: Run WinRAR -> Menue: Open file... -> change 'All archives' to 'All files'
- about ROMs: Jasjar_WWW_11353_137_10301.zip is the only rom I would update, not the Radio.
- about bootloader: In this state you can't access your device (only updating the ROM)
- about backup: It is not easy. (How to d2s (dump) the ROM ) but I think Vodafone will shortly relase a update. So it will be possible to restor the device.
How to help me out:
- you will need a Storage Card.
- Download TestWM5.rar
1. Extract TestWM5.exe from TestWM5.rar and place it to you device.
2. At the device, use File Explorer to execute the TestWM5.exe
3. Click "button1" to start the dump process, the file will then be save to \Storage Card\Dump\
4. Copy the Dump folder out and then RAR or Zip it
This will include all files in your windows dictionary -> this is what i need
Where to place exactly ?
Hi bepe,
do not know if You are still available (or again). First your issue.
I logon to FTP from XDA-developers as to upload.
In the upload directory there is only a HTC-Wizard directory, not a wizard. Is this directory the one to place your file on ?
Is there a rule how to name the file ?
I will be dumping in a minute, can upload as soon as I have your answer.
Ruud
Hi bepe,
further to your issue.
1) I do understand that no private information is copied ? or should I do a hard reset before I dump for You ?
2) Whilst running your testwm5.exe from the root-directory of the storage-card I am being asked to agree your program access. This is normal, I allow. But why are there additional programs being opened I never heard about ? I denied them access and let the program run further !
After a lot of files running through the screen (very fast) it looks like the program stopped or finished. Now which file has been created for You ?
Explorer on the Universal does not show it, through my PC I looked as well, but do not see any big file, please explain.
Ruud
Hi Bepe,
one more reply to You :
Even if I allow the file mentioned to run (during the time your program is running), I am being asked again and again if I allow it again. The name is GAC_System.Data_v1_0_5000_0_cneutral_1.dll
Even if allow access all of the occasions I being asked, no file is being created on my storage-card, nothing to dump to You. Not even the dump directory is made.
What do I do wrong here ?
To my issue :
First I noticed that the radio update is available here only as 1.04.02
My system tells me I have 1.04.10 delivered from origin. If I do a ROM-upgrade, do I loose my "radio", or will it not be touched ?
Connected to this, can I dump my "radio"-files seperately ?
WinRAR. Issue solved !
Backup : I was at the buzzdev.net link before. But I actually do not even understand where I can get or see the task32 language he dumped on his screen. And I understand that I will not be able to restore it without help anyway. So this is not really the kind of backup I want.
The information about Vodafone, where does it come from ? when is something expected ?
Ruud
For security sake only.
I am getting nearer to make that final step ;-)
My Winrar was too old, I could unzip the .zip file to a .exex, but I could not unzip the .exe file further. Just downloaded the latest Winrar, now I can see all files included in the provided .exe file.
1) I understood that I should delete the original upgrade-file called ROMUpgradeUt.exe.
2) When I start the MaUpgradeUt_noID.exe in a seperate directory with the rest of the files from the .exe I get to see a different HTC device. When I continue, it will not recognize any of the versions from my Universal. I felt unconfortable to continue.
Can it be done without a problem ??
2a) I renamed the ms_.nbf AND radio_.nbf and restart the Utility, it still shows a photo of the wrong device, but it now does recognize the versions of Device CD image version : 1.13.56 Device Extended image version : 1.13.163 and Device Radio image version : 1.04.10
It confirms to change to CD image version 1.13.53 and leaves the extended image version : "empty" as well as the Radio image version : "empty"
Does this mean that by taking away the ms_.nbf and radio_.nbf files I can stop the device from upgrading the extended rom and the radio ?
Why I ask ? Because if I renamed ms_.nbf back and ONLY radio_.nbf is unavailable now, it shows to change the Extended Rom too, but the Radio image is still empty.
Finally if I rename ALL back, it shows to change all, but all version numbers are older once ;-(
Main question here is, can I leave radio_.nbf away, upgrade and hope for radio to be my version 1.04.10 ?
Ruud
Hi,
I'm back.
I'll PM you Upload information...
private information are not copied.
Only if you have saved private information in your /windows/ folder!
i have never being asked to agree for program access :?
...but I started it of the root-directory of my device.
what is the name of your 'Storage Card' folder?
I not realy have the info from Vodafone, but for all devices before there have been more than one update. But I can't tell when the first update is expected.
If you are trying to make a backup: you will need a terminal program
About dumping
So I have a complete "new" device now.
Did a hard-reset, after which I did not give any new information to the device.
I placed the .exe file You gave me in the \windows\startmenue before, after which it is asking tonloads of access requests.
Now I replaced it in the root-directorym Yes, no additional questions asked anymore, perfect, well NO. As there is no directory made on the storage card. I tried it once with the async active and once with the device seperate. No result.
Any ideas ?
what is the name of your 'Storage Card' folder in your root?
As the device is German, it is called "Speicherkarte"
and renaming is not possible (allowed)
OK this is the problem, I'm trying to get the Source code to change that.
found something: this tool will change the folder name from different languages to "Storage card" which is often needed for different tools
Understood.
About my question, as I am still nervously waiting (cannot start the upgrade before You got your data, can I ;-)
Did I understand correctly, that the file MaUpgradeUt_noID.exe is made for different devices from HTC and therefore I do not get a photo of the universal when I start the software ?
If I start the JASJAR_WWE_11353_137_10301.exe I DO get to see the Universal, but of course get the country error.
Did I also correctly understood I can take away the radio_.nbf from the directory and the update will handle both ROM and ExtROM but leave the Radio untouched ?
Will I be entering this "bootloader" status at all, as I do not need any further updates then ? Are there any resets after the upgrade which I SHOULD or SHOULD NOT make to get the device working again ?
Ruud
Hi bebe,
storage.cab works (be it only after a soft-reset)
The program testwm5.exe is much slower now, so the result is taking minutes now (if not tens of).
Looks like the perfect speed of the program while the storage card (at least for his eyes) was absent, was due to "saving into space"
Will upload asap.
Ruud
I'm loading JASJAR_WWE_11353_137_10301.exe its at 60%
MaUpgradeUt_noID.exe is a hacked version, of another device.
So the photo should not be important. (Please wait until i have downladed the file, I'm not realy sure jet...)
OK, I have to wait anyway, because TestWM5 is very slow now, I can see file after file and calmly read it. Before it was running before my eyes. I am afraid this is going to take ages.
We are on the same frequency that the dump I am making is from a device WITH Extended Rom installed. I was NOT soft-resetting during installation, so all Vodafone add-ons, are to be there now.
If You need the one without ExtRom as well, please tell me.
The upload works OK, I prepared a directory there, but uploading is to be done after longer waiting time.
Are You afraid the JASJAR file is not good ? I downloaded it because this one was proposed on this forum.
Ruud
Its not about the ROM its about the MaUpgradeUt_noID.exe I'm not sure if ths is the exe file to update a Universal.
I dont have a Universal only a Himalaya and my up UpgradeUt starts with HimUpgradeUt... .
Was this file mentioned in the readme of the JASJAR exe?
my download is very slow... 70%
I only downloaded MaUpgradeUt_noID.exe because it was proposed here (for the Universal).
I have no Readme.txt inside the exe
EnterBL.exe
GetDeviceData.exe
ms_.nbf
nk.nbf
radio_.nbf
RUU.conf
RUU.dll
UI.dll
Well and of course the original upgrade file ROMUpgadeUt.exe, but I was suppose to delete it.
Only file which I can read is RUU.conf :
[PLATFORM]=857873
[RADIO_TYPE]=2
[SECURITY_FLAG]=1
[DECODER_KEY]=1
[RADIO_FLAG]=2
[GETADDR_TYPE]=1
[JUMPCODE_TYPE]=1
[FORMAT_TYPE]=2
[SCREEN_TYPE]=2
OK, TestWM5 is finally ready, will do compressing and uploading soon.
Ruud
Hi all,
I can't figure it myself, Can anyone from the experts here compile a andboot folder with latest initrd, kernel & Haret, so noobs like me run Android on their Kaiser from SD without deleting original WM.
many thanks in advance,
a) That's really really lazy man!
b) Not every kaiser has the same configurations (panel type, key mapping, etc)
c) Not all the users would like the same build
d) That's really really lazy! (again)
Try this guide: its noobs-proof and I assure you than in less than 15 mins ul be running android on ur kaiser:
http://sourceforge.net/apps/trac/androidhtc/wiki/HowToInstallWithAtoolsHaret
What OS does this guide use? OSX.
what about Windows based PCs? like the one I have?
Is still possible to compile Andriod on Windows? I know the answer OF COURSE NOT.
Alberto, Not everyone see it easy as you did. If you want to help, give a hand. if not thanks.
yassermekled said:
What OS does this guide use? OSX.
what about Windows based PCs? like the one I have?
Is still possible to compile Andriod on Windows? I know the answer OF COURSE NOT.
Alberto, Not everyone see it easy as you did. If you want to help, give a hand. if not thanks.
Click to expand...
Click to collapse
LOL no man! that's why we are here right? to find answer to all our doubts... some months ago I had no idea bout android!! Now im a little more "versed" in this matters but compared to a lot of ppl here i find myself as a noob! But its not that complicated ull see:
First download Haret latest ver:
http://it029000.massey.ac.nz/vogue/files/
download haret-for-kernel-2-6-32.exe file
ull copy it to your SD later...
also look at the forum and search for a build, an example can be this one, its a donut build and i have found it really stable under NAND installation:
http://forum.xda-developers.com/showthread.php?t=796193
its not the latest version of android (froyo) but ull find it easy and reliable, you can try a froyo build too but be carefull, not all builds are made to run in haret.
then download python (needed to run atools, no need of OS X )
http://www.python.org/download/
please be sure to download only the 2.6 or 2.7 version
install it
Downoad version 1.04 of atools from here:
http://sourceforge.net/projects/androidhtc/files/AtoolsRelease/
look for atools-1.0.4.py
Run it
Follow the guide I provided you before,
1. Select haret on the button "D"
2. under device select kaiser
3. select the resolution u prefer, 240 is the native res for our kaisers, but you could try the other ones..
4. select wich version you will install, in my example you would select donut, but you should try different builds and keep the one you prefer.
5. the panel type... well this is a little complicated, kaisers have diferent types of screens and there's no accurate way to now wich panel type u have unless you try out! so basically ull have to try each one of the types (1, 2 or 3) if you see strange colors, or black dots in the screen, ull have to reflash the kernel so lets start with the panel 1, you could try to use the auto option but im not totally sure it would work...
6. key map: if you have a unbranded TyTn II (not the AT&T tilt) select normal, if u got the tilt select this option or one of the other special key mappings
7. ill recomend u to leave all the rest of options unchecked for the first time, but if you want to give it a shot, try reading the guide i posted before.
8. save the file with the diskette button
Format your SD with FAT32, create a folder named andboot
copy the file previously made to it,
copy haret to it too.
download the latest zImage with the world button, save it to the andboot folder.
download latest initrd from the button with a box and an arrow, again copy it to the andboot folder.
lastly copy the androidinstall.tar (could be .tgz too dont worry) of the build u prefer to the andboot folder
insert the SD to your phone, run winmo, go to the file browser, search the andboot folder, run haret, press run, the phone will reboot, and ull se a pretty lil penguin and a lot of text scrolling down, put attention and press d-pad (silver center button) when the system prompts u to do so, select install system and wait for it to return to the main menu, select quit, and voila! remember if you find issues on the display, go back to atools and make another default.txt but this time with panel 2, or panel 3 type.
this is not as good as the guide l1qu1d made, i wrote this in 5 mins, he probably spent a lot more time writing it and testing it, i really suggest you to read that guide before trying anything, m not responsible of anything going wrong, actually the worst thing that could happen is u to NOT run android , thats why i suggested it on my post....
Thank you for this guide, i personaly found the original very hard to understand. I have spent an entire day trying to get android on my phone but to now avail. I did managed to get super froyo on for about 5 mins before it white screened on me and froze. It was also very slow. All other attempts didn't get past the linux screen. I'll keep persevering though!
I think every body should have the source to information so they can better understand what they are messing with... why waste time waiting and begging for food when you can learn to cook for yourself?! ... so here is my tutorial on breaking down CyanogenMod9 on the Acer A100( although most of this should be a general guideline to most roms) ***** I am not responsible for you breaking your stuff nor responsible what you do with this information... you have been warned! u can soft brick your tab in a heartbeat***
okay so there are countless tutorials on how to build a ROM from source... just google it.. but some ppl obviously don't have the need to spend the hours compiling because there is already a build for the ROM that they like... but on the other hand they want to add some mods and tweaks to the zip before flashing to tweak the tab to how they want it... after all it is your device and your the one that uses it most so why wouldn't you want personalized tweaks... and theres only one way to learn.. trial and error! haha but hopefully this guide will help you grasp some basic to advanced Android tweaks and mods ... again this tutorial is written for CM9 for the acer a100 but the "general" idea is about the same on the basic stuff... this tutorial is written by me from many sources too many to name but thanks for all the tutorials or I wouldn't know a lot of what I know about Android... This guide is for Ubuntu 12.04... but I would assume 10.04+ it would be compatible but don't quote me on that as I don't know so its your fault if you f* something up!!!!
First off you have your cm9.zip... its simply a zipped archive.. dur... sometimes a signed zip.. now you can simply open nautilus file explorer and go to your .zip and extract it with archive manager.. I suggest when the dialog comes up as where to extract the files that you click make a new folder and name it extractedCM9 and let it extract... okay not so hard quite yet 'eh?.. hang in there it gets a lot better ... you should now have a folder named extractedCM9 with some files in it... copy the extractedCM9 folder and paste it into the same directory that your copying from... rename the folder tweaked then cut and past that folder into extractedCM9... next open the extracted CM9... you should see the following: META-INF(a directory), system(a directory), and boot.img( this holds your initrd which is your "ramdisk", your zImage which is your kernal, and on extracting you'll also find a boot.cfg... we will get to extracting the boot image latter.. stick with the easier things to get us going!... now create another directory called stock .. you should now have the following... META-INF/(a directory), system/(a directory), stock/(a directory), tweaked(a directory), and boot.img.. okay a little more copying and pasting.. all this will be used later so if following this tutorial all the way throu you should do as instructed lol... CUT META-INF/, system/, and boot.img and paste it into stock.. you should be left with the two directories tweaked/ and stock/ both having extracted CM9 in them go into your tweaked/ directory and lets begin.... so some of the things you can tweak just from a simple extraction of the zip are as follows...
You can edit your /system directory and make tweaks as needed before ever installing the rom! .. just some of the things held in /system is the boot animation and it can be found at /system/media/bootanimation.zip its also a simple zip composed of images to be ran concurrent to appear as a single animation.. the resolution for the a100 boot animation is 1024x600 and a simple google search for either a100 custom boot animations or basically any low-def 1024x600 boot animation should work simply delete the existing bootanimation and copy the new one in its place.. remember NO MATTER WHAT THE DOWNLOAD FILE NAME is you MUST rename it to be bootanimation.zip or it wont work( I say should because I obviously have not tried every boot animation and I know there is a limit to the size for the acer animation so sticking with <6mb bootanimations should be just fine).. now if you decide to go further and extract the cm9 boot animation you will find part0( a directory), part1( a directory) and desc.txt.. the part0 and part1 directories hold the images that are to be ran and desc.txt simply states the resolution and then below that it list the directories that are included in the zip... part01 will be ran before part02.. for the novice I recommend just sticking to finding cool bootanimations already zipped for our resolution that some has posted for download so you can simply copy and past!...
also in system/media/ you will find a directory named audio.. dive into that and you find where the default sounds(aka ringtones, notifacations) that are stored for your fresh rom go back up a directory to system/media/ again and you'll see the video.. those are just some mp4's stored for the ROM.... that about it for editing in media.. lets recap.. you can basically edit/ change your boot animation and the default ringtones and notification sounds in /system/media... lets move back up to /system..
from /system you see another directory user/ ... lets go in there for a second.. what do we find.. MORE directories of course lol.. what else would we find... keychars( a directory) and keylayout( a directory) contain your configuration files for the input keys.. you can find things for the way game controllers and keyboards input are handled and what codes on keypresses.. now for our device if you proceed into keylayout/ (system/usr/keylayout/) you will see a file called gpio-keys.kl right clicking on that file and selecting open with and choosing gedit will bring up the file and you will see someything like
key 136 SEARCH WAKE_DROPPED
key 139 MENU WAKE
key 102 HOME
... and so on.....
these are what your hardware buttons do.. basically to explain whats going on is the key ### is the hardwired part... the SEARCH or MENU or what ever action you see is simply that.. an action to be called... and the WAKE_DROPPED and WAKE... well to be honest I'm not for sure what those do lol I assume having WAKE associated with a key would wake the device when pressed.. not for sure on that one thou haven't tried it.. but a quick google search and you can find list of commands that you can choose from.. one of them is being the command to call the camera.. so in essence you could bind any of your hardware keys to the camera function and it would open the camera... my little tweak to this file is to completely disable the HARDWARE HOME KEY... the only key on the front of our devices.. now I have seen some tutorials no disabling it by changing the...
key 102 HOME
... to ...
key 102 UKNOWN
... my problem with that is it does seem to disable the key.. sorta.. and what I mean by that is when you are in certain apps it will trigger the select/ hover action like if you were using a keyboard... so to completely disable it where it will call NO action simply DELETE that line! change ..
key 102 HOME
... to ...
... lol just delete that line out of the file and save it... voila! no more hitting it on mistake while playing a game or browser or w.e it is your doing *** note that this will not disable the light on the button.. it will still flash for notifications and the like...
alright once you have that saved you can exit out of gedit and go back to nautilus showing your extracted cm9 files go up your directory tree until your back in tweaked/ looking at META-INF/, system/, boot.img ... highlight all three of those... right click again and hit compress.. name the file myCM9tweak.zip or w/e you want to call it... make sure .zip is selected in the drop down menu of type of format to compress and compress... once its done you have an unsigned tweaked CM9.zip that if you didn't make any mistakes will boot.. and even if you made mistakes it could possibly boot and you will find your errors as you use it.. now if you just stuck with the simple tweaks I should you above you should be pretty safe and not worry to much about the device not booting.. if it doesn't boot a stock .zip then go back to your tweaked/ folder and try and find out what you did wrong and compress again about try it out! ... okay my fingures are tired of typing so I'm done with the tutorial for tonight.. well I might add more tonight but don't hold me to it... but this tutorial is in NO WAY finished... we are just beginning.. I haven't even showed you how to unpack-edit- and repack your boot.img to swap out kernals and from there extracting your initrd( aka "ramdisk") so you cant edit things at the very core of the ROM... don't be mad if you made the stock/ and tweaked/ directories and are wondering what the hell i had you make two directories of the same crap... just remember this tutorial is at its very begin if you plan on unpacking boot.img's with me then you need to just follow along... for what I have showed you tonight you can do this from windows of course and using notepad instead of gedit... for the advanced stuff sorry your going to need Ubuntu! ...
MORE TO COME...
--more simple system tweaks and mods--
--unpacking-modifying- and repacking boot.img's--
--extracting initrd's( aka "ramdisk") to make edits to the core of your rom and of course repacking them--
I hope someone finds some kind of useful information out of this.. tonight was pretty basic stuff but theres a lot more coming... including but not limited to a whole bunch of command prompt!
*~ENJOY~*
(please excuse any typo's.. I don't think theres any where it count's ..)
This is the guide I wish I had read the day I rooted, you rock man!
sent from your future.
hi. I'm trying to change the default dictionary in kindle fire, as it has no options for you to add or change any dictionary, im trying modificate system file
/ system / etc / labdictionary
substituting B003ODIZL6.prc
when I finish it works perfectly but if i reboot my kindle return with old dictionary o appers anything
someone could make the change dictionary?
i follows this instructions replace dictionary kindle fire, but the last part say:
"Tap the Clipboard icon and choose "Paste". Long tap the new "B003ODIZL6.prc" file and choose "More" – "Properties" – "Permissions: Change". Set the permissions like this and click "OK" to confirm."
but i cant see the image, there is no photo explaining
thanks for help, and im sorry for my bad english :good:
I suggest looking at the properties of the old file, the one that gets renamed to *.bak, and make the new file match those permissions. The instructions at that part are not clear, but what I posted should work.
I already tried and does not work
that part es confused, and i dont know its really work, i mean it work but not permanently
When you are finished, you should change the paths back to their original settings. He does not say this, but that area should not be left R/W. I think it should be mounted read only.
yes, i tried too, leave everything like original, and its the same, root explorer and properties
if i change for the original oxford dictionary and reboot, appears agains in english
Is the file changed in the directory when you reboot?
when put spanish dictionary, works. but and reboot and the dictionary doesnt work, the archive is there but when used dont see anything
when put original archive and reboot appears again english dictionary
Well, the guide is missing something. Native Kindle Fire users are all complaining that it cannot change dictionaries. It seems to me a rooted device should handle it. Need more file info.
:INTRO:
OK: here's the thread we are talking about and working on getting VoLTE & VoWiFi to work :good:. For now this is for the H930 Open EU variant only, it worked for two peoples incl. me, but I think this is applicable on other variants of V30, with respective edits (/OP, you'll read later), too. Maybe even to other phones? I don't know, LG is sth (=something) special This thread will rise with time I think, with different edits or ways to reach the goal: we want VoLTE/VoWiFi, sth, LG imho should've taken more care of...
I hope, my english is sufficient so everyone understands what's to do And, btw.: you should have "Allow OEM Unlock" switched off.
User @Krekos/CZ/ did help me in a special way: he zipped his modem config files I by accident deleted from my phone and uploaded them :good: Without them I would've not being able to complete this work, and therefore I wanted to say thanks again to him at this point (I think you can't hear this anymore, hm? ). He's btw. the second person for whom this worked, he's got VoLTE&VoWiFi now.
These files should work on other SD835 phones too, I link them here for archival. Eventually we can get a collection from every variant, this way we might be able to activate VoLTE etc. for a carrier on a phone which was not intended to being used with other operators. So a call to other variant users: can you please tar and upload these files to XDA? Procedere is:
Connect your phone via ADB and open a command prompt
type:
Code:
adb shell tar -czf /sdcard/mbn-files.tar.gz /firmware/image/modem_pr/mcfg/configs
Upload this file to your post here in this thread. I'll add it to the list then.
Links to modem cfg files (mcfg_sw.mbn):
H930 EU Open
US998 Open
These files need special permissions, of course... Otherwise it would be boring
The path (on a LG phone) for oreo firmware is as follows:
/firmware/image/modem_pr/mcfg/configs
For pie it's not /firmware/, but /vendor/firmware_mnt/: pls remember to change path in the following process accordingly when using pie.
Permissions are:
files 0440 system:system
folders 0550 system:system
Apply them via terminal emulator or adb:
Code:
cd /firmware/image/modem_pr/mcfg/configs
chown -R system:system * {apply to everything in this folder and subfolders correct user and group}
chmod -R 0550 * {apply to everything in this folder and subfolders permissions}
find . -type f -print0 | xargs -0 chmod 0440 {apply to files only (not directories) in every (sub)folder permissions}
:MAIN PART:
Prerequisites:
- H930 (or variant, later)
- rooted
- File Manager with root privileges
- eventually a decent editor of your choice
- and a little bit knowledge about giving permissions and changing owners/groups, if needed
I won't give help about e.g. files not editable because of problems with filemanagers or root, do the search work for infos and parameters you need, or anything else, sry You have to prepare and maybe investigate some time to find some infos. You have to know, that this can lead to a brick, if you're doing weird stuff
Let's begin with backing up your complete ROM via TWRP, incl. efs, data and all you need. Backup your OP partition too:
Code:
dd if=/dev/block/bootdevice/by-name/OP of=/sdcard/OP.img
It's about 344mb in size and can be restored in recovery or ROM, adb or terminal emulator:
Code:
(adb shell) dd if=/sdcard/OP.img of=/dev/block/bootdevice/by-name/OP
Then gather some infos, for now it looks we only need MNC and MCC, which identifies your operator. Maybe it later turns out that you need parts of your IMSI too. You'll find it in LG's hiddenmenu:
*#546368#*930#
Field Test => SIM Info
You can check, if the IMS Settings are available already. If yes, then there's a high chance you don't need the "some more config" part.
Write it down and have it prepared. Now the editing session begins
First we will load our modem config for our operator. The corresponding script somehow seems broken as it should do its work with files in /data/shared folder, which isn't.
These configs can give some extra parameters and contain infos about your operator / SIM provider etc.: Open your filemanager (and/or maybe editor, if isn't integrated in fm) and open the file "/firmware/image/modem_pr/mcfg/configs/mcfg_sw/mbn_sw.txt". Here find the path for your provider. O2 Germany would be "mcfg_sw/generic_/joan_glo/eu/o2d/o2d/germany/mcfg_sw.mbn". Append these = the complete path for your config file.
Code:
/firmware/image/modem_pr/mcfg/configs/mcfg_sw/generic_/joan_glo/eu/o2d/o2d/germany
Copy your op config path, you need this for one of the following edits.
Now navigate to the folder "/data/property". There should be three files we need. If they are not there, create them with root:root, 0600 and following content pls:
persist.radio.buffet_mbn_file => the long path you copied before
persist.radio.buffet_enable => enable
persist.radio.sw_mbn_update => 1
Otherwise just edit and save them afterwards. Perform a reboot and then check in hiddenmenu => Field Test = MCFG Buffet, if this file is loaded. Should
Some more config is needed. We now need the before told MNC and MCC and maybe the IMSI. We need to point your ROM in the right direction (modem itself is done): localizing it and giving the exact operator infos. Have a check of following files and a look, if they are configured already correctly for your operator, or you have to edit them.
/OP/client_id.xml:
Is your MNC & MCC inside? If not, copy and paste an example line, edit this one so it suits both.
/OP/OPEN_EU/config/carrier_code.xml:
Same as above, but a little more complicated. Explanation with an example line:
Code:
<profile carrier="O2D" suffix="O2D" carrier_code_fast="" carrier_code_late="TLF" country="DE" mcc="262" mnc="07" mvno_type="imsi" mvno_match_data="26207200xxxxxxx" />
"Profile carrier": you find this in the long path to your .mbn file you copied before O2D is O2 Germany, edit this to fit your sim provider.
"suffix": same
"mvno_match_data": this is part of your IMSI. When your provider is already listed, compare the five numbers after your operatorcode: 26207200xx. This all together has to be the same as the first ten numbers of your IMSI. If not, edit it. This is one of the reasons for VoLTE chaos on O2D, but that's another story.
/OP/OPEN_EU/config/com.lge.ims.rcs.xml
Same as above: copy and paste a line of simoperator section and edit with your operator details. "prefix" is your country calling code.
/OP/OPEN_EU/config/featureset.xml:
Change every item which is "false" to "true"
/OP/OPEN_EU/config/vo_config.xml:
Most likely you need to create an entry for your operator with mnc and mcc. do this and change both variables to "1":
Code:
<info mcc="262" mnc="07"><!-- O2D (you can write anything here or leave it, it's commented out)-->
<prop
support_volte="1"
support_vt="1"
/>
</info>
[b][i]Maybe[/i][/b] for some rare cases this is the only edit you need to do to get VoLTE & VoWiFi running :D
Reboot now, then continue. If sth in custom.prop or build.prop is edited the wrong way, this can cause bootloops, so you don't have to do the beforedone work again. And: when something in general went wrong in /OP directories edits, you can dd your OP partition back.
/OP/OPEN_EU/cust.prop (they're all case sensitive):
ro.lge.capp_cupss.rootdir=/OP/OPEN_EU
ro.build.target_operator=OPEN
ro.build.target_country=EU
ro.build.target_region=EU
ro.product.locale.region=your region, e.g. "DE" for Germany
ro.product.locale.language=your language, e.g. "de" for Germany
ro.lge.cupssgroup=GLOBAL-COM
ro.lge.opensw=EUR-XX
ro.lge.radio_mcfg=1
persist.lg.ims.volte_open=1
Reboot.
/system/build.prop:
ro.product.locale: change to match your language
ro.lge.capp_cupss.rootdir=/OP
ro.lge.capp_cupss.op.dir=/OP
Reboot again .
:0UTR0:
The VoLTE and VoWiFi switches should be present now, a) in Phone Settings (both) and b) in Network Settings (VoLTE). We should now be able to hop into IMS Settings. You find it in LG's hiddenmenu => Field Test => IMS Setting.
First we let the IMS setting show an icon in statusbar, this way we don't need to dial the hiddenmenu code everytime we need the settings. A nice sideeffect: it shows if you're connected or not To do this tip on "Test" and activate "Show Icon". After that go back to the main screen and scroll down to "GPRI VoLTE/VoWiFi". Here you can activate VoLTE/ViLTE/VoWiFi/ViWiFi, depending on what your provider offers in your contract. Go back again to main screen, go into "Test" menu, then "Load Preset Configuration" => "Initialize configuration". Now you can do a reboot and press a thumb: maybe this was it and everything is up and running! Maybe...
For seeing if VoLTE is up you can check "Debug Screen" => "VoLTE Debug Screen" inside IMS setting.
You can also turn on VoLTE and VoWiFi indicators/symbols, which are then on the right side of your statusbar near the clock. In IMS settings: => "GPRI VoLTE/VoWiFi" => "Registration" => "VoLTE" => "Indicate VoLTE", and the same for VoWiFi. To be able to place a call in flight mode but with WiFi calling on, enable "Airplane Mode" in VoWiFi menu.
In case you experiment with IMS Setting and suddenly a com.android.phone (or other) fc occurs, you can boot into TWRP, mount data and delete the directory "/data/user_de/0/com.lge.ims" with its integrated filemanager.
K, you're done :cyclops: Pls give feedback how it went for you!
Wow. Thank you.
yeah, I hope it's written in a way everyone understands it atm it's more like a dev thread, it will be rewritten for newbies when everything is clear and fully pointed out
.. Uploaded stuff ..
Hi - thanks for this info. I'm trying to work with it, and added my files. + a few extras stuff> actually not really sure how to do this .... any help? ... Thanks I have a US998 phone.: but want to get the Canadian settings all working ; specifically for Freedom Mobile ( aka : Wind ) --- the files are from a saved backup ( dump ) {{ the uploaded files are from a backup of the H933 canada firmware dump }} ... I'm currently using the US998 kdz firmware on the phone ....
let's start with
- do you see "MCFG Buffet" in your hiddenmenu?
- can you list all the content (the main directories) in your /OP folder pls?
- does the firmware modem config folder exist and is your provider inside?
- and where does your ro.lge.cupssgroup point to? (adb shell getprop ro.lge.cupssgroup)
I don't know the specialities of other variants, especially the offered providers. I don't even know if this is possible and which files you uploaded to your phone. can you either list them or point to them with a link eventually?
OK thanks - I'll work on this some more tomorrow -- I don't know where the files I uploaded went to! > but I uploaded >Folders>>> Carrier Config, Modem_pr, qcril_database, vendor, wifi & build.prop. All files were dumped from a working Phone loaded with the Canadian .Kdz H933. ... > ok so I actually took all those files,and overwrote the files om my current phone setup which is US998 .Kdz -- didn't even crash the phone <<< Go figure. I just had to clear the cache and dalvik cache. VoLTE may be working, but my Carrier has a very limited VoLTE service... so I cant check right now. VoWifi is not working. Every setting and menu has it turned "on" but is no working. .... tomorrow I'll follow your instructions after I do a fresh install. of the .KDZ. ..... be well
be warned: this can be time consuming and causing headaches, too stock files would be the best to start with.
is it a native us998 phone? it's the one one can "frankensteining", isn't it? you've overwritten these files and partitions, when I understand you correctly?
you should get hands on following stock partition disk dumps and folders first (kdz won't help as all these files are preloaded and can't be flashed via kdz):
- canadian OP partition (the more important one) (canadian_OP.img <= example filename)
- US998 OP partition (for being able to revert back to stock and trying to get volte/vowifi running with only some edited files on stock us998 partitions, only a few added files or maybe folders from canadian OP partition and only the .mbn file for your provider, taken out of firmware modem config folder). this one shoukd be flashed and worked with.
- stock system image (kdz flash us998)
- clean unencrypted data partition (factory reset and then completely set up with your apps and settings, no db or ither files copied).
- you've got a backup of your stock efs partition?
try to keep your phone as clean as you can as this can only be of help about not being confused. are there gsm/(w)cdma/band differences between us998 and canadian 993?
this could go an interesting way let's see, maybe we get it is wifi calling enabled on your contract? I wasn't able to determine this out of your post.
there's the possibility to edit the thresholds when wifi calling aborts and switches to cell telephony or volte. it's located in /system/etc and inside a filename called "andsf_your_provider_code.xml", for o2 de it's named "andsf_26207.xml". I've set every threshold to -90, this way wifi calling is still working with only one or two bars wifi reception. otherwise it would abort just too early and switches to other telephony bands.
US998 mbn-files
Thanks for the detailed info.
Not working for me. I managed to add my operator and enable IMS but can't figure out how to make IMS register. Might be because my operator is a little more retarded and uses IPv4 only. No idea where to set that policy, it isn't in IMS settings anymore on the V30.
sounds like setup session in IMS setting. go into gpri volte/vowifi setting and try enabling volte and vowifi only, then tap on "call" menu entry. choose "volte" and tip "use sip preconditions" there, use the same setting for "vowifi". check "subscription" in main menu and "IMPI" there: is there a connection adress inside? example:
your_imsi@ims.mncXXX.mccXXX.3gppnetwork.org
replace mnc and mcc with yours but add a zero at the first place of your mnc. for o2 de's mnc which is 07 it looks like
your_imsi@ims.mnc007.mcc262.3gppnetwork.org
then try test menu and restart ims process. or perform a reboot.
but you'll have to investigate more, for yourself. what's your exact provider and mnc mcc?
edit: can be you need an IMS apn for your provider. in it you can set the protocol versions. what's logcat telling?
Hi. Thanks for this. Is there any way that this can be applied to aosp ROMs?
Those mcfg files are found inside the modem partition and you can pull them out from any kdz.
Do you have an idea where this is located? (/nv/)
Edit: Also, added some picture showing volte working... when it's not (switching back to something else)
you're really sure about this? since I've flashed a kdz and a modem and unfortunately this didn't bring back these files on my phone maybe I did sth. wrong, this is really interesting now. thought they were on efs partition; but these nv files should be on efs. I'm not really sure about that, maybe someone other can finally confirm :good:. edit: I remember I've got carrier services installed, would be interesting if this makes a difference. I hardly believe but try it:
https://play.google.com/store/apps/details?id=com.google.android.ims
about aosp: there's much more needed, proprietary files and more config inside sources etc pp. I evtl. wanted to do compilings again in winter, I wanted to try this but I need additional ssd space before
Oh sh*t...
I guess I lost my efs partition then...
I tried a bunch of stuff from your first post... sadly, I don't have an /OP/ directory at all... and when I try to force the mcfg mbn (from my sdcard lol, cauz my carrier is not provided in the us998 modem)
Edited a bunch of stuff in my build.prop to make it look more like the canadian one.. but it still doesn't work (even lost the volte option now in the mobile setting menu..)
Also, I tried to flash my canadian modem files... sadly.. the phone boot but the modem doesn't initialize at all... (no wifi and no mobile network)
aye, sh¡t... and there's no efs backup from your phone done / available as it sounds. you lost your IMEI too??
can you check the directory
/dev/block/bootdevices/by-name
and see if there's an OP "file"? eventually only the script which mounts it is broken. if I remember correctly there was a thread about regathering the IMEI or at least fixing some stuff on efs. maybe this helps you, unfort. I don't know where it was, you have to search yourself.
k, sleeping now, it's hard for me these days after my shoulder operation... hopefully we get your phone back running! I'm optimistic flashing a efs backup and changing the imei back to your original one for example. don't know if this is possible, but how often did I think "sh¡t, now it's over, phone's bricked" and then a solution appears out of nothing. you should've seen my face in the moment volte came.up on my phone xD xD xD
see you later be optimistic!
Oh sorry! I still got my efs partition.. I thought it would get overwritten when doing the frankenstein method.. But I guess not.. Is there any way I can debug why the modem doesnt work at all when flashing the canadian one while using the us998 system?
there is but I don't have it in mind atm it's explained here at xda somewhere, logcat and dmesg is used for that :good: can be that it is bands related? so you have to unlock bands in your modem settings? edit: most likely not as wifi is dead too...
seadersn said:
sounds like setup session in IMS setting. go into gpri volte/vowifi setting and try enabling volte and vowifi only, then tap on "call" menu entry. choose "volte" and tip "use sip preconditions" there, use the same setting for "vowifi". check "subscription" in main menu and "IMPI" there: is there a connection adress inside? example:
your_imsi@ims.mncXXX.mccXXX.3gppnetwork.org
replace mnc and mcc with yours but add a zero at the first place of your mnc. for o2 de's mnc which is 07 it looks like
your_imsi@ims.mnc007.mcc262.3gppnetwork.org
then try test menu and restart ims process. or perform a reboot.
but you'll have to investigate more, for yourself. what's your exact provider and mnc mcc?
edit: can be you need an IMS apn for your provider. in it you can set the protocol versions. what's logcat telling?
Click to expand...
Click to collapse
I already tried to set IPMI with my data like [email protected] but IMS still don't register and the setting doesn't stick. it always reverts to a default like [email protected].
I also created the ims APN but it doesn't help with anything.
I'm still digging but so far I have no clue what's going on.
hmm, did you try configuring sip telephony? for o2 germany the registration looks like
country code + phone number @ telefonica.de = (for germany) [email protected]. have a look at /data/user_de/0/com.lge.ims/shared_prefs/impu_list.xml
(user_de: I don't know if this is indicating the language the rom uses? so for an english language build it can look like user_en? I don't know...).