Database Info

Root flytouch superpad 6 (vi) v10 cortex a8 vimicro

HI. i am opening these post for people like me that the have the same chineese pad and they cant root it.
I have try to root it with any method but with no succed.
(adb command, z4root, universal root, gingerbreak,oneclick)
at oneclick and adb tablet no recognized as usb. the first thing that i do, is to change the usb drivers with the usb googles drivers.Than oneclick it found it as rooted!but when i press to root it again i had many errors.
i upload a image with device info that i grap form adb
i am start to thinking that they put some protect that we cant have access at the rom. i use root explore r/o its highlight.its give mt the permissionto delete apk from system./app but later i can find them inside. at the info of taach u can see that device is rooted!
anyway. i found a firmware update but i havent test it yet

same issue here
Hi. I too tried to root this chinese pad (Flytouch 6) but unable to. Also I was trying to update the ROM with HoneyComb but unable to. ANy help is appreciated.
Thanks. Mounesh.

mounesh25 said:
Hi. I too tried to root this chinese pad (Flytouch 6) but unable to. Also I was trying to update the ROM with HoneyComb but unable to. ANy help is appreciated.
Thanks. Mounesh.
Click to expand...
Click to collapse
Hi my mate. i have found 2 updates i have test one only and i succed to update it.
these is from another forum:
<<ok new download link for firmware update http://www.multiupload.com/5DI5AAL5BQ
i have found a issue with it when you go into android market because this as the latest android market apk it will let you download games etc free and paid but on some it comes up not enough memory,but i noticed by going into settings and clearing google framework and shutting down tablet a few times it allowed me to download a lot more i have put a earlier android market apk on which works perfect,but when i shut down tablet it goes back to newest android market apk?so if you know of a way to delete the android market apk on the tablet let me know?
////////////////////////////////////////////////////
please note before you start you must have your tablet charging with tablet charger otherwise it will not let you put firmware on tablet
//////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
the way of flash the firmware of v10
sd-card into tablet while turned off
1,press the "menu"+""power"ON button at the same time
2.release the “power” after the boot up.and keep holding menu
3.pls release the "menu" after the there is a flash firmware picture with a android holding a brown bag/box
4. then you will have to do some scrolling with these buttons
5 function of the button front of the device is page up
6 function of the button of "meun" is page down
7 function of the button of "Home" is confirmation (to install firmware)
you will have to scroll to install from sd-card then press home button
you will have to scroll to your firmware them press home button to install
if you ever need to reflash or restart your tablet for any reason you can do this by holding the the on button and menu?which will allow you to reload firmware etc >>
motherofallbattles thanks a lot

chriskleov said:
the first thing that i do, is to change the usb drivers with the usb googles drivers.Than oneclick it found it as rooted!but when i press to root it again i had many errors.
i upload a image with device info that i grap form adb
i am start to thinking that they put some protect that we cant have access at the rom. i use root explore r/o its highlight.its give mt the permissionto delete apk from system./app but later i can find them inside. at the info of taach u can see that device is rooted!
anyway. i found a firmware update but i havent test it yet
Click to expand...
Click to collapse
I am confused as to what USB drivers you used to get the PC to recognize the FlyTouch...can you please provide a download link to these USB drivers you used? I am trying to get my device rooted as well. Thanks.

Thanks for the update
Hi Cheklov,
I did manager to update the firmware using your given link and instructions.
Thanks mate.
BTW...is there a way I can update to honeycomb version?
I've downloaded a few HC versions meant for other tablets like WMT, HTC etc..but no way could I update. Any instructions and link is appreciated.
Thx, Mounesh.

flytouch5.user said:
I am confused as to what USB drivers you used to get the PC to recognize the FlyTouch...can you please provide a download link to these USB drivers you used? I am trying to get my device rooted as well. Thanks.
Click to expand...
Click to collapse
to change the drivers of wopad go to devices and printers.there you will find it as usb storage.there press right click.then hit at the 2nd tab and then prpoerties.chancge manual the drivers.
http://www.megaupload.com/?d=JA6F5VS6

mounesh25 said:
Hi Cheklov,
I did manager to update the firmware using your given link and instructions.
Thanks mate.
BTW...is there a way I can update to honeycomb version?
I've downloaded a few HC versions meant for other tablets like WMT, HTC etc..but no way could I update. Any instructions and link is appreciated.
Thx, Mounesh.
Click to expand...
Click to collapse
i have no idea for custom rom.i think its to early..the chinese pad its to new...no one havent succed to root it.

I ROOT IT!!!!!
FINALY I SUCCED TO ROOT IT!!!
i succed by adb cmds!!
ADB root
ADB shell mount -o remount,rw /system
ADB push su-3.0.3.2-efghi-signed /system/xbin/su
ADB push su-3.0.3.2-efghi-signed /bin/su
ADB shell chown 0.0 /bin/su
ADB shell chmod 04755 /bin/su
ADB shell chown 0.0 /system/xbin/su
ADB shell chmod 04755 /system/xbin/su
ADB shell mount -o remount,ro /system
ADB install -r Superuser-3.0.7-efghi-signed.apk
reboot UNISTALL superuser.apk and INSTALL IT again!

@chriskleov can you tel me more about this updates?
is there update to android 3.0 or higher?

USB OTG control problem
I've updated the firmware successfully.
But now I have a new issue with the USB OTG. I cannot use the USB OTG control to change from host mode to device mode. Everytime I try to go and click on USB OTG control, it throws error "the application USB OTG (com....) has stopped unexpectedly". Ive tried to reset to factory defaults...but now seems the problem is still stuck there. I cannot go into ADB to do the rooting without enabling the 'device' mode connection for the USB. pl help.
Ive googled but none of the solutions seem to be working.

mounesh25 said:
I've updated the firmware successfully.
But now I have a new issue with the USB OTG. I cannot use the USB OTG control to change from host mode to device mode. Everytime I try to go and click on USB OTG control, it throws error "the application USB OTG (com....) has stopped unexpectedly". Ive tried to reset to factory defaults...but now seems the problem is still stuck there. I cannot go into ADB to do the rooting without enabling the 'device' mode connection for the USB. pl help.
Ive googled but none of the solutions seem to be working.
Click to expand...
Click to collapse
wipe data then
try to reflash the upadate
and then aagain wipe

done that
Ive already done that. But result is same.
anyone can help?

mounesh25 said:
Ive already done that. But result is same.
anyone can help?
Click to expand...
Click to collapse
http://www.apad.tv/apadforum/list.php?category/46-Flytouch-5-Wopad-Firmware

Who can tell me why the Navionics Marine 2.1 crashes (force close) after hitting "i agree" in the beginning? Your help would be highly appreciated!

USB problem
hi all
I.ve updated with the file from the above post and noe I have the same problem with the usb
force close - no way to connect to PC
please help

You can try this method to root, it is for another similar vimicro device:
Q: How to root the Haipad M8?
A: You need the GingerBreak and some manual work.
You need to have an installed Android SDK with adb.exe or take this archive with adb.exe only. And you need to have a modified USB driver.
Connect the Haipad M8 to the PC (USB OTG). You will have to install modified USB driver if it is needed.
"USB debugging mode" must be enabled in the device.
Run the cmd.exe and go to a directory where the adb.exe is located (for example: cd d:\adb)
Run command:
Code:
adb root
adb shell
must be # in the prompt (root mode)
Code:
cd /bin
check a symlink su
Code:
ls -l --color=never su
"su -> busybox" is not right. Delete the symlink su
Code:
rm ./su
Install the Gingerbreak and root device.
Install the RootCheker and check the root.
Instructions taken from here: http://www.chinadigitalcomm.com/haipad-m8-vimicro-vc882-t10830.html

mounesh25 said:
I've updated the firmware successfully.
But now I have a new issue with the USB OTG. I cannot use the USB OTG control to change from host mode to device mode. Everytime I try to go and click on USB OTG control, it throws error "the application USB OTG (com....) has stopped unexpectedly". Ive tried to reset to factory defaults...but now seems the problem is still stuck there. I cannot go into ADB to do the rooting without enabling the 'device' mode connection for the USB. pl help.
Ive googled but none of the solutions seem to be working.
Click to expand...
Click to collapse
Can you try to install the attached package and see how it goes. Just confirm you want to replace the existing version. It worked for me.

mounesh25 said:
I've updated the firmware successfully.
But now I have a new issue with the USB OTG. I cannot use the USB OTG control to change from host mode to device mode. Everytime I try to go and click on USB OTG control, it throws error "the application USB OTG (com....) has stopped unexpectedly". Ive tried to reset to factory defaults...but now seems the problem is still stuck there. I cannot go into ADB to do the rooting without enabling the 'device' mode connection for the USB. pl help.
Ive googled but none of the solutions seem to be working.
Click to expand...
Click to collapse
Go to system/app
find usbcontrol.apk
install it
you get a fault (not installed)
after that it works agian

hey!
I found this:
blog.mcbub.com/index.php/tablet-pc/10-2-zenithink-c91-android-4-0-firmware-update-guide-beta-version
Do you think it would work on superpad? Because in guess that zenithink is kind of same thing like superpad m I wrong?

czy86 said:
I found this:
blog.mcbub.com/index.php/tablet-pc/10-2-zenithink-c91-android-4-0-firmware-update-guide-beta-version
Do you think it would work on superpad? Because in guess that zenithink is kind of same thing like superpad m I wrong?
Click to expand...
Click to collapse
I don't know but would be nice!

[SOLVED] Infuse wont connect to Ubuntu....

UPDATE-SOLVED: So I used the terminal command dmesg to see what errors were coming up relating to the usb port. It turns out I was getting the popular "unable to enumerate usb device on port..." error. From a google search on this I was able to find other people with my same problem, albeit with other types of devices not working on the usb ports. So someone tried a simple fix and worked. Ill quote it here just for the sake of keeping you on this page...
Some hardware just don’t work with ehci_hcd on Karmic Koala. My memory stick from transcend refused to work no matter what I did. After plugging the device nothing happened, doing dmesg showed me the following error:
Apr 18 10:59:04 dpac-laptop kernel: [73668.388060] usb 1-2: new high speed USB device using ehci_hcd and address 5
Apr 18 10:59:04 dpac-laptop kernel: [73668.473034] hub 1-0:1.0: unable to enumerate USB device on port 2
After searching a lot, I came to a conclusion that my device doesn’t work with USB 2.0. So I disabled the ehci_hcd to make it work.
Since Karmic doesn’t use ehci_hcd as a module, modprobe -r ehci_hcd no longer works. The module is compiled into kernel. To disable it execute the following commands in terminal:
1: cd /sys/bus/pci/drivers/ehci_hcd
2: ls
You will see a file with 0000:00:xx.x format. Execute the following command:
1: sudo sh -c 'echo -n "0000:00:xx.x" > unbind'
#Replace the xx.x with the numbers displayed on your file. It should disable the ehci_hcd.
I plugged in my memory stick, and it worked.
Please note that you’ll have to do all this each time you restart.
UPDATE
You can now use the following script to disable ehci_hcd. It is far more simpler since it just needs you copy pasting the commands instead of a manual action. Here it goes:
1: cd /sys/bus/pci/drivers/ehci_hcd/
2: sudo sh -c 'find ./ -name "0000:00:*" -print| sed "s/\.\///">unbind'
Cheers!
Ok so I just finished installing a fresh copy of Ubuntu 11.04 on my g/f's old Sony Vaio from 2003/04. I tried plugging in the Infuse to see if the computer will recognize it. So when I select 'Mass storage' from the connection menu, the connect screen with the green android robot will pop up for a split second, then disappear. So there is no way for me to mount the phone to the computer. The option doesnt even appear in the notification bar. Sometimes the robot screen wont even appear at all. I check the cable, and it works 100% fine on my win 7 64 bit pc. It just doesnt seem to want to do anything on the Ubuntu pc. The phone will charge, but thats about it. Im running the clean Gingerbread update on the Infuse. Nothing modded, and as i said, the Ubuntu is clean install as well. Ive tried this with usb debugging on and off. Ive also tried restarting both phone and pc and nothing changes.
Any help would be so greatly appreciated. Thanks a million.

weird. try other USB devices. you could have motherboard driver issues.
I'd check the Ubuntu forums and see if others with that hardware have any issues with USB devices. you may need to find some alternative drivers that aren't in the stock Ubuntu build or find a different computer.

Dani897 said:
weird. try other USB devices. you could have motherboard driver issues.
I'd check the Ubuntu forums and see if others with that hardware have any issues with USB devices. you may need to find some alternative drivers that aren't in the stock Ubuntu build or find a different computer.
Click to expand...
Click to collapse
I have tried some flash drives. They seem to work just fine. When I plug the phone in under the mass storage option, I open up a terminal and type usb-devices, and i see the three ports listed, but it shows that nothing is being detected on any of them.

Linux driver should be perfect, before connects to PC the mass storage mode should be selected.

dubuntu said:
Linux driver should be perfect, before connects to PC the mass storage mode should be selected.
Click to expand...
Click to collapse
I made sure it was selected. I also just got finished setting up the Android SDK on the Ubuntu laptop. ADB does not recognize that the device is plugged in at all. It can see my flash drives, but nothing comes up for my phone. Even with usb debugging on it did not see it. Im at a loss. Im beginning to think that this may have something to do with the Gingerbread update. Can someone with the update try to connect to Ubuntu and let me know if they have success? Ide hate to have to revert my device to Froyo or an unofficial rom to develop. =/

well I see you fixed it. did you get adb going?

Dani897 said:
well I see you fixed it. did you get adb going?
Click to expand...
Click to collapse
Yes! How?
Sent from my SAMSUNG-SGH-I997 using Tapatalk

are you asking how he fixed it?(he updated the op if that's what you are interested in) or how to get adb going.? adb works on Ubuntu as long as the device connects but you need to setup some device information first.
I forget the location but you need to create a file called 70rules.android (if my memory serves me right) with the vendor I.d and some other information. let me know and ill find a link on it.

Yes! I was able to finally get adb going after I had fixed the USB detection. Once I had applied the changes above my computer would immediately recognize the phone in both normal and debug mode and I could transfer files to and from it freely. Also, typing in ./adb devices finally showed my device as being connected with the proper vendor id as well.
The file I believe yyour referring to is named 70-android.rules and its only part of a whole process on getting the sdk setup on the laptop. There are a lot of hits for setting g it up on Google. There is also a whole guide for this here on xda which I had followed.
Sent from my Samsung Silly Phone

[Q]Problem with MTP (and help with a workaround)

Hi
Some background. Like many, I bought a TF700T and like a fool installed the OTA update to JB. I then downgraded, rooted in .30, then upgraded again and flashed SU to keep root in JB. I am now, therefore, running the stock OTA JB ROM, rooted. My bootloader is also unlocked.
Initially after this, plugging the TF700 into USb on Windows 7 (x64) worked fine - the device popped up as a Media Device and I could transfer files on and off it with ease. Now, without changing anything on either end, Windows is refusing to play. It tries to install MTP drivers but fails. If I boot the device in either CWM or Fastboot it connects fine (with adb and fastboot, respectively).
I want to get files on and off the *internal* storage (I don't have an external sdcard)
Things i have tried:
- Using a different USB port
- Using one of the USB ports on the back of the machine, instead of the front ones
- Uninstalling the MTP drivers
- Using the ASUS drivers from the website
- Cleaning out all my old unconnected USB devices (show devmgr_unconnected_devices=1 or whatever) and uninstalling all THOSE drivers
- Cleaning out with USBDeview
- Fresh install of the OTA ROM, after a data wipe/factory reset and wiping cache and dalvik
The only things I haven't tried are a new USB cable (damn you ASUS and your proprietary connector), and a clean install of Windows (major ballache).
Any ideas about what I could do to sort this would be greatly appreciated.
Since I only want to be able to move files on and off the device, I tried a workaround. I tried mounting the sdcard (internal) in windows manually through adb but the command I used to use on my old S2 through adb shell (echo dev/block/mmcblk0 > /sys/devices/platform/usb_mass_storage/lun0/file) but it errors with No such path or similar. I'm unsure if the mount points are different (I guess they will be, can anyone help with telling me what the mount point for the internal emmc is on the tf700?)
Really hope someone will be able to help me!
Thanks in advance guys

I'm in a similar situation except I'm not rooted or unlocked. I've tried just about all the steps you've mentioned w/ no luck. I've even tried to three different PCs running XP, Vista, and 7 and get the same result. What makes the situation even worse is my brand new 32GB microSD card won't read on my desktop as well.

m000se said:
Hi
Some background. Like many, I bought a TF700T and like a fool installed the OTA update to JB. I then downgraded, rooted in .30, then upgraded again and flashed SU to keep root in JB. I am now, therefore, running the stock OTA JB ROM, rooted. My bootloader is also unlocked.
Initially after this, plugging the TF700 into USb on Windows 7 (x64) worked fine - the device popped up as a Media Device and I could transfer files on and off it with ease. Now, without changing anything on either end, Windows is refusing to play. It tries to install MTP drivers but fails. If I boot the device in either CWM or Fastboot it connects fine (with adb and fastboot, respectively).
I want to get files on and off the *internal* storage (I don't have an external sdcard)
Things i have tried:
- Using a different USB port
- Using one of the USB ports on the back of the machine, instead of the front ones
- Uninstalling the MTP drivers
- Using the ASUS drivers from the website
- Cleaning out all my old unconnected USB devices (show devmgr_unconnected_devices=1 or whatever) and uninstalling all THOSE drivers
- Cleaning out with USBDeview
- Fresh install of the OTA ROM, after a data wipe/factory reset and wiping cache and dalvik
The only things I haven't tried are a new USB cable (damn you ASUS and your proprietary connector), and a clean install of Windows (major ballache).
Any ideas about what I could do to sort this would be greatly appreciated.
Since I only want to be able to move files on and off the device, I tried a workaround. I tried mounting the sdcard (internal) in windows manually through adb but the command I used to use on my old S2 through adb shell (echo dev/block/mmcblk0 > /sys/devices/platform/usb_mass_storage/lun0/file) but it errors with No such path or similar. I'm unsure if the mount points are different (I guess they will be, can anyone help with telling me what the mount point for the internal emmc is on the tf700?)
Really hope someone will be able to help me!
Thanks in advance guys
Click to expand...
Click to collapse
First check make sure you have your "USB debug" and "Unknow software" checked in settings. Then go here and install the pda software for your windows. Once installed, it will installed all the driver for your tab automatically. You don't need to use the software, you can uninstall it later, but the driver will stay.
http://junefabrics.com/android/download.php

I haven't picked up a TF700 yet (out of stock locally), so these are just general suggestions...
From adb, shell into the OS (adb shell) and list the directories to try and determine their structure. If the device is booted, the internal SD should already be mounted.
I would start by looking for the following folders:
/sdcard
/mnt/sdcard
/data/media

m000se said:
Hi
Initially after this, plugging the TF700 into USb on Windows 7 (x64) worked fine - the device popped up as a Media Device and I could transfer files on and off it with ease. Now, without changing anything on either end, Windows is refusing to play. It tries to install MTP drivers but fails. If I boot the device in either CWM or Fastboot it connects fine (with adb and fastboot, respectively).
Click to expand...
Click to collapse
I had the same problem getting MTP to work on old XP machine. The following worked for me...see post #12
http://www.transformerforums.com/fo...ormer-manual-usb-drivers-sync-software-2.html

Thanks for the replies, everyone. I installed PDANet and was initially hopeful once the drivers started installing. Sadly, Windows still doesn't see my device.
adb shell-ing into the device --> mounts
This lists /dev/fuse as the internal storage. I can't echo this to /sys/devices/usb_mass_storage/lun0/file because when I do it returns "No such file or directory"
The solution posted as working on XP machines doesn't work either.
This is seriously annoying. I'm tempted to just give in and get myself a 32GB SDHC and card reader and just use that instead - at least that way I can move the files across with Root Explorer or something...

[Q] Problem regarding mounting cm10 phone as a usb storage

Hi ..I have recently flashed CM10 rom from freexperia project and the rom is just perfect and much better then my stock rom but i have a problem when i try to connect it to my tv..you see earlier..in my stock rom it was easy to switch between MTP and MSC mode but here there is no MSC mode so i had to download USB switcher for the CM10 and then i mounted it as USB storage...i got the sign USB Loading.... in my TV but then the process automatically stops.and the tv doesn't detect my device as usb..any help from you guys/gals will be helpful to me...a lot helpful..thanks in advance.

contramaster24 said:
Hi ..I have recently flashed CM10 rom from freexperia project and the rom is just perfect and much better then my stock rom but i have a problem when i try to connect it to my tv..you see earlier..in my stock rom it was easy to switch between MTP and MSC mode but here there is no MSC mode so i had to download USB switcher for the CM10 and then i mounted it as USB storage...i got the sign USB Loading.... in my TV but then the process automatically stops.and the tv doesn't detect my device as usb..any help from you guys/gals will be helpful to me...a lot helpful..thanks in advance.
Click to expand...
Click to collapse
Try using these codes what I posted before, I've heard that they vary depending on devices.
Use this code in the terminal what is installed with CM10;
su
setprop persist.sys.usb.config mass_storage,adb
reboot
That changes it to mass storage mode when you connect it to the PC, slide down the notifcation bar and click on the notification, enable mass storage mode and when you are finished enter this code into the terminal to change it back to MTP;
su
setprop persist.sys.usb.config mtp,adb
reboot

I already tried that dude but it didn't work ...i saw that my tv was recognizing it as a mass storage device but it wasn't loading ..so any other solution

Galaxy S5 with broken screen, need help controlling it from PC

Hi, I've got an old S5 with a broken screen. There's no image going on and there's no indication that the touchscreen is working.
I'm not looking to recover data, I'm looking to play around with it by controlling it from my PC. Last I remember, the phone is running a Cyanogenmod OS (I don't think LineageOS was around at that time) with either TWRP or CWM recovery, but I'd bet on TWRP.
Now: the device reaches the OS properly, I can tell because if I try to turn the ringing sound up it gives me an audio feedback.
If I connect it to a PC from the OS:
- the phone shows up in Windows Explorer as "SM-G900F"
- Device Manager shows me a "SAMSUNG Mobile USB Composite Device" under Universal Serial Bus controllers
However I cannot access any files (Windows Explorer shows the device as empty), and if I attempt to 'adb devices' in the console it shows me an empty devices list.
Now, I suspect that USB debugging might be off. So I also tried connecting it to a PC from recovery and the exact same thing as above can be observed, PLUS:
- Device manager also shows me a "SAMSUNG Android Phone" list which can be expanded to show me one entry called "SAMSUNG Android ADB Interface"
However it's the same as before, no files available and 'adb devices' shows an empty list.
Now I heard that I can theoretically enable USB debugging through ADB, by writing to a config file. That would allow me to enable USB debugging and try something like Vysor in order to control the phone from my PC.
However that's a moot point until I can figure out why the ADB service on my PC isn't seeing the device. Any help would be greatly appreciated, and if you need more info I can provide it.
Extra info:
- I installed Samsung USB drivers at some point while trying to make it work
- Windows Explorer shows a phone icon for this device, and if I recall correctly that's what happens when it's connected through MTP (Mass Storage should show it like a memory card)

_sepiroth said:
Hi, I've got an old S5 with a broken screen..........
Click to expand...
Click to collapse
I've never experienced this situation myself but, I've seen that the following thread has worked for many individuals.
https://forum.xda-developers.com/showthread.php?t=2786395
Good Luck!
~~~~~~~~~~~~~~~
Unless asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my Apple Macintosh.

Ibuprophen said:
I've never experienced this situation myself but, I've seen that the following thread has worked for many individuals.
https://forum.xda-developers.com/showthread.php?t=2786395
Good Luck!
~~~~~~~~~~~~~~~
Unless asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my Apple Macintosh.
Click to expand...
Click to collapse
Thanks a bunch, that pointed me in the right direction with my research! I solved my issue, I can now control my phone from my PC.
By doing this I ran into a couple of problems, I'm going to describe them and their solutions:
Problem 1: couldn't ADB into the device when in Recovery Mode. That is because after a long head scratching session I came to the conclusion that I didn't have TWRP Recovery installed (I had Philz Touch CWM Recovery and LineageOS 14.1 instead).
Solution 1: ADB mode is enabled in TWRP by default. So I flashed the latest TWRP through Odin, ADB instantly started working afterwards in Recovery Mode.
Problem 2: USB Debugging was disabled inside the OS.
Solution 2: from the thread that Ibuprophen posted, you can enable USB debugging in your OS by opening an ADB shell into your device and modify the build.prop like so
Code:
Adb shell
echo "persist.service.adb.enable=1" >>/system/build.prop
echo "persist.service.debuggable=1" >>/system/build.prop
echo "persist.sys.usb.config=mass_storage,adb" >>/system/build.prop
reboot
Problem 3: /system was empty so there was no build.prop. If I attempted to create a build.prop file it wouldn't be saved after a device reboot, so USB debugging still didn't work.
Solution 3: it seems like TWRP doesn't mount /system by default, only /data. You can mount it manually through ADB like this:
Code:
mount -o rw /dev/block/bootdevice/by-name/system /system
I found this out from this stackexchange question: https://android.stackexchange.com/q...data-partitions-in-recovery-mode-in-adb-shell
Problem 4: When an app tries to use USB Debugging you need to allow it to do so from the phone. Since the screen was broken, I couldn't do this.
Solution 4: You'll need to push a public key to your device with ADB. Boot into Recovery Mode and make sure your device is recognized by your PC and type
Code:
adb push <path to adbkey.pub on your PC> /data/misc/adb/adb_keys
This solution is from: https://stackoverflow.com/questions...b-rsa-key-with-broken-touch-screen-on-android
This will make sure that you won't need to confirm debugging permissions for apps coming from your machine.
So for anyone who has a broken phone screen (my screen is dead and touchscreen/touch buttons are kaput too) and wishes to control their phone from their PC but USB debugging is disabled:
1. Boot device in TWRP Recovery (flash it if you don't have it)
2. ADB into the device
3. Make sure /system is mounted (if it's empty it means it's not mounted), else mount it manually like in Solution 3
4. Configure build.prop to have USB Debugging enabled like in Solution 2
5. Push your public key to the device like in Solution 4
6. Restart the phone (into its OS)
7. Download the Chrome extension called Vysor and launch it
8. Connect your phone through a USB cable
9. The device should appear in Vysor, connect to it and have fun controlling it
Note that if you just want to backup your files, steps 1 + 2 are sufficient. After making sure ADB works you can just 'adb pull' all your files which should be located in /sdcard. Google it, it's easy to find.
The same goes for backups, you can do them directly through ADB.
Again, thanks Ibuprophen!

Vysor does not work on all graphic cards. a good free alternative is scrcpy
btw instead of flashing twrp, you can flash a modified system partition with proper entries in build.prop (for those with no custom recovery available)

aIecxs said:
Vysor does not work on all graphic cards. a good free alternative is scrcpy
btw instead of flashing twrp, you can flash a modified system partition with proper entries in build.prop (for those with no custom recovery available)
Click to expand...
Click to collapse
Very well pointed out, thanks for this.