I've got an LG G Pad 8.3 and I deleted all my files with recovery (stock) by accident. And I didn't made a save from them. I want to recover my files, but I can't do this because it can connect to PC only by MTP and If I wanted to root it via adb, adb said my device is offline. Can anyone help me in this problem?
rektilian said:
I've got an LG G Pad 8.3 and I deleted all my files with recovery (stock) by accident. And I didn't made a save from them. I want to recover my files, but I can't do this because it can connect to PC only by MTP and If I wanted to root it via adb, adb said my device is offline. Can anyone help me in this problem?
Click to expand...
Click to collapse
You mean you Factory Reset so that your internal storage were wiped, right?
There's probably some Android apps available to undelete files, but I have no experience doing so. You have USB Debugging enabled? Also, some LG devices have a solvable "bug" (at least after rooting) that after every reboot, USB Debugging is turned back off. If yours has that problem, the way to fix it is to turn USB Debugging on, hook the device up to the PC, change it to PTP mode, then back to MTP, then disconnect. From now on it should be good again until certain circumstances cause it to start happening such as after flashing a KDZ or TOT and then re-rooting.
Once USB Debugging and you try to access the device via ADB, you'll have to confirm the ADB authorization dialog on the device. Select the checkbox to remember the authorization.
Thank you
roirraW "edor" ehT said:
You mean you Factory Reset so that your internal storage were wiped, right?
There's probably some Android apps available to undelete files, but I have no experience doing so. You have USB Debugging enabled? Also, some LG devices have a solvable "bug" (at least after rooting) that after every reboot, USB Debugging is turned back off. If yours has that problem, the way to fix it is to turn USB Debugging on, hook the device up to the PC, change it to PTP mode, then back to MTP, then disconnect. From now on it should be good again until certain circumstances cause it to start happening such as after flashing a KDZ or TOT and then re-rooting.
Once USB Debugging and you try to access the device via ADB, you'll have to confirm the ADB authorization dialog on the device. Select the checkbox to remember the authorization.
Click to expand...
Click to collapse
Thank you. If i have time i will try it.
Doesn't works
roirraW "edor" ehT said:
You mean you Factory Reset so that your internal storage were wiped, right?
There's probably some Android apps available to undelete files, but I have no experience doing so. You have USB Debugging enabled? Also, some LG devices have a solvable "bug" (at least after rooting) that after every reboot, USB Debugging is turned back off. If yours has that problem, the way to fix it is to turn USB Debugging on, hook the device up to the PC, change it to PTP mode, then back to MTP, then disconnect. From now on it should be good again until certain circumstances cause it to start happening such as after flashing a KDZ or TOT and then re-rooting.
Once USB Debugging and you try to access the device via ADB, you'll have to confirm the ADB authorization dialog on the device. Select the checkbox to remember the authorization.
Click to expand...
Click to collapse
It doesn't works. adb still sais offline.
rektilian said:
It doesn't works. adb still sais offline.
Click to expand...
Click to collapse
No idea what else to suggest. I'd probably have to be there and fool with it myself to get any ideas.
Did you look for any undelete apps in the Play Store?
Related
Plz Help
I Just Got An Optimus Lte Lu6200
it was having problem that it was not Showing USB Storage When I Connect and Chose "USB Storage"
Also USB Debugging not working,Although I Enable it and connected it via LG Software
Now I Flashed ICS Engineer Mode using Download Mode,Still No Mass Storage Working ,Debugging Shows Enabled but Not Actually
I Tried
Uninstalling and Reinstalling Drivers
Checked on another Computer
No USE
Plz help Me...Appreciated
Maybe It's your phone.
yawxir said:
Plz Help
I Just Got An Optimus Lte Lu6200
it was having problem that it was not Showing USB Storage When I Connect and Chose "USB Storage"
Also USB Debugging not working,Although I Enable it and connected it via LG Software
Now I Flashed ICS Engineer Mode using Download Mode,Still No Mass Storage Working ,Debugging Shows Enabled but Not Actually
I Tried
Uninstalling and Reinstalling Drivers
Checked on another Computer
No USE
Plz help Me...Appreciated
Click to expand...
Click to collapse
Maybe your phone was damage. Did you recently bought that phone? If yes, then the concern maybe is the device itself.
But try install the latest driver for LU6200 [Make sure to download it in LG Mobile Korea] and maybe it would help. Make sure the computer is detecting your phone as you connect it.
Hope this will help you.
mac20dnangel said:
Maybe your phone was damage. Did you recently bought that phone? If yes, then the concern maybe is the device itself.
But try install the latest driver for LU6200 [Make sure to download it in LG Mobile Korea] and maybe it would help. Make sure the computer is detecting your phone as you connect it.
Hope this will help you.
Click to expand...
Click to collapse
Yes Its Not Only Detecting but i Also Put my Phone On Download Mode (Pressing Power+Vol Down) and Flashed Successfully Engineer ICS KDZ File ,The Whole Process Was Done with No Error
But Still Same Mass Storage Problem.........
mass storage is disabled in ics engineer version.
you can try to enable it with adb: "adb shell /system/bin/sdutil ums enable"
or if it doesnt work, use an android software manager like mobilego to access your mass storage.
Thnksss But.....
devcon69 said:
mass storage is disabled in ics engineer version.
you can try to enable it with adb: "adb shell /system/bin/sdutil ums enable"
or if it doesnt work, use an android software manager like mobilego to access your mass storage.
Click to expand...
Click to collapse
Really Thankful to you for reply
But Whats About Debugging Not Working?
Also Its your Suggestion Possible Without Root?As USB Debugging is not working and im unable to Root
I know my way around fastboot, adb, command line pretty well, but I just got my N7(2013) last night, so in that sense, I'm a Noob.
Questions:
Can I just root with SuperSU without TWRP? Or will the stock recovery not let me do that? i.e. is there a signed SuperSU? I would rather keep my stock recovery, if possible.
After I root, do USB storage devices connected via an OTG cable "Just Work"? Do I have to manually mount them? Does it enable a Menu?
Is there any way to enable USB Storage (The other way, when N7 is connected to PC) once I root? Is anybody working on this?
Linuxslate said:
Can I just root with SuperSU without TWRP? Or will the stock recovery not let me do that? i.e. is there a signed SuperSU? I would rather keep my stock recovery, if possible.
Click to expand...
Click to collapse
Suggest you do
fastboot boot twrp.img
instead of flashing twrp onto the tablet's recovery partition
This will run twrp temporarily to install SuperSU's update.zip but will leave stock recovery on your tablet untouched.
Linuxslate said:
After I root, do USB storage devices connected via an OTG cable "Just Work"? Do I have to manually mount them? Does it enable a Menu?
Click to expand...
Click to collapse
Recognition is automatic. Mounting is not. So yes, you need to mount them. Whether you do that manually or through a helper app like stickmount is up to you
Linuxslate said:
Is there any way to enable USB Storage (The other way, when N7 is connected to PC) once I root? Is anybody working on this?
Click to expand...
Click to collapse
Doubtful. N7 doesn't have a real sdcard partition formated fat32. It has a simulated sdcard kept in the /data/media folder. MTP/PTP are the only ways Google wants to support storage going forward.
Thanks, sfhub;
Great trick about running twrp once.
That way I can have root, and my stock recovery.
Thanks for the other info, too.
No MTP or Storage show on PC
I am running windows 7 64 bit and I have managed to get root on my new Nexus 7, but now when I plug my tablet into the PC it says on the tablet connected as media device, but it never shows up anywhere on my pc so that I can transfer files on to it. The nexus 7 never shows up as an extra drive or as an media device. Please help. can not seem to find any info on this problem. the usb icon at the bottom of the screen does say eject nexus 7 when I click on it, and if I have usb debugging turned on it says ADB device connected but I still can not see it anywhere on the pc. Please help
Are you running stock or custom ROM?
If you running stock, you can try disabling USB debugging or try this:
http://forum.xda-developers.com/showthread.php?t=2391236
If you are on custom ROM, it appears there may be an MTP issue with some ROMs.
Yes I am using the stock rom .all I did was root it and I have tried with no success with usb debugging turn Off as well. I have even tried to uninstall the drivers I used to root the tablet , but can not find them to uninstall or delete them
In devmgmt.msc the device is either listed under
Android Phone
Imaging device
Portable device
Unknown
Do you see any ? or unknown devices?
In Devices and Printers in the control panel its listed under Unspecified as Nexus 7 but you can not do anything with it there but right click on it and hit eject or properties and it says Google Nexus ADB interface ___ Android Device ___ status working properly and that's it .In Device manager it listed as Android Device ___ Google Nexus ADB Interface.
I Got it Thank you Thank you. I was able to uninstall the drivers there in the Device manager, unpluged the Nexus 7 plugged it back in it install the correct drivers and I am now able to mount my device as a MTP device and transfer files. Thanks again for the Help.
I put Android File Transfer on my Macs:
http://www.android.com/filetransfer/
and gmtp on My Ubuntu Ultrabook, and on my old Xubuntu desktop.
I put the SD card in the Ultrabook, and copied everything I wanted to the N7(2013).
In all cases, it worked pretty much plug and play, but I still consider it a work-around.
I'm having issues with unlocking/rooting my nexus 7 2013.
I downloaded and installed the nexus root toolkit at wugfresh.com
I've followed all the instructions precisely. However, I always failt the ADB Driver test.
Here are the things I've found while trying to troubleshoot my problem:
1. When I enable usb debugging mode and plug in the nexus 7, I NEVER received the RSA Fingerprint authorization screen.
2. I've installed all the drivers and when it's plugged into the PC, it is recognized as a "google nexus ADB Interface": i.imgur.WHAT/f5Rk5qg.png
3. Inside of USBDeview it is recognized as mass storage device (color purple instead of green): i.imgur.WHAT/r4SwmVM.png
4. Under My Computer I am unable to reach the harddrive anymore.
I believe this is what is preventing me from moving forward. I know this because I've plugged this into my co-workers PC (he already had NRT installed to root his 2012 Nexus 7 awhile ago) and unlocking it on his PC works fine.
5. After uninstalling the drivers installed with NRT and uninstalling the NRT, I still can't access the drive as I could before.
Any help would be appreciated.
This is my first post so I cannot post links to the image... On #2 and #3 replace the i.imgur.WHAT with i.imgur.com
I had the same issue with Wug's toolkit. I finally went the google route using the SDK and usb drivers and it worked like a charm. I would try that method if you feel comfortable enough. Here's a guide to help with that: http://forum.xda-developers.com/showthread.php?t=2382051
railed said:
I had the same issue with Wug's toolkit. I finally went the google route using the SDK and usb drivers and it worked like a charm. I would try that method if you feel comfortable enough. Here's a guide to help with that: http://forum.xda-developers.com/showthread.php?t=2382051
Click to expand...
Click to collapse
I think my issue isn't with the toolkit but with the drivers on my computer right now. I'm not sure how to fix the driver issue i'm having. The link you provided only links to drivers I've already tried.
Laxxium said:
1. When I enable usb debugging mode and plug in the nexus 7, I NEVER received the RSA Fingerprint authorization screen.
Click to expand...
Click to collapse
This is usually because you are not running the latest adb version 1.0.31, but might be for other reasons like the adb that is running in the background is the older version and you need to adb kill-server then adb devices to restart it
Don't underestimate the power of reboot. Sometimes things get in a weird state and even though you have it set up properly, the changes won't really kick in until a reboot.
Laxxium said:
3. Inside of USBDeview it is recognized as mass storage device (color purple instead of green): i.imgur.WHAT/r4SwmVM.png
Click to expand...
Click to collapse
I didn't see mass storage device where you highlighted in red.
You shouldn't see USB mass storage device with this device. It doesn't support it. Only MTP mode. If you are seeing mass storage device, then probably some drivers are out of whack and you should use usbdeview to remove them.
Laxxium said:
4. Under My Computer I am unable to reach the harddrive anymore.
Click to expand...
Click to collapse
There could be many explanations for this. The simplest one is you have USB debugging enabled. Try disabling USB debugging. If that doesn't work, try PTP mode settings->storage->3baroptions If you see PTP mode, but not MTP, then it is a USB ID problem. If you don't see PTP mode either, you probably need to remove some drivers, reboot, and reinstall the drivers.
msellsio completely
Well... my work day ended and I figured I would simply try to do it at home.
I got the drivers to work at home. The nexus was already unlocked so I click on the root button.
After clicking on root, it looks like my tablet got stuck in Bootloader mode, IE in the videos I saw people doing it, it would restart and go into bootload and do something then restart again, mine restarted and just stayed on the bootload screen until I pushed the on/off button (for yes to start).
Now it loads into the tablet and I get about 17 error messages of
"Unfortunately, Google Play Services has stopped" and
"Unfortunately, the process com.google.process.gapps has stopped".
So now I have no idea what to do, I can't even use the damn thing anymore.
Laxxium said:
So now I have no idea what to do, I can't even use the damn thing anymore.
Click to expand...
Click to collapse
Do a factory reset
settings->backup&reset->factory data reset
If you can't get into that, power down
then press Power+VolUp until you see Google, then let go.
You'll see fallen android.
Press and Hold Power, then press/release VolUp, then release Power
Use VolDown to highlight wipe data factory reset, then Power to select.
sfhub said:
Do a factory reset
settings->backup&reset->factory data reset
If you can't get into that, power down
then press Power+VolUp until you see Google, then let go.
You'll see fallen android.
Press and Hold Power, then press/release VolUp, then release Power
Use VolDown to highlight wipe data factory reset, then Power to select.
Click to expand...
Click to collapse
Thanks for this.
I FINALLY got everything to work.
1. I did a factory reset (the 1 thing i was trying to avoid). This fixed the issues with the error messages.
2. I figured out what went wrong with the root toolkit. I decided to try and do the rooting manually, while trying to flash the recovery file, it was getting an unknown error. So the toolkit was basically getting stuck there. It took me 2 hours to figure out that this was happening simply because I was using my front USB3.0 ports. I switch to the back USB2.0 ports and the flashing worked fine.
3. Since I had already managed to flash teh recovery file, I deleted the universal adb drivers and let windows handle it, it installed the regular drivers and I finally managed to access the drive. I was able to upload the supersu file thus completing the root.
I still don't know why the ADB drivers won't let me access the drive though. Guess this mystery will have to be solved anytime.
Laxxium said:
I still don't know why the ADB drivers won't let me access the drive though. Guess this mystery will have to be solved anytime.
Click to expand...
Click to collapse
If you can access the Nexus 7 over MTP (ie as a drive) while USB debugging is disabled but not when it is enabled, that is a known issue and here is a fix.
http://forum.xda-developers.com/showthread.php?t=2391236
If you can't access MTP at all, I would also look at that link to d/l Nirsoft USBDeview and remove all the drivers for the nexus 7 (sort by date and select all the nexus 7 entries) Let the drivers reinstall from scratch.
I have tried all of the suggestions for going back to factory stock. I downloaded the LG Mobile support tool and when I open it it does not detect my tablet. I have tried enabling and disabling USB debugging snd deselecting MTP. I am currently on CM11 so I don't have the option to select LG software when the USB cable is plugged in, I need help please
Edit
kevman8396 said:
I have tried all of the suggestions for going back to factory stock. I downloaded the LG Mobile support tool and when I open it it does not detect my tablet. I have tried enabling and disabling USB debugging snd deselecting MTP. I am currently on CM11 so I don't have the option to select LG software when the USB cable is plugged in, I need help please
Click to expand...
Click to collapse
I realized I was not in download mode. Now i am currently downloading the factory image to flash
Is there a way to stop the HiSuite image from mounting when connecting via USB? Mate SE, Android 8.0 (ota), rooted, macOS.
If you change the developer settings to usb debugging, usb allow adb debugging in charge only, and usb connection to charge only, that will avoid the hi Suite stuff.
If you change the settings and then connect, keep the settings app open, for some reason you have to go back and reset them again after connecting. At least that's what I have to do, they don't seem to stick.
AsItLies said:
If you change the developer settings to usb debugging, usb allow adb debugging in charge only, and usb connection to charge only, that will avoid the hi Suite stuff.
If you change the settings and then connect, keep the settings app open, for some reason you have to go back and reset them again after connecting. At least that's what I have to do, they don't seem to stick.
Click to expand...
Click to collapse
Thanks!
Just to follow up, I discovered a more permanent solution, if you're rooted:
Rename (or delete) the file autorun.iso located at /data/hw_init/version/region_comm/oversea/cdrom
Can't mount it if it's not there