Database Info

[HACK] Change qwerty -> qwertz script for linux

I use on my phone Danger SPL. I spare with this 15 MB memory, so I have enough space in the rom for extra flash. But there is a problem: this firmware changes the qwertz layout to qwerty layout. It is annoying the symbols' not being on the appropriate place. With a bit hack the layout can be changed, but this have to be done after every upgrade. I wrote a script which automates the layout changing and restarts the phone with the new configurations.
To use the script you have to install Android SDK, and the folder of the sdk tools have to be in the path: export PATH=${PATH}:~/android-sdk-linux_86/tools
You have to stick the usb cable into your phone and execute the script, then the phone restarts with the appropriate configurations.
Be careful, using the script is your risk and responsibility.

I have a QWERTZ G1 too.
I would like to ask can we able to correct the symbols instead of the 'z' and 'y'?

Here is the script - Working under linux
#!/bin/bash
#Put your sdk-dir/tools directory to your path first!
echo "Downloading the base qwertz layout from the phone..."
adb pull /system/usr/keylayout/trout-keypad-qwertz.kl ./
adb pull /system/usr/keychars/trout-keypad-qwertz.kcm.bin ./
echo "Remounting phone's filesystem rw..."
adb remount
echo "Overwrite qwerty layout..."
adb push ./trout-keypad-qwertz.kl /system/usr/keylayout/trout-keypad-v3.kl
adb push ./trout-keypad-qwertz.kcm.bin /system/usr/keychars/trout-keypad-v3.kcm.bin
echo "Reboot phone and delete temporary files..."
adb reboot
rm ./trout-keypad-qwertz.kl
rm ./trout-keypad-qwertz.kcm.bin
echo "Thank you for use!"
exit 0

Can you make a version that is QWERTY layout with correct QWERTZ symbol?

Booker-T said:
Can you make a version that is QWERTY layout with correct QWERTZ symbol?
Click to expand...
Click to collapse
Just don't do the "keylayout" step, only replace the "keychars".

To roms without correct qwertz files
Hi! This is a different script, contains the qwertz files.

Hello!
I am using this adb commands:
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
Can i just flash your QWERTZ.zip from G1 Recovery and if not is there a possible way to do this "the easy way" ?

xektop said:
Hello!
I am using this adb commands:
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
Can i just flash your QWERTZ.zip from G1 Recovery and if not is there a possible way to do this "the easy way" ?
Click to expand...
Click to collapse
No. This is not a flashable file, this is a single archive, contains a script and the "qwertz files". From windows you can use the adb command to overwrite qwerty files:
Code:
adb remount
adb push trout-keypad-qwertz.kl /system/usr/keylayout/trout-keypad-v3.kl
adb push trout-keypad-qwertz.kcm.bin /system/usr/keychars/trout-keypad-v3.kcm.bin
Bye!

apoth said:
No. This is not a flashable file, this is a single archive, contains a script and the "qwertz files". From windows you can use the adb command to overwrite qwerty files:
Code:
adb remount
adb push trout-keypad-qwertz.kl /system/usr/keylayout/trout-keypad-v3.kl
adb push trout-keypad-qwertz.kcm.bin /system/usr/keychars/trout-keypad-v3.kcm.bin
Bye!
Click to expand...
Click to collapse
THX! It was usefull
Valamilyen magyar ékezetes trükköt nem tudsz véletlenül?

feenty said:
THX! It was usefull
Valamilyen magyar ékezetes trükköt nem tudsz véletlenül?
Click to expand...
Click to collapse
Sáányii!
Nem sajnos, engem is érdekel a dolog, de eddig még nem igazán volt időm piszkálni a dolgot. Majd ha van kedved kukkants be az apoth.hu-ra, mostanában kezdek csinálni magyar-specifikus appmodokat.

apoth said:
Sáányii!
Nem sajnos, engem is érdekel a dolog, de eddig még nem igazán volt időm piszkálni a dolgot. Majd ha van kedved kukkants be az apoth.hu-ra, mostanában kezdek csinálni magyar-specifikus appmodokat.
Click to expand...
Click to collapse
Meglesz
Ui.: Jó tudni, hogy van kihez szólni itt magyarul is, néha már kezdem unni, hogy angolul bénázok itt

Készül egy magyar nyelvű ROM G1-re.
Az ékezetes bulit megoldottam, letölthetsz full magyar LatinIME-t magyar t9 szótárral. http://mamt.tk
I now working in a hungarian ROM to G1. Hungarian based LatinIME downloadable from http://mamt.tk with hungarian t9 dict.

I already have this feature in our PC Suite. It's even faster

hey dude can it fix this??
http://img195.imageshack.us/img195/6494/deviceh.jpg

jamb said:
hey dude can it fix this??
http://img195.imageshack.us/img195/6494/deviceh.jpg
Click to expand...
Click to collapse
What is this? Please, more info

i just copied these files, but the slider keys (G1) still are qwerty
am i blind? is there anything else in this script but just copying these files? (i copied them into the right directories using root manager)

jamb said:
hey dude can it fix this??
http://img195.imageshack.us/img195/6494/deviceh.jpg
Click to expand...
Click to collapse
look like your missing the keyboard completely try flashing a replacement (like swype or better keyboard)

remington.style said:
i just copied these files, but the slider keys (G1) still are qwerty
am i blind? is there anything else in this script but just copying these files? (i copied them into the right directories using root manager)
Click to expand...
Click to collapse
Reboot phone after copy the files
Best regards!

apoth said:
Reboot phone after copy the files
Best regards!
Click to expand...
Click to collapse
well - that i got out of the script, too
just did the whole procedure again - no luck
z is y, y is z, alt+o is not ö but (
(and qwerty is sooo annoying)

remington.style said:
well - that i got out of the script, too
just did the whole procedure again - no luck
z is y, y is z, alt+o is not ö but (
(and qwerty is sooo annoying)
Click to expand...
Click to collapse
Maybe try the second script: http://forum.xda-developers.com/attachment.php?attachmentid=299479&d=1269625727
Ths contains the files. If you are no lucky, try to overwrite the files by hand, or paste the script's output if you have some error.
Have fun!

Touchscreen doesnt respond after root.

Ok guys..I'm REALLY hoping we can fix this. Its really strange. I'm posting this here as well as over at another site because i used XDA much more often and have much more faith in you guys. I've rooted tons of devices in my time and this is a first. I used Superoneclick to root my Kyros MID8127 tablet. It worked just fine. Got super user and everything. But now whenever the screen times out, or i just leave it alone for a while, while its off, when i go to wake it up the touchscreen is completely unresponsive. It turns off after a few seconds but the capacitive buttons stay lit. This has my mind boggled. I tried unrooting with soc as well, no avail. The only other thing i can do once this happens is to get a pin out and press the tiny reset button hole. Does anyone have any idea what could cause something like this, and how i should go about fixing it? Thanks in advance.
EDIT : I Just confirmed that ROOT had nothing to do with this. I had a feeling it didn't. The person who gave it to me said its always done this.

FIX Touchscreen and button not responding after root ICS 4.03
Touchscreen not woiking after root. (button, gps, 3g, wlan etc...)
You lost my configuration of the devices,
1. Droid Open the Explorer (download from google market)
2. Locate the files. ko (they have the information how devices in your tablet work)
3. copy the files. ko to / system / lib / modules /
4. Find and edit the file / system / etc / init.local.rc should see something like this:
on boot
au.ui.enable_bluetooth true setprop
au.voice_capable true setprop
au.sms_capable true setprop
______________________________________________
5. add the lines (Attention here show the name of my files.ko but you must write the name of your files.ko)
6. You should see something like this after adding the lines:
on boot
au.ui.enable_bluetooth true setprop
au.voice_capable true setprop
au.sms_capable true setprop
insmod /system /lib/modules/battery.ko
insmod /system/lib/modules/button_ut7gm.ko
insmod /system/lib/modules/ft5x0x_ts.ko
************
7. Reboot the tablet ou phone and voila!
Nexus118
Em Português (In portuguese)
Deves ter perdido a configuração dos devices (não é grave desde que tenhas acesso ao tablet por adb shell)
1. Abrir o Droid Explorer (download do google market)
2. Localize os ficheiros .ko ( estes têm informação de como funciona os despositivos do seu tablet)
3. copie os ficheiros .ko para /system/lib/modules/
4. Procure e edite o ficheiro /system/etc/init.local.rc
deve ver qualquer coisa como isto:
on boot
setprop au.ui.enable_bluetooth true
setprop au.voice_capable true
setprop au.sms_capable true
______________________________________________
5. adicione as linhas
( atenção aqui mostro o nome dos meus ficheiros.ko mas você deve escrever o nome dos seus ficheiros .ko)
6. Deve ver algo como isto depois de acrescentar as linhas
on boot
setprop au.ui.enable_bluetooth true
setprop au.voice_capable true
setprop au.sms_capable true
insmod /system/lib/modules/battery.ko
insmod /system/lib/modules/button_ut7gm.ko
insmod /system/lib/modules/ft5x0x_ts.ko
7. Faça reboot e pronto!
Nexus118

Elephone Vowney lite ROM, recovery, root

Hello,
Has anyone found the vowney lite stock ROM yet ? I'd like to get the stock recovery image to eventually port a CWM recovery.
I've tried many differents things to get the image from the phone but without the root access I can't do it

check it out
http://forum.xda-developers.com/elephone-vowney/help/stock-rom-elephone-vowneyandroid-5-t3314417
If possible hit thanks sir

That's not the Lite ROM...
I just got root access, so I don't need it anymore, I can get everything by myself

luxumbra said:
That's not the Lite ROM...
I just got root access, so I don't need it anymore, I can get everything by myself
Click to expand...
Click to collapse
Could you link/post on how you got root for the lite? Noob to this all!

Right here in xda
http://forum.xda-developers.com/elephone-vowney/how-to/howto-elephone-vowney-lite-root-t3313202
This must be the only root option I had not tested.

luxumbra said:
Right here in xda
http://forum.xda-developers.com/elephone-vowney/how-to/howto-elephone-vowney-lite-root-t3313202
This must be the only root option I had not tested.
Click to expand...
Click to collapse
xenion22 posted my link as new topic.....here's the original
http://forum.xda-developers.com/showpost.php?p=65277458&postcount=9
the root works for vowney and vowney lite, but the script fail because of new kinguser 4.8

doa4ever said:
xenion22 posted my link as new topic.....here's the original
http://forum.xda-developers.com/showpost.php?p=65277458&postcount=9
the root works for vowney and vowney lite, but the script fail because of new kinguser 4.8
Click to expand...
Click to collapse
Yeah I saw your post before, thanks btw, but he put the link to change to supersu afterwards, so I quoted him
What do you mean "script fail" ? I had no problem...

luxumbra said:
Yeah I saw your post before, thanks btw, but he put the link to change to supersu afterwards, so I quoted him
What do you mean "script fail" ? I had no problem...
Click to expand...
Click to collapse
the script didnt work for me. even i changed the supersu version.
but its no reason to worry. kingroot 4.8 works fine and it looks like that kingroot uses chaindd's binarys.
no problems with busybox, etc.

doa4ever said:
the script didnt work for me. even i changed the supersu version.
but its no reason to worry. kingroot 4.8 works fine and it looks like that kingroot uses chaindd's binarys.
no problems with busybox, etc.
Click to expand...
Click to collapse
Would it be worth trying the previous version of kingroot? or is it better to use new version for supersu to not work? Sorry for the likely nooby questions, I'm not sure of the implications of different outcomes and don't want to mess up my first root

Quelqu'un pourrait il copier sa ROM est la partager
Merci

lidlband said:
Would it be worth trying the previous version of kingroot? or is it better to use new version for supersu to not work? Sorry for the likely nooby questions, I'm not sure of the implications of different outcomes and don't want to mess up my first root
Click to expand...
Click to collapse
I used version of kingroot in the link (maybe the last), and I managed to change to supersu without any problem...

Luxumbra pourrais tu partager ta ROM?

I built a flashable ROM with Android Kitchen, the device is probably not officialy supported, because it is recent and it's a MT6795, but I got no error during the manipulations.
I used dumps images from my own device, vowney lite.
Download: http://uptobox.com/uwwblc6x4iu3
Do not flash it unless your device is already broken, I have not tested it myself.
I guarantee absolutly nothing, and hold no responsability for anything you do with it.
The purpose of it is to get files from it to work on, or if you are experienced, check for problems in it please, I'm not a pro (yet).
My few modifications:
-Added root permission with superSU
-Added BusyBox
-Added Cerberus (the anti-theft app) as a system app
-maybe other minor changes as a did not make a factoy reset before getting the image from it
Go here for stock: http://forum.xda-developers.com/ele...torial-flash-stock-image-vowney-lite-t3320483
PS: Popeck parles Anglais stp, on est sur un forum international, et une ROM ça se sort pas comme ça d'un téléphone, il faut déjà être rooté et après c'est pas simple de tout reconstruire.

hello I can not downloading your file

luxumbra said:
I built a flashable ROM with Android Kitchen, the device is probably not officialy supported, because it is recent and it's a MT6795, but I got no error during the manipulations.
I used dumps images from my own device, vowney lite.
Download: http://uptobox.com/uwwblc6x4iu3
Do not flash it unless your device is already broken, I have not tested it myself.
I guarantee absolutly nothing, and hold no responsability for anything you do with it.
The purpose of it is to get files from it to work on, or if you are experienced, check for problems in it please, I'm not a pro (yet).
My few modifications:
-Added root permission with superSU
-Added BusyBox
-Added Cerberus (the anti-theft app) as a system app
-maybe other minor changes as a did not make a factoy reset before getting the image from it
PS: Popeck parles Anglais stp, on est sur un forum international, et une ROM ça se sort pas comme ça d'un téléphone, il faut déjà être rooté et après c'est pas simple de tout reconstruire.
Click to expand...
Click to collapse
Je l'ai flasher avec une ROM non compatible, celle vowney tout cours....

luxumbra said:
I used version of kingroot in the link (maybe the last), and I managed to change to supersu without any problem...
Click to expand...
Click to collapse
Using the method in the link and installing supersu using the terminal I just got errors (despite getting the correct directory) but it unistalled kingroot in the process.
I then just tried the Supersu free in the play store and it cant update the binary (just says "installation failed ! Please reboot and try again.")
So my question is, is there a way around this or should I just keep Kingroot? I read that Kingroot may be taking data etc but i'm very new to all this so sorry for the questioning!

lidlband said:
Using the method in the link and installing supersu using the terminal I just got errors (despite getting the correct directory) but it unistalled kingroot in the process.
I then just tried the Supersu free in the play store and it cant update the binary (just says "installation failed ! Please reboot and try again.")
So my question is, is there a way around this or should I just keep Kingroot? I read that Kingroot may be taking data etc but i'm very new to all this so sorry for the questioning!
Click to expand...
Click to collapse
I used ADB shell instead of a terminal emulator, maybe that made a difference, try these commands with ADB:
-must be rooted with kingroot
-must have the supersu app installed
-mrw must already be in the /sdcard
adb devices (check if you device is connected, it should say "device")
adb shell
su (grant any permission on screen)
ls -al /sdcard (verify that you have the mrw folder)
ls -al /sdcard/mrw (verify that you have the 4 files)
sh /sdcard/mrw/root.sh
After that kingroot should stop working, then open supersu and update binary

luxumbra said:
I used ADB shell instead of a terminal emulator, maybe that made a difference, try these commands with ADB:
-must be rooted with kingroot
-must have the supersu app installed
-mrw must already be in the /sdcard
adb devices (check if you device is connected, it should say "device")
adb shell
su (grant any permission on screen)
ls -al /sdcard (verify that you have the mrw folder)
ls -al /sdcard/mrw (verify that you have the 4 files)
sh /sdcard/mrw/root.sh
After that kingroot should stop working, then open supersu and update binary
Click to expand...
Click to collapse
I'm guessing you're talking about using the cmd shell on my computer in the android sdk (and platform-tools) directory? I've tried that and it's not showing a device. I've installed the google drivers within the SDK manager but it still didnt show anything and from here I don't know where to go?
Cheers for the help, i'm not sure if i'm helping the forum by clogging it up with my questions though

lidlband said:
I'm guessing you're talking about using the cmd shell on my computer in the android sdk (and platform-tools) directory? I've tried that and it's not showing a device. I've installed the google drivers within the SDK manager but it still didnt show anything and from here I don't know where to go?
Cheers for the help, i'm not sure if i'm helping the forum by clogging it up with my questions though
Click to expand...
Click to collapse
Try installing ADB like this:
http://forum.xda-developers.com/showthread.php?p=48915118#post48915118
Don't forget to turn on USB debugging in the developper options.

luxumbra said:
Try installing ADB like this:
http://forum.xda-developers.com/showthread.php?p=48915118#post48915118
Don't forget to turn on USB debugging in the developper options.
Click to expand...
Click to collapse
Sorry I was nearly about to post an update!
I got the ADB driver working and ADB shell working as you said. The commands to sdcard were not working, and I think the system (or likely myself) is getting confused with the external micro SD I have. It nearly got there, but now superSU wont open because it says it cant install the binary (without giving me any other option) then closing, and now when I try to install KingRoot to try the process again it says "Unfortunately, com.kingroot.kinguser has stopped"
I'm going to any kingroot associated files and reboot etc and try again without my microsd in and hopefully it will finally go smoother!
Really appreciate the help!
---------- Post added at 06:17 PM ---------- Previous post was at 05:36 PM ----------
luxumbra said:
I used ADB shell instead of a terminal emulator, maybe that made a difference, try these commands with ADB:
-must be rooted with kingroot
-must have the supersu app installed
-mrw must already be in the /sdcard
adb devices (check if you device is connected, it should say "device")
adb shell
su (grant any permission on screen)
ls -al /sdcard (verify that you have the mrw folder)
ls -al /sdcard/mrw (verify that you have the 4 files)
sh /sdcard/mrw/root.sh
After that kingroot should stop working, then open supersu and update binary
Click to expand...
Click to collapse
Okay I finally got there! Can't thank you enough for your help!
Unmounting the SD card was the final straw to help it all come together! :laugh:
Hopefully someone else might be helped by my failings, otherwise, sorry anyone/everyone for taking up all this space!

is there a way to enable adaptable storage on poco x3 ?

I noticed that poco x3 does not allow apps to be installed or moved to SD card. Is there a way to do that ?

You can try "Force allow all apps on external..." option in developer's settings.
Or just change the default installation location with ADB command:
adb shell pm set-install-location 0 (default as app manifest defined)
adb shell pm set-install-location 1 (for internal memory)
adb shell pm set-install-location 2 (for external storage)

Don't some apps require to be installed in internal memory to function?

AngryYoungMan said:
Don't some apps require to be installed in internal memory to function?
Click to expand...
Click to collapse
Some apps which use widgets and boot service yes, others can be moved safely to microSD as far as I remember.

Not for me. I could move my Amazon apps to the SD card on my Samsung A50. Can't do it on my Poco X3

MocnePifko said:
Você pode tentar a opção "Forçar permitir todos os aplicativos externos..." nas configurações do desenvolvedor.
Ou apenas altere o local de instalação padrão com o comando ADB:
adb shell pm set-install-location 0 (padrão como manifesto do aplicativo definido)
adb shell pm set-install-location 1 (para memória interna)
adb shell pm set-install-location 2 (para armazenamento externo)
Click to expand...
Click to collapse

I tried the option "Force allow installation of apps on external storage" but even with the function activated, it didn't work in practice. Do you know why it doesn't work?

Unable to run adb root on rooted OnePlus 7 Pro with Android 11

Hi all,
I've spent the better half of my Sunday trying to finally get `adb root` to work on my device (rooted with magisk).
I've tried a variety of things, such as using the `resetprop` tool to modify the ro.debuggable and ro.secure properties (supposedly successful upon checking the output of `resetprop ro.debuggable`, however upon exiting the shell and attempting to run adb root, it doesn't work. I assume it's because I need to reboot, but the `-p` flag for percistence doesn't appear to work for me.
I've attempted modifying the build.prop file directly, with no avail. I just want to add a CA cert to my /system/etc/security/cacerts to intercept an app's requests through burpsuite (a HTTP proxy).
If anyone has any recommendations on what to try, I'm all ears, and would be massively appreciative of any help.

If it's rooted just patch adbd to not care about that stuff.

Renate said:
If it's rooted just patch adbd to not care about that stuff.
Click to expand...
Click to collapse
Any idea where I can find a patched binary or more information on how to do this? I would've thought I can't patch as it requires writing to read-only parts of the system (I've been unsuccessful in trying to remount it with write permissions too... not sure why when I am in a root shell.

Sorry, I wasn't trying to give you totally worthless advice.
Production builds of adbd don't respond to "adbd root".
Since it's all open source you can build from source to have a rooted adbd.
OTOH, I never build from source, I find it easier to mod.
To put that on your device you'll need Magisk or somehow rooted.
Modding /system requires Magisk or that you abandon the concept of incremental updates (without restoring to last official version).

Renate said:
Sorry, I wasn't trying to give you totally worthless advice.
Production builds of adbd don't respond to "adbd root".
Since it's all open source you can build from source to have a rooted adbd.
OTOH, I never build from source, I find it easier to mod.
To put that on your device you'll need Magisk or somehow rooted.
Modding /system requires Magisk or that you abandon the concept of incremental updates (without restoring to last official version).
Click to expand...
Click to collapse
Interesting, thank you for the detailed response, I really appreciate it.
Gonna dig into this for the next couple days as I'd like to have a good phone for mobile security testing.

Not saying that this is the best route or the sane route. There are devices that I care about and devices that I can't be bothered about.
For the device that I care about:
I modify the dtb in the boot image so that /vendor is loaded without verifying.
I modify the fstab in /vendor so that /system is loaded without verifying.
I modify both /vendor and /system so that there is no error correction (wipe the last 4096 of each partition).
I patch (SE Linux) sepolicy for what I need in .cil
I patch adbd to be rooted (without any adb root or su command)
Yes, one could use Magisk, but I don't know where that is going. It's a clever program, but mod some stuff and look at all the stuff that a mount command shows.
For me, it's above the threshold. The downside of my approach is that you can't do incremental updates (without reverting to stock).

hola amigo disculpa lo que veo tu dispositivo esta rooteado y quisiera saber si me puedes ayudar a pasarme algunos archivos del sistema, ya que tengo un problema con las camaras que no puedo solucionar...