Database Info

[Let's Get] Root Achieved for Le Pan II (TC979)

JCASE HAS DONE IT GUYS:
http://www.forum.lepanlife.com/showthread.php?tid=322

No luck,
I followed the steps, but when I connected the Lepan2 to the computer, it started to find devices, and finally it got this as I show in this graphic:
imageshack.us/f/838/anydatahsusbdevice.jpg (I cannot post links so I place it like that)
So I tried the 'update driver software" for the one with the yellow question mark under "Other Devices" called ANY_DATA HSUSB Device" and none i386 or amd64 work with that device. I don't know why it shows 2 devices, the other as you can see is under "Portable Devices" and it was recognized by Windows 7 64-bit witch is the OS i'm running. Also if I right-click on that "LePanII" device and select 'update driver software' and point to the unzipped files that you posted above, it says that "The device LepanII already has the best windows drivers"
So when I run SuperOneclick, the one you also posted above, the application became "unresponsive' after clicking on "Root"
I checked on windows task manager and there are 2 adb.exe processes running, and the only way I can terminate the Superoneclick app is by terminating those 2 adb.exe processes. I have tried several times and same result, it becomes unresponsive after starting adb server on port 5037

rocketero said:
No luck,
I followed the steps, but when I connected the Lepan2 to the computer, it started to find devices, and finally it got this as I show in this graphic:
imageshack.us/f/838/anydatahsusbdevice.jpg (I cannot post links so I place it like that)
So I tried the 'update driver software" for the one with the yellow question mark under "Other Devices" called ANY_DATA HSUSB Device" and none i386 or amd64 work with that device. I don't know why it shows 2 devices, the other as you can see is under "Portable Devices" and it was recognized by Windows 7 64-bit witch is the OS i'm running. Also if I right-click on that "LePanII" device and select 'update driver software' and point to the unzipped files that you posted above, it says that "The device LepanII already has the best windows drivers"
So when I run SuperOneclick, the one you also posted above, the application became "unresponsive' after clicking on "Root"
I checked on windows task manager and there are 2 adb.exe processes running, and the only way I can terminate the Superoneclick app is by terminating those 2 adb.exe processes. I have tried several times and same result, it becomes unresponsive after starting adb server on port 5037
Click to expand...
Click to collapse
Yep, Bear was having the same issues when he tried. Adam and I have fixed the drivers partially (they are re-uploaded, so re-download them). When you use the re-up'ped drivers and update the AnyData HSUSB Device it will work now and change it to an Android ADB Composite Interface Device.
However, getting ADB working is another story. Adam and myself have been working on Bear's computer remotely and we've done what we can do from there. When we both get our Le Pan II's this week (Tues/Wednesday, respectively), we are going to push forward full speed ahead in Linux to attempt to get ADB to recognize the device.
It's started to look like the drivers that leaked are not for the LP2, which is disappointing to say the least. In order to root it without the drivers, it's gonna take time and patience and we're going to need to find an unpatched exploit in the HC OS by modifying Gingerbreak or Zerg.
I'll keep you updated as it progresses.

Hey,
Could any of you owners of the Le Pan II (TC979) do a dump of the ROM?
(including the drivers, kernel, etc)
It would be GREATLY beneficial to the XDA / RootzWiki HP TouchPad community since it would assist with the development of Ice Cream Sandwich, given how similar, if not identical the hardware on the Le Pan II is to the HP TouchPad.
Thanks.

PresidentMcCain said:
Hey,
Could any of you owners of the Le Pan II (TC979) do a dump of the ROM?
(including the drivers, kernel, etc)
It would be GREATLY beneficial to the XDA / RootzWiki HP TouchPad community since it would assist with the development of Ice Cream Sandwich, given how similar, if not identical the hardware on the Le Pan II is to the HP TouchPad.
Thanks.
Click to expand...
Click to collapse
As soon as we get this thing rooted, I'd be more than happy too
We have no firmware files, just OTA updates - they do not post firmwares, source code, adb drivers or anything on their site. But we'll get it and when we do, I'll get you that info.

dbaybay said:
As soon as we get this thing rooted, I'd be more than happy too
We have no firmware files, just OTA updates - they do not post firmwares, source code, adb drivers or anything on their site. But we'll get it and when we do, I'll get you that info.
Click to expand...
Click to collapse
Maybe this will help you with ADB drivers:
http://rootzwiki.com/topic/15624-how-tocm9-adb-interface-on-usb/
---------- Post added 24th January 2012 at 12:15 AM ---------- Previous post was 23rd January 2012 at 11:50 PM ----------
If you can at least use Root Explorer to zip up some of it, it'd be helpful
(I believe the drivers are .so files in the lib folder under /)

dbaybay said:
Yep, Bear was having the same issues when he tried. Adam and I have fixed the drivers partially (they are re-uploaded, so re-download them). When you use the re-up'ped drivers and update the AnyData HSUSB Device it will work now and change it to an Android ADB Composite Interface Device.
However, getting ADB working is another story. Adam and myself have been working on Bear's computer remotely and we've done what we can do from there. When we both get our Le Pan II's this week (Tues/Wednesday, respectively), we are going to push forward full speed ahead in Linux to attempt to get ADB to recognize the device.
It's started to look like the drivers that leaked are not for the LP2, which is disappointing to say the least. In order to root it without the drivers, it's gonna take time and patience and we're going to need to find an unpatched exploit in the HC OS by modifying Gingerbreak or Zerg.
I'll keep you updated as it progresses.
Click to expand...
Click to collapse
I just downloaded again the link for "Drivers" and I connected the Lepan2 again to the computer and the same problem as before.
Then I checked the "File hashes" for the files "WdfCoInstaller01009.dll" and the other 2 inside the folder "amd64" and the cr32/md5/sha-1 are identical for the ones I had downloaded before and this ones. So where are the new ones you said you re-uploaded ?
About the ROM, I am also interested on obtaining the "original" ROM that came with the LepanII, as I updated the system with a still-in-development that Lepan tech support had uploaded to the server without even first testing it, and now I can not revert back to the original because they have not provided to me in a support-ticket I opened at their website. I don't know much about ROM extracting or management but I could learn a thing or two about it.

WHOOOOOOOOOOOOOOOOOOOO!!!!
I got ADB working on the Le Pan 2!!! Screw Le Pan and their locked down drivers!
I can't get root access yet, but I got a sysdump and am combing through it. Recovery doesn't show the device being plugged in and I can't figure out how to get into fastboot as of yet, but progress is being MADE!

There is not rush, in the mean time I opened a ticket at lepan.supportsync.com to see if they supply me with this driver. who knows I may get lucky.

rocketero said:
There is not rush, in the mean time I opened a ticket at lepan.supportsync.com to see if they supply me with this driver. who knows I may get lucky.
Click to expand...
Click to collapse
Been there, done that. Hopefully you'll have better luck, but their standard reply is to email two people from HQ if you are a developer, which I've also been there and done that. They don't reply. I'm fairly positive that we are on our own considering they didn't release the ADB drivers for the LP1 or LP2 as of yet and no source code for either, either. They are GPL-violators to the MAX. *puke*
We'll get it tho.

dbaybay said:
WHOOOOOOOOOOOOOOOOOOOO!!!!
I got ADB working on the Le Pan 2!!! Screw Le Pan and their locked down drivers!
I can't get root access yet, but I got a sysdump and am combing through it. Recovery doesn't show the device being plugged in and I can't figure out how to get into fastboot as of yet, but progress is being MADE!
Click to expand...
Click to collapse
Can you please upload somewhere zip with content of /system/lib/? One of the major problems community have with porting of ICS to any Qualcomm platform is absense of userspace video drivers (and inability to run hw-acceleration). TC979 seems to have hw-accel enabled in Honeycomb, which is quite close to ICS in this area.

ghuron said:
Can you please upload somewhere zip with content of /system/lib/? One of the major problems community have with porting of ICS to any Qualcomm platform is absense of userspace video drivers (and inability to run hw-acceleration). TC979 seems to have hw-accel enabled in Honeycomb, which is quite close to ICS in this area.
Click to expand...
Click to collapse
As soon as I can get ADB working in recovery or fastboot and have root access, I will be glad to, as I already said before. ADB is working when the device is running normally, but I do not have SU privileges. I can see the list of files, but can't copy, push, pull, or anything as of right now. My project for today is to get ADB working in fastboot so I can get root permissions.

dbaybay said:
As soon as I can get ADB working in recovery or fastboot and have root access, I will be glad to, as I already said before. ADB is working when the device is running normally, but I do not have SU privileges. I can see the list of files, but can't copy, push, pull, or anything as of right now. My project for today is to get ADB working in fastboot so I can get root permissions.
Click to expand...
Click to collapse
I thought adb pull /system/lib/ does not require root

ghuron said:
I thought adb pull /system/lib/ does not require root
Click to expand...
Click to collapse
Nor did I, but I'm getting permission denied for about everything except adb reboot [recovery / bootloader] or 'ls'. SU, Pull, Push, Root, Remount, etc. etc. etc. are giving me "permission denied" or "can't in manufactor mode" errors.
I'm working on getting it to work in Fastboot, but ADB just won't recognize the device in Fastboot no matter what I do. I'm at a loss right now, so any suggestions would be helpful. I'm gonna keep trying different methods to get ADB to work with root permissions.
Code:
$ pull /system/lib c:\users\admin\desktop
pull /system/lib c:\users\admin\desktop
pull: permission denied
$
A list of the contents is the best I can get for you atm - http://pastebin.com/ZqvXqE0Q

Those files are exactly what the HP Touch pad needs
---------- Post added at 08:03 PM ---------- Previous post was at 08:01 PM ----------
are you sure you can't install superuser ?

PresidentMcCain said:
Those files are exactly what the HP Touch pad needs
---------- Post added at 08:03 PM ---------- Previous post was at 08:01 PM ----------
are you sure you can't install superuser ?
Click to expand...
Click to collapse
110% positive.
I have no permissions to do anything except CD into folders and get a list, or reboot into recovery or bootloader. In bootloader ADB and fastboot do not recognize the device and the modified drivers do not work. We are working on it, but no such luck as of yet. As soon as I can gain SU permissions in ADB, I'll get you the files, don't worry.

dbaybay said:
110% positive.
I have no permissions to do anything except CD into folders and get a list, or reboot into recovery or bootloader. In bootloader ADB and fastboot do not recognize the device and the modified drivers do not work. We are working on it, but no such luck as of yet. As soon as I can gain SU permissions in ADB, I'll get you the files, don't worry.
Click to expand...
Click to collapse
just a simple question: how do you get out of bootloader mode? After I did "adb reboot bootloader", I got to a black screen with the text "Fastboot Mode" and then nothing works, not even the power button. Can't access it via USB either. Guess I can wait till the battery runs down, but there should be a simpler way...
Edit: never mind, the reset button worked

anonguy2 said:
just a simple question: how do you get out of bootloader mode? After I did "adb reboot bootloader", I got to a black screen with the text "Fastboot Mode" and then nothing works, not even the power button. Can't access it via USB either. Guess I can wait till the battery runs down, but there should be a simpler way...
Click to expand...
Click to collapse
Try holding power button + home button at same time for 10 seconds.

Bootloader/fastboot are the same thing from my understanding. When I use adb reboot bootloader, it reboots to my fastboot screen. I use the reset button, as you figured out to get out of it.
I need to get adb or fastboot.exe [platform tools] working in fastboot mode and I should have root access but no such luck.
Any Le Pan II users who managed to get the v116 update - did you get an update.zip placed on your SD Card that you can share? If I can get an properly signed update.zip with the stock ROM inside, I can most likely modify it for with SU access built in.

this may be a stupid question, does this app http://www.androidapps.com/finance/apps/299480-root-explorer-file-manager-speed-software give you root access or do you need to have root permission in order to use that app.

Broken screen, need to retrieve files off phone! help please

My screen first cracked and then the LCD completely went now... I have files I need to retrieve off the phone. It is rooted and running some ICS build... I believe the phone is in USB debugging mode, the screen still 'works' I can unlock the phone but nothing is displayed on the screen. Possibly someone could help me out with the adb process for pulling the contents off the /sd
Any help will be GREATLY appreciated, thank you for your time.

ur usb mass storage should still work. can u just plug ur phone to a usb port and get things off the phone ?

As previously stated. I believe the phone was in USB debugging mode. And now the screen is completely black... impossible to navigate to where i need to be.

You'll need adb setup on your computer, and you'll need to cd your way into the folder with adb.exe. Forgive me for hotlinking, but this will make it easier: Download this file, courtesy of NexusSHacks.com (I believe it is Zedomax around here). I would advise to unzip the contents in this file to your C:\Nexus directory, so that adb.exe is at C:\Nexus\adb.exe.
Now, plug in your phone. Open your start menu and search for "cmd" and open up Command Prompt. This is the basic Windows CLI (Command Line Interface).
First, you'll need to open the directory of the Nexus folder you created earlier. To do this, type in the command prompt:
Code:
cd C:\Nexus
Now, you want to make sure adb sees your phone:
Code:
adb devices
The adb service should start and if it sees your phone it will pop up a serial number. If there is no serial number, you can't use adb while inside android and you'll need to tick the option or find an alternative way. Assuming it finds your device, you are good to go.
In order to copy the /sdcard folder of your Nexus S, you will use the pull command. We will throw all of the files into C:\Nexus\sdcard, for reference. So in the command prompt, type:
Code:
adb pull /sdcard .\sdcard
It looks a little confusing but don't stress. Just make sure you type it in exactly (dot, correct slash, etc). This will take a little while since it might transfer up to ~15GB worth. You'll see a new line with "C:\Nexus>" with a flashing cursor when it is done. Then you can view all the contents of your sdcard at C:\Nexus\sdcard and do with them as you please.
Also note, for this you'll need up to ~15GB of free space on your C:\ partition, make sure you have this before you start. Good luck

old post I know, but I just dropped my Samsung Captivate (rooted with debugging on) and internal screen cracked (gorilla glass is perfectly fine!), so I am in the same boat. After DAYS... actually DAYS of trying everything from every forum I FOUND A FIX!!!
Now admittedly, I am unsure which of these two (or both) fixed the issue, but here is what I did:
via Google Play's online "shop", I installed "Auto Mount Your SD Card" by JRTStudio (admittingly, unsure if this did anything as I cannot verify if it installed or anything via the phone)
https://play.google.com/store/apps/...wsMSwxLDEsImNvbS5qcnRzdHVkaW8uYXV0b21vdW50Il0.
then I DL'ed MoboRobo and after a few frustrated phone reboots, usb cable connections and much cursing IT CONNECTED!
http://www.moborobo.com/
I am currently DLing all my files from my broken phone!
I had to pass this along as I said... NOBODY seems to know about this as it has taken me DAYS to do this! Not even ATT (Current carrier) nor Spring (whom I am switching to in a month or so) could help me!

You save my life with that "moborobo". Thank you very much.

Glad I could help!!!

Thanks went to both of u, quit important piece of knowledge.
One question; r u downloading "moborobo" on ur Android, on your pc or on both of them?

just on PC, not needed on the phone unless you want to go via WiFi

Harbb said:
If there is no serial number, you can't use adb while inside android and you'll need to tick the option or find an alternative way.
Click to expand...
Click to collapse
What do you mean by this?
My adb service doesn't detect my phone, I used Droidzone's tutorial. I believe usb debugging needs to be on for adb to work, which in my case is useless cause my screen is broken so can't turn on usb debugging.
This is what happens:
---------------------------
C:\>adb devices
List of devices attached
C:\>
---------------------------
---------- Post added at 11:31 PM ---------- Previous post was at 11:23 PM ----------
^when I say broken, I mean the whole screen is distorted, I cannot see anything

droidoidoid said:
What do you mean by this?
My adb service doesn't detect my phone, I used Droidzone's tutorial. I believe usb debugging needs to be on for adb to work, which in my case is useless cause my screen is broken so can't turn on usb debugging.
This is what happens:
---------------------------
C:\>adb devices
List of devices attached
C:\>
---------------------------
---------- Post added at 11:31 PM ---------- Previous post was at 11:23 PM ----------
^when I say broken, I mean the whole screen is distorted, I cannot see anything
Click to expand...
Click to collapse
Reboot to recovery. Bam, working ADB. You can navigate there pretty easily. Pull battery, then re-insert. VOL + & PWR, two click on VOL -, PWR button once. You're in recovery now.

QtADB also can be used is this case
http://qtadb.wordpress.com/download/

paskalion said:
QtADB also can be used is this case
http://qtadb.wordpress.com/download/
Click to expand...
Click to collapse
No go on this either.
Downloaded QtADB, ran the .exe
Pointed to the folder with the aapt and adb binaries, program opened up
Phone's connected and on (I can hear texts coming through), hit refresh a few times, still not detecting

polobunny said:
Reboot to recovery. Bam, working ADB. You can navigate there pretty easily. Pull battery, then re-insert. VOL + & PWR, two click on VOL -, PWR button once. You're in recovery now.
Click to expand...
Click to collapse
That's a little tough. I'm using a Galaxy S so I'm following instructions for that, but it's hard to know if I'm in recovery mode or not. Since adb doesn't detect the device, it's hard to know whether the phone went into recovery mode, or whether adb is setup correctly. It would be handy for a voice sample to play "recovery mode" once the phone boots into it.

droidoidoid said:
That's a little tough. I'm using a Galaxy S so I'm following instructions for that, but it's hard to know if I'm in recovery mode or not. Since adb doesn't detect the device, it's hard to know whether the phone went into recovery mode, or whether adb is setup correctly. It would be handy for a voice sample to play "recovery mode" once the phone boots into it.
Click to expand...
Click to collapse
You're in the wrong forum, then.
And whether or not adb is installed properly, you would know in your device manager under Windows. Appears as a device.

polobunny said:
You're in the wrong forum, then.
And whether or not adb is installed properly, you would know in your device manager under Windows. Appears as a device.
Click to expand...
Click to collapse
Ok... Galaxy S i9000 stuff goes in the Galaxy S i9000 forum.... that's probably why my other post got deleted! :laugh:
As for adb... it appears as a process in task manager, so it's running - I know that much. It's not appearing as a device in device manager (why would it if it's a process? or are you referring to my phone appearing as a device?)
Only areas I can think of that aren't correct are the environment variable and the way I'm doing recovery mode. Since I can't see the screen, I don't know which one is causing the issue! :crying:

Samsung broken??
Contact this guy in Paris , he's very good and friendly!! he repairs my blue Galaxy S3 in front of me
Tel: 0950 850 500 Direct Technique
repare-galaxy com
don't hesitate to call them because i know their skills and it's very good!!
tell them that u call from Mike ciao guys!!

Problem!
Harbb said:
Code:
adb pull /sdcard .\sdcard
It looks a little confusing but don't stress. Just make sure you type it in exactly (dot, correct slash, etc). This will take a little while since it might transfer up to ~15GB worth. You'll see a new line with "C:\Nexus>" with a flashing cursor when it is done. Then you can view all the contents of your sdcard at C:\Nexus\sdcard and do with them as you please.
Click to expand...
Click to collapse
Hey, I got to this problem and I got stuck. I also have a Nexus S with a cracked screen. When I put in the final phrase into the command window it just told me that 0 filles were pulled! Why didnt it pull my files?
What I am trying to do is get all of my pictures and others off the phone.
Please help!

SkullMblem said:
Hey, I got to this problem and I got stuck. I also have a Nexus S with a cracked screen. When I put in the final phrase into the command window it just told me that 0 filles were pulled! Why didnt it pull my files?
What I am trying to do is get all of my pictures and others off the phone.
Please help!
Click to expand...
Click to collapse
This happened to me as well. You have to make sure that your phone has its sdcard folder mounted. Type "adb shell" to get access to the phones command terminal. Then type in "mount /sdcard" I think, or maybe it was "mount sdcard". Either way will probably work so long as you are in the root directory of the phone. You can navigate around in the phone just like a normal linux terminal. "ls" shows list of files and folders in the current directory, "cd foldername" moves into a folder, "cd ../" moves back, "cd /" goes to root directory, etc. Anyhow, once you have mounted the sdcard, you can type exit to leave the shell terminal, and then issue the command "adb pull /sdcard .\sdcard" to get the files. I had a custom rom image in the root of my sdcard so the move took quite a while ~15 minutes. On success of the pull command you should see a bunch of statuses like:
pull: sdcard/data/somefile -> .\sdcard/data/somefile
pull: sdcard/DCIM/somefile -> .\sdcard/DCIM/somefile
.
.
.
XXXX files pulled. 0 files skipped
(Some more transmission stats)
Hope it works out for who ever reads this.
Side note:
On my phone the screen was smashed. I replaced it and it still would not turn on, but it was still running. I had a rooted phone with CM10 rom on it. ADB debugging was one (if its off your pretty much screwed). I started up the phone, and plugged in the usb cable. I tried to use both adb and fastboot from windows terminal. "fastboot devices" would echo back nothing, and "adb devices" would echo back my phone's device number but state it was offline. So to get it online I did the following:
1.) pull batttery.
2.) boot into bootloader (hold power and volume up) the phone shouldn't vibrate if it does you have just normally powered it on. It took me quite a few times to get this to go into the bootloader. To make sure you get in the bootloader type "fastboot devices". If nothing comes up you not there.
3.) once verified you are in the bootloader you need to go into recover mode. Press volume down twice and then hit power (this would normally move the cursor on your phone down to recovery and select it if you could see whats happening on the screen).
4.) wait a bit for it to load into recovery, try typing "adb devices". You should eventually see you device show up as online. At this point you may enter the shell as above, mount the sdcard, exit the shell and pull your files.
Windows instuctions:
Prerequisites are installing adb.exe and fastboot.exe via installing the Android SDK on your computer. They will show up in the platform-tools folder of the install location. Add that folder to your environmental path variable so you can run the ADB and fastboot commands from any folder. Install the ADB driver for your phone (allows you to issue adb commands to your phone when USB is plugged in) by plugging in your phone and going to device manager, find your phone which should show up as a exclamation point, right click update driver, click "browse...", then "let me pick...", click top entry something like "show all", and then let the list populate. On the left look for "samsung" and then select the first one that is something like "samsung adb driver interface". And you should be good to go.
Sorry for the long winded post, I just like to try and explain as much as possible.

Successfully Recoverd data
Well My Samsung S2's Screen broke down few days ago.. Now i have retrieved the data by following the 2nd method in the following article..! I Hope this works for you aswell...
I can not Post the link here.. PM me if you want the link...!

ATTN: Backup your boot0 block today

ATTENTION: PUBLIC SERVICE ANNOUNCEMENT
It has come to my attention that under certain circumstances when the Kindle HD's get stuck in a bootloader bootloop the information on the "boot0" block of the internal storage can be ERASED and RESET.
This partition is special and contains ALL of your device's hardware specific information:
- Wifi MAC address + Encoded Secret for registering w/ Amazon services
- BT MAC address
- Serial #
etc
FOR BACKING UP THIS PARTITION:
Code:
adb shell su -c "dd if=/dev/block/mmcblk0boot0 of=/sdcard/boot0block.img"
adb pull /sdcard/boot0block.img
Place the "boot0block.img" file with the other files that you backed up in the original instructions for safe keeping.
FOR RESTORING THIS PARTITION:
(do not do this unless you are absolutely SURE that your boot0 block got wiped out -- hopefully you never need to)
This is done via adb from your PC while the device is in TWRP recovery or in the Android OS (not fastboot):
Code:
cd <your safekeeping files>
adb push boot0block /sdcard/boot0block.img
adb shell "echo 0 > /sys/block/mmcblk0boot0/force_ro; dd if=/sdcard/boot0block.img of=/dev/block/mmcblk0boot0;"
THIS FILE IS UNIQUE TO YOUR DEVICE AND CANNOT BE REPLACED OR REBUILT FROM ANOTHER DEVICE. DO NOT SHARE IT WITH ANYONE AS IT CONTAINS INFORMATION ABOUT YOUR DEVICE USED BY AMAZON DURING REGISTRATION.

very interesting Hashcode,thanks for the information :good:

Odd, I can't seem to find the file after I pulled it with ADB.
EDIT: I didn't even assign the command an output location to begin with. LOL.

Thanks for the info.
How can I access KFHD via ADB if CM10.1 installed.
I can't see my device in device manager only as a media storage or sth like that.
Should I remove KFHD adb driver and install the google driver?
Or just using the hidden trick in cm10.1?
"Enable Developer options in your phone (Settings > About phone and tap Build Number until you are a developer (about 7 times)
Set root access for APPS and ADB in: Settings > Developer Options > Root Access
Enable Android debugging at the same page (Developer Options). Enable ADB over network if you need.
Check if your Settings > Security > Unknown Sources is checked. you will need it to install over ADB."
Yeah...it helped

esox_hu said:
Thanks for the info.
How can I access KFHD via ADB if CM10.1 installed.
I can't see my device in device manager only as a media storage or sth like that.
Should I remove KFHD adb driver and install the google driver?
Or just using the hidden trick in cm10.1?
"Enable Developer options in your phone (Settings > About phone and tap Build Number until you are a developer (about 7 times)
Set root access for APPS and ADB in: Settings > Developer Options > Root Access
Enable Android debugging at the same page (Developer Options). Enable ADB over network if you need.
Check if your Settings > Security > Unknown Sources is checked. you will need it to install over ADB."
Yeah...it helped
Click to expand...
Click to collapse
Just turn on ADB debugging on the tablet, and plug it into the computer. On the computer, open command prompt, use the command "adb devices" to see if your ADB is working.
Other than that, I don't know what happened in your post.

Ok i really can't figure this one out, I used adb many times while testing KFFAide tool so I am 100% sure my adb drivers are installed correctly, But since i switched to cm10.1 (Thanks hashcode) ADB cannot recognize my device anymore, I have enabled ADB on my KFHD and when i connect it to my pc a small notification appears "Android debugging enabled" but when i use "adb devices" command nothing shows up!
Can anyone help me with this i'm completely lost here!

AmrBanawan said:
Ok i really can't figure this one out, I used adb many times while testing KFFAide tool so I am 100% sure my adb drivers are installed correctly, But since i switched to cm10.1 (Thanks hashcode) ADB cannot recognize my device anymore, I have enabled ADB on my KFHD and when i connect it to my pc a small notification appears "Android debugging enabled" but when i use "adb devices" command nothing shows up!
Can anyone help me with this i'm completely lost here!
Click to expand...
Click to collapse
Leave the device plugged in, go to Developer Setting and uncheck ADB debugging, then check it again. You should see a prompt, select OK for both.

seokhun said:
Leave the device plugged in, go to Developer Setting and uncheck ADB debugging, then check it again. You should see a prompt, select OK for both.
Click to expand...
Click to collapse
Ok thanks i tried but to no avail

AmrBanawan said:
Ok thanks i tried but to no avail
Click to expand...
Click to collapse
Yeah I actually have the same problem too now

Thanks for the heads up hash, got it on a usb stick now
---------- Post added at 11:41 PM ---------- Previous post was at 11:39 PM ----------
Protomartyr said:
Yeah I actually have the same problem too now
Click to expand...
Click to collapse
I had to manually check android debugging and usb debugging notify and it worked just fine.... make sure adb over network is not checked

Protomartyr said:
Yeah I actually have the same problem too now
Click to expand...
Click to collapse
AmrBanawan said:
Ok thanks i tried but to no avail
Click to expand...
Click to collapse
Why don't you guys try this, go into CMD while connected with the device (ADB debugging on), and type "adb devices" to start the daemon, then try the commands. Other than that, I don't know what else to do.

seokhun said:
Why don't you guys try this, go into CMD while connected with the device (ADB debugging on), and type "adb devices" to start the daemon, then try the commands. Other than that, I don't know what else to do.
Click to expand...
Click to collapse
Nope. Just get "List of Devices Attached" but no serial number. Checked device manager and it's showing up as a portable device. Probably will reinstall them and see if that solves it.
On a side note:
if we ran these commands in terminal emulator on the device, would that be sufficient?

Protomartyr said:
Nope. Just get "List of Devices Attached" but no serial number. Checked device manager and it's showing up as a portable device. Probably will reinstall them and see if that solves it.
On a side note:
if we ran these commands in terminal emulator on the device, would that be sufficient?
Click to expand...
Click to collapse
Yes
run the first command then pull it manually
But we need to know what's going on, i will need adb sometime soon when prokennexusa releases the next version of KFFAide

AmrBanawan said:
Yes
run the first command then pull it manually
But we need to know what's going on, i will need adb sometime soon when prokennexusa releases the next version of KFFAide
Click to expand...
Click to collapse
you can always open up your device manager and manually apply the adb drivers to your kindle

How do we know the boot0 partition is erased?
Sent from a Kindle Fire HD running CM10.1 using Tapatalk 2

had same probs on cm10 getting the files no matter what i tried.in windows 7 and xp it wouldnt install normal driver so i could see kindle as a drive so flashed an amazon zip and pc recognizes it without any problems and now have the files needed

dugoy13 said:
How do we know the boot0 partition is erased?
Sent from a Kindle Fire HD running CM10.1 using Tapatalk 2
Click to expand...
Click to collapse
Normally you would notice WiFi doesn't work under any circumstances same for BT. And when on Amazon's software it won't let you register.
Sent from my Amazon Kindle Fire HD using Tapatalk 2

I can't get ADB to find it either, think i'll revert back to stock to get the file then go back to CM - I notice though on CM turning USB Debugging on doesn't change anything in device manager, it still stays connected as a media device or camera, depending on which you have ticked in storage setting *shrugs*
Thank you Hashcode

PaulJCW said:
I can't get ADB to find it either, think i'll revert back to stock to get the file then go back to CM - I notice though on CM turning USB Debugging on doesn't change anything in device manager, it still stays connected as a media device or camera, depending on which you have ticked in storage setting *shrugs*
Thank you Hashcode
Click to expand...
Click to collapse
No don't, just type the command hashcode provided in terminal emulator and you'll find the backup in your sdcard, just copy it to your pc like normal!

You can do it from the terminal without typing ADB. that may be why people are confused. Start with hashcodes command but start with "su -c" in the terminal.
Sent from my Nexus S 4G using xda app-developers app

[TOOL] ADB Data Recovery (recover data from a phone with broken screen)

**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 RECOVERY​first, 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 RECOVERY​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
SCREEN BROKEN TOUCH BROKEN WITH CUSTOM RECOVERY​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
SCREEN BROKEN TOUCH BROKEN NO CUSTOM RECOVERY​now 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:

Kindle Fire HD 1st Generation (2012) v7.5.1 Root/Re-Root [Confirmed]

Hello guys,
Sorry if this is redundant but I did search before making this post so feel free to edit or remove moderators.
I had root prior to last update 7.5.1. Lost root and I could not re-root using Qemu/Root Many/KFAide and I spent a lot of time playing with the CMD prompts. So I was curious and tried Root Master 1.3.6. Sure enough it worked for me in 1 MINUTE!!! So I am only posting this in case there are others out there like me. I found this post to be helpful since it had a lot of pics so I will not put up my own pictures:
http://forum.xda-developers.com/showthread.php?t=2783447
Otherwise, the my cliff notes of the install is:
Copy/transfer Root_Master_1-3-6.apk to any folder on Kindle via usb cable (assuming you installed drivers already, if not search forum)
Install/Open
Select Mulai Root
Popup with two choices will appear Root/Batal (cancel): Select Root
Another popup will show strange characters/Batal: Select Batal this time
You're Done!
Last step: Clean up by going to apps and press/hold root master to remove from device (it's no longer needed since you are rooted and I read it may contain some kind of script that sends your device information to someone bored, however the root itself is safe - I hope!)
Also, four common terms you'll see when you open apps that asks for root permission not covered in the thread above:
jangan tanya lagi - do not ask again
Perizinan - Allow
Tolak - reject
di izinkan xxxxxxxxxxxx dapatkan izin - authorized xxxxxxxxxxxx to get "root" permission (xxx is the name of the app you are opening)
I will post up my version of the file I've used but I believe the file in the thread above is also identical.
Thanks to all and this forum,
Nano out
P.S. Another solution working to removing the Special Offers Lockscreen Ads is to freeze it with Titanium Backup ($$) or ROM Toolbox Lite (free) both can be found on the Google Play Store:
For ROM Toolbox Lite: Open after install, select app manager, click on Kindle Special Offers, select Freeze, then Yes. I'm unsure what the advanced freeze is but my ads are gone and still gone after reboot so I'm a happy camper.

i also have 7.5.1 but stock. never been rooted. i downloaded this APK and followed the instructions... but it didn't successfully root it for me. so... now there's like a Perizinan rumah tangga app that i can't get rid in the app store.... so i'm factory resetting everything again hahaha i think it's malware
---------- Post added at 12:29 AM ---------- Previous post was at 12:17 AM ----------
this is great, this malware has survived a factory reset.... thanks a lot

JediFonger said:
i also have 7.5.1 but stock. never been rooted. i downloaded this APK and followed the instructions... but it didn't successfully root it for me. so... now there's like a Perizinan rumah tangga app that i can't get rid in the app store.... so i'm factory resetting everything again hahaha i think it's malware
---------- Post added at 12:29 AM ---------- Previous post was at 12:17 AM ----------
this is great, this malware has survived a factory reset.... thanks a lot
Click to expand...
Click to collapse
follow the unrooting part mentioned in this guide:
http://forum.xda-developers.com/showthread.php?t=2783447
this is the best method of rooting on 7.5.1:
http://akauntu.blogspot.com/2014/12/install-custom-rom-on-amazon-kindle_26.html

so i did follow both, the first link didn't do anything but load an app and hten it loaded an app that wouldn't go away even after factory reset. great.
secondly, i used the 'best method of rooting on 7.5.1' and the only difference i saw was using non-admin to run commandlines so that made some differences. but i'm not i still have root. the major issue is i can't reboot into fastboot... so that defeats the purpose since i can't downgrade to 7.2.3, which is needed to proceed.
any other tips?
according to a few root checker apps. i have root... but i just can't reboot into fastboot
lolwatpear said:
follow the unrooting part mentioned in this guide:
http://forum.xda-developers.com/showthread.php?t=2783447
this is the best method of rooting on 7.5.1:
http://akauntu.blogspot.com/2014/12/install-custom-rom-on-amazon-kindle_26.html
Click to expand...
Click to collapse

JediFonger said:
so i did follow both, the first link didn't do anything but load an app and hten it loaded an app that wouldn't go away even after factory reset. great.
secondly, i used the 'best method of rooting on 7.5.1' and the only difference i saw was using non-admin to run commandlines so that made some differences. but i'm not i still have root. the major issue is i can't reboot into fastboot... so that defeats the purpose since i can't downgrade to 7.2.3, which is needed to proceed.
any other tips?
according to a few root checker apps. i have root... but i just can't reboot into fastboot
Click to expand...
Click to collapse
The first link I posted was to remove that app installed from root master where is says unrooting and "1.Open "Perizinan rumah tangga."
As for the second link, you should follow the youtube videos as well as some of the info isn't mentioned in the text. You need to make sure the kindle fire drivers are installed properly when using adb and fastboot. One time they were fine for me for adb, but when I went into fastboot, they weren't properly installed. So, I uninstalled them in the device manager and replugged in the kindle and they worked properly.
But since root checker apps are saying you have root, adb shell su -c "reboot bootloader" should get you into fastboot mode. Then you run that other tool to downgrade.

when i run that command i get connection io timer error and thats it. it will only reboot into recovery but never fastboot. i'm tryjng to make or acquire a fastboot cable. the original kindle usb cable is a fastboot cable right? i have to find it not sure where i stored it
---------- Post added at 09:04 PM ---------- Previous post was at 09:02 PM ----------
i dont have any other issues adb driverd and cmd run fine i just cannot get into fastboot no matter what i have used

JediFonger said:
when i run that command i get connection io timer error and thats it. it will only reboot into recovery but never fastboot. i'm tryjng to make or acquire a fastboot cable. the original kindle usb cable is a fastboot cable right? i have to find it not sure where i stored it
---------- Post added at 09:04 PM ---------- Previous post was at 09:02 PM ----------
i dont have any other issues adb driverd and cmd run fine i just cannot get into fastboot no matter what i have used
Click to expand...
Click to collapse
you don't need a fastboot cable for that method. I don't have one myself and have no issue.
when you do "adb devices", does a serial come up?

yes i can run adb devices no problem. i know how to adb kill-server and restart the devices as well so it is detected. i have drivers properly installed as a ADB device under device manager. i can adb reboot and even adb reboot recovery but i can't run adb reboot-bootloader or adb reboot bootloader
and adb shell gets me non-su user prompt but i can't su into the root access #. when i run adb shell su -c "whatever" i get:
[-] connect ui: Timer expired
and that's it. when i run bin4ry rooting i get permission denied i'm guessing on places where it needs to get into fastboot screens.

bought fastboot and now i can get fastboot only through poweron process. which is good! i've downgraded to 7.2.3

July 2017
File: Root_Master_1.3.6_Cekas.apk
VirusTotal: 31 / 61
Root if you like to be hack !