Database Info

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

How to get over Insufficient Space in android

hey guys, it took me a long while to figure out what "Insufficient space cannot install" meant.
FIRST: IT IS ON ONE OF THE DIFFERENT PARTITIONS ON YOUR ANDROID. THIS DOESNT MEAN THAT YOU STILL CANNOT INSTALL IT.
SECOND: These partitions may be:
System
Storage
Internal
External
etc...
THIRD: of these, one is filled up and unfortunately your phone is trying to install the app on this partition itself.
like this one time, i had 400+Mb on my "System" partition, but never was able to install anything on it. finally i uninstalled many apps just to install one. I thought its a market error, but the error lies in MARKET NOT TELLING US WHICH PARTITION IS FILLED.​
FOURTH: upto today, i had no clue about the options provided by android, there is an option to choose where to install apps. my micro SDCARd of 8gb was filled, and i was unable to install 300kb apps, but could install 4mb,10mb+ apps. i did not know this was the reason(micro sdcard filled). well i came across "8 Simple Steps to Fix 'Insufficient Storage Available' on Android" and not even 8 steps will be required if you already have ADB shell. search for this on google, coz im not allowed to post links! yet
If you used ADB shell before with your phone, just go there and type:
Code:
adb shell pm get-install-location
mine returned 2
meaning all this while it was trying to install in my sdcard. I don't know how this was set.
i changed it to 1 using
Code:
adb shell pm set-install-location 1
and now i can install peacefully on my system partition with 400 mb left!
hope this helps all those poor souls out there who had been stuck in this nightmare !!

nice tip
'get-install-location' isn't available on 4.3.3 apparently, but you can still set the install location...
Code:
usage: pm [list|path|install|uninstall]
pm list packages [-f] [-d] [-e] [-u] [FILTER]
pm list permission-groups
pm list permissions [-g] [-f] [-d] [-u] [GROUP]
pm list instrumentation [-f] [TARGET-PACKAGE]
pm list features
pm list libraries
pm path PACKAGE
pm install [-l] [-r] [-t] [-i INSTALLER_PACKAGE_NAME] [-s] [-f] PATH
pm uninstall [-k] PACKAGE
pm clear PACKAGE
pm enable PACKAGE_OR_COMPONENT
pm disable PACKAGE_OR_COMPONENT
[B]pm setInstallLocation [0/auto] [1/internal] [2/external][/B]
EDIT...
ah-ha - 'getInstallLocation' is available ... so...
Code:
pm getInstallLocation
in my case it returns 0 (auto)

library linking error
.man said:
nice tip
'get-install-location' isn't available on 4.3.3 apparently, but you can still set the install location...
Code:
usage: pm [list|path|install|uninstall]
pm list packages [-f] [-d] [-e] [-u] [FILTER]
pm list permission-groups
pm list permissions [-g] [-f] [-d] [-u] [GROUP]
pm list instrumentation [-f] [TARGET-PACKAGE]
pm list features
pm list libraries
pm path PACKAGE
pm install [-l] [-r] [-t] [-i INSTALLER_PACKAGE_NAME] [-s] [-f] PATH
pm uninstall [-k] PACKAGE
pm clear PACKAGE
pm enable PACKAGE_OR_COMPONENT
pm disable PACKAGE_OR_COMPONENT
[B]pm setInstallLocation [0/auto] [1/internal] [2/external][/B]
EDIT...
ah-ha - 'getInstallLocation' is available ... so...
Code:
pm getInstallLocation
in my case it returns 0 (auto)
Click to expand...
Click to collapse
I tried this but I am getting a linking error. "Could not load needed library
libandroid_runtime.so for app_process." I fear something is seriously hosed.
I can't update / install anything.
Bummer

Good
Good tutorials, i will reconsider, tks

First off, I'm really sorry for resurrecting this thread after so long, but since this has something to do with what I'm dealing with, I think it wouldn't hurt posting here, and besides the post reply button was still available, so...
Anyway, LG user here. I'm currently using a LG G2 derivative model aka LG G2 Lite (for Brazilian users only), which is running stock Android v 4.4.2.
I've installed JDK, Android Studio, SDK tools, all my drivers, enabled USB debug, went through the commands successfully , and now the phone outputs "2" to the 'adb shell pm get-install-location', which is external SD. On top of that, according to AppMgr III, I got:
1.1GB used size out of 1.5GB (25% remaining) - internal
1.1GB used size out of 1.5GB (25% remaining) - /storage/emulated/0
1.7GB used size out of 29.5GB (94% remaining) - /storage/external_SD
As you can see, there's plenty of space, so how come the Play Store won't let me install anything at all? I mean, I can't even download the Twitter app which is less than 50MB (as far as I remember).
I've been searching for an answer and asking away for almost a month. Running out of ideas.
I already tried removing the Play Store Services' updates, downgrading it to the stock version, nada. I can't help but wonder what I did was half the solution, is there anything else I need to do in order to make Play Store install applications on the external SD card? What's left to do?
Could someone please shed some light on this issue? I'm sure I'm not the only one.
Thanks.

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!

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...

|Help me!|Generic gamepads in android

I'm looking for a way to make a generic gamepad driver for android. But I already made one in a failed attempt. The d-pad was not working. I went in the path system/usr/keylayout. I'm using Android 7.1 I made the driver using an app called gamepad tester it generates a file and then I just put the file in the folder
The remap buttons not work

usb bt joystick center not work in my device

You have to name the file correctly. I don't see any Vendor_0810_Product_0001.kl in your screenshot.
Check if/what keylayout is being loaded (plug/unplug the device):
Code:
C:\>adb shell
$ adb logcat|grep keylayout
Also, you don't have to put the file in /system/usr/keylayout (where you need R/W or Magisk).
You could put the file in /data/system/devices/keylayout (although you have to be root to install it).

Renate said:
Renate said:
Você tem que nomear o arquivo corretamente. Eu não vejo nenhum Vendor_0801_Product_0001.kl em sua captura de tela.
Verifique se/qual keylayout está sendo carregado (conecte/desconecte o dispositivo):
[código] C:\>adb shell
$ adb logcat|grep keylayout[/código]
Além disso, você não precisa colocar o arquivo em /system/usr/keylayout (onde você precisa de R/W ou Magisk).
Você pode colocar o arquivo em /data/system/devices/keylayout (embora você tenha que ser root para instalá-lo).
Click to expand...
Click to collapse
Click to expand...
Click to collapse
actually I had already done it the right name in the file but thank you I will test this : )

Renate said:
C:\>adb shell $ adb logcat|grep keylayout
Click to expand...
Click to collapse
but im using a tv box

OxyZin said:
but im using a tv box
Click to expand...
Click to collapse
Yeah, but it still has ADB somewhere, doesn't it.?
You need to verify what keylayout got loaded.
You can also try my UsbMode.akp (in the sig) to see what the buttons are doing.
You're going to have to get more detailed on what's not working.
When you say "driver" do you mean "Vendor_0810_Product_0001.kl"
That's really not a driver.
Sorry, I don't know what's going on here.