Related
Hello,
some of us who have bought a Hero locked to Orange can't seem to get it unlocked (http://forum.xda-developers.com/showthread.php?t=555424).
For those have you who have managed to successfully unlock an Hero on Orange please can you advise on your experience- did you have to do something differently? And who you used to get the code? I have used Unlock Now (www.unlock-now.com) but the code they have supplied didn't work (they refunded me).
I have never had a problem unlocking a HTC phone until now and I find it hard to believe that Orange Heros can't be unlocked.
Please help if you can.
*********************************************************
[Update 16/10/09]
I am glad this thread has been of use to people.
I thought I would add and update to the first page so people don't have to wade through the whole thread.
If you are experiencing this issue you have two choices:
1)CID unlock your Hero (http://forum.xda-developers.com/showthread.php?t=559806).
2)Use a Rebel II Sim.
OK there are three choices.
3) Use your Hero on an Orange contract for about three months then ring up Orange and ask them for a unlock code. They will charge about £20 for it and you may have to wait up to two weeks for em to send it.
C'est tout.
*********************************************************
[Update 24/10/09]
OK, after discussions and PM's on this thread I was advised to use the code I had previously bought with a different rom (when I first got my Hero tried it I was using the Orange stock rom then Modacos 2.3).
I just tested it now, took out my rebel sim put in the code and it works! I am currently using Modaco's 2.8.
Hope this helps.
I used http://hero.unlock-now.com/sim-unlock-HTC-Hero/ and the code worked for me. I did get my Hero within a few days of release. My work collegue also did the same with no problems.
What network do you use your hero on now?
hi i bought one locked to orange uk and unlocked it here
http://www.simunlock-htchero.com/buy.html
i received the code in 2 minutes and it worked, i use now Optimus in Portugal
Got my second one (for the wife) off eBay a week or two back. Poster claimed it was days old. Unlocked through htcunlock fine. Three sim seems to work better with Orange radio than the tmobile hero I purchased earlier.
Zuber
RetroFlux: I'm now on o2 after my unlock.
i'm getting the same thing with my orange locked hero, I have even tried a foreign sim as suggested. But does not seem to unlock with the correct unlock code. Is there a cable method for unlocking?
I have the same problem.
First case:
Turn on the phone with orange SIM card - everything works fine.
Turn on the phone with any other SIM card (I actually tried 3 other SIM card from 3 different providers). It asks unlock code. Enter unlock code I bought (actually any code containing 8 digits) it says "Network unlock successful." But after that it allow only emergency calls and if I try to make a call I see "Not registered in network" message. After reboot it asks unlock code again.
Second case:
If I do "restore to factory defaults" and turn it on the first time with my (no orange) SIM card, it asks unlock code I enter correct unlock code (salesman gave me one, and after that I also bought the same code in the Internet )
it hangs with phrase "Unlocking SIM card...". (Actually "turn off menu" works, I even can make an emergency call, but that is all I can get from it)
Also I noticed that in the first case there is strange line on the bottom of the screen (of the size of the notification bar).
I have tried different ROMS (original, rooted, latest, modacos) all the same. I also tried to downgrade radio firmware. I even tried all SIM cards I can obtain, the problem is obviously doesn't caused by SIM/Network incompatibility. Btw, my SIM card works OK in another HTC Hero (which was bought with my one).
I think it is problem with unlock procedure itself, not with code correctness. If wrong code entered it must say something like "wrong code", but for any 8 digit code it says "Network unlock successful". Is is the symptom! )
I do not know what to do further
I got a (UK) Orange Hero about 3 weeks ago from dial-a-phone. Unlocked it without a problem about a week later from:
http://hero.unlock-now.com/sim-unlock-HTC-Hero/
Took about 20 mins and worked 1st time. Now running with an UK O2 sim. Sorry!
As I mentioned above, while first boot with my local SIM card it hangs with "Unlocking SIM card..." message. At this time I see the following processes running.
Code:
# ps wwwwwww
PID USER VSZ STAT COMMAND
1 0 292 S /init
2 0 0 SW< [kthreadd]
3 0 0 SW< [ksoftirqd/0]
4 0 0 SW< [watchdog/0]
5 0 0 SW< [events/0]
6 0 0 SW< [khelper]
7 0 0 SW< [suspend]
8 0 0 SW< [early_suspend]
9 0 0 SW< [kblockd/0]
10 0 0 SW< [kmmcd]
11 0 0 SW< [btaddconn]
12 0 0 SW< [btdelconn]
13 0 0 SW< [kondemand/0]
14 0 0 SW< [qmi]
15 0 0 DW< [rpcrouter]
16 0 0 SW< [detection/0]
17 0 0 SW< [krpcserversd]
18 0 0 SW [pdflush]
19 0 0 SW [pdflush]
20 0 0 SW< [kswapd0]
21 0 0 SW< [aio/0]
22 0 0 SW< [panel_on/0]
23 0 0 SW< [cabc_work_q]
24 0 0 SW< [mtdblockd]
25 0 0 SW< [kadspd]
26 0 0 SW< [USB mass_storag]
27 0 0 SW< [synaptics_wq]
29 0 0 SW< [kstriped]
30 0 0 SW< [krfcommd]
31 0 0 SW< [mmcqd]
33 0 3328 S /sbin/adbd
50 1000 808 S /system/bin/servicemanager
51 0 852 S /system/bin/vold
52 0 668 S /system/bin/debuggerd
53 1001 11064 S /system/bin/rild
54 0 73504 S zygote /bin/app_process -Xzygote /system/bin --zygote --start-system-server
55 1013 30172 S /system/bin/mediaserver
57 1002 1180 S /system/bin/dbus-daemon --system --nofork
59 0 800 S /system/bin/installd
61 1008 1196 S /system/bin/akm8973
73 0 0 DW< [snd_rpc]
77 1000 173m S system_server
140 9998 159m S android.process.acore
142 1001 132m S com.android.phone
144 1000 96660 S com.htc.android.htcsetupwizard
166 10002 111m S com.google.process.gapps
179 0 0 DW< [ksdiorqd]
180 0 0 SW< [tiwlan_wifi_wq]
186 10004 96600 S com.htc.android.worldclock
193 10005 101m S com.htc.provider
207 1010 3160 S /system/bin/wpa_supplicant -Dtiwlan0 -itiwlan0 -c/data/misc/wifi/wpa_supplicant.conf
237 10031 121m S com.htc.android.htcime
244 9999 140m S com.htc.launcher
253 10016 98640 S com.htc.android.psclient
265 10017 107m S com.android.mms
285 10019 97736 S android.process.media
296 10020 106m S com.google.android.apps.maps:FriendService
307 10022 99016 S com.esmertec.android.jbed
322 10036 97.6m S com.google.android.partnersetup
332 10042 100m S com.htc.calendar
346 1000 100m S com.android.settings
356 10029 98612 S com.htc.android.footprints
366 10013 98012 S com.android.setupwizard
430 0 740 S /system/bin/sh -
468 0 2072 R ps wwwwwww
Im having the same issue, I got a new HTC Hero on Orange today, and it wont unlock. I used Unlock-now, so I have sent them a message asking for my money back, will that suffice. Has anyone been able to get there Orange UK, branded and locked phones unlocked.
nintendolinky, what is your ROM version ? There may be a possibility you have the latest firmware build... maybe...
i'm in the same boat! bought the code but no joy. it say's unlocked but could not register my voda sim. Anyone?
I tried to contact Orange today to buy an unlock code from them directly, after been passed about I eventually got through to someone bureaucratic wench who was completely unhelpful and I ended up telling them to F off and hung up. Kind of shot myself in the foot there.
I know this doesn't help our situation but I am still looking into it.
joemax said:
nintendolinky, what is your ROM version ? There may be a possibility you have the latest firmware build... maybe...
Click to expand...
Click to collapse
So are you saying there is an issue with the new firmware? When you say firmware do you mean ROM? As I have already flashed Modacos latest ROM and my Three/Vodafone/O2 sim still won't work.
I don't have my Hero with me at the moment but will post back my firmware number later, if other people (who are having the same issue) can post theirs maybe we can find a common firmware at fault.
nintendolinky said:
I used Unlock-now, so I have sent them a message asking for my money back, will that suffice.
Click to expand...
Click to collapse
I used Unlock-Now, they did refund me after your usual basic diagnostics.
joemax said:
nintendolinky, what is your ROM version ? There may be a possibility you have the latest firmware build... maybe...
Click to expand...
Click to collapse
Ok, here are my firmware details:
Firmware version: 1.5
Baseband Version: 63.18.55.06EU_6.35.06.18
Kernel Version: 2.6.27-8dd6deee [email protected]
Build Number: 2.73.405.5 146733 CL#61267 MCR2.2c release keys
Software Version: 1.0.0.A6288
Someone out there must be able to help fix this, pros/cooks/anyone can you shed anylight on this?
I've tried oldest/newes/custom ROMs, it looks like unlocking procedure doesn't depend on ROM at all.
is there a way to unlock this via cable? what about flashing the rom?
my build number is
Build Number: 1.76.61.3 whats the difference with this and Build Number: 2.73.405.5?
Here is my info:
Firmware version: 1.5
Baseband Version: 63.18.55.06EU_6.35.06.18
Kernel Version: 2.6.27-8dd6deee [email protected]
Build Number: 2.73.405.5 146733 CL#61267 MCR2.2e release keys
Software Version: 1.0.0.A6288
My build number is different, to the one listed here.
Hi, (Edited with merged post below and new information.)
I have an Onda Vi140 10" tablet and the capacitive touchscreen is useless for real writing apps.
Is there any way to add a graphics tablet like Wacom to Android via USB?
I know they work in Linux, but I wouldn't have a clue how to port a driver to Android.
Is there a technical (battery drain?) reason why this isn't feasible?
I've searched the web and trawled through countless pages, so whether I'm searching wrong, or it's an option only a few people would want and therefore of no interest, I'm not sure.
There are a few questions dotted around the web, but no answers.
For me, I'm about to buy an A5 tablet for Photoshop, so slipping it into my android sleeve and using it in meetings would be a bonus.
If it's just drivers, maybe someone would know how to try? I just need the basic writing ability. All other features wouldn't be needed, or supported by apps.
Any advice would be appreciated.
David.
Sorry if this is in the wrong thread, but although not specific to my device, the earlier thread mentions a specific area of Android I'm interested in. If it's in the wrong place, please post it here - where I've so far had no luck. I don't want to double-post. Here, user d10221 seems to know what he's doing.
d10221 said:
The Manhattan/WALTOP tablet din't work "plug&pray" with 3.2, or 4.0 (HC, ICS)
it needed to be setup first...
Click to expand...
Click to collapse
From this earlier post in this thread by user d10221 it seems that an external USB HID compliant graphics tablet might work.
1) I have a cheap graphics tablet which appears to be HID compliant and works as a mouse in Windows & without drivers.
2) My HID compliant mouse works perfectly on my ICS tablet.
Does anyone know why, if it's HID compliant, the pen/tablet is recognised in WIn7, but not in Android; but a similarly compliant mouse does?
I just need the mouse functions.
My /proc/bus/input shows:
I: Bus=0019 Vendor=0001 Product=0001 Version=0100
N: Name="sun4i-keyboard"
P: Phys=sun4ikbd/input0
S: Sysfs=/devices/virtual/input/input0
U: Uniq=
H: Handlers=kbd event0
B: PROP=0
B: EV=3
B: KEY=2000000 0 800 c0040 0 0 10000002
I: Bus=0019 Vendor=0001 Product=0001 Version=0100
N: Name="axp20-supplyer"
P: Phys=m1kbd/input2
S: Sysfs=/devices/platform/sun4i-i2c.0/i2c-0/0-0034/axp20-supplyer.28/input/input1
U: Uniq=
H: Handlers=kbd event1
B: PROP=0
B: EV=7
B: KEY=100000 0 0 0
B: REL=0
I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name="ft5x_ts"
P: Phys=
S: Sysfs=/devices/virtual/input/input2
U: Uniq=
H: Handlers=event2
B: PROP=0
B: EV=b
B: KEY=400 0 0 0 0 0 0 0 0 0 0
B: ABS=2650000 0
I: Bus=0018 Vendor=0000 Product=0000 Version=0000
N: Name="mma7660"
P: Phys=
S: Sysfs=/devices/virtual/input/input3
U: Uniq=
H: Handlers=js0 event3
B: PROP=0
B: EV=9
B: ABS=7
Which, as far as I can tell, are all standard devices from the tablet. So, I'm guessing ICS isn't picking the HID drawing tablet up in the same way as windows.
Anyone any ideas? Can I force Android to look and set it up this way? I dabble a bit in Ubuntu and have already modified my Onda Vi40 tablet to read/write to my external TF and USB sticks. However, I'm lost - although I think it may be possible.
Thanks for any help in advance.
David.
Update edit:
Using this USB scanning App I got this:
Device List 1-1
Device Info
Device Path: /sys/bus/usb/devices/1-1/
Device Class: Use class information in the Interface Descriptors (0x0)
Vendor ID: 0b57
Vendor Name (reported): Han Wang Technoloy Center
Vendor Name (from DB): Beijing HanwangTechnology Co., Ltd
Product ID: 8004
Product Name (reported): JB8 USB Tablet
Product Name (from DB): not in db
Additional Info
USB Version: 1.00
Speed: 1.5
Protocol: 00
Maximum Power: 40mA
Serial Number:
The Android scan option found nothing: This is from the Linux Kernel scan.
So, it seems the Linux Kernel finds something, but not Android.
Am I any closer?
David. Edit: (Thanks mods for merging these posts.)
first: find out if your android device supports to act as a USB-host at all.
for drivers you wan hope for it to be detected as a normal mouse und use it with any sketch app I suppose.
If you use it at home only, maybe there is an app to use your computers pointer as a mouse on the android through wifi.
cougarten said:
first: find out if your android device supports to act as a USB-host at all.
for drivers you wan hope for it to be detected as a normal mouse und use it with any sketch app I suppose.
If you use it at home only, maybe there is an app to use your computers pointer as a mouse on the android through wifi.
Click to expand...
Click to collapse
My device supports a mouse - thank you. So basic sketchpads should work if they have Android/Linux drivers? Or with the built-in mouse drivers?
Thanks very much for your comments and help.
David.
I tried a Wacom tablet on my phone which has USB host support. It was recognized, but I could not use it as an input device. You might have better luck with your tablet/tablet combination.
*Bump* as there's more information from a merged thread after lots of digging.
Still stumped, but does the new info in the OP help?
David.
Graphic tablet wasn't like generic-input device, it seems.
I'd like to use wacom bamboo tablet on acer a500 tablet.
So when I connected to a500, light was on but it doesn't do anything.
Of course, I also tried my usb keyboard and mice and also wireless keyboard and mice. And also usb memory stick and external hard disk. It worked them all. But wacom bamboo tablet doesn't work.
Anyway, I've got other information from articles here.
[Q] USB Pen Tablet like Wacom Bamboo Tablet work on Android?
http://forum.xda-developers.com/showthread.php?t=1447905
Use USB Tablet Pen such as Wacom with Prime
http://forum.xda-developers.com/showthread.php?t=1591872
And interesting thing is plurch said that it worked on Nexus 7. You can find plurch's post in first link.
Thank you.
Hey guys,
I have a Lumia 800 with a "messed up" Qualcomm bootloader. Here's what's different about it:
- Power+Vol.UP button combination doesn't work. Every other combination works great (FTM, Hard Reset, etc.).
- Since that combination doesn't work, I can't get to OSBL mode without NSSPro.
- When in OSBL mode, it shows up as Qualcomm CDMA Technologies MSM on Windows, OS X and Ubuntu but doesn't show its NAND partitions.
- In the Device Manager on Windows, the device has a tiny yellow warning sign like it's not working properly or it doesn't have the correct drivers. I tried installing/uninstalling the Qualcomm drivers from the other thread but nothing changed.
Is there any way to "repair"/reset the bootloader or force it to show its partitions ? Obviously I'm very careful with it so it doesn't get replaced with a DLOAD one.
I can put the USB debug logs from any/all of the OS if it might help.
Please help if you have any idea. Thanks.
I have tried all kinds of things on Windows.
I tried forcing the generic USB Mass Storage Device driver but it said it couldn't "start" the device.
I also installed all kinds of Qualcomm drivers I could find. I found the correct one, Qualcomm HS-Diagnostics 9006 (COMx), though unsigned (and still showing the yellow warning sign). Lumia still doesn't show the partitions.
Installed QPST (had weird errors about not being able to register a lot of DLLs while installing) and the Lumia didn't even appear in the devices list. (might be because of the broken install, I don't know)
Any ideas ?
inket said:
I have tried all kinds of things on Windows.
I tried forcing the generic USB Mass Storage Device driver but it said it couldn't "start" the device.
I also installed all kinds of Qualcomm drivers I could find. I found the correct one, Qualcomm HS-Diagnostics 9006 (COMx), though unsigned (and still showing the yellow warning sign). Lumia still doesn't show the partitions.
Installed QPST (had weird errors about not being able to register a lot of DLLs while installing) and the Lumia didn't even appear in the devices list. (might be because of the broken install, I don't know)
Any ideas ?
Click to expand...
Click to collapse
Mine does the same thing... My guess is that it is a intermediate version between full dev qualcomm bootloader and nokia dload that they rushed out.
What's your phone info?
My Lumia's information (weird bootloader):
Firmware: 12070
Hardware revison: 112.1402.2.3
Radio SW version: 1.6.00.24
Radio HW version: 8255
Bootloader version: 7.35.0.0
Chip SOC version: 0.74.2.1
ROM Language: 0C0A (Spanish (Spain))
ROM version: 7.0.8107.0
OEM Device Name: RM-801 EU 238
Mobile Operator: 000-ES
IMEI: 35928904 67xxxxx
Friend's (Nokia DLOAD):
Firmware: 12070
Hardware revison: 112.1402.2.3
Radio SW version: 1.6.00.24
Radio HW version: 8255
Bootloader version: 7.35.0.0
Chip SOC version: 0.74.2.1
ROM Language: 0809 (English (United Kingdom))
ROM version: 7.0.8107.0
OEM Device Name: RM-801 EU NDT EURO1
Mobile Operator: 000-33
IMEI: 35928904 79xxxxx
I have thought to open the phone and remove the battery to see if it helps, but I haven't tried it yet.
At least, I'm not the only one.
Here's mine:
OS: 7.10.8107.79
Firmware: 1600.2489.8107.12072
Hardware revision: 112.1402.2.3
Radio SW version: 1.6.00.24
Radio HW version: 8255
Bootloader version: 7.35.0.0
Chip SOC version: 0.74.2.1
IMEI: 3592890464xxxxx
Product Code: 059L702
Basic Product Code: 059J2N6
Type Designator: RM-801
Production SN (PSN): 004370FAB (< copied this because it seemed interesting)
That's all I found on WP, NCS and NSSPro. Where did you find the other info ?
I know that mine came from Vodafone Spain and 11414 firmware. Interesting, right ? Both from Spain.
My phone is the Unlocked Spanish country version, came with 11412.
I got the information from the diagnostics app (dial ##634#). I don't know if the diagnostics from 12072 has all this data (it should), I haven't updated mine from 11500.
Where did you get the PSN?
The question is: it is related to the country variant or to the production run?
I found the PSN on both NSSPro and NCS. Look in the Extended Info in NCS, I think.
My Lumia's info from Diagnostics:
ROM Language: 0C0A (doesn't say "(Spanish(Spain))" or anything, just 0C0A)
ROM version: 7.0.8107.0
OEM Device Name: RM-801 EU 214
Mobile Operator: VOD-ES
So far the only similarity is that they're both from Spain.
Nothing new, I guess ?
I'm thinking of trying NCS' "Refurbish" or "Recovery".
Anyone care to explain how do they work or what do they do exactly ?
I still don't want to replace the bootloader with Nokia's; I'm looking if there's a way to "refresh" the bootloader or something like that.
just take the battery out and insert after 10 or more second..then press and hold the vol up and insert the usb cable while holding vol up ....usb should be connected to pc from other end...after u inserted usb in phone u feel a short vibration, then leave the vol button and u'll be in qpst mode..
@debbuger
Are you sure that would work ?
I mean, did you have the same problem and you fixed it by removing the battery ?
sorry bro i thought that u've lumia 710.. don't remove battery do as follows --
as u r on l800
force it off by pressing the power switch for about 10 to 15 sec ,
then press and hold vol up and insert the usb ..a short vibratin means u r in osbl mode...
Already tried that. Doesn't work. Thanks anyway.
can u tell me if ur lumia is shipped with qualcom boot or you have flashed it after ...
It shipped that way.
Can you post the USB ID of the phone in bootloader mode? (lsusb -n in Linux, or Details tab in the Windows device manager)
Oh my brothers lumia 710 was given for a repair ang was returned with dload
Sent from my MB865 using xda premium
lsusb:
Bus 001 Device 002: ID 05c6:9006 Qualcomm, Inc.
Ubuntu's lsusb doesn't have the option '-n' so I'll paste the verbose output:
Code:
Bus 001 Device 002: ID 05c6:9006 Qualcomm, Inc.
Couldn't open device, some information will be missing
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x05c6 Qualcomm, Inc.
idProduct 0x9006
bcdDevice 0.00
iManufacturer 3
iProduct 2
iSerial 0
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 32
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 1
bmAttributes 0xe0
Self Powered
Remote Wakeup
MaxPower 500mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 255 Vendor Specific Subclass
bInterfaceProtocol 255 Vendor Specific Protocol
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 32
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x01 EP 1 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 32
Seems like your phone is going into QHSUSB_DLOAD mode, whenever you try to use bootloader mode. Also, you get "Couldn't open device", which sounds like a hardware issue. Take it to the repair shop.
One thing to try is plug in the phone normally into your computer (while in Linux), and turning it on. Post the device IDs that show up in "dmesg" after doing that.
Thanks NetRoller.
.NetRolller 3D said:
Seems like your phone is going into QHSUSB_DLOAD mode, whenever you try to use bootloader mode.
Click to expand...
Click to collapse
What's QHSUSB_DLOAD mode ? I looked all over the internet and found nothing answering that...
Please note that this mode isn't triggered with the Power+VolUp combination, but by selecting OSBL Mode in NSSPro. I don't know much about this but maybe selecting other modes in NSSPro could be more "useful" ?
.NetRolller 3D said:
Also, you get "Couldn't open device", which sounds like a hardware issue. Take it to the repair shop.
Click to expand...
Click to collapse
I just realized, the "Couldn't open device" is because I ran lsusb as a user (without sudo)... I'll try it again and paste the output.
.NetRolller 3D said:
One thing to try is plug in the phone normally into your computer (while in Linux), and turning it on. Post the device IDs that show up in "dmesg" after doing that.
Click to expand...
Click to collapse
Doesn't seem to have anything important (I added comments):
Code:
[345141.576034] usb 1-6: new high-speed USB device number 3 using ehci_hcd
[345142.410405] generic-usb 0003:045E:041E.0001: hiddev0,hidraw0: USB HID v1.10 Device [Microsoft Windows Phone] on usb-0000:00:1d.7-6/input0
[345142.410441] usbcore: registered new interface driver usbhid
[345142.410445] usbhid: USB HID core driver
# vibration
# screen ON but black, stays like that for 15s
[345157.617055] usb 1-6: USB disconnect, device number 3
# shuts down
# vibration
# boots
[345178.864037] usb 1-6: new high-speed USB device number 4 using ehci_hcd
Does Power+VolUP put it into "mass storage" mode?
Power+VolUp does nothing. Long vibration and it just boots normally. Here's the `sudo lsusb -v` after switching to "OSBL Mode" through NSSPro:
Code:
Bus 001 Device 005: ID 05c6:9006 Qualcomm, Inc.
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x05c6 Qualcomm, Inc.
idProduct 0x9006
bcdDevice 0.00
iManufacturer 3 Qualcomm, Incorporated
iProduct 2 Qualcomm CDMA Technologies MSM
iSerial 0
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 32
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 1 Qualcomm Configuration
bmAttributes 0xe0
Self Powered
Remote Wakeup
MaxPower 500mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 255 Vendor Specific Subclass
bInterfaceProtocol 255 Vendor Specific Protocol
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 32
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x01 EP 1 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 32
Device Qualifier (for other device speed):
bLength 10
bDescriptorType 6
bcdUSB 2.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
bNumConfigurations 1
Device Status: 0x0000
(Bus Powered)
Hi
I just bought a samsung bkc 1B1 bluetooth keyboard, and I'm trying to use it with my galaxy tab 2 10.1 (p5110) with Cyanogenmod 10.1.1.
My problem is that is recognized as QWERTY keyboard, which it's not. So I decide to write a custom keylayout for the keyboard. First I searched for the vendor and product id :
Code:
$ : cat /proc/bus/input/devices
I : Bus=0005 Vendor=04e8 Product=7021 Version=0001
N : Name="Broadcom Bluetooth HID"
P : Phys=
S : Sysfs=/devices/virtual/misc/uhid/input9
U : Uniq=
H : Handler=sysrq kbd event8
B : PROP=0
B : EV=2001b
B : KEY=1f 0 0 0 0 0 0 0 0 0 0 10000 0 0 0 10013 2000007 ff9f307a c9405fff febeffdf ffafffff ffffffff fffffffe
B : ABS=f00 0
B : MSC=10
B : LED=1f
I duplicated Generic.kl and rename the copy "Vendor_04e8_Product_7021.kl". I tried to change a letter, but it seems the modification has not been taken into count even after a reboot.
I also tried "Vendor_04e8_Product_7021_Version_0001.kl" and "Broadcom Bluetooth HID.kl" but none of them seems to work.as well.
Is that normal ? How can I fix it ?
Mouarf said:
I also tried "Vendor_04e8_Product_7021_Version_0001.kl" and "Broadcom Bluetooth HID.kl" but none of them seems to work.as well. Is that normal ? How can I fix it ?
Click to expand...
Click to collapse
Try using "BroadcomBluetoothHID.kl" or "Broadcom_Bluetooth_HID.kl" instead.
Any update? Did you ever get this working? I'm experiencing the same issue. logcat shows that it never touches my custom kl file and just uses the Generic.kl. I can modify that file and my changes work fine, but that's obviously not the right solution. I'm working with a Nexus 7 stock Android 4.4.2 ROM. According to the documentation, this should work!
http://source.android.com/devices/tech/input/key-layout-files.html
Thanks
New to android, but fairly good in linux so I can understand most technical stuff with these devices.
I have a chinese tablet, softwinners a13 clone. I rooted it the day I got it, and it was running fine until one day it booted into recovery, and wouldnt restore anything because it could not mount any folders. Long story short, I flashed the faastjb to it, and it booted up like a charm. I should also note no other images would succeed in livesuit, all gave error 162 except faaastjb.
As mentioned the TS would not work, so I cracked the tablet open and seen that the chip is a zet6251 chip??
Foolishly, I did not dump the factory rom, but I did do some sort of backup in which I was able to view the factory init.sun5i.rc file to see what drivers it had installed. Shows the zet6221 driver. Here I thought, awesome, theres a zet6221 driver in the thread. So I ran the batch file to insert the drivers, and still my touchscreen doesn't work. The gsensor works properly, but no touchscreen.
I tried to manually insmod the driver, but it gives me file already exists, and when I check lsmod, it shows zet6221 as loading, all other drivers are live.
insmod attempt :
Code:
[email protected]:/vendor # insmod zet6221.ko
insmod zet6221.ko
insmod : init_module 'zet6221.ko' failed (File exists)
dmesg output (snippet) :
Code:
page 127 [0] doesn't match! continue to download!
<4>[ 177.021251]
<4>[ 177.021254] write : 2c
<4>[ 177.040032] read : 3d 3d 3d page=123 offset[0]=113 offset[1]=116 offset[2]=119 offset[3]=122
<4>[ 177.404167] page=125 offset[4]=118 offset[5]=121 offset[6]=124 offset[7]=127
<4>[ 177.411239] page 127 [0] doesn't match! continue to download!
<4>[ 177.411247]
<4>[ 177.411250] write : 2c
<4>[ 177.430029] read : 3d 3d 3d page=123 offset[0]=113 offset[1]=116 offset[2]=119 offset[3]=122
<4>[ 177.794167] page=125 offset[4]=118 offset[5]=121 offset[6]=124 offset[7]=127
<4>[ 177.801243] page 127 [0] doesn't match! continue to download!
<4>[ 177.801252]
<4>[ 177.801255] write : 2c
<4>[ 177.820032] read : 3d 3d 3d page=123 offset[0]=113 offset[1]=116 offset[2]=119 offset[3]=122
<4>[ 178.184164] page=125 offset[4]=118 offset[5]=121 offset[6]=124 offset[7]=127
<4>[ 178.191233]
I didnt paste all of the dmesg output. It was pretty much all this over and over with varying offsets.
lsmod output :
Code:
zet6221 46023 1 - Loading 0x00000000
device 26862 0 - Live 0x00000000
rtl8150 10305 0 - Live 0x00000000
mcs7830 7581 0 - Live 0x00000000
qf9700 9152 0 - Live 0x00000000
asix 24601 0 - Live 0x00000000
camera 53105 0 - Live 0x00000000
videobuf_dma_contig 6243 0 - Live 0x00000000
videobuf_core 20242 1 videobuf_dma_contig, Live 0x00000000
cedarx 11869 0 - Live 0x00000000
mali 200007 21 - Live 0x00000000
ump 34213 9 mali, Live 0x00000000
mxc622x 6310 0 - Live 0x00000000
nand 225000 8 - Live 0x00000000
And finally the original init file that I fortunately had backed up. This was backed up after rooting, but the tablet was fully functioning.
Just the part that is relevant...
Code:
#insmod key & tp driver
# insmod /system/vendor/modules/sun4i-ts.ko
insmod /system/vendor/modules/sun4i-keyboard.ko
# insmod /system/vendor/modules/ft5x_ts.ko
# insmod /system/vendor/modules/gt811_ts.ko
insmod /system/vendor/modules/zet6221.ko
# touch key
insmod /system/vendor/modules/hv2605.ko
# insmod mali driver
insmod /system/vendor/modules/ump.ko
insmod /system/vendor/modules/mali.ko
#insmod video driver
insmod /system/vendor/modules/cedarx.ko
#insmod gsensor driver
insmod /system/vendor/modules/gsensor.ko
# insmod /system/vendor/modules/bma250.ko
# insmod /system/vendor/modules/mma7660.ko
# insmod /system/vendor/modules/dmard06.ko
I will be getting another tablet from the friend that got me this one sometime in the next week, and I will do a factory backup from it to extract drivers. I really don't want the factory firmware on it again... it seemed to run very slow in comparison to this. it was originally 4.1.1
Hi.
Did you manage to fix this? I have the exact same problem
same problem
Hello.
I have 2 identical A13 tablets. I wanted to install CWM for sdext --> ended with endless recovery mode. One is still with its original rom and working.
For the problematic one I've tried several roms - but touch was not working. I can't find the factory image.
At the moment I loaded FaaastJB 2.5. Tried every touch drivers stated in that topic but without success. Did managed to get the g-senzor working with one of the users driver pack (M3AT5O5_V1).
I also tried to import original .ko and modifying script.bin but without success (could be that I'm doing sth wrong).
Can someone please help me make my driver pack or help me by creating it.
Here are all the possible info about the tablet that i can think of. Msg me if something is missing
A13, 10 partitions.
Model name: TY_MID, android 4.2.2, TYnuclear-ococci-eng 4.2.2 JDQ39 20131120 test-keys
Code:
[email protected]:/ # lsmod
lsmod
8188eu 767523 0 - Live 0x00000000 - wifi
device 26958 0 - Live 0x00000000
rtl8150 10305 0 - Live 0x00000000
mcs7830 7581 0 - Live 0x00000000 - usb/eth
qf9700 9152 0 - Live 0x00000000
asix 24601 0 - Live 0x00000000
sun5i_csi0 34042 0 - Live 0x00000000 - video
siv120d 18948 1 - Live 0x00000000 - camera
camera 59581 1 sun5i_csi0, Live 0x00000000
videobuf_dma_contig 6243 1 sun5i_csi0, Live 0x00000000
videobuf_core 20242 2 sun5i_csi0,videobuf_dma_contig, Live 0x00000000
dmard06 11119 0 - Live 0x00000000 - G-sensor
mc32x0 14040 0 - Live 0x00000000 - G-sensor?
cedarx 11869 0 - Live 0x00000000 - video
mali 199863 80 - Live 0x00000000
ump 34137 17 mali, Live 0x00000000
A13_gslX680 119756 0 - Live 0x00000000 (F)
nand 225000 8 - Live 0x00000000
[email protected]:/ #
Can't share outside links, but I have uberizer backup and rom dump available. Can also upload to any file sharing service if needed.
After much searching, and flashing, I found a rom that gets the TS working again. It indeed has a zet6251 driver, and I flashed it to my tablet. now works like a charm. Be forewarned, its default is not english, and I couldn't tell you what language it is, but you can set it to english.
This is a factory ROM, not rooted, no bells and whistles, but it does have a working TS and Gsensor!!
I'm just syncing the compressed image on my google drive, and will share once completed.
Google drive link :
drive.google.com/file/d/0B5un_i3IN5ecclYzM2xDeXlWaVE/edit?usp=sharing
add https to the beginning... unable to post links.
Hope it helps
midnightmekanik said:
After much searching, and flashing, I found a rom that gets the TS working again. It indeed has a zet6251 driver, and I flashed it to my tablet. now works like a charm. Be forewarned, its default is not english, and I couldn't tell you what language it is, but you can set it to english.
This is a factory ROM, not rooted, no bells and whistles, but it does have a working TS and Gsensor!!
I'm just syncing the compressed image on my google drive, and will share once completed.
Google drive link :
drive.google.com/file/d/0B5un_i3IN5ecclYzM2xDeXlWaVE/edit?usp=sharing
add https to the beginning... unable to post links.
Hope it helps
Click to expand...
Click to collapse
Hi.
First of all, thanks a lot for answering this after such a long time. I completely forgot that I posted in here.
I suffered a lot with this issue, but I managed to get a module working to solve the problem after a few weeks working on it. I forgot about this post, or I would have replied to you with my solution.
If you still want to try FaaastJB rom, you can get the patch that I develop in reply #2038 in page 68 of the FaaastJB topic, and let me know the result.
Regards