Database Info

How to use QWERTZ keyboard in Haykuro 6r1

Download this attachment:
http://forum.xda-developers.com/showpost.php?p=3838743&postcount=8
Then:
in windows:
adb pull /system/usr/keychars/trout-keypad-v3.kcm.bin trout-keypad-v3.kcm.bin
This backups your existing keylayout.
Then: (you must have the downloaded (unzipped!) file on C: !!)
cd C:\
adb remount
adb push trout-keypad-v3.kcm.bin /sdcard/trout-keypad-v3.kcm.bin
adb shell
cd /sdcard
dd if=trout-keypad-v3.kcm.bin of=/system/usr/keychars/trout-keypad-v3.kcm.bin
reboot
Your device should reboot now and TADA you have fully working QWERTZ!
Please correct my commands if they are wrong.
Disclaimer:
You know this..

can you give me codes to work with the terminal (I don't use sdk -ADB)
And , does it fixes all other stuff to like + - :.... or just swap Z and Y.
(I need that fix so much)
Thanks

Copy the file to your sdcard then:
su
mount -o rw,remount /system
cp /sdcard/trout-keypad-v3.kcm.bin /system/usr/keychars
i think it fixes all including + etc..

ok did it, typing reboot....
g1 htc booting
waiting.....
OMG thanks a million....... close this thread or just move it to (make one with USEFULL THINGS).... will help other people in europe.
Thanks again.

maxisma said:
Your device should reboot now and TADA you have fully working QWERTZ!
Click to expand...
Click to collapse
Hi!
This only works reliably with ROMs with the Google virtual keyboard. With the HTC one (which function-wise is better), the hardkeyboard eventually switches back and forth from qwertz to qwerty and back.
Is there a solution for that issue?
Greets

It's because of the Hardwarekeyboardcorrection.
You can try to deactivate it in Settings/Locale Settings/Touch Input/...

maxisma said:
It's because of the Hardwarekeyboardcorrection.
You can try to deactivate it in Settings/Locale Settings/Touch Input/...
Click to expand...
Click to collapse
Yeah, that's my experience as well that it is due to the hardware keyboard correction.
However, even when I switch that off (correction and completion switched off), this strange behavior of switching back and forth continues :-(.
Is there a solution to this?
Or alternatively how can I install the Google IME on a HTC build as a workaround?
Just pushing GoogleIME.apk doesn't help unfortunately.

I wanna remove the clear lockscreen and put the original one??

I am on fresh 1.1 but i dont like the clear lockscreen. Is there a way i can change it??

yes try looking

just push this to system/app
you can use the fresh kitchen or adb
btw you can take apps out of any rom.zip on your computer, that's where i got this

Thank You thedudejdog it worked perferct

You can take the HtcLockscreen.apk out of the /system/app dir of any ROM you like to get that rom's lockscreen going.

thedudejdog said:
just push this to system/app
you can use the fresh kitchen or adb
btw you can take apps out of any rom.zip on your computer, that's where i got this
Click to expand...
Click to collapse
am a newly rooted hero owner. read/re-read/followed the steps to do it on this forum and am grateful to those who lent their knowledge/expertise.
want to have the original hero lockscreen and downloaded this HtcLockScreen.apk file.
i searched online to see if i could find instructions to push this but can't seem to figure it out.
i've done the following:
- copied HtcLockScreen.apk to the root of my sd card.
- opened a command prompt
- got to "C:\android-sdk-windows\tools>"
from here am i supposed to type:
- "adb shell"
- "su"
'cause i think to push this is the command, right:
- "push /sdcard/HtcLockScreen.apk /system/app/"?
help please!
thank you.

ok, put the file that you want to push in your tools directory of the sdk (c:\sdk\tools) these are the commands to push the file using adb
make sure you are in the command prompt and in your android sdk/tools directory.
you can copy/paste these one line at a time
i always do a
Code:
adb devices
first just to make sure adb sees your phone. if your phone shows up then continue
then mount system read/write
Code:
adb remount
then push the new lockscreen (this will overwrite the one that is there now)
Code:
adb push HtcLockScreen.apk /system/app
then close the cmd prompt window
Code:
exit
or you can use the fresh kitchen for a nice gui that does all the dirty work for you.
then reboot and there ya go, new lockscreen (or whatever)
i've never used the shell to push files, but i assume those commands that you listed should work for that, but you have to remount the filesystem first.

I thought I saw on here a little while back that showed you how to remove just the image from the lockscreen so all you have is the grey bar. Does anyone know where that is because I thought that that was kinda cool.

thedudejdog said:
ok, put the file that you want to push in your tools directory of the sdk (c:\sdk\tools) these are the commands to push the file using adb
make sure you are in the command prompt and in your android sdk/tools directory.
you can copy/paste these one line at a time
i always do a
Code:
adb devices
first just to make sure adb sees your phone. if your phone shows up then continue
then mount system read/write
Code:
adb remount
then push the new lockscreen (this will overwrite the one that is there now)
Code:
adb push HtcLockScreen.apk /system/app
then close the cmd prompt window
Code:
exit
or you can use the fresh kitchen for a nice gui that does all the dirty work for you.
then reboot and there ya go, new lockscreen (or whatever)
i've never used the shell to push files, but i assume those commands that you listed should work for that, but you have to remount the filesystem first.
Click to expand...
Click to collapse
thank you! it worked...

i want to get rid of my custom lockscreen

so i followed some debug tut to install some custom lockscreen on my sprint hero and i dont want it anymore.. the codes i followed were
REPLACE LOCKSCREEN - WORKS
cd C:\android-sdk-windows\tools
adb remount
adb shell
cd /system/app/
rm HtcLockScreen*
exit
reboot phone
how do i get RID of the lock screen ?????

Warrior 3000 said:
so i followed some debug tut to install some custom lockscreen on my sprint hero and i dont want it anymore.. the codes i followed were
REPLACE LOCKSCREEN - WORKS
cd C:\android-sdk-windows\tools
adb remount
adb shell
cd /system/app/
rm HtcLockScreen*
exit
reboot phone
how do i get RID of the lock screen ?????
Click to expand...
Click to collapse
put HtcLockScreen.apk on your c:\ drive
plug your phone into your pc and:
Code:
adb remount
adb push c:\HtcLockScreen.apk /system/app
adb reboot

where do i get HtcLockScreen.apk ?

do you still have the update.zip that you downloaded to flash your rom?
if so, open it and look in system/app. it is located there.

Warrior 3000 said:
where do i get HtcLockScreen.apk ?
Click to expand...
Click to collapse
If you've downloaded any roms there will be one inside it.
Actually NVM, here you go
View attachment HtcLockScreen.apk

Warrior 3000 said:
where do i get HtcLockScreen.apk ?
Click to expand...
Click to collapse
Almost any custom rom has it, including the one you flashed. I also attached it below if you need it.
*edit* Neb beat me.. =)

Dank,
did you post in my thread? It's on page 4 atm, I needs a bump!!
ps. the bottom line in my sig will take you to it
*edit - Thanks Dank!

How to root the Droid 2

All credit for the binary goes to Sebastian Krahmer at http://c-skills.blogspot.com/. Please see fit to donate via Paypal to [email protected]
If you want a simpler 'one-click' process, go to this thread: Easier 1-2-3 Droid 2 Root for Windows / Linux / Mac
***NOTE: Proceed at your own risk. I and the providers of this code are not responsible for anything you do to your phone!***
Setup:
- Install adb (here) and Motorola drivers for windows(32-bit or 64-bit)
- Download attached archive
- Extract to a directory, I used c:\Droid2Root
- Make sure you have USB degugging enabled
- Change connection to PC Mode
Process:
- Open command prompt
- cd c:/wherever-your-sdk-tools-folder-is
- adb devices (to verify the connection)
- cd c:/Droid2Root
- adb push Superuser.apk /sdcard/Superuser.apk
- adb push su /sdcard/su
- adb push busybox /sdcard/busybox
- adb push rageagainstthecage-arm5.bin /data/local/tmp/rageagainstthecage-arm5.bin
- adb shell
- cd data/local/tmp
- chmod 0755 rageagainstthecage-arm5.bin
- ./rageagainstthecage-arm5.bin
- let the process run until it 'kicks' you out (may take a minute or two) to c:/Droid2Root
- cd c:/wherever-your-sdk-tools-folder-is
- adb kill-server
- adb devices (to verify the connection)
- adb shell (you should now have a # prompt, if not return to ./rage step above)
- mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
- cp /sdcard/Superuser.apk /system/app/Superuser.apk
- cp /sdcard/su /system/bin/su
- cp /sdcard/busybox /system/bin/busybox
- chmod 4755 /system/bin/su
- chmod 4755 /system/bin/busybox
- mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
- exit
- exit
I'm sure there are certain steps that could be streamlined or eliminated, so please feel free to make a suggestion and I'll edit the post.
Additional thanks to @rainabba and AllDroid.org for their excellent Droid X rooting tutorial, which assisted me greatly in this process.

waiting for a recovery, glad to see its rooted

Android n00b here, I can remove the Verizon crapware with this right? And tether?

thelolotov said:
Android n00b here, I can remove the Verizon crapware with this right? And tether?
Click to expand...
Click to collapse
yes and yes

thelolotov said:
Android n00b here, I can remove the Verizon crapware with this right? And tether?
Click to expand...
Click to collapse
I wouldn't remove anything yet since we don't have a sbf file to recover from partial bricks. However, tethering and any other apps that require root can be used now.

I'm new to doing this all the adb way.
When you say extract to a directory what do you mean to extract. After it downloads the achive files its done.....
i understand the rest of the commands but im lost there

Hmm, alright, that's still worth it, will I lose my data/have to hard reset to root?

Right click the downloaded archive and "extract files". You need to do this so adb can push them to the phone.

thelolotov said:
Hmm, alright, that's still worth it, will I lose my data/have to hard reset to root?
Click to expand...
Click to collapse
Nope, it just gives you access. Nothing deleted.

I'm retarded i didnt realize it was attached to the post, i thought it was what adb downloaded when i first opened it cause it called them archives.

cannot access
I got as far as pushing super user su and busy box onto my phone but it says that system in read only.. how do i fix this?

Anybody actually try this?

Hello,
I am following your directions and when I get to the "adb push Superuser.apk" step I receive the following error:
"failed to copy 'Superuser.apk' to '/system/app/Superuser.apk': Read-only file system"
I get this same error for the other adb push steps that follow.
Edit: To verify, I get a # shell.
Edit 2: I tried pushing the Superuser.apk to /data/local/tmp then cp to /system/app/, this also popped up a read-only file system error.

I'm currently trying it.
I have a 64 bit driver on my computer that i used to use for my D1 but it doesn't recognize my D2 when doing adb devices and i cant install the 32 bit driver

GSletta said:
I got as far as pushing super user su and busy box onto my phone but it says that system in read only.. how do i fix this?
Click to expand...
Click to collapse
Did you verify you have the # prompt three steps before that?

Yeah i get the # but it wont let me push superuser su and busybox

GSletta said:
Yeah i get the # but it wont let me push superuser su and busybox
Click to expand...
Click to collapse
Weird.. I didn't need to mount the system manually, but let me if there's a step I left out.

and some more screens (feel free to use in first post):
http://i.imgur.com/nPllt.jpg
http://i.imgur.com/COTEA.jpg
http://i.imgur.com/open3.jpg

djh816 said:
and some more screens (feel free to use in first post):
http://i.imgur.com/nPllt.jpg
http://i.imgur.com/COTEA.jpg
http://i.imgur.com/open3.jpg
Click to expand...
Click to collapse
Did you add any steps to mount the system? I don't believe I did, but it seems others are finding it to be read-only.

jerseyh22accord said:
I'm currently trying it.
I have a 64 bit driver on my computer that i used to use for my D1 but it doesn't recognize my D2 when doing adb devices and i cant install the 32 bit driver
Click to expand...
Click to collapse
Don't know if it will help you, but if it's anything like the DInc, you could just use the SDK's drivers and add a few device identifier lines to the INF file before installing them.

[HOW TO] re-odex your ROM by yourself...

Big Thanks: original [email protected] [http://classic.cx/android/dexo-universal-odex-tool/]
ADVANTAGES & DISADVANTANGES OF RE-ODEX
Advantages:
-All needed things are in one apk, so modding/theming is (better) possible
-Needs less space on /system
Disavantages:
-Needs more space on /data
-Is not so stable than a odexed rom
-Slower on first boot(because a odexed rom has already execute ready .odex files, a deodexed rom needs to generate dalvik cache)
===============================================
First step, please make a nandroid if you are unsure of what you are doing.
Second step, install busybox if it is not already installed. Either from the app or
from the binary I included (ie, adb shell busybox –install /system/xbin/)
Third step, push the four files zip, zipalign, dexo and dexopt-wrapper to /system/bin/
Fourth step, give the three files executable permissions (ie, chmod 755 zip zipalign dexo dexopt-wrapper)
Fifth step, run it!
Once the script is done, your phone will reboot. Your device will appear to be “frozen” until it reboots. That is ok.
Then all you will have to do is run:
adb pull /system/framework # JUST INCASE...YOU CAN SKIP THIS STEP.
adb pull /system/app # JUST INCASE...YOU CAN SKIP THIS STEP.
You are now done! The tool will automatically remove the classes.dex from your files as well as zipalign them. So you are optimized and ready to go.
Sample Terminal/Command prompt session. Basically you can copy and paste, ignoring the text after the # of course:
# Commands on Host computer
cd Downloads/universal-odex # change to the location you unzipped the odex tool.
adb remount
adb push dexo /system/bin/
adb push dexopt-wrapper /system/bin/
adb push zip /system/xbin/
adb push zipalign /system/xbin
adb push busybox /system/xbin # you may or may not already have busybox installed, but this will ensure that you have the correct applets installed
# Commands in ADB SHELL
adb shell # you just entered your Device’s shell
chmod 755 /system/bin/dexo /system/bin/dexopt-wrapper /system/xbin/zip /system/xbin/zipalign /system/xbin/busybox
busybox –install /system/xbin # maybe fail in this step..but it seems okay,go to the next step anyway.
dexo # this will be the last command before your exit adb shell and your device reboots
# The “dexo” command executes SUPER fast. It should be done within 30s-1m, depending on ROM and device
# Commands on Host computer
cd Desktop
mkdir framework
mkdir app
adb pull /system/framework framework
adb pull /system/app app
# Rejoice.
If it doesn’t work for you, then you did something wrong. This is version 3.1 of the script and I’d like to think that I’ve fool-proofed it pretty well.
If you have any questions, comments, or suggestions, please post here.
Exclusive to theMikMik.
Tommy
enjoy the possibilities…
FILES_NEEDED:
View attachment re_odex_needed.tar.gz

Bro, you mean de-odex instead of re-odex??

Or even re-de-odex lol
Sent from my Nexus 7 using Tapatalk 2

kingCV said:
Bro, you mean de-odex instead of re-odex??
Click to expand...
Click to collapse
yesyes..