Related
Hi,
I have a Spice Mi-270 dual sim android 2.2 phone.Searching on the internet I came across an article where the procedure for installing the apps by default to sdcard is possible for non rooted phones.I tried it but when I type "adb devices" I get a blank list under list of devices attached.My phone came with the usb drivers, I have installed that.Tried installing Google USB driver package,revision 4.When the phone is plugged in get the message on the phone "USB Debugging started".Windows device manager shows "Android Phone" > Android Composite ADB Interface.Still my device is not detected with the "adb devices" command.I am using winxp pro sp3 32bit.Please Guide!
(If I have posted in the wrong section please inform me where to post)
I probably won't be helping. But on my un-rooted HTC Sensation i just have an app called app2sd. After i installed an app, if it's supported, i copy it to sd card.
Can't you just use that and save the hassle?
try this apps2sd
I have already installed the apps2sd but as said one can move the apps to sd if and only if supported by the app.Besides Android 2.2 by default provides the option to supported apps.How do I change the default install path to sd without rooting?
sounds like u need to root it and add the a2sd+ scripts OR root, install rom with a2sd+ and partition sd card accordingly.
do0b said:
sounds like u need to root it and add the a2sd+ scripts OR root, install rom with a2sd+ and partition sd card accordingly.
Click to expand...
Click to collapse
Sorry doOb but I am not looking at rooting my phone but use the option
adb shell pm setInstallLocation 2.
Why not root your phone? At the end or the day you still can unroot it. It's not like you flash to a different Rom and lost your stock Rom.
As far as I know your running froyo you already have move app to SD at the manage application in setting. There are free market app that can help you to move apps to SD with simple clicks without going to setting with the slow loading.
I'm afraid there are no default to app to SD unless you root your Rom and flash a2sd script like darktermor to make the whole process default. Better still, you also need to partition your card with an ext partition for it to work.
By the way... You should be able to adb shell your phone with a proper setup from your pc. You need to look for adb shell howto.
Sounds like your doing it from the wrong folder at cmd if your using windows. Try start cmd from the folder with adb.exe or set your system path to include the folder with adb.exe. I'm not with a pc now, I can't direct you. You have to look for it on what I mean.
By the way, can you also post the link for the article you found?
I have friends that can't root their phone. E.g HTC wildfire s
Sent from my HTC Legend using XDA App
darryl_co said:
Hi,
I have a Spice Mi-270 dual sim android 2.2 phone.Searching on the internet I came across an article where the procedure for installing the apps by default to sdcard is possible for non rooted phones.I tried it but when I type "adb devices" I get a blank list under list of devices attached.My phone came with the usb drivers, I have installed that.Tried installing Google USB driver package,revision 4.When the phone is plugged in get the message on the phone "USB Debugging started".Windows device manager shows "Android Phone" > Android Composite ADB Interface.Still my device is not detected with the "adb devices" command.I am using winxp pro sp3 32bit.Please Guide!
(If I have posted in the wrong section please inform me where to post)
Click to expand...
Click to collapse
Sounds like the original issue was the pc not seeing the device....I know this may be elementary, but do you have it in "charge only" mode and not in the disk drive mode?
"Sounds like your doing it from the wrong folder at cmd if your using windows. Try start cmd from the folder with adb.exe or set your system path to include the folder with adb.exe." - pysionx
I am starting cmd from the folder with adb.exe that laocated in platform-tools.If I was not doing so I would get the error " 'adb' is not recognized as an internal or external command operable program or batch file." and on typing adb devices in the cmd prompt I would not get the answer "list of devices"
pysionx - "By the way, can you also post the link for the article you found?"
Unfortunately no as this is my first post I am not allowed by the administrator to do so.Please Check out the attachment.Sorry for giving you the trouble to download attachment.
pfroyjr - "Sounds like the original issue was the pc not seeing the device"
If the pc does not see the device how do I get in Windows device manager showing "Android Phone" > Android Composite ADB Interface.
pfroyjr - "I know this may be elementary, but do you have it in "charge only" mode and not in the disk drive mode?"
I do not have it in "charge only" mode but in the disk drive mode, USB debugging started is the message received in the notification area.
But this causes hw to crash!
root_toor said:
But this causes hw to crash!
Click to expand...
Click to collapse
I sorry but I did not understand. what causes hardware to crash?
Google "Spice driver" I'll find a link if you can't. Windows is odd with its drivers sometimes. I remember the first time I ever used SDK I had to remove the default drivers and install the one from HTC but recently just installing the driver was good enough and I've only used adb and not the SDK. just a suggestion.
Sent from my HTC Glacier using xda premium
EDIT: I forgot which posting I was replying to, sorry....
I found THIS which sounds like it's an issue with the phone and maybe not the same Android OS that everyone else has....just what I read. Happy Googling my friend. Sounds like it's a cool device, just not quite up to par with adb.
I do have the drivers of my mobile Spice Mi-270 which was shipped along with the phone. The drivers files are of similar names with that of the google usb drivers for android except for the file versions.
Thanks pfroyjr for the link.It seems it is the problem with the phone itself as I am not the only one facing the problem with adb comand.
darryl_co said:
I do have the drivers of my mobile Spice Mi-270 which was shipped along with the phone. The drivers files are of similar names with that of the google usb drivers for android except for the file versions.
Thanks pfroyjr for the link.It seems it is the problem with the phone itself as I am not the only one facing the problem with adb comand.
Click to expand...
Click to collapse
Best advice is stay active searching for an answer...someone will eventually figure it out
I think it can be done with the help of adb .
Just run command from the folder having adb.exe file after connecting your phone in USB Debugging Mode.
"adb shell pm setInstallLocation 2"
YOu can change it to default by the following command.
"adb shell pm setInstallLocation 0"
Type the commands without quotes....
Hope it helps!!!
darryl_co said:
I have already installed the apps2sd but as said one can move the apps to sd if and only if supported by the app.Besides Android 2.2 by default provides the option to supported apps.How do I change the default install path to sd without rooting?
Click to expand...
Click to collapse
Hey try this adb command from the directory having adb.exe file after connecting your phone to your pc by enabling USB Debugging Mode on it.
adb shell pm setInstallLocation 2
You can change it back to default by this command ..
adb shell pm setInstallLocation 0
Hope it helps you ...
yagya said:
Hey try this adb command from the directory having adb.exe file after connecting your phone to your pc by enabling USB Debugging Mode on it.
adb shell pm setInstallLocation 2
You can change it back to default by this command ..
adb shell pm setInstallLocation 0
Hope it helps you ...
Click to expand...
Click to collapse
when I type "adb devices" I get a blank list under list of devices attached.When my phone is not listed how would the adb shell pm setInstallLocation command work ?
but The pc does see the device and I get in Windows device manager showing "Android Phone" > Android Composite ADB Interface.
Try to install universal root/z4root/any other rooting app and shell commander in your phone then root your device temporarily (temporary root means root will be removed when you reboot)with universal root asn then in shell commander type the commands
su
pm SetInstallLocation 2
and then you can unroot your phone
Also if you want to change back do the same but change 2(externel) to 0(auto)
Hope it helped you!!!
---------- Post added at 09:34 PM ---------- Previous post was at 09:33 PM ----------
Try to install universal root/z4root/any other rooting app and shell commander in your phone then root your device temporarily (temporary root means root will be removed when you reboot)with universal root asn then in shell commander type the commands
su
pm SetInstallLocation 2
and then you can unroot your phone
Also if you want to change back do the same but change 2(externel) to 0(auto)
Hope it helped you!!!
yagya said:
Try to install universal root/z4root/any other rooting app and shell commander in your phone then root your device temporarily (temporary root means root will be removed when you reboot)with universal root asn then in shell commander type the commands
su
pm SetInstallLocation 2
and then you can unroot your phone
Also if you want to change back do the same but change 2(externel) to 0(auto)
Hope it helped you!!!)
Click to expand...
Click to collapse
I installed universal androot and rooted the phone.
Instead of shell commander I installed Move2SD Enabler.The move2sd had three radio buttons Auto, Internal and External.Initially it displayed the radio button on Auto.I selected External and clicked apply.Now it shows External.Then I unrooted the phone.In Apps2SD I found many apps that were listed under phone only under movable apps.Few questions do arise
1.If I restore to factory defaults will the installation to external storage be resetted?
2.Whenever I Install new apps it gets installed in the phones internal storage and the I have to move to sd.Why is that so?
3.Even after moving to the sd some amount remains in the phone internal storage.why?
4.Can I check using shell commander if the install location has changed? what is the command? Do I have to root the phone again to use the command?
darryl_co said:
I installed universal androot and rooted the phone.
Instead of shell commander I installed Move2SD Enabler.The move2sd had three radio buttons Auto, Internal and External.Initially it displayed the radio button on Auto.I selected External and clicked apply.Now it shows External.Then I unrooted the phone.In Apps2SD I found many apps that were listed under phone only under movable apps.Few questions do arise
1.If I restore to factory defaults will the installation to external storage be resetted?
2.Whenever I Install new apps it gets installed in the phones internal storage and the I have to move to sd.Why is that so?
3.Even after moving to the sd some amount remains in the phone internal storage.why?
4.Can I check using shell commander if the install location has changed? what is the command? Do I have to root the phone again to use the command?
Click to expand...
Click to collapse
Restoring factory default settings will reset default install location to auto.
Since you used move to sd enabler it only makes all apps movable to sd but doesn't move them automatically.
System apps and Those apps that don't support app to sd by default can't be completely moved to sd card
Yes, you can check using shell commander but you need to riot you phone to use the command.
pm getInstallLocation
(returns default install location)
pm setInstallLocation 2
(installs app direct to external storage)
Sent from my GT-S5570 using XDA Premium App
Before yesterday when powering up my nook tablet I would get the "Installing factory Software...Do not Turn off your device" but immediately after I would get the error message "Please contact nook support." Now my nt just turns off after powering on and displaying the n screen. I have absolutely no clue what is wrong with my tablet or what steps to follow in order to fix it. I would greatly appreciate any input from the knowledgeable members here to point me in the right direction in terms of what procedures need to be followed. Thanks
Heathie89 said:
Before yesterday when powering up my nook tablet I would get the "Installing factory Software...Do not Turn off your device" but immediately after I would get the error message "Please contact nook support." Now my nt just turns off after powering on and displaying the n screen. I have absolutely no clue what is wrong with my tablet or what steps to follow in order to fix it. I would greatly appreciate any input from the knowledgeable members here to point me in the right direction in terms of what procedures need to be followed. Thanks
Click to expand...
Click to collapse
Okay! Step one, you need to make a bootable CWM card.
Get yourself a microSD card, format it, and copy the files from HERE (download, unzip to your SD card).
Power your NT completely down, plug in the card, and then plug in the USB cable.
You should boot to a "cardboard" box screen.
After that, its going to boot into CWM recovery. Now you're not going to have alot of tools on the card at this point, but you may see some errors about stuff not being able to be mounted, etc.
Once you've got that done, post back here, and also include any errors you see!
From there, we can try to figure out exactly what's gone wrong, and the best approach to fix it.
--Also! Include the information about your NT, Is it rooted? What firmware or Rom? Other than powering up, what had you done (If anything) previously before the error!
^ Thanks for your quick reply!
As I wrote in my first post I'm a complete noob when it comes to rooting or hacking any devices. I have not once tried rooting my NT. What I did do though in order to have android as an option on my tablet is buy one of those Nook2Android cards. Now I think I may have accidentally pressed Format SD card or something like that when trying to do something else. That's all that I can think of that I may have done to cause the error.
I'm going to try and make the bootable CWM card right now. I'll make sure to report back!
lag0matic,
I now have a bootable CWM card.
So when I boot into CWM I get this error:
E: Can't mount /cache/recovery/command
E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
E: Can't mount /cache/recovery/last_log
E: Can't open /cache/recovery/last_log
What needs to be done now? Thanks
Heathie89 said:
lag0matic,
I now have a bootable CWM card.
So when I boot into CWM I get this error:
E: Can't mount /cache/recovery/command
E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
E: Can't mount /cache/recovery/last_log
E: Can't open /cache/recovery/last_log
What needs to be done now? Thanks
Click to expand...
Click to collapse
Erf. Okay, you've managed to bork your partitions.
Lets hope this goes easily!
First, lets get Parted (and some other tools) on your CWM recovery card.
Download this file here then unzip them to the root of your CWM Sd card.
Then you need to get ADB up and installed.
I used This forum to get the drivers, however, I couldnt get ADB to work right off the bat.
I'll copy/paste the steps I used and helped others get ADB runnng.
First, google this application: Usbdeview
Download the appropriate one for your system.
Unplug all USB mass storage devices (USB HDD's, Card readers, Memory sticks, etc)
Run USBDeview, delete anything Google, Android, Nook, Barnes and Noble, and Mass storage.
Reboot.
Open device manager
Run the "Runmefirst" or whatever its called from the ADB directory
Plug in your NT.
Go to device manager - look for a broken driver on the tablet, and tell it to install the drivers (you may have to use "have disk" and point to the usb driver directory)
This should install the driver for your NT.
You may also need to edit a file in the .android directory, at the root of your windows username folder.
in which case, drop to a command prompt and type
echo 0x2080 > %username%\.android\adb_usb.ini
after that, switch to the directory you unziped the ADB files to (I used C:\ntroot) and try to connect to your NT by typing "adb devices"
you _should_ see something like
1234567890 Recovery
Or
000000000 Recovery
Now, once you see one of the above messages
in the same command promt window enter the follwing commands
adb shell
mount /sdcard/
cd /sdcard/
parted /dev/block/mmcblk0
you'll then get a prompt that looks like
(parted)
type "print"
and hopefully you'll see a few errors, and it will ask you to fix them, choose fix for both.
Once you get this far (Or, if you run into troubles) post again and i'll see what I can do for you!
(I have successfully un-bricked my NT, but I did it in a way I want to avoid fo you, as we want yours to run stock roms)
lag0matic said:
Erf. Okay, you've managed to bork your partitions.
Lets hope this goes easily!
First, lets get Parted (and some other tools) on your CWM recovery card.
Download this file here then unzip them to the root of your CWM Sd card.
Then you need to get ADB up and installed.
I used This forum to get the drivers, however, I couldnt get ADB to work right off the bat.
I'll copy/paste the steps I used and helped others get ADB runnng.
First, google this application: Usbdeview
Download the appropriate one for your system.
Unplug all USB mass storage devices (USB HDD's, Card readers, Memory sticks, etc)
Run USBDeview, delete anything Google, Android, Nook, Barnes and Noble, and Mass storage.
Reboot.
Open device manager
Run the "Runmefirst" or whatever its called from the ADB directory
Plug in your NT.
Go to device manager - look for a broken driver on the tablet, and tell it to install the drivers (you may have to use "have disk" and point to the usb driver directory)
This should install the driver for your NT.
You may also need to edit a file in the .android directory, at the root of your windows username folder.
in which case, drop to a command prompt and type
echo 0x2080 > %username%\.android\adb_usb.ini
after that, switch to the directory you unziped the ADB files to (I used C:\ntroot) and try to connect to your NT by typing "adb devices"
you _should_ see something like
1234567890 Recovery
Or
000000000 Recovery
Now, once you see one of the above messages
in the same command promt window enter the follwing commands
adb shell
mount /sdcard/
cd /sdcard/
parted /dev/block/mmcblk0
you'll then get a prompt that looks like
(parted)
type "print"
and hopefully you'll see a few errors, and it will ask you to fix them, choose fix for both.
Once you get this far (Or, if you run into troubles) post again and i'll see what I can do for you!
(I have successfully un-bricked my NT, but I did it in a way I want to avoid fo you, as we want yours to run stock roms)
Click to expand...
Click to collapse
So I'm currently going through the process of installing the drivers but I keep getting OMAP4430 under Other devices while Device Manager keeps refreshing.
Heathie89 said:
So I'm currently going through the process of installing the drivers but I keep getting OMAP4430 under Other devices while Device Manager keeps refreshing.
Click to expand...
Click to collapse
^ wow.... that is exactly what i got after the second time my unit barfed.
can you right click on the "omap4430" entry in the device manager and update the drivers by pointing to the folder that has the "nook drivers" folder in the adb + driver + fast zip file?
I imagine you will get a error telling you the drivers are not for this device.
Question to you, did you happen to try formatting the "internal sdcard" ?
@ Lag0matic. this is what killed my unit *dead* today. but it only occured *after* using the 2.3.7 memory managers (not rom-manager) to format the SDcard and the internal SDcard...
maxxcool7421 said:
^ wow.... that is exactly what i got after the second time my unit barfed.
can you right click on the "omap4430" entry in the device manager and update the drivers by pointing to the folder that has the "nook drivers" folder in the adb + driver + fast zip file?
I imagine you will get a error telling you the drivers are not for this device.
Question to you, did you happen to try formatting the "internal sdcard" ?
@ Lag0matic. this is what killed my unit *dead* today. but it only occured *after* using the 2.3.7 memory managers (not rom-manager) to format the SDcard and the internal SDcard...
Click to expand...
Click to collapse
The good news is I have now installed the drivers! My NT under Android Phone appears as Android Composite ADB Interface in Device Manager.
Sadly,though, after getting this far it seems adb still does not recognize my device?
After imputing "adb devices" in cmd in the directory containing the adb files what I get is:
List of devices attached
I don't know if I have missed a step or did one incorrectly.
Heathie89 said:
The good news is I have now installed the drivers! My NT under Android Phone appears as Android Composite ADB Interface in Device Manager.
Sadly,though, after getting this far it seems adb still does not recognize my device?
After imputing "adb devices" in cmd in the directory containing the adb files what I get is:
List of devices attached
I don't know if I have missed a step or did one incorrectly.
Click to expand...
Click to collapse
couple different things to try
#1
adb kill-server
adb start-server
adb devices
try this a couple times. my nook did not get hooked until i did this 2,3 times
#2 with the unit booted from cwm recovery *on the sd card*, reboot windows while leaving the device plugged in.
once back in windows try the adb devices command again.
failing that you are where i was. but at least you can get into cwm, mine ceased booting from sd entirely. heres a thought and a test. can you make the bootable-apla SD card and still use the nook via sd card only? or does it freeze up... ?
Heathie89 said:
The good news is I have now installed the drivers! My NT under Android Phone appears as Android Composite ADB Interface in Device Manager.
Sadly,though, after getting this far it seems adb still does not recognize my device?
After imputing "adb devices" in cmd in the directory containing the adb files what I get is:
List of devices attached
I don't know if I have missed a step or did one incorrectly.
Click to expand...
Click to collapse
i have had that happen a few times and the problem was that my drivers were not installing correctly. sure it appeared as android adb composite device, but it most likely installed the wrong driver for the wrong device.
this is where things get a bit complicated because you need to look for the product and vendor id's for the nook tablet and modify them correspondingly in the android_winusb.inf.
also make sure you execute the runmefirst.bat
that creates a .android folder in your user folder. that was the step i kept missing when i had your problem with the drivers... ironic right? "runmefirst" and i run it last haha...
Hey guys,
is it possible to access the internal storage via adb, without having a display?
My Galaxy SII Display is broken, but the rest should work.
usually i have to lock in with the security points that have to be connected (i dont know how that is called in english),
to allow access via usb.
now that the display does not work, i can not go that way.
so is it possible to access the internal storage via adb?
or do you have another way for me to get my data back?
i am not going to buy a new galaxy s2 and replacing the motherboard,
because its not worth it.
i have cm10.1 installed with dorimanx kernel, and root is allowed for adb and apps.
i never used adb, so i dont know how to start my search.
i also have the problem that i dont know how to look for that thing,
because im not english.
it would be nice if you can give me a start,
or another way to access the internal storage.
i also thougt about accessing via recovery.
i think i can go into recovery, and by pressing volume and power keys,
i can naviagte to mount data.
but im not sure about the steps,
so if anyone have a dorimanx 7.xx kernel,
can you please write the steps down for me?
thank you.
Grandtheftman said:
Hey guys,
is it possible to access the internal storage via adb, without having a display?
My Galaxy SII Display is broken, but the rest should work.
usually i have to lock in with the security points that have to be connected (i dont know how that is called in english),
to allow access via usb.
now that the display does not work, i can not go that way.
so is it possible to access the internal storage via adb?
or do you have another way for me to get my data back?
i am not going to buy a new galaxy s2 and replacing the motherboard,
because its not worth it.
i have cm10.1 installed with dorimanx kernel, and root is allowed for adb and apps.
i never used adb, so i dont know how to start my search.
i also have the problem that i dont know how to look for that thing,
because im not english.
it would be nice if you can give me a start,
or another way to access the internal storage.
i also thougt about accessing via recovery.
i think i can go into recovery, and by pressing volume and power keys,
i can naviagte to mount data.
but im not sure about the steps,
so if anyone have a dorimanx 7.xx kernel,
can you please write the steps down for me?
thank you.
Click to expand...
Click to collapse
if you can mount in recovery then mount everything in recovery,connect your device to PC and the open command prompt and navaigate to folder where you have set up android sdk.
now do the following
1) adb shell
2) now type ls -it'll list all folder and files.
3) now navigate to your sd-card (can't tell exact name for internal sd card) by typing cd <directory name>
4) you can list all files by using ls command.
5) Once you find the exact directory name of sd card and files to be recovered then type exit
6) now type adb pull /path/to/your/folder/filename.File will be saved in working directory...
i don't have s2,just helping you with some common adb stuffs.
btw you can use adb file managers which provides GUI.Like this one http://forum.xda-developers.com/showthread.php?t=1821601
adb
Connect the phone to system, Open terminal and do adb remount then adb shell.
Now do ls, you will be able to see all the folder and everything. Go to Sd-card folder and there you should have all your data.
There is and app ADBExplorer. I have never used this tool, but you can check it is GUI.
Thanks,
The ADBFileexplorer worked very well for me.
Just booted in recovery and started the explorer.jar in the adb folder.
Thank you for the tips.
This can be closed now
Your problem: You have a Nook Tablet running CM10.1 or above, and have been trying to get ADB working on Linux with no results. Android 4.2.2+ OSes have security measures (such as RSA fingerprint matching) that disallows unknown computers to use ADB. On the one hand this is good, but on the other, it's a major pain in the ass. What's even more retarded is, the POPUP SHOWING IF YOU WANT TO ALLOW YOUR COMPUTER TO USE ADB DOES NOT SHOW UP, but only on Linux for some reason. The majority of Windows users using ADB on the NT have no problems at all.
Your issue: I'm having problems getting ADB to work with the Nook Tablet on a Linux distribution! HALLLP!
Your issue: Hallp! My device shows as being "unauthorized"!
SOLVED! Here is the simplest solution I have found.
So, I spent literally weeks looking for a solution, tearing my hairs out, to this problem and I found absolutely NOBODY who knew the answer, except this ONE person, who is apparently the only one besides me that is using Linux. This person DESERVES a medal for a short and simple answer. http://stackoverflow.com/questions/...ed-nexus4-device-in-the-adb/18542792#18542792
Noob friendly version below:
Step one: Copy over your adbkey.pub located in your .android (hidden) folder, located in your home directory most likely (unless you use a root account all the time like a mad man), and put it onto your Nook Tablet's SD card somehow (for example, you can use an FTP server if you do not have an external SD or a card reader around).
Step two: On your Nook Tablet, open a terminal and "cd" to your sdcard's location.
For the internal SD, it's usually /storage/sdcard0 ; for external /storage/sdcard1
(ex: you would type in: cd /storage/sdcard0 )
Step three: Gain superuser access. Type in "su" and allow once.
Step four: Remove the previous adb key located on your Nook Tablet
Type in: rm /data/misc/adb/adb_key
Step five: Append your key, located on your sdcard, to the following location
Type in: cat adbkey.pub >> /data/misc/adb/adb_keys
(Make sure you type in ">>" instead of one ">" because a ">>" means "to append/add" but a ">" means "to replace")
(For each additional computer you want to use adb with, you would simply copy over the adbkey from that computer and follow the same steps)
Easiest and last step: Reboot your Nook Tablet.
Kill the adb server on your computer: adb kill-server
After the Nook Tablet reboots, plug in the USB cable to your Nook and PC, now type in "adb devices. It will be recognized at last!
(I don't really think the reboot was necessary, but oh well).
TL;DR version below (for experienced users):
Code:
rm /data/misc/adb/adb_key
Send adbkey (adbkey.pub in ~/.android/) from computer to device
adb kill-server
cat adbkey.pub >> /data/misc/adb/adb_keys
adb devices
adb shell
Rejoice! ADB finally works!
Don't forget to leave thanks! Press the damn thanks button, how lazy are you guys?!? :victory::victory:
Bump
BUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUMP
Seriously? not a single one of you brainy people know what's going on? and not a single one of you run Linux and happen to have a Nook Tablet?
sagirfahmid3 said:
BUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUMP
Seriously? not a single one of you brainy people know what's going on? and not a single one of you run Linux and happen to have a Nook Tablet?
Click to expand...
Click to collapse
The vast majority of people here have no need whatsoever to use ADB with their Nooks. I think many with an interest of developing (that are the only ones that have a real need for ADB) have moved on to other devices and probably don't check in here much. Sorry to be the barer of bad news.
Out of curiousity, why do you need ADB? I suspect you are fiddling with something fun and intersting. Anything you want to share? If it's interesting enough maybe you'll get more attention! One can always hope...
Yuh huh, I plan on installing Debian on the Nook Tablet and Nook Color following this guy's directions. Since they both have an unlocked bootloader, I'm hoping it wont be too difficult.
http://whiteboard.ping.se/Android/Debian
He also posted the tutorial on this site as well: http://forum.xda-developers.com/showpost.php?p=28943303
BUMP (wanted to push this up the thread in case someone using Linux is having trouble getting ADB working).
SOLUTION IS LISTED AS THE FIRST POST!
Are you sure to delete
"/data/misc/adb/adb_key"
and recreate
"/data/misc/adb/adb_keys"
?
/////
Ok, for me adb_key didn't even exist, and inserting my public key into the /data/misc/adb/adb_keys file worked (despite having bugs shown in dmesg!)
Now, I just need working mtp or usb storage....
/////
Wow, and even this seems to work now, it was just a question of setting/changing the settings when looking at the options for "storage" - maybe there is an initial setup problem in CM10.1, hmmm...
Thank you very much!
bluesock said:
Are you sure to delete
"/data/misc/adb/adb_key"
and recreate
"/data/misc/adb/adb_keys"
?
/////
Ok, for me adb_key didn't even exist, and inserting my public key into the /data/misc/adb/adb_keys file worked (despite having bugs shown in dmesg!)
Now, I just need working mtp or usb storage....
/////
Wow, and even this seems to work now, it was just a question of setting/changing the settings when looking at the options for "storage" - maybe there is an initial setup problem in CM10.1, hmmm...
Thank you very much!
Click to expand...
Click to collapse
No problem! Thanks for your feedback. If there is any way I can make this small guide better, please let me know :victory:
I want to make my android settings to be able move any apps to SD card.My phone is Lenovo A850.So,I tried this option.Using command promt on windows and type this adb devices but my device not on list attached. How to install drivers for this devices. I already enable usb debugging.Please help me.!!!
YoLanC said:
I want to make my android settings to be able move any apps to SD card.My phone is Lenovo A850.So,I tried this option.Using command promt on windows and type this adb devices but my device not on list attached. How to install drivers for this devices. I already enable usb debugging.Please help me.!!!
Click to expand...
Click to collapse
If you have root, you can use a simple app called AppMgr III (Apps 2 SD):
https://play.google.com/store/apps/details?id=com.a0soft.gphone.app2sd
It allows you to move apps to either internal or external storage easily!