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!
My daughter's Nexus S touchscreen has died. It died slowly in that on the first few occasions she couild pop the battery and it would come back. Now it won't come back at all and is stuck on the pattern lock screen.
Before we send the phone for repair under warranty she is keen to get the photos off the phone since a repair might reset the phone. I was thinking we could mount the phone as a USB device but it doesn't show up perhaps because it won't until the pattern lock is entered else anybody could get data off your phone bypassing security.
Any other things we could try before giving up and hoping the repair doesn't delete all the data?
Thanks
Boot into recovery, make a nand then extract data through adb?
adb pull /sdcard/path-to-whatever
Can you explain the path to whatever? Like if I want it in folder "A" on the desktop.
Sent from my Galaxy Nexus using Tapatalk 2
Check this thread
http://forum.xda-developers.com/showthread.php?t=1573744
treUse said:
adb pull /sdcard/path-to-whatever
Click to expand...
Click to collapse
Out of interest I tried this on my GN. adb recognises the phone and adb devices shows the serial number. But adb pull /sdcard says invalid remote file. No idea what that means since using ES File Explorer sdcard is a valid directory on the phone (and I suppose it would also be on the Nexus S)
lchiu7 said:
Out of interest I tried this on my GN. adb recognises the phone and adb devices shows the serial number. But adb pull /sdcard says invalid remote file. No idea what that means since using ES File Explorer sdcard is a valid directory on the phone (and I suppose it would also be on the Nexus S)
Click to expand...
Click to collapse
ADB "thought" you meant to copy a file.
To copy the entire sdcard directory you should do something like this:
Code:
adb pull /sdcard/ sdcard/backup/on/pc/
The command parameters are "adb pull <source> <destination>"
Just make sure source ends with a /
Maybe a Windows based software?? Droid Explorer, very useful.. http://de.codeplex.com/ :good:
Well I finally got the phone to play with. The screen indeed dead. I installed the Google USB drivers from the SDK and also the Samsung drivers.
When I boot the phone into the recovery menu I can run fastboot devices and see the following
????0AC4B09900?? fastboot (of course the ? are not there but I wanted to anonmyuse the serial)
So far so good.
In device manager under Android Phone it show Samsung Android ADB Interface
But if I try adb devices I get nothing.
Forgot to mention my daughter said USB Debugging was turned off but I am not sure that makes any difference and anyway, we can't boot Android to turn it on
So I select Recovery and see the Android with the exclamation mark. Windows beeps to indicate that some sort of devices has been installed,
But in Device Manager no phone shows which explains why adb can't fidn the phone but not why.
I can bring up the recovery menu but still no adb
Any suggestions?
Thanks
Boot into Fastboot and flash CWM Recovery.
RL77LUC said:
Boot into Fastboot and flash CWM Recovery.
Click to expand...
Click to collapse
But it looks like I have to unlock the bootloader to do that and the phone is still under warranty so that would invalidate the warranty wouldn't it? She would like to get the data off the phone. A screen fix shouldn't zap the memory but you never know.
what this device installed CWM?? if installed cwm just bot it to cwm an goto mass storage
cukdus said:
what this device installed CWM?? if installed cwm just bot it to cwm an goto mass storage
Click to expand...
Click to collapse
The phone is stock
lchiu7 said:
The phone is stock
Click to expand...
Click to collapse
If you unlock the bootloader to flash CWM your memory will also be wiped, so you will loose all the photos you want to save, so don't do that.
Also if you have the USB debugging off, the ADB commands won't work. I'm afraid you're SOL, since you have the bootloader locked you can't flash a kernel with USB host, that would allow you to use a mouse to navigate in the phone and since you don't have USB debug you can't pull files from the "SDcard"... Better take it to the store and try to ask them if they can save the photos before they do anything to the phone, but i guess if it's a digitalizer problem, they won't mess with the NAND.
Check out http://www.moborobo.com/ and see if it works for you.
If you have root you have extended functionality, like control the device from the PC. But if i recall correctly, even without root you should be able to get your files.
For those who may be flashing ROMs, cannot mount the SD Card any more, and may have accidentally corrupted their SD Card, here are some helpful steps.
Preliminary Review - Check to see if you can mount in recovery or bootloader
First, go back to your bootloader screen and click on fastboot (reset your phone and hold the power and vol down button). Once in bootloader check your computer drives to see if the sd card is recognized
Your computer may be able to recognize the drive even if it cant open it. If thats the case, you may be able to format it from your computer (use FAT32 formatting).
Second, If you cannot see your SD Card in your ROM or from the PC, and you are using Clockwork Recovery (CW), try flashing TWRP recovery first. Do this by going through the following steps:
Step #1
Download TWRP recovery from http://teamw.in/project/twrp2/100 Make sure to download the correct version for your device
Step #2
Place the recovery file into a folder with fastboot.exe
Step #3
Reboot your phone and hold down the Vol Down Button and Power Button until your bootloader screen appears, then enter fastboot. Then connect to your computer. I find this method works best by holding down the buttons right away. If your phone is off, press the power button then immediately press and hold the power and vol off buttons again until bootloader screen shows up. Dont let go until the screen shows.
Step #4
Type
Code:
fastboot flash recovery twrp.img
but replace the twrp.img wording with the exact name of your downloaded TWRP recovery
Step #5
Enter TWRP recovery by selecting it from your bootloader screen. Then ensure the device is connected to your computer and select the Mount option and then mount your sd card.
IF you still cant see your SD Card from TWRP recovery or you get an error, proceed to the next steps. Your computer may be able to recognize the drive, even if it cant open it (if your lucky).
If your computer recognizes the drive but cant open it, you can try formatting it from your computer (make sure to format as FAT32)
If you really cant see your SD Card, and your fairly sure its corrupted, and you have no way formatting it from your computer, continue on below:
Basic Solution
Reflashing Stock Recovery to your device using fasboot, then doing a full factory reset. This would be using the method in post http://forum.xda-developers.com/showthread.php?t=1630459
PLEASE NOTE THIS METHOD WILL WIPE THE DATA FROM YOUR DEVICE AS WELL AS FROM YOUR SD CARD
This method works because custom recoveries cannot re format SD Cards on the HTC One S, only wipe data from them. However, the stock recovery does have a proprietary feature that will reformat the internal sd card if it has been corrupted.
Inotherwords:
Step #1
Download the stock recovery from: http://loadbalancing.modaco.com/download.php?file=ville_recovery_signed.img
*******Note that this file is a stock recovery for S4 devices, not S3.
Place the file into the same folder as your fastboot.exe
Step #2
On your device, go into bootloader and fastboot mode, connect your computer to the device, and type
Code:
fastboot flash recovery ville_recovery_signed.img
Step #3
Reboot into the bootloader and then choose to "clear storage" from the main screen and afterwards reset to factory defaults.
Step #4
Go back into the bootloader once step #3 is done and enter fastboot, connect your device and reflash your original custom recovery again. Your SD Card should be visible
Advanced Solution - If you do not want to wipe the data from your device
This method does not require reflashing the original recovery and factory reseting the whole phone. However, it still means that the info on your sd card will be lost. It also needs a rooted device.
This method does not require you to access your bootloader or use fastboot. You can do this while having your phone in custom recovery.
DO NOT ATTEMPT UNLESS YOU FEEL COMFORTABLE WITH THE INSTRUCTIONS. THERE ARE ALWAYS RISKS WITH FORMATTING. DO NOT HOLD ME RESPONSIBLE FOR BRICKED DEVICES. YOUR DEVICE IS LIKELY OUTSIDE OF WARRANTY ALREADY SINCE YOU WOULD HAVE UNLOCKED THE BOOTLOADER.
I have taken this solution from HTC One X forums namely from post 17 at http://forum.xda-developers.com/showthread.php?t=1647806&page=2
However, I have also confirmed (SneakyGhost's partition list for HTC One S) that the correct mmcblk0p for the HTC One S sd card is mmcblk0p36.
Step #1: Download the version of busybox listed below, unzip it and also put this in the folder with ADB before you get started. You only need to do this if you dont already have busybox installed on your HTC One S. Sometimes this busybox file can be found under /system/bin or /system/xbin if youve previously installed it. If so, replace the paths in the instructions below for that of your busybox. If you have busy box already installed in /system/bin , then you do not need to type in the paths since the adb shell automatically picks up programs in that folder
Step #2: Go to your command prompt in the folder with adb.exe . Connect your HTC One S to your computer and type
Code:
adb devices
and ensure your computer sees your HTC One S. This command should work even if you are in a custom recovery like TWRP or CW (but for gods sake, if your on CW, the first thing you should do is flash TWRP, but thats just an editorial opinion, lol).
Step #3: Type
Code:
adb push busybox /data/local/tmp
This pushes busybox to a temp folder on your HTC One S. Make sure you are pushing the busybox file and not the zip file. If you already have busy box installed you do not need to do this step. (you can delete it from this folder later if you like)
Step #4: Type
Code:
adb shell
to get into your linux shell. Then type
Code:
su
to get root access. Your command prompt should now be a # and not $.
Step #5: Type
Code:
chmod 755 /data/local/tmp/busybox
to fix permissions for busybox. You may not need to do this if you already have busy box installed with the correct permissions. If these instructions dont work with your version of busy box, try setting the permissions with this code but replace the path with the location of your busybox.
Step #6: Type
Code:
cat /proc/partitions
and just ensure you see mmcblk0p36. This is the sdcard partition for HTC One S
Step #7:Type
Code:
/data/local/tmp/busybox mkfs.vfat /dev/block/mmcblk0p36
Make sure you type this correctly. You dont want to format the wrong partition accidentally.
That should work. Pls let me know if it doesnt. If it doesnt work with your version of busybox just try using the one in the zip file below. Also remember, dont just push the zip file. Extract the busybox file from the zip and push that to your device instead.
Also, it may help to use adb through a custom recovery instead of being in your ROM (ie if it doesnt work when your phone is booted normally, try doing the steps with recovery loaded).
There are other methods to try too They would be:
Other Solutions
Other Method #1: Relocking your bootloader and using a compatible RUU with your phone. This will fully wipe your device
Other Method #2: If your computer sees your sdcard even if it cant open it when your device is connected, you can try formatting it that way (ie the way you would format any other drive on your computer)
Only use the busybox method if you are comfortable with it and if other methods have failed. You can learn more about the formatting command (ie mkfs.vfat) by googling it.
So if I got this right if I have busybox already I only have to do is step 7.
Almost, but yes, that is the key step. Although you would still want to open a terminal Window, either an adb shell or from the phone, and type su to get root, and double check to ensure the shell sees the partition. Also, I did hear in the one X forums that not every version of busy box worked. I would imagine an updated version would likely work though.
Sent from my HTC One S using xda premium
Step 4, a quicker way: adb shell su , get you into shell as root right away
AKToronto said:
Almost, but yes, that is the key step. Although you would still want to open a terminal Window, either an adb shell or from the phone, and type su to get root, and double check to ensure the shell sees the partition. Also, I did hear in the one X forums that not every version of busy box worked. I would imagine an updated version would likely work though.
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
Oh right hope I don't need it lol.
I think this should be moved to Q&A and replace the other sticky that's there.
Darknites said:
Oh right hope I don't need it lol.
I think this should be moved to Q&A and replace the other sticky that's there.
Click to expand...
Click to collapse
Im thinking it would be helpful to have this post there. Im not sure how I request to do that though. Should I PM a moderator?
AKToronto said:
Im thinking it would be helpful to have this post there. Im not sure how I request to do that though. Should I PM a moderator?
Click to expand...
Click to collapse
No idea but does sounds like a good start lol.
Darknites said:
No idea but does sounds like a good start lol.
Click to expand...
Click to collapse
I asked a moderater to review by clicking on the ! in the post, but I havent heard back yet. I also updated the post to be more n00b friendly too, and tried to cover off all sd card related issues.
AKToronto said:
I asked a moderater to review by clicking on the ! in the post, but I havent heard back yet. I also updated the post to be more n00b friendly too, and tried to cover off all sd card related issues.
Click to expand...
Click to collapse
Nice update. Ya I wish they hurry up with sorting it, the other one is a load of crap and this really should replace it.
Updated with a link to another good tutorial about pushing ROMs to the phone
Its like they don't care about stickys any more, come mods its about time this replaced the crappy one.
Cant get past the
'fastboot flash recovery ville_recovery_signed.img'
step at the moment, just keep getting 'waiting for device'.
Steveh8204 said:
Cant get past the
'fastboot flash recovery ville_recovery_signed.img'
step at the moment, just keep getting 'waiting for device'.
Click to expand...
Click to collapse
Does your bootloaderscreen say "fastboot usb" anywhere? There is an option that you have to select in your bootloader called fastboot... If it says fastboot usb then you are connected, and you shouldnt get a waiting for device error.
AKToronto said:
Does your bootloaderscreen say "fastboot usb" anywhere? There is an option that you have to select in your bootloader called fastboot... If it says fastboot usb then you are connected, and you shouldnt get a waiting for device error.
Click to expand...
Click to collapse
yea I got into the bootloader and then fast boot. ive managed to sort it now, for some reason my pc was the problem, I had to reboot my computer after a command window prompt otherwise I just got the waiting for device screen.
typical really, my laptop and phone both conspiring against me.
eventually managed to flash another recovery which did see my sdcard so all is good now.
thanks for your reply though!
AKToronto said:
For those who may be flashing ROMs, cannot mount the SD Card any more, and may have accidentally corrupted their SD Card, here are some helpful steps.
Click to expand...
Click to collapse
Dude, this works flawless!
Thought I had a soft-brick, but your instructions bring back my sd-card!
I choose the "advanced Option", it works fine....
Typing su-command generated an error message, but the other steps still functioned....
I will place link in section "helpfull links" in my signatur
Big THX to you good sir, ...
Steveh8204 said:
Cant get past the
'fastboot flash recovery ville_recovery_signed.img'
step at the moment, just keep getting 'waiting for device'.
Click to expand...
Click to collapse
Just format your phone using your PC... That's all you need to do...all those steps are overkill... Bootloader on phone... Connect to pc .. Navigate to devices on PC and format your phone...then flash recovery like stated above..
Sent from my One S using xda premium
$droyd$ said:
Just format your phone using your PC... That's all you need to do...all those steps are overkill... Bootloader on phone... Connect to pc .. Navigate to devices on PC and format your phone...then flash recovery like stated above..
Sent from my One S using xda premium
Click to expand...
Click to collapse
Some people had reported not being able to see their phone from their PC no matter what they tried... Hence the advanced steps
Dude add S3 stock recovery please.
Darknites said:
Dude add S3 stock recovery please.
Click to expand...
Click to collapse
Good point Darknites. Thank you. Do you have a link to S3 stock recovery? I dont seem to have one handy... But I did edit the OP to make that point a bit clearer (that the link is for S4 devices). Thanks again bud. Good catch.
AKToronto said:
Good point Darknites. Thank you. Do you have a link to S3 stock recovery? I dont seem to have one handy... But I did edit the OP to make that point a bit clearer (that the link is for S4 devices). Thanks again bud. Good catch.
Click to expand...
Click to collapse
Nope but a RUU will have it.
**UPDATE**
NEW VERSION
THIS RELIES ON ADB COMMANDS, SO IF YOU DO NOT HAVE USB DEBUGGING TURNED ON, OR A CUSTOM RECOVERY TO BOOT TO, THEN IT WILL NOT BE AS SIMPLE AS JUST RUNING THE PROGRAM.
Another user was having issues because he had an emulator installed, so I updated the file to give you the choice between an emulator, or device. I intend to update further to allow you to check for and select an individual device, that will come soon..
----------------------------------------------------------------------------------------------------------------
Recently my Galaxy s2's screen smashed, and, after replacing it with a GS4, i realized that many of my pictures were stuck on the internal sd card of the GS2. Being unable to turn on mass storage mode, I made a very simple tool that makes using adb pull a simple, painless process, even for the most computer illiterate of android users. Hope this helps if anyone needs it.
For anyone having issues...
If you had not previously activated USB Debugging, there are several steps you need to follow in order to enable ADB
SCREEN WORKING TOUCH BROKEN NO CUSTOM RECOVERYfirst, if you can see your screen, and have access to an otg cable, plug a mouse in to the otg cable, and the otg cable into the phone. Use the mouse to enable USB debugging, or to transfer files.
HOW TO ENABLE USB DEBUGGING
SCREEN WORKING TOUCH BROKEN WITH CUSTOM RECOVERYboot to your custom recovery ADB commands will work here. (usually hold vol- + pwr)
HOW TO BOOT TO RECOVERY
Once in custom recovery, connect the device to the PC.
open CMD and enter the following commands;
cd c:\android (this is your ADB path, c:\android is default)
adb devices
The result should be something like
List of devices attached
051a4dd5 recovery
^^this number will be different for you
if you get a result on ADB devices, then you can use the program
SCREEN BROKEN TOUCH BROKEN WITH CUSTOM RECOVERYboot to your custom recovery ADB commands will work here. (usually hold vol- + pwr)
HOW TO BOOT TO RECOVERY
Once in custom recovery, connect the device to the PC.
open CMD and enter the following commands;
cd c:\android (this is your ADB path, c:\android is default)
adb devices
The result should be something like
List of devices attached
051a4dd5 recovery
^^this number will be different for you
if you get a result on ADB devices, then you can use the program
SCREEN BROKEN TOUCH BROKEN NO CUSTOM RECOVERYnow things get complicated...
*The following is paraphrased from this site
1. download the custom recovery image for your device. Copy the recovery image to a convenient location on your computer, preferably with a short path. We will be placing it on the C Drive directly (not in any folder) and using that in the next steps.
Note: The recovery image should have .img extension. If it is in a zip file, extract the .img file from it.
I recommend clockwork mod non touch from this page
2. Power your device off and reboot your device to FASTBOOT or DOWNLOAD MODE depending on which type of device you have.
(most devices are fastboot, SAMSUNG typically uses DOWNLOAD MODE)
how to boot to fastboot or download mode
[FASTBOOT]3. Connect your device to your computer via USB and wait till you see the PC recognize the device
to check if your device is in fastboot and connected use CMD and enter the following commands;
cd c:\android (this is your ADB path, c:\android is default)
fastboot devices
you will see a list of connected devices. if not, something went wrong.
4. Launch Command Prompt and type the following commands;
cd c:\android (this is your ADB path, c:\android is default)
fastboot flash recovery c:\recovery.img
5. Wait for the process to finish.
6. Turn device off then boot to your custom recovery ADB commands will work here. (usually hold vol- + pwr)
HOW TO BOOT TO RECOVERY
Once in custom recovery, connect the device to the PC.
open CMD and enter the following commands;
cd c:\android (this is your ADB path, c:\android is default)
adb devices
The result should be something like
List of devices attached
051a4dd5 recovery
^^this number will be different for you
if you get a result on ADB devices, then you can use the program
[RECOVERY MODE (SAMSUNG)]USE THE INSTRUCTIONS ON THIS PAGE
Once in custom recovery, connect the device to the PC.
open CMD and enter the following commands;
cd c:\android (this is your ADB path, c:\android is default)
adb devices
The result should be something like
List of devices attached
051a4dd5 recovery
^^this number will be different for you
if you get a result on ADB devices, then you can use the program
HOPEFULLY THIS HELPS. REMEMBER TO CHECK THE FORUM PAGE FOR YOUR DEVICE IF YOU RUN INTO ISSUES. THIS ISN'T ANYTHING THE MEMBERS OF XDA HAVEN'T DONE THOUSANDS OF TIMES OVER.
Don't forget to hit "Thanks"
i'll bump this thread for those who didn't see this amazing tool, this tool is really useful, thank you very much
Hi,
Sturggling to find the .adb file as my phone shows up as a "Portable Device" any ideas?
Cheers
Thank you!
I joined just to say thank you to FuzzyMeep Two. Thanks for an awesome tool! It worked better than advertised!
:good:
Thanks again!
-th3r3isnospoon
Question
Hi! Can I use that to restore data not from sdcard but from internal memory of the device? I was storing photos on device memory on my Asus TF300T and now its bricked. I need to restore these photos, my girlfriend has something like 1000 of them from her trip to Caracas. Its very important for her. I already managed to connect the device through fastboot and I launched anb in cmd. What should I do next? Please help me guys
koperkowy said:
Hi! Can I use that to restore data not from sdcard but from internal memory of the device? I was storing photos on device memory on my Asus TF300T and now its bricked. I need to restore these photos, my girlfriend has something like 1000 of them from her trip to Caracas. Its very important for her. I already managed to connect the device through fastboot and I launched anb in cmd. What should I do next? Please help me guys
Click to expand...
Click to collapse
Yes, when it references SD Card it means the internal "SD" storage built in to the phone, not the removable one. It should work as long as ADB can connect.
Sorry for taking so long to reply, i really hope you got your pictures back.
FuzzyMeep Two said:
Recently my Galaxy s2's screen smashed, and, after replacing it with a GS4, i realized that many of my pictures were stuck on the internal sd card of the GS2. Being unable to turn on mass storage mode, I made a very simple tool that makes using adb pull a simple, painless process, even for the most computer illiterate of android users. Hope this helps if anyone needs it.
P.S. I apologize if i have posted this in the wrong place, if so please let me know.
Click to expand...
Click to collapse
Really great stuff - so simple but so effective. Cheers and thanks.
Error msg
zobes said:
Really great stuff - so simple but so effective. Cheers and thanks.
Click to expand...
Click to collapse
When i run that tool, i get the error mesg: more than one device and emulator,
I dont want to uninstall the emulator coz it was a headache getting it running
How i procede to select the device to be used
alisdairjk said:
When i run that tool, i get the error mesg: more than one device and emulator,
I dont want to uninstall the emulator coz it was a headache getting it running
How i procede to select the device to be used
Click to expand...
Click to collapse
NEW VERSION
Try this, i haven't gotten to test it, so please let me know if it worked for you, I added the option of selecting an emulator or USB device, because of your post. Hopefully it helps.
When I try to run this I also get an error message saying that the adb.exe file cannot be found.
Please can anyone help?
Joeb29 said:
When I try to run this I also get an error message saying that the adb.exe file cannot be found.
Please can anyone help?
Click to expand...
Click to collapse
Have you also installed ADB, as well as this software?
I'm also having an issue - I have installed java, java SDK and ADB, so I can now run the data recovery tool. But when I do I'm getting "error:device not found" - am I missing drivers or something? I couldn't get all the way on the ADB configuration, because part of it required me to do something on the device... anyway, looks like the computer isn't recognising the the phone at the moment.
Any help very gratefully received (phone is Samsung Galaxy S2).
joffmeister said:
Have you also installed ADB, as well as this software?
I'm also having an issue - I have installed java, java SDK and ADB, so I can now run the data recovery tool. But when I do I'm getting "error:device not found" - am I missing drivers or something? I couldn't get all the way on the ADB configuration, because part of it required me to do something on the device... anyway, looks like the computer isn't recognising the the phone at the moment.
Any help very gratefully received (phone is Samsung Galaxy S2).
Click to expand...
Click to collapse
I have the same situation right now. Managed to make your program work then I get the "error:device not found". My phone does show up in the computer folder(albeit not in mass storage mode), but isn't that what this program was made to work around?
My phone is a LG Optimus G with a smashed glass... The LCD still displays fine, but I'm stuck at my swipe lock because the digitizer is dead.
Thank you for your help and your wonderful program.
Thanks for this app. My girlfriend broke her screen and digitizer on her Galaxy S4. She never turned USB Debugging mode and has a lock on her screen. When using your app I get the same error when I use adb by itself which is "error: closed". ADB detects my phone but any command I use in ADB or with your app I get that same error.
Do you know how to fix this? Thanks in advance.
Thanks a lot man.
dude this tool is just amazing and does exactly what it promised. I was spending sleepless nights thinking about how to recover my data from my broken galaxy nexus and now that I have it I can rest easy. Seriously can't thank you enough for this. Just joined xda to thank you buddy.:laugh::fingers-crossed:
Getting an error "The system cannot find the path specified."
I start the recovery tool, set eh adb path successfully, and then I get this error. If I try running the recovery to pull the DCIM library I get this:
"error: device not found"
What can I do?
Thanks!
Either way this is an amazing tool, seeing how it helped some people already. :good:
Hi, Seem to have the same problem as many others, Device not found. I cant change to MTP mode on my LG G2.
I hope someone can find a solution to this problem.
Program seems amazing doh.
Hello,
This is really a great tool ! I was wondering if you could add the possibility to recover the external sd card aswell.
Device not found
Tried to recover a Samsung Galaxy S3 mini with a broken screen
I installed adb and RecoverData, run it and then get a "device not found error"
What can I do?
Amazing app. thank you so much :good:
FuzzyMeep Two said:
**UPDATE**
NEW VERSION
Another user was having issues because he had an emulator installed, so I updated the file to give you the choice between an emulator, or device. I intend to update further to allow you to check for and select an individual device, that will come soon..
----------------------------------------------------------------------------------------------------------------
Recently my Galaxy s2's screen smashed, and, after replacing it with a GS4, i realized that many of my pictures were stuck on the internal sd card of the GS2. Being unable to turn on mass storage mode, I made a very simple tool that makes using adb pull a simple, painless process, even for the most computer illiterate of android users. Hope this helps if anyone needs it.
Don't forget to hit "Thanks"
Click to expand...
Click to collapse
Hi, Thank you very musch, It's so usefull for me.. :angel:
Hello. I am trying to use rootmyvalet.apk to root my phone. I am extremely confused on how to do this.
Here are the steps on how to do it...
The Second way (app way):
1)Push the su binary to /data/local/tmp using adb push su /data/local/tmp
2)Push the roothandler binary to /data/local/tmp using adb push roothandler /data/local/tmp
3)Set the roothandler binary permission using adb shell chmod 0755 /data/local/tmp/roothandler
4)Push the installsu.sh script to /data/local/tmp using adb push installsu.sh /data/local/tmp
5)Set the installsu.sh script the execution permission using adb shell chmod 0755 /data/local/tmp/installsu.sh
6)Install the APK using adb install RootMyValet.apk. If that does not work then type the full path to the apk. E.G. adb install /path/to/apk/app.apk
Start the app on the device, hit the button that says "Push SU Binary"
Wait about a minute
Enjoy your root!
If root fails, try rebooting the device
Which of the steps have you taken so far? Where did you get to in that list?
KodyChristianson said:
Which of the steps have you taken so far? Where did you get to in that list?
Click to expand...
Click to collapse
Sadly enough, I am stuck on step one. I'm probably going to need help on every single step.
Do you have windows drivers working with the device? ie, does it show up when you run:
adb devices
if so, what happens when you run:
adb push su /data/local/tmp
Also,
I've noticed a sticky here which may be of help to you. [GUIDE][30/10/2013]New To Adb And Fastboot Guide by Ricky Divjakovski
KodyChristianson said:
Do you have windows drivers working with the device? ie, does it show up when you run:
adb devices
if so, what happens when you run:
adb push su /data/local/tmp
Also,
I've noticed a sticky here which may be of help to you. [GUIDE][30/10/2013]New To Adb And Fastboot Guide by Ricky Divjakovski
Click to expand...
Click to collapse
1) To install the drivers, I use connect to PC right?
2) To run the command adb push su /data/local/tmp , do I use command prompt?
Use the "package" which is at the start of the guide linked above.
KodyChristianson said:
Use the "package" which is at the start of the guide linked above.
Click to expand...
Click to collapse
I also have a command terminal on my phone, is there any way i can do this from there? Because at the moment, i do not have a usb cable to connect my phone to my computer. I have all of the files i need already on my phone. I just need to move them to the proper directory.
CurtisNHL1 said:
I also have a command terminal on my phone, is there any way i can do this from there? Because at the moment, i do not have a usb cable to connect my phone to my computer. I have all of the files i need already on my phone. I just need to move them to the proper directory.
Click to expand...
Click to collapse
Yeah, i guess you could move the files using a filemanager app, just search it in the playstore.
The problem is, if something goes wrong, for example you get stuck in a boot loop, you will need the computer to resolve the problem.
If that happens, you want to be sure that you have all the drivers installed and properly working.
Imagine having your phone not working, you can´t get the computer to talk to the phone, and you don´t know whether the problem is adb, your drivers, or your phone.
If you want to follow those instructions, i think you should get a cable and follow them exactly.
Why do you want to use that rootkit, anyway? what phone do you have?
KodyChristianson said:
Yeah, i guess you could move the files using a filemanager app, just search it in the playstore.
The problem is, if something goes wrong, for example you get stuck in a boot loop, you will need the computer to resolve the problem.
If that happens, you want to be sure that you have all the drivers installed and properly working.
Imagine having your phone not working, you can´t get the computer to talk to the phone, and you don´t know whether the problem is adb, your drivers, or your phone.
If you want to follow those instructions, i think you should get a cable and follow them exactly.
Why do you want to use that rootkit, anyway? what phone do you have?
Click to expand...
Click to collapse
I have the zte valet z665c tracfone. This is the last option i have to root my phone. I've tried everything i can.
CurtisNHL1 said:
I have the zte valet z665c tracfone. This is the last option i have to root my phone. I've tried everything i can.
Click to expand...
Click to collapse
The problem is, if something goes wrong, for example you get stuck in a boot loop, you will need the computer to resolve the problem.
If that happens, you want to be sure that you have all the drivers installed and properly working.
Imagine having your phone not working, you can´t get the computer to talk to the phone, and you don´t know whether the problem is adb, your drivers, or your phone.
KodyChristianson said:
The problem is, if something goes wrong, for example you get stuck in a boot loop, you will need the computer to resolve the problem.
If that happens, you want to be sure that you have all the drivers installed and properly working.
Imagine having your phone not working, you can´t get the computer to talk to the phone, and you don´t know whether the problem is adb, your drivers, or your phone.
Click to expand...
Click to collapse
Believe it or not, the information you told me here just saved my ass. I recently bought a phone that could be rooted and got it stuck in a boot loop. Thank you so much!