Related
There are certain tricks to regain a couple of MB here and there, like clearing the cache that some applications use, but for those with a taste for apps and games, the phone storage limitation has been quite a nuisance. Android users with root access have been able to enjoy the Apps2SD utility, but getting it to work is a comparatively complicated process. Frozen yogurt to the rescue!
To install an app to the SD card on Android, the application itself needs to support it. In my experience though, most current apps can be moved to the external storage. However, the system installs all new applications on your device’s internal memory by default, except for those that explicitly request external installation. Luckily, it’s possible to make your Android 2.2+ phone put apps on the SD card by default instead. Here’s how:
1. First you have to enable USB debugging on your Android device from Settings > Applications > Development > USB debugging.
2. Now you need to download and install the Android SDK on your computer from the attached file. Once you’ve downloaded and extracted the package to the folder of your choice, run SDK Setup.exe and click on Available Packages to the left. If you get an error message at this point, enable “Force http: in the Settings. From the list of available packages, select “Usb Driver package”, click on the Install Selected button in the bottom right corner and follow the prompts.
3. Connect your phone to your computer with a USB-cable. Your OS will prompt you to install new drivers. Choose to install them from the android-sdk/usb_driver folder. Do not mount your device; you only need to plug-in the cable.
4. Next, run a command prompt and navigate to the Android-SDK\tools folder. In Windows, this is done by selecting Run from the Start Menu (or by pressing Win+R) and typing cmd. You change drives in the command prompt by entering the drive letter followed by a colon (, and change folders with the CD command. For example, to enter the Android-SDK folder, simply type cd android-sdk.
5. In the Android-SDK\tools folder, type in adb devices and you should get a serial number starting with “H” in return. All you have to do next is entering adb shell pm setInstallLocation 2. You’re done! Android will now install apps to the SD card by default.
6. To switch back to storing software on the internal memory, enter adb shell pm setInstallLocation 0.
problem
darkangel_ said:
There are certain tricks to regain a couple of MB here and there, like clearing the cache that some applications use, but for those with a taste for apps and games, the phone storage limitation has been quite a nuisance. Android users with root access have been able to enjoy the Apps2SD utility, but getting it to work is a comparatively complicated process. Frozen yogurt to the rescue!
To install an app to the SD card on Android, the application itself needs to support it. In my experience though, most current apps can be moved to the external storage. However, the system installs all new applications on your device’s internal memory by default, except for those that explicitly request external installation. Luckily, it’s possible to make your Android 2.2+ phone put apps on the SD card by default instead. Here’s how:
1. First you have to enable USB debugging on your Android device from Settings > Applications > Development > USB debugging.
2. Now you need to download and install the Android SDK on your computer from the attached file. Once you’ve downloaded and extracted the package to the folder of your choice, run SDK Setup.exe and click on Available Packages to the left. If you get an error message at this point, enable “Force http: in the Settings. From the list of available packages, select “Usb Driver package”, click on the Install Selected button in the bottom right corner and follow the prompts.
3. Connect your phone to your computer with a USB-cable. Your OS will prompt you to install new drivers. Choose to install them from the android-sdk/usb_driver folder. Do not mount your device; you only need to plug-in the cable.
4. Next, run a command prompt and navigate to the Android-SDK\tools folder. In Windows, this is done by selecting Run from the Start Menu (or by pressing Win+R) and typing cmd. You change drives in the command prompt by entering the drive letter followed by a colon (, and change folders with the CD command. For example, to enter the Android-SDK folder, simply type cd android-sdk.
5. In the Android-SDK\tools folder, type in adb devices and you should get a serial number starting with “H” in return. All you have to do next is entering adb shell pm setInstallLocation 2. You’re done! Android will now install apps to the SD card by default.
6. To switch back to storing software on the internal memory, enter adb shell pm setInstallLocation 0.
Click to expand...
Click to collapse
first of all i get message that the command is not recognized and it should be "pm set-install-location 2" so i do that and nothing changes.i have the lg l70 unrooted.when i "get-location..." it return 2 external but apps get installed to internal and most preinstalled apps like google apps are greyed out to move to sd.Help?
There are quite a few different apps that you wouldn't want to install there such as home launchers, widgets, and keyboards, just to name a few.
1 more
now its telling me error no space when i try to install apps from store but in settings it says there is space,like 600 mb omg
answer
To answer my own question, after setting location to 2 i can move some apps to sd but after that i need to set back to 0 to be able to install apps.Hope it helps somebody.
metro l70 kitkat 4.4
--Edit--
This is finally solved. There was a problem with my computer's ADB RSA key, so I simply had to delete the key file and rerun ADB and I Received the RSA Key Fingerprint window instantly on my G3.
For the full description of the problem look here:
I'm having issues trying to root my phone. I'm using the ioroot method mentioned here.
I get to "* daemon started successfully *" then nothing. After a lot of troubleshooting I know it's because my phone won't allow access by my computer. I never receive the RSA Fingerprint window allowing my computer access to my phone. Here's what all I've tried:
-Put phone into Internet>Ethernet mode (and I've also tried Internet>Modem, MTP and Camera modes as well just to say I did).
-Enable Developer Options and enable USB Debugging.
-Installed the drivers linked in the ioroot page (I've also downloaded the drivers directly from LG - believe it or not ... it's the same file).
-Installed the Verizon Software Assistant from the phone after connecting to the computer.
-Updated my ADB version with the SDK Manager.
-Used different USB ports on my computer as well as two different USB cables (one of which came with the G3).
-Checked Device Manager, all is as it should be and no unrecognized devices.
When I ran the adb server without the ioroot batch file, typing "adb devices" would return my phone's serial followed by "offline." It did this until I updated ADB; then when typing "adb devices" it would return the serial followed by "unauthorized." I've tried all various methods and combinations of switching adb debugging on and off, switching developer options on and off, installing and uninstalling and reinstalling the LG drivers, unplugging and replugging the USB cable, power-cycling all devices including myself at night, doing these methods with long pauses in between (10 minutes to ensure I wasn't being impatient), scratching my head, drinking more coffee, switching to rum and swearing at all devices but nothing seems to make a difference.
What am I missing?
I've got the Verizon LG G3 in White (LG-VS985W)
Software version VS98510B
Windows laptop running Vista 32 bit (I know I know, "eeew Vista")
I was able to obtain root using a different computer, here's what I tried with my laptop after gaining root to get it and my G3 on speaking terms:
-Deleted the ADB_Keys file on the G3 (/data/misc/adb/adb_key): no change.
-Compared running Windows services between Vista and 8.1 and started services which were running on 8.1 but not vista: no change.
Here was the resolution:
There turned out to be a problem with my laptop's ADB RSA key. I'm assuming my G3 was rejecting a bad key and disallowing my laptop to connect to it via ADB.
ADB saves a key file in one of multiple places on a Windows computer, the first is in the location where adb.exe is (C:\android), the second is in the user's profile (C:\Users\*username*\.android), the third place is in the Windows system files (C:\Windows\System32\config\systemprofile\.android), the file is simply named "adbkey" with no extension. If there is no key file when ADB runs, it will generate one automatically.
Mine was located in my user folder (C:\Users\*username*\.android\). All I had to do was delete the adbkey file (there was also a file named "adbkey.pub" which I deleted as well), restart the adb server in command prompt (adb start-server) and plug my phone in. I instantly received the RSA Fingerprint Key window on my G3 allowing connection between the two devices. Then typing "adb devices" returned my phone's serial number followed by "device" showing it was available. I went back to the C:\Users\*username*\.android\ folder and sure enought there were new "adbkey" and "adbkey.pub" files.
Problem finally fixed!
Here are some VERY useful links which helped me come to this fix:
How ADB enables a secure connection
Reconstructing ADB's RSA key file
Try using this set of Vertizon g3 drivers: https://mega.co.nz/#!58YHAZaQ!yNlgZG1m7toHBZp_0HF1jSQ66gMoZmmiDrNq9W5aJIc
Open the .zip, run the .msi file on Windows.
I do not run the G3's auto-install software when I plug it into the PC.
I do set the G3 to "PTP" USB before initially connecting to the PC.
The adb file in the ioroot "bts" subfolder should be okay to run on Windows.
When the phone is attached to the PC, change its USB connection type to Internet, with submenu type Ethernet. At least on my phone, right when I change the phone connection to Internet/Ethernet is when I get the phone popup to accept the PC's RSA fingerprint.
If I then run "adb devices" on my PC, I'll see the random ID followed by "attached", which means I have a good connection. If this doesn't happen, unplug, then replug, the USB connection at the PC side.
Then I can "cd .." and run ioroot.bat.
Good luck!
markfm said:
Try using this set of Vertizon g3 drivers: https://mega.co.nz/#!58YHAZaQ!yNlgZG1m7toHBZp_0HF1jSQ66gMoZmmiDrNq9W5aJIc
Open the .zip, run the .msi file on Windows.
I do not run the G3's auto-install software when I plug it into the PC.
I do set the G3 to "PTP" USB before initially connecting to the PC.
The adb file in the ioroot "bts" subfolder should be okay to run on Windows.
When the phone is attached to the PC, change its USB connection type to Internet, with submenu type Ethernet. At least on my phone, right when I change the phone connection to Internet/Ethernet is when I get the phone popup to accept the PC's RSA fingerprint.
If I then run "adb devices" on my PC, I'll see the random ID followed by "attached", which means I have a good connection. If this doesn't happen, unplug, then replug, the USB connection at the PC side.
Then I can "cd .." and run ioroot.bat.
Good luck!
Click to expand...
Click to collapse
... no dice.
Ok, I'm switching to my Windows 8.1 machine (my laptop is my server and android-dirty-work machine).
So it worked without hesitation on my 8.1 machine. I used the drivers listed in the ioroot thread (same as the drivers from LG) and the process went off without a hitch. I have no idea why my Vista machine and G3 don't get along but I'll need to figure it out when I do further adb work because I use my laptop for that.
Thank you markfm for the extra drivers.
I'll call this solved for now but if I find out further reasons why it didn't work I'll post it here for others who have similar struggles.
Ok I finally solved this. It turned out there was something wrong with my laptop's ADB RSA key. All I had to do was delete the key file, run the ADB Server and connect the phone. ADB will automatically generate an RSA key if none exists. The RSA key was located in C:\Users\*username*\.android and was simply named "adbkey" with no extension. There was also a file named adbkey.pub (Microsoft Publisher) which I'm assuming is a viewable version of the key. I deleted both of these, re-ran the ADB server and voila I instantly received the RSA Key Fingerprint confirmation window on my G3.
Done and done!
unable to generate RSA key on my MCB
I've read and re-read all the entries addressing this issue. I have a black G3 and am using a 2013 Mac Book Pro. I've followed the instructions to the letter many times but with no success. I'm at a loss. Any ideas would be greatly appreciated.
scooterd said:
I've read and re-read all the entries addressing this issue. I have a black G3 and am using a 2013 Mac Book Pro. I've followed the instructions to the letter many times but with no success. I'm at a loss. Any ideas would be greatly appreciated.
Click to expand...
Click to collapse
You'll have to bear with me because I'm not familiar with Mac file structure.
I would start from scratch. Do all these before trying to run adb again.
On your computer:
-Delete adbkey & adbkey.pub from the .android folder (I'm not sure where that is on a Mac, Home\.android?).
-I'm not sure if Macs have a device manager, but check that your phone is correctly recognized and the drivers are installed properly.
On your phone:
-Ensure you've got developer features unlocked
-Double check that you've got usb debugging enabled.
-Tap the "Revoke USB Debugging Authorizations" button below USB debugging in developer options.
-When you're plugged in be sure to set your connection to Internet >>Ethernet (you'll see the debugging icon in the notification bar if it's connected right).
I know a lot of that is basic and redundant but if it's all done correctly then it should work. If it doesn't work it gives us a good starting point to troubleshoot.
If you want to test it open terminal, change directory to the bts folder in the ioroot folder and start adb (adb start-server), with everything done right you should get the rsa window on your phone right now. Type "adb devices" and see what comes back.
Thanks for the assistance. I never could get anywhere with my MBP so I used Windows. I downloaded the drivers and got the RSA key after revoking all prior authorizations. However, but my computer still won't see my G3 in internet/usb debugging mode. It reads it in MTP, PTP and USB charge mode. But that's it. I've rooted numerous phones before, mostly Samsung, but this one has me stumped. Any ideas?
scooterd said:
Thanks for the assistance. I never could get anywhere with my MBP so I used Windows. I downloaded the drivers and got the RSA key after revoking all prior authorizations. However, but my computer still won't see my G3 in internet/usb debugging mode. It reads it in MTP, PTP and USB charge mode. But that's it. I've rooted numerous phones before, mostly Samsung, but this one has me stumped. Any ideas?
Click to expand...
Click to collapse
Use whatever mode will enable USB Debugging. If Internet>>Ethernet doesn't work then use any other mode that will. It's not necessarily important what mode your phone is in, but what mode will allow USB Debugging. If you have it in MTP, PTP, Camera or any other, and you have the USB Debugging icon in the notification bar, try the "adb devices" command and if it returns "*serial* device" then you should be good to go to root.
Once your phone has enabled USB Debugging and accepted the RSA key from your computer then the connection is made and your phone will accept the ioroot commands.
scooterd said:
Thanks for the assistance. I never could get anywhere with my MBP so I used Windows. I downloaded the drivers and got the RSA key after revoking all prior authorizations. However, but my computer still won't see my G3 in internet/usb debugging mode. It reads it in MTP, PTP and USB charge mode. But that's it. I've rooted numerous phones before, mostly Samsung, but this one has me stumped. Any ideas?
Click to expand...
Click to collapse
Is your phone a Verizon Model (VS985)? I'm assuming not because I don't have PTP mode on my G3. If it's not Verizon, the ioroot method suggests using PTP mode.
Yes it is a Verizon VS985. I bought it last week. I have four options, charge, MTP, internet and PTP when I connect my phone to the PC. I get usb debugging under either ethernet or modem. Device Manegr sees my phone and I get the RSA key. I never get a terminal which let's me know something isn't right. This is truly weird but I won't give up. I'll start over and see what happens. Again, thanks for your patience.
scooterd said:
Yes it is a Verizon VS985. I bought it last week. I have four options, charge, MTP, internet and PTP when I connect my phone to the PC. I get usb debugging under either ethernet or modem. Device Manegr sees my phone and I get the RSA key. I never get a terminal which let's me know something isn't right. This is truly weird but I won't give up. I'll start over and see what happens. Again, thanks for your patience.
Click to expand...
Click to collapse
No problem at all, happy to help! It sounds like you have everything set up properly, however the terminal doesn't open automatically (you need to do it manually). But you shouldn't need to open the terminal to get ioroot to work, after you've unzipped the ioroot.zip file, simply navigate to the ioroot folder, right-click on ioroot.bat and choose Run as Administrator. That should run through the entire process for you.
If you want to test your adb connection (testing not required for ioroot to work) you'll need to open the command prompt manually. Press Windows Key+R, in the run window, type cmd and press enter, this will open the command prompt. When you're in the command prompt, you'll need to change directory to the location of adb.exe in the bts folder inside the ioroot folder. Mine was in a folder named android on my C drive so the address looked something like this: C:\android\ioroot\bts the command you'll type in command prompt would be: cd C:\android\ioroot\bts then press enter. Then you can type adb devices and see if you're connected properly.
Okay. Here's where we are. I did everything you suggested. I got the RSA key and the G3 went into recovery mode. I toggeld down to the appropriate command and hit the power button. The little green guy fell over with the dreaded red triange and I got the message "This version of ioroot does not support your device/firmware combo. Please downgrade to previously supported software version. My G3 is running VS98510B. I can't post in the devlopment section but wonder if a software update prevents root the the version being used. Just a question but at least I know I'm not going crazy.
---------- Post added at 04:33 PM ---------- Previous post was at 03:46 PM ----------
scooterd said:
Okay. Here's where we are. I did everything you suggested. I got the RSA key and the G3 went into recovery mode. I toggeld down to the appropriate command and hit the power button. The little green guy fell over with the dreaded red triange and I got the message "This version of ioroot does not support your device/firmware combo. Please downgrade to previously supported software version. My G3 is running VS98510B. I can't post in the devlopment section but wonder if a software update prevents root the the version being used. Just a question but at least I know I'm not going crazy.
Click to expand...
Click to collapse
You sir are a genious. After changing my USB cord, I'm rooted and all is well in the world. It's always the little things that matter
My Pleasure! It's the little things that matter and the little things that kill!! I'm glad you're finally victorious!:laugh:
EDIT: Nevermind, I got it to work through Internet>Ethernet.
postal302 said:
Is your phone a Verizon Model (VS985)? I'm assuming not because I don't have PTP mode on my G3. If it's not Verizon, the ioroot method suggests using PTP mode.
Click to expand...
Click to collapse
Hi, hope this thread is somewhat still alive. sorry for the late add on... please help.
Sorry I'm a complete moron when it comes to rooting and ADB / RSA stuff and have no idea what exactly i am doing but for some reason my macbook won't allow me to authorize my oneplus. the authorize computer dialog box never pops up however i get a notification when my phone is plugged in that debugging is active. developer options have been reset, multiple usb cables have been used, and authorization has been revoked multiple times as well.
Im not sure how to access my adb settings on mac and when i attempt to go into terminal and try kill-server / start-server commands i get error messages as commands are not recognized.
Any help is appreciated as i can no longer use stock rom on OPO and i can't go about rooting my device
Wrong forum area -- this is for the Verizon LG G3 smartphone.
Same here! WITH NEXUS 7
Tried all the methods and spent almost 20hrs experimenting to retrieve rsa fingerprint, but in vain
Can you please suggest any remedy?
I cant install any os and unfortunately, my status bar and softkeys disappeared after using softkeyz apk...Dont tell to delete dalvaik data and cache[ it didnt work]
Please...
Jesusmaryqueen said:
Tried all the methods and spent almost 20hrs experimenting to retrieve rsa fingerprint, but in vain
Can you please suggest any remedy?
I cant install any os and unfortunately, my status bar and softkeys disappeared after using softkeyz apk...Dont tell to delete dalvaik data and cache[ it didnt work]
Please...
Click to expand...
Click to collapse
It is also possible to overcome the situation, by installing Mobilego software on your PC and follow the instructions accordingly (connecting your android using usb & debugging etc,.). You will get a RSA fingerprint request.. Easy Once it's done, u can close the mobilego software in the PC and open someother software for example Bacon root toolkit for oneplus one etc etc.. Hope this helps
adbkey doesn't exist
I don't know what i did wrong before, but my computer just DOES NOT have adbkey and adbkey.pub anywhere! First, i thought it was my phone's fault. Then, i tested in a different pc, and it worked. How do i generate those keys? There are no helpful answers in the internet yet...
Hey guys.
I have Samsung galaxy ace 5839i (stock for 5830i) and I am using it for a few years, but this problem came for the first time.
Always, when I try to connect my mobile to pc using cable, it just won't connect, it won't even show me the notification of connecting.
Before this problem, I connected it to fedora linux and it was succesful, but now? It won't show me that USB sign even in windows.
Any help?
Thanks in advance
@LiQuDiAk, basically s5839i and s5830 i are identical in many areas ,, few questions though,, did you root your device or you are on android 2.3.6 stock version / kernel 2.6.35.7 ?
when you are in your windows device manager ( while you are connected , do you see any exclamation / question marks in front of the corresponding driver), you can always uninstall your old driver, reboot , then try compiled driver in attachment , and reboot to take proper effect in your registry (tested on win xp/7 -32bit) . Also check your device settings>Application>Development > USB Debugging and make sure the option is checked. now lets check your debugging mode through ADB command and see if your device is being recognized. download platform zip attachment, unzip it and put the folder someplace like your desktop. Now open your command prompt (cmd) through whatever means you are comfortable and change directory (cd) to the unzip folder or simply open your folder and drag/drop adb.exe into your CMD to be in the right place very fast. Then type "adb devices" without quotation marks and report for more troubleshooting .Assuming your Samsung cable is not faulty of course.
@ehsanotaku Yes i did root my phone on pheonix fire rom. No i do not see any. And debugging is checked, that was my first guess why it was causing this. I was checking, whether my device is recognized in linux (only available OS in present) and it was NOT, but the cable is not faulty, because it was charging my phone... but i will do recognize process on windows, hope it will get better. But thanks so far!
so, the driver didnt help, but the adb devices got me something long which i do not completely understand (i am a girl and not IT) so...
LiQuDiAk said:
so, the driver didnt help, but the adb devices got me something long which i do not completely understand (i am a girl and not IT) so...
Click to expand...
Click to collapse
off topic though, gender discrimination is prejudice,, sorry if you are offended . Learning from each other despite your gender,does not undermine your knowledge EVER mate You might find it hard to believe, but I am quite novice in android stuff myself ( learning a great deal from some female members though ).
Back to topic at hand now,,,So let Perfectly Clear take away the time-consuming tasks and fix some stuff ..1. so you can not access your sdcard's content from either systems,, even if you try some live bootable Ubuntu disk/flash into your system and boot it up,, you can't access the mount drive content , right?
2. screenshot of your device manger while you are connected always help mate
3. those long streams of numbers and words is supposed to be your device name , it means your device is communicating with your pc ( /sdcard/ should not be corrupted). You can push (copy ) some vital files to your device with following command :
again same path >> put some file into your desktop (drag/drop to cmd)
i.e: "adb push C:\Users\ehsanotaku\Desktop\test.txt /sdcard/"
back to your device and check root of your files with whatever file explorer you got to approve the theory
4. forgot to ask , just to be on the safe side your device is not in boot loop process, stuck on samsung splash screen or something like that, right?
okay, thanks!
1. I cannot access it trough USB to mobile way, but from SD card adapter, yeah I can (it is just the weird feeling, when you always have to put out your sd and do it that way, i would like to sort this out)
2. http://s1.postimg.org/nkta50u3x/Untitleddas.png I suppose the unknown device is my phone.
3. Just a question, my phone is not connected, i cannot access it and this doesn't help
4. Nope, it is working, i can access everything, just this connecting problem i have. anything else is running smoothly.
Let's say any of this will work, do you think flashing a stock rom will help? I am not sure, if this is problem of rom or not, so...
And maybe i wasn't clear (my bad if not) but when i plug the cable in my device and pc, pc will make this sound of new device found, but it wont show me anything, so my phone. It will charge, but it wont connect, it is behaving like it is on a charger and not connected to the phone.
@LiQuDiAk, Hasty actions are done in a hurry, sometimes without the necessary care or thought. Now let's not leap to any conclusion about your Android custom Rom and flashing back to stock. lets focus on your first most obvious problems,which is driver related.
You didn't declare your flavor of windows: i.e: Windows x86 based-PC;professional 7
Not so sure of your OS Name/Version and System Type, search "system information" in your search box.
Your task manger depicted ACPI x64 ( 64-bit system, no wonder previous 32-bit compatible didn't work out for you ).
Symptoms observed so far:
1. USB cable only charges ( remember your USB cable data line might be the culprit. Just in case of only charging,checking with another set recommended. Your USB port might be problem, some dirt or faulty data line, checking with another USP port doesn't heart though.
2. Windows recognizes something more (like in your case, struggling to find proper corresponding driver), but cannot see it as a Samsung android device (cannot allocate the installed USB drivers to the device).
-If you got Kies (Samsung proprietary software) installed on your PC, delete it with a descent uninstaller program such as CCleaner free version .Kies might cause driver conflict , use it as only last resort , if all drivers failed to communicate with s5830i device.
-Also Uninstall your previous given driver same way, now restart , back to system and grab set of universal Samsung Drivers from attachment .
3.Can't see your "USB connected" in Android notification bar, so you cant click on it and mount your storage data part while you are connected to your PC.
-Normally, when you plug in your Android device, Windows will recognize it as an MTP (Media Transfer Protocol) device and quietly mount it.
However, if you’ve ever attempted to unlock your device such as to install a new ROM or root it, then such miss behaviors might be expected occasionally .
Before i go for more troubleshooting , please provide a full screenshot from your "About Phone" page in your settings . I am quite curious about this phoenix Rom you have mentioned though . I am quite familiar with at least dozen of discontinued/ported projects, but never heard of such ported Rom from other models into s5830i .
Couple of solutions :
Navigate to your settings,Storage and touch the upper-right corner for the “USB computer connection” options, if you have this part available.
make sure “Media device (MTP)” is selected. ( if you have USB Utilities section or whatever added section in your custom settings go there . Selecting that will do the trick. If it does not, then you likely have a driver problem.
Open your device manager, Right click on your unrecognized device in question,choose update driver software, choose Browse my computer,find it through given x64 drivers in your package ,Restart. ( After a successful installation, restart your PC, you must have something like the picture in attachment ) .
Problem was not resolved, Uncheck your debugging option,power off your phone. Now hold Volume(+) + Home + Power for a couple of seconds simultaneously to get to your Samsung Recovery or your Clockwork Recovery, choose Reboot( might be some process/service in your background, which interfere with your Auto USB connected feature of your device. See if the problem is being resolved .
Problems have been persisting, we might need to format your SD card, but before that, insert it into your card reader, in your file explorer window choose Tools>Folder options>select view tab> tick your select hidden file.folders. Now copy all of your SD card's contents into some folder, safe inside your PC.
We can format your card through your clockwork mod recovery console, or some partition tools such as free mini partition wizard,,
problem still persist? let me know
Hey
After some rest with this, my mobile got it solved (dunno why, just once tried to do it and it works.)
So, thank you very much with your answers!!!!
And about that screenshots, I will PM you
But, really, thanks a lot, mate!!!!
Symptoms
The classic symptoms of the issue are at some point the Nvidia Dreamtab will stop booting and hang at the Dreamworks characters screen and never boot any further. The frequency ranges from once a month to a year. You are able to factory reset and the issue goes away for some periodicity and then returns.
NOTE: If you recently bought a new Nvidia Dreamtab and you have this character freeze right after doing the OTA then this probably isn't the issue, I am working on a different fix for that problem in this thread. If however this solution does fix your issue I'd like to hear about it.
Background
The tablet uses the linux ext4 filesystem. The Dreamtab kernel requests a filesystem check every 20 partition mounts(typically during reboots) or when the files system is marked dirty(the tablet is hard powered off, or some other glitch). The tablet is missing the fsck binary which is the filesystem checker similar to what you might have seen in windows with chkdsk. Without this file the tablet can not check filesystem and the kernel waits indefinitely for that to happen and your tablet sits and the Dreamworks characters.
Solution
Temporarily boot to a program(TWRP) that can install the filesystem file on the tablet. To temporarily boot to TWRP the bootloader must be unlocked. The unlock procedure requires erasing all information on the tablet which isn't an issue if you are currently experiencing the problem as a factory reset was the only way to recover anyway. If you have a working tablet and want to apply this fix you should find a way to backup your files prior to attempting this. To better understand how the low level Nabi functions this should be required reading and will help better understand what you are doing. http://forum.xda-developers.com/nabi-2/general/nabi-information-t3229119
Procedure
Only for Nvidia Dreamtab NV08B. Use this at your own risk, your warranty is void. You will lose all personal data on the device
Link to video Youtube video installation
1) Down load the drivers.
-- There are 3 popular options included in the link from above in the driver section of the Nabi General Information thread. Have them handy for the next step.
2) Download TWRP recovery.
-- The file is attached at bottom of post. DTTWRPinstaller300.zip
-- Note: You can automate some of the bootloader unlock and installing TWRP steps below with the install.bat file if you have a working Nabi.
3) Download the fsck patch.
-- The file is attached at bottom of post. NV08B_FSCK_PATCH.zip
4) Reboot to fastboot protocol
-- With Nabi powered off press and hold the power button and the vol + button until a small menu(bootloader menu) appears. Quickly release both buttons or the tablet will start booting normally. Using the vol- button to highlight the fastboot protocol(2nd option from top) and then press the vol+ button to select it. Note: Depending on if the drivers are installed the screen will change or stay the same.
5) Verify drivers installed or install drivers.
-- Open windows device manager. On Windows 10 type "device manager" in to the Cortana search bar. On other versions open run by pressing the "windows key" in lower left of keyboard while also pressing R key. Then type: devmgmt.msc
-- If you have "Android Device" and it's sub menu says bootloader/fastboot then you are set up. If down by "other devices" you have an unknown device then you will need to install the drivers from the selection and download you made from reading the Nabi General Information thread.
6) Unlock the bootloader
-- This step will ERASE ALL information on the tablet.
-- Unzip the DTTWRPinstaller300.zip to a location of your choosing. If you use Windows built in unzip utility make sure you check the box that says to open when unzipping is complete.
-- Hold the shift key on the keyboard while right clicking on the "files" folder. Then select "open command window here"
-- At the prompt type:
Code:
fastboot oem unlock
Note: You need to move quickly to the tablet and do the next step as there is a timeout
-- On the tablet it will ask if you want to unlock. Using the vol- key select "yes" with vol+ or pwr. If you do this properly in the command window on your computer it will tell you it is erasing the device.
7) Temporary boot TWRP
-- I can't remember if after the bootloader unlock if tablet is at fastboot, or if you have to power off the tablet and do step 4 again. I think you can just proceed.
-- At the prompt type
Code:
fastboot boot recovery.img
8) Get the patch file on the tablet
-- Option A: There are a couple options for this. Check the file explorer on your computer. If you see t8400n as a device you can just copy and paste the NV08B_FSCK_PATCH.zip to the internal storage by copy and pasting in windows. Go to step 9.
-- Option B: Insert a microSD card in your computer and copy the NV08B_FSCK_PATCH.zip to your microsd card and insert the sdcard in the tablet.
-- Option C: If the t8400n does not show up on your computer then you will need to transfer via ADB. This will require you to setup the ADB driver like you did for fastboot in step 5. Now in sub Android Device in Device Manager you should see ADB, if you don't install driver.
--Copy the NV08B_FSCK_PATCH.zip to the "files" folder where you extracted DTTWRPinstaller300.zip. It should be in a folder with adb, fastboot, AdbWinAPi, etc
-- At the command prompt type:
Code:
adb push NV08B_FSCK_PATCH.zip /sdcard
9) Install patch
-- In TWRP on tablet click the install tab. Generally you will now see the NV08B_FSCK_PATCH.zip if you picked option A or C. If not navigate to the sdcard folder. If you picked option B navigate up a folder and find external_sdcard folder and look in there.
Note: For external_sdcard it may be necessary to exit to TWRP main menu and select mount tab and make sure Micro SDcard is checked.
-- Once you have found the NV08B_FSCK_PATCH.zip from inside the install tab you can select it and then swipe to install. You should get verification it completed normally.
I know this is rather old, but I have a couple of these tablets I'm trying to get working again to give to a friend's kids, but this doesn't seem to work. Did you have to have USB debugging checked before the tablets stopped booting in order for this to work properly?
Basically I can do all the fastboot stuff without any errors, but when I try to boot to TWRP all the tablets do is pretty much rotate the screen 180° so the bootloader screen is in the opposite corner and the volume buttons no longer work until I hold power for ten seconds to power it off... Any help is greatly appreciated!
Background:
I have a rooted SM-G900V (Verizon Galaxy S5) running Lollipop with a broken screen. I have Titanium Backup installed and it was supposed to be running weekly but wasn't. I have recovered my photos, contacts, etc. by connecting to my PC and copying the internal storage and from my gmail restore to a new GS5. I want to recover app data from a couple apps. The phone has USB debug turned on and I can connect with ADB.
I thought I could just run an ADB backup, but apparently in order for the backup to initiate I have to press a button on the lower right of the screen...which is broken. I suppose if I could connect via WiFi and then use a MHL cable I could use a keyboard/mouse to click the button on the phone but I don't have a MHL cable right now and I don't know if that would work anyway (WiFi ADB hasn't worked for me to this point).
THE QUESTION:
I've done a lot of reading and found a number of ADB options that sounded viable, but have not been successful. I have TitaniumBackup installed and thought that I could launch the "backup all" batch process but don't see how to make that happen. I have a new GS5 that is identical setup so I could record some actions on that one and play them on the broken one potentially.
I'm open to any suggestions.
bkenobi69 said:
......... THE QUESTION: I've done a lot of reading and found a number of ADB options that sounded viable, but have not been successful..........
Click to expand...
Click to collapse
The only thing I can think of is to guide you to the following thread that should, hopefully, be what you need.
https://forum.xda-developers.com/showthread.php?t=2786395
Good Luck!
~~~~~~~~~~~~~~~
UNLESS asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my Enigma Machine {aenigma = Latin for "Riddle"}.
I really appreciate the suggestion. FWIW, I sort of came up with a similar approach myself that I almost have working. I turned on ADB WiFi on the device and then plugged in my wireless USB mouse/keyboard. I set up a script that performs a screen capture every 2 seconds and downloads it locally. With Windows7 image viewer, it automatically updates when the image changes so I get a slide show of what's happening on screen. The only issue I have is that the SD card isn't set up for TitaniumBackup apparently since I get an error when I select the backup action. If I can get TitaniumBackup set up correctly, I should be golden!
Thanks for posting that link. Ironically, the solution I developed was very similar in concept. I will give a short description for others who may need to recover data from a phone with a broken screen.
Prerequisites:
* TitaniumBackup - This can be installed from the Play store even if the phone is not functioning
* USB debug mode enabled - Without this, you are stuck. The only issue here is newer phones don't always enable MTP on connection. My old on did but the new one does not. If it doesn't connect via MTP, you will need to install MTPEnabler or similar.
* USB keyboard/mouse combination
* USB cable
* Charged fully functional phone sans screen
* ADB software - You must have the same version on the phone and PC. If not, it won't work reliably/at all. I went with fastboot_adb(1.0.32)_071114_r21 since I have 1.0.32 on my SM-G900V.
Basic steps:
1) Unpack the ADB software on your PC in a convenient location (C:\ADB)
2) Connect phone to PC via USB
3) Send command to enable WiFi ADB connection
4) Disconnect phone from USB
5) Connect ADB via WiFi
6) Run following batch script:
:loop
adb shell screencap /sdcard/screen.png
del screen.png
adb pull /sdcard/screen.png
echo captured
timeout /t 2
goto loop
Click to expand...
Click to collapse
This will dump a screen shot every 2 seconds
7) Open screen.png in Windows image viewer. It should automatically update when the image is refreshed.
8) Type "launch titaniumbackup" and press enter on wireless keyboard.
9) Using either tab or mouse, select the check box to launch TB.
10) Using either tab or mouse, select "menu" from upper right.
11) Using mouse, select "batch actions" from the list.
12) Using mouse, select "RUN" next to "Backup all user apps" from the list.
If all went well, you now have your phone backup up all application data to your SD card which can be easily used on a new phone to restore data.
NOTE:
It may be possible to also use the built-in ADB backup function. I attempted this at one point, but it requires selecting a button in the lower right on the phone. Since I was using ADB over USB at the time, I could not click the button on the phone since I only had one device connected (no hub). If you have a hub it may be possible to use that approach. Alternately, if you use ADB over WiFi, it should also work. However, be aware that there is no way to see where you are clicking or confirm that it worked other than looking at the files on the SD card as ADB backup doesn't appear to give any feedback. Also, this isn't as easy as TB when it comes to restoring as you either have to backup every app one at a time or all together. When restoring, it's also a one shot deal so you can't select specific apps to restore from a larger set.