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.
Related
This a small application I wrote to automatically retrieve the DeviceID on your PC without having to open the registry editor. It can also create the DeviceID.txt file with the id value stored. It's written in Java so it requires JRE to be installed (most of you already have this)
http://rapidshare.com/files/403680176/DeviceID.jar.html
Make sure you have Sony Ericsson Update Service installed otherwise the device id will not be created in the registry
UPDATE: App updated to show all Device Ids stored in the registry
still dont work for me
windows 7 x64
It's been downloaded too many times (10) for a Free Rapid Share account, it is no longer downloadable, you'll have to upload elsewhere
Balur said:
It's been downloaded too many times (10) for a Free Rapid Share account, it is no longer downloadable, you'll have to upload elsewhere
Click to expand...
Click to collapse
new link posted
Hi !
As you can see I have more Strings in the registry ?
Whats your methot of determining which is the right one as they all show different DeviceID Strings ?
THX
pietropizzi said:
Hi !
As you can see I have more Strings in the registry ?
Whats your methot of determining which is the right one as they all show different DeviceID Strings ?
THX
Click to expand...
Click to collapse
I always get the first one, there is no way afaik to determine which one is getting used at any point. I can maybe change it so that it displays everything and lets u select the one you want to use
Well the point's not what I want to use, it more what's the right one at time of flashing. Is it save to delete those keys so the right one is rebuilt inn case of reconnecting the device ?
it's really not easy to find which one is being used at any point. i don't know if it's safe to delete them from the registry, although i would suspect that it is. just make sure you use the same usb port whenever you flash. that way you avoid overcomplications with this issue
THX for the info. I'd try to find out the right one.
In my case it was the second key found, not the first!
So this tool does not work for everyone.
Hi,
I first tried the method below:
Is someone trying to develop a Custom ROM for the Huawei Ascend G600 (U8950D)?
http://forum.xda-developers.com/showthread.php?t=1943003
But the phones are not just different band versions, as mentioned in post 58 of the thread above. The T8950 is not kernal compatible with the U8950D:
http://www.jetdroid.org/forum/viewtopic.php?f=106&t=8383
Indeed, the T8950 is equipped with MTK6517 dual-core processor, the MT6517 and MT6577 are the same, A9 architecture 40nm processor, clock ed speed is 1.0Ghz.
http://defendgun.com/2013/01/22/mobile-customized-huawei-glory-t8950-listed-price-at-261/
I don't pretend to have any knowledge about rooting phones, I just was able to find the correct information on the web. I spend two weeks figuring this out. So I hope I can save somebody else his time with this information.
this is how I did it.
UNLOCKING THE BOOTLOADER
--------------------------------------------------
the bootloader of the T8950 is not locked, so it does not need to be unlocked. Allight, step one done!
INSTALLING THE CMW CUSTOM RECOVERY TOOL
------------------------------------------------------------------------------
The T8950 does indeed not have a fastboot mode. the CWM custom recovery can be installed by flashing the ROM using the Flash tool of Mediatek
tutorial: http://bm-smartphone-reviews.blogspot.com/2012/05/mt6575-flashing-tutorial.htmlthe correct files to use in the tutorial can be found here:
- SP_Flash_Tool_exe_v3.1224.01 --> http://www.mediafire.com/?c8lr368ceaqk7tv
- MediaTek DA USB VCOM drivers --> http://www.mediafire.com/?h0ytkyagj0kf89u
if all went well, you should have a different recovery screen now.
ROOTING
-----------
Tutorial: http://bm-smartphone-reviews.blogspot.com/2012/02/complete-guide-to-clockworkmod-recovery.html
The fileto be used is:
- RootT8950.zip --> http://www.mediafire.com/?je47wz2ozjr7oth
After the update is finished, reboot . Now, you should see Superuser in your Huawei T8950 app list. You can double check if you have root, using the "got root?" app.-->https://play.google.com/store/apps/details?id=com.island51.gotroot
INSTALLING THE GOOGLE SERVICES
----------------------------------------------------------
Since the the CWM custom recovery tool is installed now and the phone is rooted, it's very simple to add the google services to the phone. I used the GAPPS of Cyanogen. You can find them on many places, e.g.
http://www.needrom.com/mobile/gapps-cyanogen/
choose the right version, most likely your T8950 will have android ICS 4.0.4
istallation is the same as installing the rooting ROM
REFERENCES
----------------------
http://bm-smartphone-reviews.blogspot.com/2012/05/mt6575-flashing-tutorial.html
http://bm-smartphone-reviews.blogspot.com/2012/02/complete-guide-to-clockworkmod-recovery.html
http://www.aiothudanu.com/2013/01/huawei-t8950-install-cwm-recovery-and.html
http://forum.xda-developers.com/showthread.php?t=1911475
http://www.needrom.com/mobile/gapps-cyanogen/
Regards,
TeTTiweTTi
Hey TeTTiweTTi!
I can not say how glad I am that you wrote this tutorial. It seems that this is actually the only tutorial on how to truly unlock the T8950 (at least for non russian-speakers )
Still, I'd have some questions:
How do you install the VCOM driver? I downloaded it, but I can only find .inf files.. How do you install them?
Did you flash the whole ROM or just a part of it, as shown in the tutorial? And what exactly happens when you flash the ROM? Are you able to boot afterwards? It seems to just install CWM - right?
How do you apply the update RootT8950.zip?
Help would be appreciated a lot, since you seem to be the only one who knows how to properly do it
Oh and btw: did everything work for you after flashing the ROM? Or did you encounter any errors?
Cheers,
amannn
Hi, it was indeed not so easy to collect these bits and pieces together
here an answer to your questions
1.
The .inf files are the drivers. There are two ways to install the drivers. One way is to right click on the .inf file and choose "Install". The other way is to start the process with SP Flash Tool and as soon as you plug in the phone a new device will be detected and you have the choice to install the drivers.
Also, it is very important to make sure that you click "Download" first before you connect the device. Actually there is a trick, below the sp flash tool, you will see something that says "USB". Click "Download" and wait for the "USB" to become "Searching". Once it is "searching" then connect the USB. SP-Flashtool should be able to capture it before it disconnects itself again.
2.
yes, you only flash a part of the ROM, so you don't need to have all the files in the SP Flash Tool. Only the ones mentioned in the tutorial. Your phone will boot normal, nothing will be changed yet. But now you will have the CWM custom recovery when you start up in recovery mode.
3.
the linked tutorial is quite clear. Let me know if you cannot reach the page or you encounter a problem.
Regards,
TeTTiweTTi
Sent from my ASUS Transformer Pad TF700T using xda app-developers app
Hey TeTTiweTTi!
Thank you very much again for your detailed explanation!
So i think I've installed CWM recovery successful. Therefore, I'm now working on the rooting part.
The RootT8950.zip file needs to be applied, using the "choose zip from sdcard" option from CWM recovery right? When I choose that option, I encounter the error "E:Can't mount /sdcard/". Also when I'm trying to create a backup, it says "Can't mount backup path.". So it seems that there is a problem with accessing the sdcard. I then tried the "mount /sdcard" option, but it also says "Error mounting /sdcard".
Did you have any problem like that? When my phone is booted up, there is no problem with accessing the sd card... Or is there a option how I can check if the sd card is inserted correctly? I guess it's internal and therefore impossible to even remove it..
Your help would be highly appreciated!
Many thanks in advance and best wishes,
amannn
EDIT: I was now able to upload the update with an external micro sd. Therefore everything works so far - thanks again
Similar phone mtk6517 svp s580
Hi
I have this. svp. Phone with ARMV7 ( see cpuz snapshot
)
It says mkt6517 with A5 cortex
I tried jnstalling all drivers linked here for ADB
but windows xp disqualified em as valid drivers for this hardware
Finally I got android device driver to install on
All 3 devices ( see pic- there are 3 devices
That show up )
I don't think this generic driver is the right one
So rooting this is still not done .does anyone hace luck with this device
Any idea ......? With getting the right driver and root
Procedure
I tried eroot too amongst other rooting s/w's
CPU screenshot
CPU screenshot
sieger007 said:
Finally I got android device driver to install on
All 3 devices ( see pic- there are 3 devices
That show up )
I don't think this generic driver is the right one
So rooting this is still not done .does anyone hace luck with this device
Any idea ......? With getting the right driver and root
Procedure
I tried eroot too amongst other rooting s/w's
Click to expand...
Click to collapse
Hi sieger007,
It can be a little bit tricky to install the drivers, since it are .inf files only. But these are the driver files
http://bm-smartphone-reviews.blogspot.be/2012/05/mt6575-flashing-tutorial.html said:
There are two ways to install the drivers. One way is to right click on the .inf file and choose "Install". The other way is to start the process with SP Flash Tool and as soon as you plug in the phone a new device will be detected and you have the choice to install the drivers.
It is very important to make sure that you click "Download" first before you connect the device. Actually there is a trick, below the sp flash tool, you will see something that says "USB". Click "Download" and wait for the "USB" to become "Searching". Once it is "searching" then connect the USB. SP-Flashtool should be able to capture it before it disconnects itself again.
Click to expand...
Click to collapse
This second way worked just fine for me.
You can find the drivers and tools also here
http://mt65xx-tools.4shared.com/
he password to login is bm-smartphone-reviews.blogspot.com.
But always make sure that you trust the sources of the ROM you download and know that it is meant for your phone. After flashing a wrong preloader, your phone will be completely dead (can't be powered on, it will not charge and won't be detected anymore by the computer) and there is no way to recover it.
In order to root you first need to install a custom recovery. In this case it is CWM.
hope this helps
still stuck in driver hell
thanks for your help . I had a previous Chinese MTK (MT6575 ARM A9 cortex ) phone , whose ADB drivers successfully installed when I installed the SDK .
Now this one is MTK6517 ARM A5 Cortex. and none of the methods ( #1 or #2 ) help, in those drivers being recognized.
By method #1 : Right click install - It maybe just copying the driver file to system folder and then on windows would auto detect it when the device is inserted -assuming there is a match .
Method # 2 : Uses the new h/w found dialogue . Not sure if invoking sp_tool is related anyways in invoking that dialogue . It shows up anyways - soon as you plug in the phone .
I could not get the driver files in with the blogspot password to be recognized . Kept giving me "specified location. does not contain info about your h/w msg"
I have the EXACT same problem with ALL drivers hunted on the net , that say MTK driver. Some files say MTK65xx some say MTK_USB_Driver etc.
the h/w ID's and instance IDs associated with the devices are attached .
USB\VID_1782&Pid_5d04&Rev_0229&MI_01
Now the driver.inf file did have one ray of hope with this mention ..wonder if that'd make it compatible with a modified inf file.
But I am lost about HOW to add the h/w ID info ( format and what specific data to add ) to the inf file -most data is of the form VID_eXXX something in that file ( see below quote )
MT6516 USB VCOM drivers\readme.txt
Code:
3. Customers can customize usb2ser_XXX.inf file.
There is a string in the file:
MTK6218 = "USB Modem Driver"
You can modify it for your product name, for example:
MTK6218 = "MY_PRODUCT Modem Driver"
The other perplexing thing is that there are 3 Devices that show up under XP device manager. I managed to get one of em installed as device "android phone" with driver "android ADB interface" from Google and can possibly manage to get ALL of em installed the same way since those device ID's are close ( the last '1' becomes 2 and 3 respectively ) in this
Code:
USB\VID_1782&Pid_5d04&Rev_0229&MI_01
After pushing all these device ID's as "android ADB interface" - and attempting to root- the android rooting s/w's will NOT work at the identification step , erring out with "ADP device not found "- conclusively indicating that those drivers probably did not work well and I ought to look around for better ones - something I am trying to address by this thread.
Lastly - sp_tool when you start it - it will ask for scatter file. The scatter file out there is for MTK6577 (vs my model 6517 ) . If I choose that file - it gives me a warning - yes it out - and click download - it will then just freeze doing nothing
after some more G-mining ( Google) - i found out that I have to stick my VID in that hardware ID's and create an adb_usb.ini file to get the device recognized. Will update on happened next
sieger007 said:
after some more G-mining ( Google) - i found out that I have to stick my VID in that hardware ID's and create an adb_usb.ini file to get the device recognized. Will update on happened next
Click to expand...
Click to collapse
good luck!
That's why I stay away from these little brands. It's very difficult to find good information for it.
found something !!! I hope this is perm and not "leased"
TeTTiweTTi said:
good luck!
That's why I stay away from these little brands. It's very difficult to find good information for it.
Click to expand...
Click to collapse
TeTTiweTTi said:
good luck!
That's why I stay away from these little brands. It's very difficult to find good information for it.
Click to expand...
Click to collapse
ADB driver issue
> adb_usb.ini needed oXXXX as device ID . Where XXXX is the ID that shows up on Device manager. This is detailed here
http://blog.fh-kaernten.at/wehr/?p=1182
after that there will be 2 yellow marks for the rest of the unknowns in device manager. for this you have to modify the .inf file to include the entire h/w ID strings. I guess that makes just about any driver get along with anyone unknown - so here I am not sure if showing them as the such h/w by changing the driver files - gives them the actual intended functionality or all it does it just makes the device manager look clean without yellow marks. Maybe someone could help expand the talk here
[
Code:
android_winusb.inf
%SingleAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C01
%CompositeAdbInterface% = USB_Install, USB\VID_1782&PID_5D04&MI_01
/*ADDED*/
%CompositeAdbInterface% = USB_Install, USB\VID_1782&PID_5D04&MI_02
%CompositeAdbInterface% = USB_Install, USB\VID_1782&PID_5D04&MI_03
So with that - I get 1 ADB interface and 3 devices show up under "com and LPT" - alright that completes the drivers
ROOTING
I found this Chinese rooting program Vroot . I still have'nt figured out what exactly it means but it looks like it DID root that sucker after all. I tested with one app - root checker - got an dialogue in Chinese , asking me whether to give or not and I think I said Y but that app still does not say I have root. Its probably the apps thats at fault because I can get Linked2SD do ALL the stuff it would be doing running as root - .e.g force move programs to SD to free up space etc.
If someone out there can make English out of that and tell me if its mine to keep or leased out ( trial ) - that'd be damn nice !!!
ROMS
- WIP- when I get some more time
the chinese rooting program - now hiring English interpreters
the chinese rooting program - now hiring English interpreters
sieger007 said:
ADB driver issue
> adb_usb.ini needed oXXXX as device ID . Where XXXX is the ID that shows up on Device manager. This is detailed here
http://blog.fh-kaernten.at/wehr/?p=1182
after that there will be 2 yellow marks for the rest of the unknowns in device manager. for this you have to modify the .inf file to include the entire h/w ID strings. I guess that makes just about any driver get along with anyone unknown - so here I am not sure if showing them as the such h/w by changing the driver files - gives them the actual intended functionality or all it does it just makes the device manager look clean without yellow marks. Maybe someone could help expand the talk here
[
Code:
android_winusb.inf
%SingleAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C01
%CompositeAdbInterface% = USB_Install, USB\VID_1782&PID_5D04&MI_01
/*ADDED*/
%CompositeAdbInterface% = USB_Install, USB\VID_1782&PID_5D04&MI_02
%CompositeAdbInterface% = USB_Install, USB\VID_1782&PID_5D04&MI_03
So with that - I get 1 ADB interface and 3 devices show up under "com and LPT" - alright that completes the drivers
ROOTING
I found this Chinese rooting program Vroot . I still have'nt figured out what exactly it means but it looks like it DID root that sucker after all. I tested with one app - root checker - got an dialogue in Chinese , asking me whether to give or not and I think I said Y but that app still does not say I have root. Its probably the apps thats at fault because I can get Linked2SD do ALL the stuff it would be doing running as root - .e.g force move programs to SD to free up space etc.
If someone out there can make English out of that and tell me if its mine to keep or leased out ( trial ) - that'd be damn nice !!!
ROMS
- WIP- when I get some more time
Click to expand...
Click to collapse
sieger007 said:
the chinese rooting program - now hiring English interpreters
Click to expand...
Click to collapse
Post some screenshots of the text you want translated and I will ask the help of one of my Chinese colleagues.
Sent from my ASUS Transformer Pad TF700T using xda app-developers app
some screenshots of the text you want translated
here goes ..thank you . Combined several screens together in '4 lets '
TeTTiweTTi said:
Post some screenshots of the text you want translated and I will ask the help of one of my Chinese colleagues.
Sent from my ASUS Transformer Pad TF700T using xda app-developers app
Click to expand...
Click to collapse
sieger007 said:
here goes ..thank you . Combined several screens together in '4 lets '
Click to expand...
Click to collapse
ROM Basic Information Huawei T8950 Emotion UI 1.6 official pure version of the card brush pack
Author: Hay.
Size: 398MB
Android Version: 4.1.2
UI type: official factory style
Suitable models: Huawei T8950
Release date: 2013-07-31
MD5 code: F7A21630317EE4239DC145E75FF8A276
ROM presentation
1, based on the official code base package and Qualcomm made to upgrade to 4.1.2
2, emui upgrade to 1.6
3, repair legendary SMS unlit issue
4, full root privileges
5, caused during an upgrade wifi loss problem to fix
6, clean up some pit length useless underlying file
7, adjust the signal and the network connection speed
8 streamlining TTS voice database file
9, usb debugging is enabled by default
10 to adjust the overall Desktop Note: Upgrading from 4.0 to 4.1 need to upgrade Bottom bag bottom package
download address: http://pan.baidu.com/share/link?shareid=805743044&uk=137718883
recover before upgrade to upgrade the official recovery Brush back REC official and third-party tools
brush download address: HTTP :/ / pan.baidu.com / share / link? shareid = 807162397 & uk = 137718883
1.6 EMUI ROM Download: http://t.cn/zQWgp1r
3G not accessible
Hi again,
so I've been struggling with another issue.
Somehow my T8950 isn't capable of connecting to the 3G network of my carrier. When I search for networks, only the 2G networks are being found.
Does anybody have a clue why that is and how to solve that problem? My carrier is from Austria and is called "tele.ring" which is operated by T-Mobile.
I'd really appreciate your help, since 2G is reaaally slow for data connections
EDIT: I just tried allowing my phone only to connect to 3G networks by using the Network app from Philipp Mangelow (which shows the same menu as if you dial *#*#4636#*#* as i just found out). This results into no 3G networks being found at all.. I thought maybe the problem occurs because I'm always connected in roaming mode. As I bought the phone in China, it seems to believe that i need to be in roaming mode to connect to my local carrier. However, I have a local SIM-card, so this is somewhat weird..
EDIT 2: So after some googling I've found out that China has the TD-SCDMA radio interface for 3G (at least China Mobile, and that's from where I've bought the phone), but in europe it's W-CDMA.. Remains the question how to change that (if possible at all)..
EDIT 3: So I've wrote an email to Huawei about the issue, and that's the reply:
Sorry that T8950 doesn’t support the W-CDMA mode.
Below please kindly check the frequence band of T8950 for your reference.
• GSM/EDGE：900/1800/1900MHz
• TD-SCDMA：A frequency（2010-2025MHz）/F frequency（1880-1920MHz)
So that means that there is nothing i can do about it?
Thanks and all the best,
amannn
amannn said:
Hi again,
so I've been struggling with another issue.
Somehow my T8950 isn't capable of connecting to the 3G network of my carrier. When I search for networks, only the 2G networks are being found.
Does anybody have a clue why that is and how to solve that problem? My carrier is from Austria and is called "tele.ring" which is operated by T-Mobile.
I'd really appreciate your help, since 2G is reaaally slow for data connections
EDIT: I just tried allowing my phone only to connect to 3G networks by using the Network app from Philipp Mangelow (which shows the same menu as if you dial *#*#4636#*#* as i just found out). This results into no 3G networks being found at all.. I thought maybe the problem occurs because I'm always connected in roaming mode. As I bought the phone in China, it seems to believe that i need to be in roaming mode to connect to my local carrier. However, I have a local SIM-card, so this is somewhat weird..
EDIT 2: So after some googling I've found out that China has the TD-SCDMA radio interface for 3G (at least China Mobile, and that's from where I've bought the phone), but in europe it's W-CDMA.. Remains the question how to change that (if possible at all)..
EDIT 3: So I've wrote an email to Huawei about the issue, and that's the reply:
Sorry that T8950 doesn’t support the W-CDMA mode.
Below please kindly check the frequence band of T8950 for your reference.
• GSM/EDGE：900/1800/1900MHz
• TD-SCDMA：A frequency（2010-2025MHz）/F frequency（1880-1920MHz)
So that means that there is nothing i can do about it?
Thanks and all the best,
amannn
Click to expand...
Click to collapse
No, unfortunatly not. this is not a software setting, but a different hardware chip. my t8950 also does not support 3G in Belgium
TeTTiweTTi said:
No, unfortunatly not. this is not a software setting, but a different hardware chip. my t8950 also does not support 3G in Belgium
Click to expand...
Click to collapse
Mmmmh, ok – that's what i thought too.
Thank you very much anyway for your response TeTTiweTTi!
Hi everyone!
I am trying to connect my Qmobile A900i with Qmobile PC suite but failed. When I turn on the debuggin mode of my phone, in device manager I get my device name in other devices,
I think i need to make some modification to android_winusb.inf-file driver but i do not know how to do it.
Best Regards.
windowstoweb said:
Hi everyone!
I am trying to connect my Qmobile A900i with Qmobile PC suite but failed. When I turn on the debuggin mode of my phone, in device manager I get my device name in other devices,
I think i need to make some modification to android_winusb.inf-file driver but i do not know how to do it.
Best Regards.
Click to expand...
Click to collapse
No worries, mate. I'll fix it for you.
Okay, send me the android_winusb.inf file of the driver.
Also, do the following carefully if you are using Windows:
Click Start, search for Device Manager. Now find Qmobile A900i, it should be under Other Devices like you said. Now right click, select Properties. A dialog box should appear, click the Details Tab and under the Property , click on Description and choose Hardware Ids. Now two seperate values should appear in the Value box.
Copy those values and also send them to me.
Dom3616 said:
No worries, mate. I'll fix it for you.
Okay, send me the android_winusb.inf file of the driver.
Also, do the following carefully if you are using Windows:
Click Start, search for Device Manager. Now find Qmobile A900i, it should be under Other Devices like you said. Now right click, select Properties. A dialog box should appear, click the Details Tab and under the Property , click on Description and choose Hardware Ids. Now two seperate values should appear in the Value box.
Copy those values and also send them to me.
Click to expand...
Click to collapse
Thanks bro, I know Pakistani People always rocks.. I have sent you pm, please check it.
Thanks
Regards.
Hello,
I have a X96 Max Plus tv box buyed on december last year.
I want to use a USB game controller VID 0x0079 PID 0x0006 DragonRise Inc. generic USB Joystick.
The device is seen by the app called USB host viewer but don't generate events when key is pressed.
Also the analog button don't work.
How can I make android seen the device?
Maybe I need correct keydev.ko file? Where to find it? and how to install?
Thank in advance
mauro.
Mauro_IT said:
Hello,
I have a X96 Max Plus tv box buyed on december last year.
I want to use a USB game controller VID 0x0079 PID 0x0006 DragonRise Inc. generic USB Joystick.
The device is seen by the app called USB host viewer but don't generate events when key is pressed.
Also the analog button don't work.
How can I make android seen the device?
Maybe I need correct keydev.ko file? Where to find it? and how to install?
Thank in advance
mauro.
Click to expand...
Click to collapse
hi, what android version are you running?
you will need hid-dr.ko, i have this file for android 7 and older (amlogic kernel 3.xx) if your running 8/9 then you will have kernel 4.xx and this ko file may not work
aidanmacgregor said:
hi, what android version are you running?
you will need hid-dr.ko, i have this file for android 7 and older (amlogic kernel 3.xx) if your running 8/9 then you will have kernel 4.xx and this ko file may not work
Click to expand...
Click to collapse
Thanks for answer, I have Android 9, where to find the right file?
I have hid-dr.ko file from a working copy of coreelec that support my usb joypad, may I use this file? And How?
Hello, anyone can help? I can't find the right hid-dr.ko. Maybe someone that make custum rom have this file. I need for amlogic s903X3 android 9.
Thanks.
Mauro_IT said:
Hello, anyone can help? I can't find the right hid-dr.ko. Maybe someone that make custum rom have this file. I need for amlogic s903X3 android 9.
Thanks.
Click to expand...
Click to collapse
You can take the file from any amlogic android 8+, as 8+ uses the new 4.x kernel I have a fair few roms and i cant find that file in any of the 9.0 roms, it may have never been compiled for the newer kernel but it give alot of options for you to look
edit:
I found the file, check it on https://github.com/ewwink/Root-Android-S905X3-plus-Dragonrise-generic-USB-Joystick-driver
---------------------
have you found the file?
I would have a problem with an X96max +, namely what happens (it has any android system on it) when the HDR logo appears on the LG TV at boot, the system slows down (freezes) at the boot screen and "System UI isn't responding for a long time "subtitle for wait or close will be followed by another, then it will be very difficult to load the system, but the Wifi will be turned off. It plays on almost every boot, whether you switch from CE to droid or not. Can anyone help?
reset to factory default or flash with another ROM
h
ewwink said:
edit:
I found the file, check it on https://github.com/ewwink/Root-Android-S905X3-plus-Dragonrise-generic-USB-Joystick-driver
---------------------
have you found the file?
Click to expand...
Click to collapse
nice
Lesboy said:
I would have a problem with an X96max +, namely what happens (it has any android system on it) when the HDR logo appears on the LG TV at boot, the system slows down (freezes) at the boot screen and "System UI isn't responding for a long time "subtitle for wait or close will be followed by another, then it will be very difficult to load the system, but the Wifi will be turned off. It plays on almost every boot, whether you switch from CE to droid or not. Can anyone help?
Click to expand...
Click to collapse
cn hdr be turned off on the tv side? may point to if its causing the issue or it its just somthing else that triggers at the same time as the hdr service starts
No description
What is normally in a /data/vendor/modem_fdr folder? I am trying to use this on another device and it doesn't have that folder.. My device has /data/vendor/modem_config it has all the mcfg_hw, mcfg_sw nd ver_info.txt. Is that the same thing?
removed
hardplastic said:
If VoLTE is working on your device, just leave it alone. It's unnecessary but only if you find the module no longer working, delete these two folders to reset.
No, configs won't store at /data since factory reset will wipe them all. I'm not sure if it's working on other devices. You need manual editing the module by adding mbn file if your device doesn't contain your carrier's, add the path on mbn_sw.txt and sign the zip
Click to expand...
Click to collapse
Volte isn't working, that's why I'm here.
I have used efstools to write my mbn to /nv/item_files - but one file keeps on restoring it's self to default -
/nv/item_files/ims/ims_user_agent. My carrier needs the header in this file for volte to work. It worked fine on Android 10 but not 11.
My device doesn't contain the folder /data/vendor/modem_fdr.
When I delete the files in /data/vendor/radio/ they come back when I reboot - so I'm guess that's what it is meant to do.
removed
hardplastic said:
Sounds like not good.
I haven't found the path on my phone, are you using Pixel 3/XL? It's not strict for my carrier to detect header, this device has preinstalled lots of mbn files from various carriers, which also contains my carrier, so all I need is to add the path to make it work. And that's how the module working.
Can you find your carrier from /vendor/rfs/msm/mpss/readonly/vendor/mbn/mcfg_sw/generic?
Click to expand...
Click to collapse
My phone is a Xiaomi Poco F2,
Yep I can find the path, my carrier is Telstra.
The path is slightly different on this device,
It's /vendor/rfs/mdm/mpss/readonly/vendor/mbn/mcfg_sw/generic so I modified the module to that. But still the header reverts.
The actual mbn file does have the correct header in, but ims_user_agent reverts in the /nv/item_files/ims/ - where does it revert it from?
removed
hardplastic said:
Sorry, I haven't used any Xiaomi devices nor MIUI. I guess I can't help you handle this issue. MIUI is completely different from AOSP, which has many deeply modification. Go ask some experts who knows to fix that. Good luck.
Click to expand...
Click to collapse
I'm running AOSP on this device!
Can anyone tell me if this works with any Portuguese carrier?? if not, @hardplastic can you add support for the 3 portuguese carriers?!
I saw the mbn_sw.txt but think that only Vodafone Portugal it's there, it misses two more carriers, NOS and MEO
removed
hardplastic said:
It seems like there's no configuration files for carriers you said above. So it won't work. I would like to update if you can provide them(*.mbn)
Click to expand...
Click to collapse
How can one aquire that?? From other phones that are compatible with VoLTE (prob every new android phone out there except the pixels ones)
removed
what the hell happened here?!