Related
Here is the guide to remap the Genius button to Google search.
A press will give you text search and long press will give you voice search.
Items needed:
Root access (Perm root required as not having perm root will result in changes being undone on reboot)
Root explorer
MT4G
Fingers
If you misspell the word you will lose button functionality. Your Power button and volume buttons won't work. All is not lost though, pull the battery follow the steps again. I would recommend making a backup of the file before you edit it (Root explorer makes a backup, but you can never make too many. That and Root explorer makes a backup of the file before editing).
Steps:
1. Open Root explorer and navigate /system/usr/keylayout/ (That is scroll down and press the system folder. Scroll down again and press the usr folder. Press the keylayout folder)
2. At the top right corner of the screen press mount r/w
3. Long press "glacier-keypad.kl"
4. A screen will pop up, scroll down to "Open in Text Editor"
5. key 183 will say FUNC_4, change this to SEARCH (all caps)
6. Press the menu button
7. Press "Save Changes"
8. Long press power button
9. Press Restart
10.Try it out, and say thank you after it works.
Sorry but I was always told to explain it as if you were 10yrs old to prevent questions. Wasn't trying to offend anyone's intelligence.
Also while you're in there if you want to add WAKE_DROPPED after HOME, your phone will now wake when you press the home button.
If someone wants to make a guide for how to do this with adb, post it and I will update the op.
Update: The google voice search on this phone sucks balls. Go to the market and download Vlingo. The first time you long press search after this it will give you the option to make it the default voice search. Imo it is superior to the native voice search, at least on this phone.
Update: The latest update for Voice Search has fixed whatever the problem may have been. But Vlingo is still a great app so feel free to give it a try.
Update: Mftek has given you another alternative. Please see this post For instruction on how to get Google search on a short press, and the Genius button on a long press.
Update
Absolutely genius... I will try it soon.
Before I do... we can reverse by simply changing it from SEARCH back to FUNC_4, I assume?
Already tried to change it back and it worked no problem.
You are the man! Thanks
Works perfect
Sent from my HTC Glacier using XDA App
21productionz said:
Here is the guide to remap the Genius button to Google search.
A press will give you text search and long press will give you voice search.
Items needed:
Root access
Root explorer
MT4G
Fingers
If misspell the word you will lose button functionality. Your Power button and volume buttons won't work. All is not lost though, pull the battery follow the steps again. I would recommend making a backup of the file before you edit it (Root explorer makes a backup, but you can never make too many. That and Root explorer makes a backup of the file before editing).
Steps:
1. Open Root explorer and navigate /system/usr/keylayout/ (That is scroll down and press the system folder. Scroll down again and press the usr folder. Press the keylayout folder)
2. At the top right corner of the screen press mount r/w
3. Long press "glacier-keypad.kl"
4. A screen will pop up, scroll down to "Open in Text Editor"
5. key 183 will say FUNC_4, change this to SEARCH (all caps)
6. Press the menu button
7. Press "Save Changes"
8. Long press power button
9. Press Restart
10.Try it out, and say thank you after it works.
Sorry but I was always told to explain it as if you were 10yrs old to prevent questions. Wasn't trying to offend anyone's intelligence.
Also while you're in there if you want to add WAKE_DROPPED after HOME, your phone will now wake when you press the home button.
If someone wants to make a guide for how to do this with adb, post it and I will update the op.
Click to expand...
Click to collapse
OMG this has been bugging me since my first boot! Thank you!!
Tried this while temprooted with visionary and didn't work. Copied the file to sdcard and edited it there, then moved it back to its original location, overwriting the original.
On reboot nothing changed. What'd I do wrong?
Brilliant!
Phateless said:
Tried this while temprooted with visionary and didn't work. Copied the file to sdcard and edited it there, then moved it back to its original location, overwriting the original.
On reboot nothing changed. What'd I do wrong?
Click to expand...
Click to collapse
If you only had temproot and have not unlocked then Nand, then when you reboot it likely didn't stick.......
Gr8gorilla said:
If you only had temproot and have not unlocked then Nand, then when you reboot it likely didn't stick.......
Click to expand...
Click to collapse
Ah... So is S-OFF required to achieve real permanent root? Or can I just use visionary to temp root --> perm root --> remount system as r/w and then go on my merry way?
Perm root is required, I have updated op to say that. Sorry for the confusion. S-off is required for this to stick, unless someone with S-on figures out a way to make it work.
21productionz said:
Perm root is required, I have updated op to say that. Sorry for the confusion. S-off is required for this to stick, unless someone with S-on figures out a way to make it work.
Click to expand...
Click to collapse
Ah ok, this will just have to wait a little then.
Hmm I just noticed something strange when I did this, my text on my lockscreen disappeared after doing this .. along with when I press the power button, the text for each option was gone .. restoring back to stock the text is back .. weird.
Worked perfectly!!! Home button now wakes screen and Genius button does Google search. Thank you so much.
Just did it without any hitches. Added Home_Dropped as well. THANK YOU DUDE!!! This made my day even better. Rooted and key re-mapping sweet.
wow awesome that was fast
Ok problem figured out, it was the font I replaced in my system it started acting weird thanks again!
I actually went back to the genius button, for some reason the voice search function could not get a single command right, it couldnt understand "call home" in a perfectly quiet environment, let alone any other commands, like texts, but thanks for the write up.
PolishDude said:
I actually went back to the genius button, for some reason the voice search function could not get a single command right, it couldnt understand "call home" in a perfectly quiet environment, let alone any other commands, like texts, but thanks for the write up.
Click to expand...
Click to collapse
I haven't rooted yet and I've also noticed that voice search performs surprisingly poorly on this phone. Wonder what's up with that?
I'm looking into a solution. It has nothing to do with changing it though. It's hearing it correctly, but not understanding commands. I say "call blah" and the search box comes up with call blah. Not cool.
Sent from my HTC Glacier using XDA App
21productionz said:
I'm looking into a solution. It has nothing to do with changing it though. It's hearing it correctly, but not understanding commands. I say "call blah" and the search box comes up with call blah. Not cool.
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
Mine's blatantly missing words. If I didn't know better I'd say the phone is sassing me for not using the genius button.
If you are like me you are not happy with the power button placement. I modded a few files that will allow any bluetooth keyboard to wake the screen from sleep. Very handy when the Xoom is docked. Requires Reboot.
Modded Files
Push the files via adb to /system/usr/keylayout/
Example:
adb remount
adb push Generic.kl /system/usr/keylayout/Generic.kl
adb reboot
Apple Keyboard (Vendor_05ac_Product_0239.kl) - Wake with eject key
Generic Keyboard (Generic.kl) - Wake with F1
Motorola Keyboard (Vendor_22b8_Product_093d.kl) - Wake with right ctrl key (Not Tested - Sorry do not have one)
Note:
After the keyboard and the Xoom have been asleep for a while, there may be a delay before the Xoom wakes. Bluetooth devices sleep to save power and it takes about 15-30 seconds to wake and sync again.
Thorough Explanation of Key Remapping:
Better explanation of this is here.
Getting back to default:
If you want to return things to default, download the default files and adb push them back to the Xoom.
Sweet! I'm going to give this a try later. Thanks!
Works great with the Motorola BT Keyboard...
edit: I did remap it back to the default CTRL_RIGHT and instead used the unmapped "reserved" key on the keyboard. It is the 4th key from the top right with 3 lines. Since this key is unused, it seemed more appropriate for now. It is key 226 in the mapping.
@triadX1
Sent from my Xoom using XDA App
Maybe someone in this thread can help me. I posted in other threads but nobody replied. I bought a generic BT keyboard with Apple keys. To remap the keys I downloaded a program to get the scancodes for each key and modified the Generic.kl. It di not change anything. The question is now, is there a way to name the .kl file like the other 3 already present, i.e. with a manufacturer-specific name? How else will HC know which file to use when the BT keyboard is connected? I hope I got my point across...Thanks everyone!
[sent with Xooming Android technology]
Just a heads-up: I have what must be an older version of the Apple Keyboard (bought in '97); the VID:DID are 05AC:022C :
Code:
apple 0005:05AC:022C.0001: input,hidraw0: BLUETOOTH HID v1.36 Keyboard [Apple Wireless Keyboard] on 40:FC:89:27:62:5C
I just copied your Vendor_05ac_Product_0239.kl to Vendor_05ac_Product_022c.kl and it works fine. Thanks for the mod!
funnycreature said:
is there a way to name the .kl file like the other 3 already present, i.e. with a manufacturer-specific name? How else will HC know which file to use when the BT keyboard is connected?
Click to expand...
Click to collapse
Can you get the Vendor ID/Device ID from the Keyboard?
"adb shell dmesg" once it's connected should be able to tell you. After that, it's just a matter of naming the file as such. For example a device with VID:DID 1234:ABCD would be named Vendor_1234_Product_abcd.kl .
HTH!
it was easy i just edited one file one line next to menu i put wake
Sent from my Xoom using XDA App
system/ust/keylayout/ and vrdb ....093 something then r/w then right click to edit text and scroll to 125 where it says MENU and make it look like this MENU WAKE and reboot and your good menu key is now wake one press wakes and two presses unlocks
Sent from my Xoom using XDA App
kcrudup said:
Can you get the Vendor ID/Device ID from the Keyboard?
"adb shell dmesg" once it's connected should be able to tell you. After that, it's just a matter of naming the file as such. For example a device with VID:DID 1234:ABCD would be named Vendor_1234_Product_abcd.kl .
HTH!
Click to expand...
Click to collapse
I found out that the generic keyboard uses the Apple layout. I want to post a How-to soon but I have very little time lately Thanks for the info though; how would I find the information? I tried connecting the keyboard to my laptop via BT and opened the device manager. Is there any property that shows the VID:DID?
I'm curious as to why the key 226 isn't being used when there's actually no key used to open the app menu. I would have assumed the key used for menu (two keys to the right of the spacebar) would be used for the app menu and the unused key (three horizontal lines) would've been for the menu since most apps I've seen with the on-screen menu looks the same. Plus the icon for the Apps menu actually looks like what is on the Menu key for the keyboard.
What would I need to add to the keyboard file to make a key open the application menu? After looking over the keymaps in the file I couldn't see any key on the keyboard that would open the app menu.
Use 226 for whatever
You can remap 226 to be menu if you want, but i don't know the command to open the app "drawer" on honeycomb.
Just like they said above, the file you want to edit is in
/system/usr/keylayout/
I use root explorer because it lets me edit easily as well. If you want to do it the way i do just follow the steps below:
1- Mount R/W when you get in the folder
2- Long hold on "Vendor_22b8_Product_093d.kl"
3- Select "Open in Text Editor"
4- Scroll all the way to the bottom where it says 226 and edit the line to read
key 226 MENU (3 spaces between 226 and MENU)
if you simply want it to be another Menu key. (Before editing, it says unused or tbd or something, just erase all of that )
Alternatively try:
key 226 MENU WAKEif you also want it to wake up your tablet.
Personally, I edited key 125 to wake up the tablet as described above, and put
key 226 POWERso that i could also lock the screen, thus using the otherwise useless key.
As a sidenote, Root Explorer *should* automatically make a backup for you when you edit the keylayout file, but doing one manually (aka: copy and paste somewhere else on your sdcard) is always a smart move.
Good Luck!
kcrudup said:
Can you get the Vendor ID/Device ID from the Keyboard?
"adb shell dmesg" once it's connected should be able to tell you. After that, it's just a matter of naming the file as such. For example a device with VID:DID 1234:ABCD would be named Vendor_1234_Product_abcd.kl .
HTH!
Click to expand...
Click to collapse
I tried this command and I get a "error: device not found" message. I am using my droid 1 and the blueputdroid app to use my hard keyboard as a bluetooth one. The keyboard works... I just would like to map some things out to open the app drawer and such. Thank you in advance for any help
Sent from my Droid using Tapatalk
That error means adb can't find your xoom. Make sure you have USB debugging enabled
sangreal06 said:
That error means adb can't find your xoom. Make sure you have USB debugging enabled
Click to expand...
Click to collapse
Hmm I have tried it from the zoom itself with a terminal app as well as from the PC and have made sure debugging is running and have gotten the same result each time :/
Sent from my Xoom using Tapatalk
This requires root. I am assuming those having trouble have rooted their phones and have the moto drivers installed on their PC. If adb devices does not show your device then try running the following:
adb kill-sever
adb start-server
adb devices
See if the device shows up now. I am calling these commands from my memory so I could be wrong about the wording. Running adb /? will give you a list of command line switches.
Sent from my Xoom using XDA Premium App
B Dizzle said:
This requires root. I am assuming those having trouble have rooted their phones and have the moto drivers installed on their PC. If adb devices does not show your device then try running the following:
adb kill-sever
adb start-server
adb devices
See if the device shows up now. I am calling these commands from my memory so I could be wrong about the wording. Running adb /? will give you a list of command line switches.
Sent from my Xoom using XDA Premium App
Click to expand...
Click to collapse
Hmm it STILL doesn't see it. I know I am an unlocked and rooted xoom. I am running rooted apps just fine and browsing all my system files just fine on the computer with Droid explorer. I just can't get it to see my device in adb. Any ideas?
Sent from my Xoom using Tapatalk
Does anyone here have 3.1? I updated to 3.1 which removed the customized file I replaced for the zoom keyboard, but I read in another thread where a person talked with a rep (i'm thinking from either moto or vzw) about the update stating that the update included "Additional shortcut key support for Bluetooth keyboard".
The file I used was from 3.0 and since I didn't know this at the time, I didn't back it up first. I know...it was stupid not to do so, but whatever lol
If anyone could pull the new 3.1 keyboard layout file for the motorola keyboard and post it, that would be great.
SPIDERTECH said:
Does anyone here have 3.1? I updated to 3.1 which removed the customized file I replaced for the zoom keyboard, but I read in another thread where a person talked with a rep (i'm thinking from either moto or vzw) about the update stating that the update included "Additional shortcut key support for Bluetooth keyboard".
The file I used was from 3.0 and since I didn't know this at the time, I didn't back it up first. I know...it was stupid not to do so, but whatever lol
If anyone could pull the new 3.1 keyboard layout file for the motorola keyboard and post it, that would be great.
Click to expand...
Click to collapse
Anyone able to pull this file for me? It's the Vendor_22b8_Product_093d.kl
SPIDERTECH said:
Anyone able to pull this file for me? It's the Vendor_22b8_Product_093d.kl
Click to expand...
Click to collapse
Here ya go http://db.tt/9fAD3NS
Sent from my Xoom using Tapatalk
ruvort said:
Here ya go http://db.tt/9fAD3NS
Sent from my Xoom using Tapatalk
Click to expand...
Click to collapse
Thanks for that. It looks like the 226 key is STILL not being used. I'm curious now as to what the additional shortcuts were supposed to be.
*Note: By using this method you don't have to worry about re-imaging with someone else's nook rom and overwriting your mac address and serial # with someone else's.
There are two parts to the re-flash, you must do both in this order
1. Re-imaging the PROGRAM portion of the nook.
2. Re-imaging the data portion of the nook.
Part one: Re-image the Nook Touch /system partition
Your nook must already be properly rooted for this to work. Install adb on your PC if you don't have it already. Prep your nook by installing "adb wireless" from the app store and run the app. (if you don't know how to use adb, google it)
Run the "adb wireless" app on your nook and press the "big button" and take note of your nooks ip address.
We now can connect the nook through the adb shell and manually change the BootCnt file so that the boot count is 8. This avoids the pain of manually interrupting the boot process 8 times.
connect to your nook by typing "adb connect (nook ip)" from your pc
Once you have connected to your nook, use the following commands:
adb shell
echo -n -e "\x08\x00\x00\x00" > /rom/devconf/BootCnt
reboot
Thats it for part one. Your nook will reboot and start the re-imaging process. Let it finish and reboot again.
Part two: Re-imaging the data portion of the nook
1. Go to Settings
2. Select "Device Info" under the top "Device Settings" section
3. Select "Erase & Deregister Device"
4. Select the "Erase & Deregister Device" button
5. Select the "Reset Nook" button
A Deregistration message will appear and the nook will reboot.
Upon reset a Clearing data message will appear
This may take a few minutes. The nook will reboot again once complete.
Thats it! Smell that Fresh clean stock nook!
I must give credit to nookdevs dot com. They posted this process for unrooting the nook color. The process is exactly the same for the nook touch. I am a noob on this board so I can't post links yet. I have verified this process works. I had to unroot my nook to get the Shop to work again. Hope this helps. Good luck!
Is it normal for the nook to at the very end of the process bar ? What do I do ? Did I screw it ? I am afraid to try powering it off ?
Please edit your question. I don't understand what you are asking.
Thanks
vacano said:
Is it normal for the nook to at the very end of the process bar ? What do I do ? Did I screw it ? I am afraid to try powering it off ?
Click to expand...
Click to collapse
Are you asking if it is safe to turn off the nook while the progress bar is still visible? Did the progress bar freeze? Please provide more information, I don't understand your question.
Yes. It froze at the very end
Here I have attached a picture as well.
http://forum.xda-developers.com/showthread.php?p=15880635#post15880635
vacano said:
Yes. It froze at the very end
Here I have attached a picture as well.
http://forum.xda-developers.com/showthread.php?p=15880635#post15880635
Click to expand...
Click to collapse
I would just power it down. There is nothing else you can do in that state. How long did you wait?
I'm having trouble getting the Market app to find the adb wireless app...any idea if there's a direct way to install it? Thanks!
coolkatz321 said:
I'm having trouble getting the Market app to find the adb wireless app...any idea if there's a direct way to install it? Thanks!
Click to expand...
Click to collapse
If you rooted with TouchNooter than you shoud have the ADB packages installed. Using the ADB wireless makes things easier, however you can run ADB over usb. Just google "ADB over USB nook" and you will see the link for the nookdevs forum. It gives the instructions for windows, mac, and linux.
I would post the links, but I can't as of yet because I am a noob. One more post should get me to 8.
coolkatz321 said:
I'm having trouble getting the Market app to find the adb wireless app...any idea if there's a direct way to install it? Thanks!
Click to expand...
Click to collapse
Oh yeah... I almost forgot...try this first... There is a known problem where you can't search in the android market. Just go to amazon and get the amazon android market instead. That is what I did.. and if all else falls...you can use the ADB over usb.
J.Harmon said:
Oh yeah... I almost forgot...try this first... There is a known problem where you can't search in the android market. Just go to amazon and get the amazon android market instead. That is what I did.. and if all else falls...you can use the ADB over usb.
Click to expand...
Click to collapse
How did you get the Amazon market?! My Nook simply does not want to play nice.
coolkatz321 said:
How did you get the Amazon market?! My Nook simply does not want to play nice.
Click to expand...
Click to collapse
open up your browser on your nook and go to:
http://www.appbrain.com/app/siir.es.adbWireless
appbrain.com will probably have you set up an account before you can download it.
google is your friend.
My Unroot Method
Maybe this will work for you all too. It worked really well for me (but this is assuming you don't have the 1.0.1 update):
1 - Turn nook off and turn on pushing power button than 2 bottom buttons.
2 - Press home twice to clear data
3 - Login as normal and then go to Settings and Erase and DeRegister your Nook
4 - When nook comes back up login and register nook as normal
5 - Download http://su.barnesandnoble.com/nook/n...Dpomf5qvKtTeXxjxcgaa2cS/nook_1_0_1_update.zip and put it on the root of your nook (not SD card)
6 - Let nook apply the update
7 - That should be it.
I deregistered it after that. Rebooted. Reset. Rebooted. Every time came up stock for me to register.
Kohr-Ah said:
Maybe this will work for you all too. It worked really well for me (but this is assuming you don't have the 1.0.1 update):
1 - Turn nook off and turn on pushing power button than 2 bottom buttons.
2 - Press home twice to clear data
3 - Login as normal and then go to Settings and Erase and DeRegister your Nook
4 - When nook comes back up login and register nook as normal
5 - Download http://su.barnesandnoble.com/nook/n...Dpomf5qvKtTeXxjxcgaa2cS/nook_1_0_1_update.zip and put it on the root of your nook (not SD card)
6 - Let nook apply the update
7 - That should be it.
I deregistered it after that. Rebooted. Reset. Rebooted. Every time came up stock for me to register.
Click to expand...
Click to collapse
Thanks! This method has worked best for me.
Now that you upgraded to the 1.01 update, will this method still work?
Have you tried it?
I have not yet as I haven't tried rerooting it again.
Sent from my HTC Sensation 4G using XDA App
I have a big problem on my HTC Droid Incredible.
Bypassing the activation screen really irritates me and i can't turn on the USB Debugging which is the key to root and s-off my phone and to bypass the activation screen.
The procedure i did for bypassing the activation screen are: tap 4 corners, safe mode, call *228 and end call after few seconds (did this several times), cdma workshop, ##778 change the nam setting, and non of them works for me.
cmlusco member of xda told me that the best way to bypass it is to change the build.prop in any rom i'm going to flash on my phone. Then he give me this link http://forum.xda-developers.com/showthread.php?t=1306400 and i think this is it, but in the end still failed because i need to turn on my USB Debugging.
Please help me to bypass my Droid Incredible.
I'm here in Philippines and there is no Verizon network provider here.
I already solve this problem and I can use my Droid Incredible. Sweet!!!View the 3rd post how did i do that.
Click to expand...
Click to collapse
are you able to fix this?im having EXACTLY the same problem.
yup I already fix it, just follow this procedure.
1) try to enable usb debugging mode by doing this procedures.
for this,you should need wi-fi.
so,let's start
1)when the phone calls to *228 tap contacts icon,right to the "end call"
2)try to add a new contact and enter facebook or other socialnet dialog.
phone asks you to enable wifi, do this and connect your wifi network
3)next hold the search button and (via voice search) search in google "market"
4)tap to the official market page, phone asks you about opening this page,choose market app.login in the google accounts,if you need.
5)search in market "usb debug" app. install it and tap "open' in the market app
6)enable usb debugging and enjoy)
and for those who don't have a wifi connection in there home, this procedure is for you.
1. call *228 and tap the contact on the right side of end call.
2. add contact and put any information.
3. try to connect it in facebook to prompt the setting window.
4. tap setting.
5. tap search softkey and type application.
6. finally you can enable usb debugging without any problem.
thanks to ramazancik94 for giving this life saver step for enabling usb debugging mode.
2) root and s-off your phone by following this procedure root 2.3.4,downgrade,and s-off
3) if you already have CWM, rooted, and s-off your phone try to install some ROM using CWM in development section. Double check if your phone is s-off via hboot (press and hold power button and volume down), your phone is rooted if you install CWM, and find some ROM that suits your need.
4) Try to use the "end call bypass" if this method doesn't work with you this will be your last resort. Delete the phone.apk before you install the rom, to delete the phone.apk open the "blah blah blah rom.zip" and go to data> system app> find phone.apk and please don't extract the rom and delete the phone.apk or i won't work, just delete it from the zip.
Note: Deleting the phone.apk will result for disable your phone signal. So you're going to use your phone for music, game, watch some movies and wifi internet. You won't be able to use it for call, text and mobile data, and also please read it carefully so you won't **** your phone. You've been warned
For more information visit this thread: help bypass the activation
All big thanks to cmlusco, ramazancik94 and tiny4579 for their help
need help
sir maybe you can help me with this...im new to android phones and i dont think i can make it
can you please send me the step by step procedure of the things i need to do after i put my phone in USB debugging mode?hope you dont mind
my email is [email protected]
my tcp account is kian0926, im here in the Philippines as well and im glad that you were able too fix yours, hoping that i can use mine as well, saving this device from a trash can
many thanx in advance...
i can't get my ADB working
after i extracted mini-adb under c drive (c:\mini-adb_inc) i extracted adb inside of it
but icant get adb working
when i tried to open adb it just flashes (like blink of an eye) and closes itself immediately
i cant proceed
pls help..............
Kian0926 said:
i can't get my ADB working
after i extracted mini-adb under c drive (c:\mini-adb_inc) i extracted adb inside of it
but icant get adb working
when i tried to open adb it just flashes (like blink of an eye) and closes itself immediately
i cant proceed
pls help..............
Click to expand...
Click to collapse
You cant just click on the adb.exe file, it is a cmd line program. Open a cmd prompt on your pc and type " cd C:\mini-adb_inc " then type in your adb command, example " adb devices " this should show the serial number of your phone if connected to the pc and adb and drivers are setup correctly.
thnx for the reply
but this " cd C:\mini-adb_inc " seems to be invalid when im trying to enter n the command prompt window
i already tried removing those that i downloaded and download them again but still the same thing...
---------- Post added at 02:19 AM ---------- Previous post was at 02:11 AM ----------
also inside of mini-adb extracted on my c drive theres no adb.exe.it just say's adb
under that is AdbWinApi....so cunfused now
Kian0926 said:
thnx for the reply
but this " cd C:\mini-adb_inc " seems to be invalid when im trying to enter n the command prompt window
i already tried removing those that i downloaded and download them again but still the same thing...
---------- Post added at 02:19 AM ---------- Previous post was at 02:11 AM ----------
also inside of mini-adb extracted on my c drive theres no adb.exe.it just say's adb
under that is AdbWinApi....so cunfused now
Click to expand...
Click to collapse
What makes you think the cd command didnt work, did it give an error? All cd does is change the directory to C:\mini-adb_inc where the adb file is located. It is ok if it says just adb and not adb.exe, your pc is just set to hide extensions. When you first open the cmd prompt to the left of where you type it will say something like C:\users\your_user_name\desktop >, when you type cd C:\mini-adb_inc it should go to the next line, and to the left of where you type now it should say C:\mini-adb_inc >Then type adb devices and see if a serial number comes up.
"C:\users\your_user_name\desktop" his is what i exactly saw on my laptop and when i tried enterring "c:\mini-adb_inc" a message appears say's like "incorrect path/directory"
im gonna try using another PC and hope this time it works..
Kian0926 said:
"C:\users\your_user_name\desktop" his is what i exactly saw on my laptop and when i tried enterring "c:\mini-adb_inc" a message appears say's like "incorrect path/directory"
im gonna try using another PC and hope this time it works..
Click to expand...
Click to collapse
You have to type " cd C:\mini-adb_inc " or what ever the path is to the adb file. here actually try this. Go to the folder where the adb file you unziped is. Then hold ctrl + shift and right click on an empty space in that folder, and select open cmd prompt here. then type in your adb command, ie adb devices.
after i successfully activated,rooted to 2.3.7 with cm7 ROM my droid incredible it was working perfectly fine,but after a couple of hours using my droid it unexpectedly shut itself down and left me with just a blinking orange led at the top of it..last application running is viber,im on a call actually..and my phone is on charge...
what might be the cause of it?and can this be fixed?..my phone is completely dead
i even tried resetting the phone(pressing volume down button and power button but still no reponse..
Kian0926 said:
after i successfully activated,rooted to 2.3.7 with cm7 ROM my droid incredible it was working perfectly fine,but after a couple of hours using my droid it unexpectedly shut itself down and left me with just a blinking orange led at the top of it..last application running is viber,im on a call actually..and my phone is on charge...
what might be the cause of it?and can this be fixed?..my phone is completely dead
i even tried resetting the phone(pressing volume down button and power button but still no reponse..
Click to expand...
Click to collapse
Sorry to say, but if you cant enter hboot, or boot up to the os or recovery, then the phone is more thsn likley bricked. Unless its a battery issue. Does it vibrate at all when trying to start?
Kian0926 said:
after i successfully activated,rooted to 2.3.7 with cm7 ROM my droid incredible it was working perfectly fine,but after a couple of hours using my droid it unexpectedly shut itself down and left me with just a blinking orange led at the top of it..last application running is viber,im on a call actually..and my phone is on charge...
what might be the cause of it?and can this be fixed?..my phone is completely dead
i even tried resetting the phone(pressing volume down button and power button but still no reponse..
Click to expand...
Click to collapse
Does it boot when plugged in? There MAY be some help if it can boot when connected to AC power.
Kian0926 said:
after i successfully activated,rooted to 2.3.7 with cm7 ROM my droid incredible it was working perfectly fine,but after a couple of hours using my droid it unexpectedly shut itself down and left me with just a blinking orange led at the top of it..last application running is viber,im on a call actually..and my phone is on charge...
what might be the cause of it?and can this be fixed?..my phone is completely dead
i even tried resetting the phone(pressing volume down button and power button but still no reponse..
Click to expand...
Click to collapse
I've experience this, just a blinking orange led. What did I do was i charge it and a couple of minute the the blinking orange led stops and it become a steady orange led.
Easier way (offline)
Found what could be an easier way, I'm playing with my sister's incredible and I can get usb debugging enabled by using any of the official verizon update packages (could be a rom, but I downloaded the smallest hboot upgrade from htcdev), it appears to send some commands in usb mode that trigger the activation of usb debugging, what's funny if that if you either disconnect before it's done, or it fails, it leaves usb debugging on.
Non-sense.
EDIT: You just have to open the utility, you don't to flash or disconnect.
Such and old thread but I have a Incredible that a friend gives me and I couldn't access the market app by search function. What I did was search anything with voice commands, then a navigator window opens and change the URL to: market://details?id=usb, it opens the market app and I can install the USB debug app
Simple method, without the use of USB Debudding/rooting flashing:
Go to Emergency dialer,
Enter ##778, and press 'call'
Select 'Edit Mode'.
Password is: 000000
Select 'NAM Settings'
Make the following changes:
MDN = your 10 digit phone# (0000000000)*
MIN1 = your 7 digit phone# (0000000)
MIN2 = the area code of your phone# (000)
Press the 'back' key and go to 'HOME SID/Home NID' settings
Select 'Home SID/NID #1', and change the first value to '189' (Leave the 65535 alone).
Now press your 'menu' key
Press 'commit modifications' "button"
Phone Should reboot now.
Changing MDN using cdmaDevTerm
In some phones MDN cannot be changed, in this case you need to connect the phone to the computer as a "modem" device, and use the opensource cdmaworkshoptool / cdmaDevTerm from here:
http://code.google.com/p/cdmaworkshoptool/
Connect the tool, select manually / automatically the COMPORT for your HTC device, Read from device, Change the MDN to 0000000000 Select write
Disconnect and reboot your device.
It should now by pass the activation.
most of the ref. from
http://androidforums.com/incredible...g-activation-screen-no-service-available.html
hi,im new here,i just wanna seek some help regarding to my xplay multifunctional key button(the third key beside home button.)its always stock when i wanna use that key.sometimes working and sometimes most of the time not functioning.you need to push it a lot of times until it works again.any idea why its happening in xplays or only just for me?thank for any help
I think you mean the Menu key. Perhaps its broken. If you have root, you can edit the file "/system/usr/keylayout/keypad-zeus.kl" to change the function of each physical buttons. You could for example remap the Search button to Menu.
eksasol said:
I think you mean the Menu key. Perhaps its broken. If you have root, you can edit the file "/system/usr/keylayout/keypad-zeus.kl" to change the function of each physical buttons. You could for example remap the Search button to Menu.
Click to expand...
Click to collapse
thanks buddy i have a root but problem is i dont know how to remap each button.im noob and only basic knowledge iknow regarding that.can you help me how to do that step by step.i check system/usr/keylayout/keypad-zeus.kl using es file xplorer.i dont know what to type and to do.a big help from you is much appreciated.
please i need help.now my home bu
tton stuck also when i try to tap on it.but when my play are open i mean the gamepad is visible,the home button works fine and the menu button also working.is this some kind of hardware issues/malfunction?please any help would be appreciate
Sent from my R800i using Tapatalk 2
By malfunctioning you mean your buttons are broken then yes. Of you want to avoid this issue in the future, buy a Nexus.
Enable root permission for ES File Explorer, copy the file to your sdcard, tap and hold on the file and choose Open As -> Text -> Es text editor. Edit the file to remap the button to how you like it. Copy it back to its original location. Tap and hold on the file again and choose Permission. Set the permission to rw-r-r.
Also if you know how to install custom roms, with Slim Bean rom you can enable onscreen button.
Sent from XDA app
eksasol said:
By malfunctioning you mean your buttons are broken then yes. Of you want to avoid this issue in the future, buy a Nexus.
Enable root permission for ES File Explorer, copy the file to your sdcard, tap and hold on the file and choose Open As -> Text -> Es text editor. Edit the file to remap the button to how you like it. Copy it back to its original location. Tap and hold on the file again and choose Permission. Set the permission to rw-r-r.
Also if you know how to install custom roms, with Slim Bean rom you can enable onscreen button.
Sent from XDA app
Click to expand...
Click to collapse
I DO WHAT YOU TUTORIAL.but it seems its the same thing happened.still doesnt workwhen you slide up the play i mean gaming buttons are visible,the home button is working even i used it for CWM.but also the search menu.but when i close the lid,agin it doesnt work.