Hi masters!
I read a lot about editing software but i've special challange so here we go...
1. We've got flashtool and soft for device on android and we want to change text under icon camera in menu from "Camre" to "Camera"(little mistake in china). I know that it's simple but i want to know how to do it in professional way.
2. When we install software on our device1 picture is project on lcd in wrong resolution. We know that correct driver for our lcd is in software for device2 so we need to take this form device2 and replace it in software for device1. I can send a good and tasty bootle of vodka for this help. I'm waiting
Related
Dear all,
As I write I have a Lenovo ET960 sitting on my desk, which is lying there for the last 2 weeks as I am unable to figure out how to change its menu language from Chinese to English. My uncle who was never able to use it gave it to me after all these years. It has WM2003SE (I think!), although I am sure the experts here will know all about it. I am very keen on fixing this issue, the trouble is I am novice in this area.
I have done some background research, but I still need some help from all you guys here. I have the the following requests.
1) I understand that there is no way to change the language of this phone as the OS is hard-coded in the Chinese ROM. One way is to hack this Chinese ROM and change it to English using a HEX-editor. An alternate way would be to use a third-party software to change the language, however I could not find one for WM2003. Once I hack the ROM and make the necessary changes, I should, in principle be able to install an upgrade to WM2003 (which I also do not have with me!).
To hack the Chinese ROM in ET960 and solve this issue I would need to know two things:
(a) Where to locate the ROM in this pocket PC using my desktop PC (via a USB cable connection)?
(b) I need a reference ET960 ROM (ET980 ROM may also work!) in English to compare the values to change accordingly.
(c) Finally, an upgrade to WM2003/WM2003SE (the firmware upgrade d/l link) and the upgrade method.
Now the trouble is I have never flashed a ROM before, so I need to know the steps. In addition I would also need to know the steps to the upgrade process.
I have managed to download the following softwares/tools which I think will help in the process, but I dont want to start the process until I get some feedback from you guys here.
(1)The lenovo.zip file _ftp: / / ftp.roverbook.com / RoverPC /Lenovo_ET960/
and the (2) ET960update.exe from gsmforum.ru, which can be used as an update tool for both Lenevo ET960 and ET980. I have also managed to download the upgrade instructions, but only in Chinese!. This is where my research ends. Now I request you guys to help me with the missing links to convert my ppc into English.
Thanks,
Jay
This Thai review (use Google Chrome and translate it to English) states the following:
Languages: Support English, Simplified Chinese, Tranditional Chinese Input but can not display Traditional Chinese character.
The screenshots also show the phone is using English. It might be as simple as changing the system language in your MUI settings (in the registry: HKLM>MUI and change SysLang to 1033 Dec/0409 Hex...HKCU>MUI and change CurLang to 1033 Dec/0409 Hex).
Hi rete, Thanks for the reply. I have never edited the registry in a pda. Is there a special tool that I have to use for editing the registry? The ET960 I have with me has a interface similar to this _http:/ / video.pomoho.com/ent/762870.
As everything is in Chinese, I am unable to make head or tail of anything. Please guide me if possible. Cheers, Jay
I am getting back to my ET960 issue after a gap. I really want to make this device (which has a great design) usable, for which I will need to convert the user interface to English.
Rete, I made the registry changes you suggested but nothing changed. So I will need to to find an alternate solution.
The ET960 has WM2003SE (ROM version: S603 051229 which is not WWE). It displays all the system folders as well as some of the installed applications UIs in English. But most of it is in Chinese.
I installed an English localization software (Paragon Inc, LEng for WM6) which translated my ET960s interface completely to English. But, the ActiveSync stopped working and the system folders could not be accessed after the installation of LEng. This tells me that if I can replace the *.mui files from CHS to ENG in the ROM, I will get an English interface.
But the trouble is that I am new to all this and do not know where to start. So I request for some guidance.
The other option to make the device usable is to boot Android from a microSD card, but I could not find an Android version anywhere from my ET960 (which has similar hardware to MDA compact & Yakumo Omikron). Please advice.
Hello
[INTRO](a little background)
This is a guide for those who want to have their phone in their language but the operating system does not have it built in. You can flash a new ROM that has it or install an app right? Not so much. There are reasons for these methods to fail or simply not work for your situation. My problem was that the bootlegged hardware was not supported by the official ROMs or the Android community. This forum is also riddled with threds that started by people who need to mod something about their phone but have no technical knowhow. There wouldn't be annything wrong with that exept that the awnsers in these threds are something along the lines "Oh you just need to do this thingnemabob" that's it one sentence pointing to a technical slang word that means nothing to anyone but a seasoned developer despite first post DIRECTLY STATES IT WAS MADE BY A PERSON ASKING FOR A STEP BY STEP SOLUTION OR A LINK TO A TUTORIAL!
[pre-procedure]
List of necessary software:
Zipsigner (this goes on your phone)
ADB
text editor of choice( notepad++ recommended)
AIO-Flasher
smali/backsmali (depeding on wether your system files are odexed more on that later)
APKstudio
[installing above software]
Zipsigner
Why you need it?
As you modify your apk files their signature changes. Basically if you change anything about them the phone will no longer recognise these as "its" therfor you need to convince your phone that these are in fact okay with zipsigner.
how to install?
This is an app. If you ever installed anything from Google playstore before than you know how to install it. Go to your Google play store app on your phone. Search for Zipsigner and pick the top app. Agree to all the demands and tap on install
ADB
why you need it?
this is a command line piece of software. these might be very scary to use but don't worry follow the tutorial and you'll be okay. That aside what is it used for. ADB is a powerful tool but we will use it only to copy and paste files to and from Phone
how to install it?
ADB comes packed up with Android Development Kit so the easiest way to install it is to get the ADK
[STEP 1]
Okay so you want to translate your phone for one reason or another. Make backup! Backups are important. You want to have something when you fail to fall back on. Yes "When" you fail. Not "if" you fail. You will screw up but as long as you have a proper backup everything is okay.
You can back up your phone in few different ways.
Hello
[INTRO] (skip if you are not interrested in fluff)
For the past week I lived in Android Hell looking for what I thought would be a simple procedure and I wanted to share my expieriences somewhere so that no one else has to go through this flustrating expierience.
I got two phones (Galaxy S5 and Galaxy S5 mini)and I was taked with translating them. Well It should not be a problem I thought because it should be as easy as going into [settings]>>[region and langages] and choosing Polish. There is no Polish. So that was my first step towards the translating thiese.
[STEP 1]
First thing first backup. I am by no means a talented programmer or modder so I went with Samsung Kies but software didn't recognise neither phone. After fiddling with drivers and a back-and-forth with samsung costumer support we came to conclusion that phones are fake. IMEI of one identifies it as a Blackberry and other as Nokia >_< well okay they still have some sort of Android so there should be a way to translate them anyway. First thing on the agenda is still backup. So I went through a triall and error to get both roms dumped. I was successful with ANDROID AIO FLASHER which was a godsend after I failed time and again to push romdump's INSTALL into the phone. I managed to get one ROM off by now but other Phone still insists on denying me ability to dump the rom because of Segmentation error. but at least I have one rom backed up.
[STEP 2]
Okay I got myself ROM now what? I decided to make a transfusion. Why bother with getting down and dirty when you can just use the work of others. So I downloaded a ROM with same version of the Android OS and begun looking for language pack or something similar. No luck this is not how Android works. After some research I came to the conclusion that in order to make things work I need to basically decompile each and every APK file that refers to system functionality and translate Strings.xml by hand in order to ensure compatibility.
[PRESENT DAY]
this is where I am now. all I wonder if there is a way to add a new file in the APKs with polish in it or should I just translate English "strings.xml" file and set langage to english?
Feel free to point out faults in my logic as well as provide tips and tricks for those of us who bought our phones on the cheap and just want to usethem with language they are comfortable with. I will build up this topic with factual information that I come across and try to make this into a universal guide to Android translation with resources to download. I do this because no one should be subjected to this and there is no decent step by step guide on this forum just disjointed and incompleate information in posths here and there. Belive me I looked both here and Google and after two weeks of finding nothing more than a hints I want to just give back to the community all I found.
Not sure if I'm posting this in the correct place but, here we go.
I am being asked to install work related software on a personal device by an employer. The device in question is a Samsung Note 3. Due to the software being work related, I can't mention what it is or what it is for.
Since I am unsure of what exact changes this software will make to my device, or what features will be disabled or locked down, I would like the ability to run a utility that will record the exact changes that are being made so I can revert them after I am done with the software.
I have used software like this before for a Windows system. It made a log of where files were placed and what changes it made to files, system files, registry, etc. Basically a snapshot of before and after, with the ability to view the changes made.
If anyone knows of a utility that can do this on an Android system, the help and recommendation would be greatly appreciated.
Stock KK rom for my phone have a big problem in LK.BIN module, LCD driver is not choice correctly.
I opened the file with a binary editor and i can see there are 3 LCD driver included the correct driver for my display, but auto detection choice the wrong one, so only random lines appear on screen.
There is a way to modify LK.BIN to remove the wrong driver and leave only the correct one?
Or there is a way to force manual detection of display driver?
ilmira said:
Stock KK rom for my phone have a big problem in LK.BIN module, LCD driver is not choice correctly.
I opened the file with a binary editor and i can see there are 3 LCD driver included the correct driver for my display, but auto detection choice the wrong one, so only random lines appear on screen.
There is a way to modify LK.BIN to remove the wrong driver and leave only the correct one?
Or there is a way to force manual detection of display driver?
Click to expand...
Click to collapse
I would recommend taking a look at this article, which also deals with modifying the little kernel binary file. If you can figure out what lines are dealing with the other display drivers and comment them out or remove them, another resource would be this online dissembler that tells you what's going on in the code. As always make a backup of the unmodified file and be very careful as you could modify the file to the point where the phone won't boot or display anything at all.
thanks a lot for your answer, but there isn't any useful info in links you gave me.
what else i can try ?
ilmira said:
thanks a lot for your answer, but there isn't any useful info in links you gave me.
what else i can try ?
Click to expand...
Click to collapse
What is the model and manufacturer of your device?
shimp208 said:
What is the model and manufacturer of your device?
Click to expand...
Click to collapse
my device is a Mediatek based phone, model Doogee DG2014
No other ideas?
ilmira said:
No other ideas?
Click to expand...
Click to collapse
Sorry for the delay in getting back to you another idea would be going into the engineering device menu from the dial pad and seeing if you change things that way sometimes you can do it that way.
Are you sure there is an option to select LCD driver inside engineer mode menu ?
ilmira said:
Are you sure there is an option to select LCD driver inside engineer mode menu ?
Click to expand...
Click to collapse
Other people have mentioned similar options before on Mediatek based devices however sometimes not all engineering mode menu items can be used.
Hi there,
I am a photographer and have almost complete my 8-year journey of developing [the ultimate digital photography workflow] .
If it was not for this problem I need your with help
Everything works but.... : PLEASE HELP.
----------
TLDR:
Snapseed can't open raw files, Let this please just be a simple Build.Prop edit that tricks Snapseed into thinking the emulator is a compatible device.
-----------
Full Story:
Part of the workflow does entail editing the raw files in android running emmulated on a windows machine.
Everytime I try to open a .ARW file with Snapseed running on various android Emulators* it will give me the following message which I do not get on my phone (Oneplus 3T).
Snapseed, The ultimate workflow killer
The research so far got me to edit the Build.Prop with the line:" 'persist.camera.HAL3.enabled=1'
Something that is supposed to make the CAMERA2 API work.
Link:https://forum.xda...579
This was based upon the assumption I drew from the quote below from a google help forum in which a Snapseed developer basically was hinting that the error has something to do with RAW support of the phone in general. quote:
Quote:
RAW capture on Android has similar requirements to Snapseed with RAW. That's why I say that if it can capture RAW, it probably supports RAW in Snapseed. Some devices that can capture RAW need a third party camera app to use it.
Bonus tip: Camera apps with RAW will disable it if the phone/tablet doesn't support it.
-Zach
link:https://productforums.google.co...orum/snapseed
-------
Possible solutions?:
-This does give me at least some hope that there is some other thing (Build.prop.-wise) we can do in order to make Snapseed open and edit RAW (.ARW) files.
-Maybe someone with know how could look at the actual code of the APK of snapseed in order to figure out what we could change? I am not technical any further than rooting and flashing a rom once in a while.
You would be of serious help, finding out how to make this work.
For what matters, you will be helping me creating art, my Instagram page:
www.instagram.com/thi_js
Greetings from Amsterdam,
Thijs.
PS.
Ofcourse I will share the final workflow if it will see it's complete light someday. (Since it only works as a whole)
(*I know there is something like Phoenix and Remix OS that do not have this described problem, It does however give rise to the the BIG problem of not being able to calibrate the display with a remote callibrator tool (Idisplay) . If ran on an Emulator the windows in the background will still provide the just and real colors) Emulators I tried? : Memu, Andy and NOX show the same error)
Possible other angle:
Quote:
For the OP problem I was having the same error and it was because my phone doesn't have the RAW capability, meaning the CameraCharacteristics.REQUEST_AVAILABLE_CAPABILITI ES_RAW (https://developer.android.com/refere...PABILITIES_RAW), so the mCharacteristics is never set.
You can remove all the RAW references and implementations and it should work.
from:
https://github.com/googlesamples/and...a2Raw/issues/2
Someone?
bumb