Related
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!
nexus s i9023 with ics offical rom rooted and unlocked but power button suddenly stopped working so i flashed a jb volume wake zip to enable this feature but it gave me a bootloop now i cant even recover because of the power button i managed to get in the fastboot mode by putting the battery and quickly press volume up but in fastboot the device is not even detected by the usb (original) i have sdk and usb drivers but the problem is i put my phone in usb its like ive put a potato nothing happens and the sentences usb control init and usb control init end have disappeared in fastboot mode so i cant send commands to the phone through adb is there a way to make my phone detectable although when my phone is in the bootloop process its detected by the computer normally but no response of course.
THANKS in ADVANCE
osos96 said:
nexus s i9023 with ics offical rom rooted and unlocked but power button suddenly stopped working so i flashed a jb volume wake zip to enable this feature but it gave me a bootloop now i cant even recover because of the power button i managed to get in the fastboot mode by putting the battery and quickly press volume up but in fastboot the device is not even detected by the usb (original) i have sdk and usb drivers but the problem is i put my phone in usb its like ive put a potato nothing happens and the sentences usb control init and usb control init end have disappeared in fastboot mode so i cant send commands to the phone through adb is there a way to make my phone detectable although when my phone is in the bootloop process its detected by the computer normally but no response of course.
THANKS in ADVANCE
Click to expand...
Click to collapse
EDIT/UPDATE 1: i managed to get into recovery mode :victory:
HOW? NOTICE: IM NOT RESPONSIBLE FOR ANY DAMAGE OF ANY KINND YOU DO TO YOUR PHONE USE AT YOUR OWN RISK
1. keep phone plugged in usb
2.download SDK Manager from (http://developer.android.com/sdk/index.html)
3.install it in root path in Windows 7>>>>>C:/Users/[yourusername]/SDK
4.boot your phone NORMALLY in boot loop
5.connect your phone in usb if you neglected step one
6.your computer should detect it
7.open command promote (CMD) (shortcut windows flag+R) type cmd
8.a black screen will appear type in it "cd SDK/sdk/platform-tools" and press enter
9.path now should be C:\users\[your user name] \SDK\sdk\platform-tools>adb shell second line [email protected]:/ #
10.now type this (copy and paste is recommended) "mount -o remount,rw -t yaffs2 /system /system"
11.now simply type reboot recovery and your phone should reboot in recovery img
12.wipe factory settings now you should be good
osos96 said:
EDIT/UPDATE 1: i managed to get into recovery mode :victory:
HOW? NOTICE: IM NOT RESPONSIBLE FOR ANY DAMAGE OF ANY KINND YOU DO TO YOUR PHONE USE AT YOUR OWN RISK
1. keep phone plugged in usb
2.download SDK Manager from (http://developer.android.com/sdk/index.html)
3.install it in root path in Windows 7>>>>>C:/Users/[yourusername]/SDK
4.boot your phone NORMALLY in boot loop
5.connect your phone in usb if you neglected step one
6.your computer should detect it
7.open command promote (CMD) (shortcut windows flag+R) type cmd
8.a black screen will appear type in it "cd SDK/sdk/platform-tools" and press enter
9.path now should be C:\users\[your user name] \SDK\sdk\platform-tools>adb shell second line [email protected]:/ #
10.now type this (copy and paste is recommended) "mount -o remount,rw -t yaffs2 /system /system"
11.now simply type reboot recovery and your phone should reboot in recovery img
12.wipe factory settings now you should be good
Click to expand...
Click to collapse
I will try it now! If this works, then you are superman for me :good:
Edit:
1. should I type "adb shell second line [email protected]:/ #" after the new path is set and press enter?
2. if I do it, i always get the message "the command mount is wrong or can not be found"
!Lür said:
I will try it now! If this works, then you are superman for me :good:
Edit:
1. should I type "adb shell second line [email protected]:/ #" after the new path is set and press enter?
2. if I do it, i always get the message "the command mount is wrong or can not be found"
Click to expand...
Click to collapse
Was much easier for me, don´t know why.
Solution for me:
1. Turn device into Bootloop
2. Connect it via USB (PC founds it)
3. type in CMD "adb reboot recovery"
4. device is in recovery
Requirement is a working Android-SDK.
!Lür said:
Was much easier for me, don´t know why.
Solution for me:
1. Turn device into Bootloop
2. Connect it via USB (PC founds it)
3. type in CMD "adb reboot recovery"
4. device is in recovery
Requirement is a working Android-SDK.
Click to expand...
Click to collapse
yup i just made it a step by step tut for noobs and your welcome
Hi,
was using this guide online to try to recover and move stuff around in my Nexus5 while it is broken as far as i know this is a LCD problem not a digitiser problem.
http://www.techlife.net/2014/09/access-your-android-device-after-breaking-your-screen.html/
http://forum.xda-developers.com/showthread.php?t=2786395
ran into a problem that I can't turn on USB Debugging on my phone without being able to see what i am pressing.
According to the end of the guide it told me to flash a kernel with USB debugging enabled by default but I am unsure of what this means.
Rooted: No (I dont mind if i have to)
Fastboot: No idea
Installed ADB on computer: Yes
The custom kernel will need to have USB debugging ON by default/on boot. Usually through a custom initrc.
If you manage to get rooted, you could try:
androidscreencast
- Flash TWRP if you haven't already
- boot to recovery
- adb shell
- mount system
- edit build.prop
- reboot
- figure out adbkey.pub stuff
I have gone the same way, but could not get a screen display. It was on my wife's Gnex though. The rest works.
Now to get debian or something installed...ultralow power wireless server.
You need to install ADB/Fastboot to your PC
GO HERE
Then you can
Enable usb debugging via recovery using the following ABD commands:
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
joegestes said:
You need to install ADB/Fastboot to your PC
GO HERE
Then you can
Enable usb debugging via recovery using the following ABD commands:
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
Click to expand...
Click to collapse
OP, try this.
The two previous posts are forgetting you need usb debugging before you can adb shell.
Booting to recovery gives you access to your system and build.prop.
Bubble-be said:
The two previous posts are forgetting you need usb debugging before you can adb shell.
Booting to recovery gives you access to your system and build.prop.
Click to expand...
Click to collapse
recoveries have adbd enabled by default. what we're doing here is making the OS have adbd enabled.
Yes, we're on the same page there.
You can't just adb to your device to enable adb, get it ?
You need a way to access build.prop out of android, so booting to recovery will allow you this.
Just dugg up the link for the adbkey as well. http://forum.xda-developers.com/showthread.php?t=2408802
get a USB OTG cable and connect your mouse to your phone
Bubble-be said:
Yes, we're on the same page there.
You can't just adb to your device to enable adb, get it ?
You need a way to access build.prop out of android, so booting to recovery will allow you this.
Just dugg up the link for the adbkey as well. http://forum.xda-developers.com/showthread.php?t=2408802
Click to expand...
Click to collapse
Huh...
Even if display isn't coming on... You can 3bc to fastboot, press down twice (iirc) and press power. wait a few secs, custom recovery should be running.
`adb shell` .. out of android, adb running. profit.
I think the OP is not rooted, nor does he have a custom recovery.
In that case you will need boot temporarily into a custom recovery that will allow root ADB shell access.
Download the TWRP recovery image to you PC.
HERE
For simplicity, rename the file recovery.img
Place the renamed file in your \sdk\platform-tools folder on PC.
Turn off you phone and then hold volume up button while pressing power button to get into fastboot mode.
Then, open a command prompt from within the platform-tools folder and run the following command:
fastboot boot recovery.img
Your phone should reboot into TWRP recovery.
You can then run the ADB commands outlined in my first post to enable usb debugging:
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
Best of luck
Bubble-be said:
The two previous posts are forgetting you need usb debugging before you can adb shell.
Booting to recovery gives you access to your system and build.prop.
Click to expand...
Click to collapse
This is incorrect.
I do not need usb debugging enabled to run ADB shell in custom recovery.
Bubble-be said:
Yes, we're on the same page there.
You can't just adb to your device to enable adb, get it ?
You need a way to access build.prop out of android, so booting to recovery will allow you this.
Just dugg up the link for the adbkey as well. http://forum.xda-developers.com/showthread.php?t=2408802
Click to expand...
Click to collapse
Huh
My post clearly stated via recovery
---------- Post added at 06:31 PM ---------- Previous post was at 06:13 PM ----------
4n3ver said:
get a USB OTG cable and connect your mouse to your phone
Click to expand...
Click to collapse
I've never tried this, but think you need to be rooted and install some hacks to get a mouse
to work via OTG.
Hello again,
Thanks for all the replies so far.
Unfortunately i'm still unable to enable USB debugging.
I'm getting stuck, I have managed to install adb and fast boot using the 15 second thing but am unable to get it to detect via "adb devices" and am currently troubleshooting this step
I can't upload images so i'm just gonna type what it says
Code:
C:\Users\blah> fastboot boot recovery.img
<waiting for device >
^C
C:\Users\blah> adb devices
List of devices attached
C:\Users\blah>
probably something to do with how my adb drivers are installed
Just to clarify my screen is impossible to use as its just coloured lines due to cracks in the LCD screen.
Hopefully all goes well and i'll be able to fastboot TWRP with the instructions you guys have given me.
fuzznuzz said:
Hello again,
Thanks for all the replies so far.
Unfortunately i'm still unable to enable USB debugging.
I'm getting stuck, I have managed to install adb and fast boot using the 15 second thing but am unable to get it to detect via "adb devices" and am currently troubleshooting this step
I
Click to expand...
Click to collapse
Your welcome.
It's probably just simple a driver issue. You will need to look in Device manager on PC while phone is connected.
Download the howto_driver.zip from the "15 seconds ADB Installer thread" and follow the picture tutorial contained in the zip file. This should fix your connectivity issues:good:
---------- Post added at 03:23 AM ---------- Previous post was at 02:58 AM ----------
If it helps, I don't have the "Android Bootloader Interface" driver option. So for me,
selecting "Android Composite ADB Interface" allows me to detect my Nexus5 in both ADB and Fastboot mode.
Keep in mind, my OS Win7 64bit and my 64 bit ADBdriver package may be entirely different than yours.
Okay i'm having some other problems now
can anyone help?
fuzznuzz said:
Okay i'm having some other problems now
can anyone help?
Click to expand...
Click to collapse
Your bootloader is locked.
Sent from my Nexus 5 using XDA Free mobile app
fuzznuzz said:
Okay i'm having some other problems now
can anyone help?
Click to expand...
Click to collapse
Locked bootloader
It is the first question I or anyone replying should have asked you.
Unfortunately, as far as I know, it's game over recovering any user data with
a busted non-viewable LCD, no USB debugging and a locked bootloader.
Unless, you can by some luck, miracle or Power of the Force, pull off using your touchscreen to enable USB debugging.
Then you could use Simple ADB Backup or Holo Backup to get your data.
If not and your data is important enough to you, then replacing the screen would be your last option.
Worth replacing IMHO because your Nexus 5 is still a really great phone with nice specs and plenty of power.
Found one HERE shipped from China for $46.76 or HERE from USA $69.99 from US on ebay.
didn't work
joegestes said:
You need to install ADB/Fastboot to your PC
GO HERE
Then you can
Enable usb debugging via recovery using the following ABD commands:
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
Click to expand...
Click to collapse
i followed all these steps and adb devices shows nothing while phone is in recovery mode
fastboot devices shows my phone when in fastboot mode
just adb not working
help asap please
halo_95 said:
i followed all these steps and adb devices shows nothing while phone is in recovery mode
fastboot devices shows my phone when in fastboot mode
just adb not working
help asap please
Click to expand...
Click to collapse
Do you have a stock recovery or a custom one?
You'll need to boot a custom recovery, not the stock recovery.
Now that you don't have to install the custom recovery, just boot it.
Hi
I have a old nexus with broken touchscreen . I want to use it via mirror on pc.
unfortunatly USB debuggin wasn't enable so i can't install any app.
any tips?
thanks
PS: i saw many use usb adapter to connect a mouse but i don't have it
EDIT: right now i just need a rom/kernel with USB debugging mode enabled by default
the screen still works , only the touch screen is broken
power , and volume bottons still work
the device is rooted
If it's only installing apps you could install them via recovery. (as zip)
Or you could check for a cheap replacement touchscreen.
nonameleft4me said:
If it's only installing apps you could install them via recovery. (as zip)
Or you could check for a cheap replacement touchscreen.
Click to expand...
Click to collapse
thanks for the answer!
sorry i forgot to mention that i need USB debuggin for make the app works correctly.
I'm trying now to find out what rom i have installed and maybe then find a kernel with OTG support . (yes i found a otg cable )
i'm not a expert of rooting
I think google has an app called voice control. Not sure how operational it is though. Supposedly you can control the entire system via voice.
nonameleft4me said:
I think google has an app called voice control. Not sure how operational it is though. Supposedly you can control the entire system via voice.
Click to expand...
Click to collapse
i need to unlock the phone and tap on the widget "search" to start voice command .
I think the best way is to find a way to enable OTG and then use a usb mouse
Boot into Recovery and mount*Data*partition.
Open a shell on PC and type:
adb pull /data/property/persist.sys.usb.config ~/
Repace*~/*with home directory of your OS.
Open that file in a text editor and you would possibly see*mtp*written there. Change it to*mtp,adb.
Note that sometimes Android doesn't understand the text file changes if the line terminator is "DOS Terminators" which Notepad would probably do on Windows (mine is Linux so no issue here).
In that case, I would suggest not using*adb pullbut doing:
adb shell echo 'mtp,adb' > /data/property/persist.sys.usb.config
You may verify that the*echo*command overwrote the file by using:
adb pull /data/property/persist.sys.usb.config ~/
and seeing the file's content in some text editor.
Unmount*Data*and reboot into Android OS. USB Debugging would probably be enabled.
Sent from my Aqua Trend using Tapatalk
Itzabhaysingj said:
Boot into Recovery and mount*Data*partition.
Open a shell on PC and type:
adb pull /data/property/persist.sys.usb.config ~/
Repace*~/*with home directory of your OS.
Open that file in a text editor and you would possibly see*mtp*written there. Change it to*mtp,adb.
Note that sometimes Android doesn't understand the text file changes if the line terminator is "DOS Terminators" which Notepad would probably do on Windows (mine is Linux so no issue here).
In that case, I would suggest not using*adb pullbut doing:
adb shell echo 'mtp,adb' > /data/property/persist.sys.usb.config
You may verify that the*echo*command overwrote the file by using:
adb pull /data/property/persist.sys.usb.config ~/
and seeing the file's content in some text editor.
Unmount*Data*and reboot into Android OS. USB Debugging would probably be enabled.
Sent from my Aqua Trend using Tapatalk
Click to expand...
Click to collapse
thanks!
i tryed
1) i went in recovery mode
2) i connect via usb the nexus4 to my pc
3)went in "mounts and storage"
4)then "mount /data"
5)in cmd i tryed your command "adb pull /data/property/persist.sys.usb.config" but i says i'm unauthorized
i checked via command "adb devices" and it return a alphanumerica string plus "unauthorized"
i tryed then to
Reboot your phone into recovery mode.
Connect it to your computer.
Open the terminal and type:
cd ~/.android
adb push adbkey.pub /data/misc/adb/adb_keys
adb shell reboot
but it still says error : device unauthorizated . please check the confirmation dialog on your device
i tryed also with a different version of adb and now gives me after "adb devices" an "offline" response
NB: if i connect the phone (not in recovery mode) via usb i can copy files in and out (i can explore onlyfew folders) , maybe this could help.
hartman11 said:
i tryed also with a different version of adb and now gives me after "adb devices" an "offline" response
NB: if i connect the phone (not in recovery mode) via usb i can copy files in and out (i can explore onlyfew folders) , maybe this could help.
Click to expand...
Click to collapse
Sorry but this could not help... Now only thing you can do is connect any USB mouse to your phone via otg cable (as it is not costly also), and you can also try USB gamepad. I also have used USB gamepad before when my touchscreen was not working.
Second thing you can do is download any android device manager for your PC like mobogenie or mobilego they directly install any app from play store to you android device, through USB.And I don't think they need USB debugging option to be enabled.
Sent from my Aqua Trend using Tapatalk
my problem is not installing an app (i could do it in recovery mode with a .zip) but enabling the USB debuggin
I have a otg cable but not the "Y" type ( the one with power source ) , also i don't know if OTG is supported by my kernel . I would like to install maybe another kernel which has OTG support and usb debuggin mode enable by default but i don't know what kind of rom i have D:
right now i just need a rom/kernel with USB debugging mode enabled by default
up
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.