Hello guys...
I've trying to reach the recovery menu, but I got myself uncessful.
My X key from the keyboard are strange, for example when I go type a menssage with the physical keyboard, I press "X" and it type "dEXAW".
Also the "del" key isn't working, neither "enter" or "j" and some more...
I found this Milestone and it was locked with a password at CM7, so I downgraded it to 2.1 stock and done nothing else, I put OpenRecovery on it but I can't acess the OR cause the "x" is crazy...
All the keyboard is weird.
Please, I beg for some help.
Thanks so much
Someone knows if I need to replace this file sholes-keypad.kcm.bin at /system/usr/keychars/sholes-keypad.kcm.bin?
Another uptade...
I tried replace the files: /system/etc/motorola/12m/key_code_map.txt and OpenRecovery/bin/change_keyboard_layout.sh
But nothing changed.
The issue started when I did again the OpenVulnerable on SBF..
Im totally lost, I can't do nothing!!!! Without the acess at OR menu I can't try CM7.
Related
Hey all,
I have a problem with my keys on the phone.. as of right now my home key the green send key and my keyboard shortcuts for apps are not working.
I'm running the apps to sd mod on the jf 1.5 rom... its been running ok for about 2 weeks nowand out of nowhere my hardware keys stopped working.
I have rebooted the phone plenty of times and everytime I reboot it tells me a process name cool.magic has to force close.. could that have something to do with it?
I have also searched the forums and could not find anything relevant.. I have never needed to post a question till now because I'm usually pretty successful at searching the forum.
Please help.. I really don't wanna have to wipe my fone.
Thanks in advance. =)
Can you reflash your phone with the JF 1.5??
Hey i Itried to re-flash the jf 1.5 update and nothing.. the keys still don't work.
I think it has something to do with the coolmagic.app.toggle5 that keeps force closing when I reboot... any other suggestions before I wipe the phone?
When I first got my g1 I loved it. Then the cupcake update happened. Everyone was overjoyed - except me. My phone went much slower and juddery, and loads of little errors happened. Now these are the 2 problems i need help with:
Rotating. The phone stays in either portrait or landscape mode and won't rotate to the correct mode with the keyboard sliding in or out.
And
Messaging. Whenever I send an sms message i get a force error as soon as the text is sent through.
PLEASE HELP ME :'( :'( before i go to t-mobile and cancel my phone - it has got that bad ((((((((((((((((((((((
If you need anymore info just ask thanks,
Ross.
You might want to try re-flashing the cupcake update, if your phone is rooted then you can search around and find out how to do it easily. If not you need to find the official tmobile cupcake update, I dont have any link for it but I am sure if you search here or google you will find it. You then need to plug your g1 into the usb on your pc and mount the sd card, if it is a .nbh file name it DREAMIMG.nbh, if its a .zip name it update.zip and copy it over. Then reboot into spl by holding camera+power and follow onscreen instructions. Good luck.
Try doing a wipe and see if that fixes your problems.
If wiping doesnt fix your problem id hit t mobile up for a replacement
hey guys, i am running JACXHERO 1.8 and i love the rom, one problem though. when i flashed the rom i had that text box with the circle around the M and it wouldnt go away so i just de-selected touch input and then pressed home, and tried to go back to settings and enable it again, but now i cant even access locale and text, when i click on it i get a FC. if i remove HTC_IME.apk via appmanager i can access the menu... i have tried pushing HTC_IME from the .zip file of the rom and no luck... i am about to try an older HTC_IME. you guys have any other ideas, or a way that i can enable Touch Input without accessing that Locale and text menu?
Long press hold on a text box and it will have a menu allowing you to select Input Method.
h.nocturna said:
Long press hold on a text box and it will have a menu allowing you to select Input Method.
Click to expand...
Click to collapse
i rememeber seeing this on other builds, so i know its possible, but when i long press i dont get any options that come up. i can copy and paste but thats about it.
palosjr said:
i rememeber seeing this on other builds, so i know its possible, but when i long press i dont get any options that come up. i can copy and paste but thats about it.
Click to expand...
Click to collapse
Probably because you disabled On Screen Keyboard via the Locale and Input Menu... not much you can do to fix that other than re-flash the ROM. =/ Sorry.
h.nocturna said:
Probably because you disabled On Screen Keyboard via the Locale and Input Menu... not much you can do to fix that other than re-flash the ROM. =/ Sorry.
Click to expand...
Click to collapse
ok thanks. quick question. can i just reflash without wiping everything? i know its a noob thing to ask but wouldnt the reflash just fix anything i have changed as far as the ROM is concerned. if not no biggie i can restore all my apps, i just was trying to find an easy way to get it working
@ palosjr: did you ever figure this one out? i'm having the exact same problem and I've flashed the ROM like 7 times, but nothing helps.
I got a G1 the other day, and for some reason the home button doesn't work. I've tried restoring the phone, and taking the battery out, and etc. but the home button still doesn't work. Now for some reason my internet isn't working on the G1 so I can't pass through the G1 activation screen. I'm have the web2go internet plan. I have my apn set up as internet2.voicestream.com and I got another one internet3.voicestream.com and wap.voicestream.com none of them worked on my G1, there's also no wifi option on it, but everything functions perfectly on my Nexus one. Can anybody help me figure this out? I also tried to install drivers, but Windows says that the drivers I have are already the best ones, it still comes up as an unknown device.
So to sum it up, I need help bypassing the activation screen, and getting the web2go to work.
You can always try this method to sign into the Google account via WiFi. This involves setting up ADB on your computer and using commands to access your phone's Settings screen, and then turning on wifi on your phone to connect. If you want to try this method, make sure you're on a stock Android RC29, or else it won't work. To check if you're on RC29, go to your phone and type <enter>reboot<enter>, if your phone reboots, you're on RC29.
<enter> is where you should press the enter key on your keyboard.
http://wiki.cyanogenmod.com/index.php?title=G1_logon_to_google_via_wifi
Sleeps17 said:
You can always try this method to sign into the Google account via WiFi. This involves setting up ADB on your computer and using commands to access your phone's Settings screen, and then turning on wifi on your phone to connect. If you want to try this method, make sure you're on a stock Android RC29, or else it won't work. To check if you're on RC29, go to your phone and type <enter>reboot<enter>, if your phone reboots, you're on RC29.
<enter> is where you should press the enter key on your keyboard.
http://wiki.cyanogenmod.com/index.php?title=G1_logon_to_google_via_wifi
Click to expand...
Click to collapse
I tried the method above, but my phone doesn't reboot. I think I'm probably on RC30. This phone has 1.5 on it.
Download this and put it on the root of your SD card, make sure it's named as DREAIMG.nbh exactly, case sensitive. Go to your phone and hold down the Camera and Power button to enter bootloader mode. Flash the file and restart your phone, you'll be on RC29 now.
Sleeps17 said:
Download this and put it on the root of your SD card, make sure it's named as DREAIMG.nbh exactly, case sensitive. Go to your phone and hold down the Camera and Power button to enter bootloader mode. Flash the file and restart your phone, you'll be on RC29 now.
Click to expand...
Click to collapse
Thanks I'll try it out.
Alright, that worked great, but I want to root it too now. Like I mentioned my home button is broken, so I can't boot into recovery by holding Home+End, I tried adb shell reboot recovery but I get something like "Operation denied"
I think that command needs root access to fuction.
Just follow the rooting tutorial.
http://forum.xda-developers.com/showthread.php?t=442480
Sent from my HTC Dream using XDA App
CyanogenMod V6.0.0 Stable // HBOOT-1.33.2005 // Radio 2.22.23.02 T-Mobile USA
Thanks for all your guy's help. I was wondering is it not possible to use the internet2.voicestream.com apn on the G1?
I wouldn't know. Go to the APN settings and click the Menu button and then select "Set to default", should automatically choose the correct APN for you.
Sent from my HTC Dream using XDA App
CyanogenMod V6.0.0 Stable / HBOOT-1.33.2005 / Radio 2.22.23.02 T-Mobile USA
Well I'm using the web2go internet. I was wondering if it works with the G1?
Keyfix
Hi, you can spray isopropyl Alcohol (the one that does not contain water, find it very cheap on electronic shops) all over the button and press it repeatedly (without battery) and wait a couple of hours, some buttons on my keyboard didn't work and after this they're working fine
I searched in the Rocket, midnote and Criskelo threads but I couldnt really find any solutions. A few people have had same issue but I couldnt find any solutions.
I have tried all of the above ICS roms and they all work great other than the fact that the home button does not work to go home. It will wake up the device however. Am I missing something?
Also searching.
Until yet only got to know its the ICS Pre-Keyboard causing a remapping of the Numbers assigned to functions (Hardkeys)
My homebutton isnt working either anywhere but it can unlock the device (Escape Lockscreen)
Yet trying to find out whats the keynumber in the generic.kl (/system/usr/keylayout) to assign the "ESCAPE" by myself to the correct number. Hope it helps - also heard rumours talking about its a driver issue - i dont hope so ...
Maybe someone with a note (edit: [email protected]) could post his "generic.kl", maybe theres a simple difference and we could easy get rid of it ;-)
I had the same issue even after a full factory reset and reroot. It happened with the chinese leak and with midnote. I'd give anything for a solution to this problem.
The funny thing is:
If i flash the stock buggy ICS "I9220LP1-N7000-ICS-REPACK.tar" via Odin the Homebutton is fully working (But everything else not very well ). I am doing it right now for getting a backup of the whole /usr folder.
After that i will flash the rocketrom again where the homebutton isnt working and going to try to find the difference in these keyboard files. Maybe thats all ...
Hope ill get it soon - maybe even my approach is totally wrong, but hey: try is in the eating. If it is really driver related i cant do anything to get that button working - just wait till some devs get intouch with that issue.
I'm rooting for you, friend.
Call it coincidence, but right after reading your thread, my home button has topped working too
Anyhow, in sec_key.kl, the HOME key is listed with 102. Same in gpio-keys. kl, and qwerty.kl. This value is the same across AOSP v4, v5 and MIUI rev 4a, and ROMOW V1.
In generic.kl, 102 is MOVE_HOME.
This leads me to believe that the key is indeed mapped correctly, and that changing it to ESCAPE won't work. Why? I tried something. In 'melfas-touchkey.kl' and 'sec_touchkey.kl', keycodes for both the capacitive buttons are assigned.
key 158 BACK WAKE
key 139 MENU WAKE
I changed 139 to HOME in both the files, and rebooted. The button itself stopped working, but was able to wake the phone(behaving exactly like the home key). This suggests that the problem has nothing to do with the key mapping, but the HOME action itself.
I haven't tried to change 102 with something else, but I'm about to do just that, to see if the button works if mapped to some other command. If nothing works, I'll flash the whole thing again (GB->CF repack>AOSP) and pray it works
If flashing the whole thing over again ends up working, can you please give us the details of what stock rom you used at the start? I did a full wipe to a stock KK1 rom and went from there and the home button issue persisted. I'll promise to donate to the first person that comes up with a solution
Lance Uppercut said:
If flashing the whole thing over again ends up working, can you please give us the details of what stock rom you used at the start? I did a full wipe to a stock KK1 rom and went from there and the home button issue persisted. I'll promise to donate to the first person that comes up with a solution
Click to expand...
Click to collapse
Yes, flashing the whole thing again works. You NEED to flash Chainfire's ICS repack before flashing any ICS ROM. Get it here : http://www.mirorii.com/fichier/3/501208/I9220LP1-N7000-ICS-REPACK-tar.html
I'm on AOSPv4.
CF's repack can be flashed via mobile/PC Odin(PC Odin will increase your binary count and give you a yellow triangle, mobile odin will NOT.)
What I did was to go to KL3 rootable GB ROM(India), root it with zergrush, install CF root kernel, then Mobile ODIN-ed to CF ICS repack. (Make sure you keep 'enable everroot' UNCHECKED. CF repack is already rooted.)
After that, you have CWM to go to any other ROM. I believe you need to flash a base and the final release for RocketRom, or MIUI.
You are my hero bloodyhippo! Set up a donate link. You've earned it
Lance Uppercut said:
You are my hero bloodyhippo! Set up a donate link. You've earned it
Click to expand...
Click to collapse
Haha
Glad to help Lance! Though this is nothing new, flashing the whole thing in the manner it is supposed to be done removes most all problems that aren't official bugs. So, it's definitely not donation-worthy, but I've added a donation email, just in case ;-)
It's donate-worthy to me! You have no idea how many headaches I've had over this thing. Now I finally get to enjoy some ICS goodness.
Aw, thanks!
Lance Uppercut said:
It's donate-worthy to me! You have no idea how many headaches I've had over this thing. Now I finally get to enjoy some ICS goodness.
Click to expand...
Click to collapse
I really didn't think it was that big a headache for you! You know, I didn't read most of the developer's thread, so I had no idea this problem even existed. And my button stopped working after I updated to AOSP v5, while reading this thread
Anyhow, I'm glad(and lucky ) to have helped you out! Thanks for the $$
[EDIT] I think I'll re-donate it to some dev. Now that's a lot of options
home button working again
I upgraded from Stock Samsung N7000DDLB2 2.3.6 2012 February to (18.05.2012) AlBa XXLPY Full Repack v2.2 with a full wipe.
Everything was working fine in the beginning (i had setup a pattern lock too), till I restored all apps and data. I had restored contacts, sms too after which I noticed the home button stopped taking me back other than waking up the device and there was no pattern lock either. Somehow, that had gotten disabled and reset to back to swype unlock. Now, I setup the pattern lock again and the home button started working again. Went back to swype instead of pattern(without reboot) and home button still works. Any thought on how that happening?