Related
This post is meant to be the beginning of a FAQ to prevent the same questions from being posted over and over again in the other threads.
How do I write the nooter/auto-nooter/super-nooter image to my sd card?
Under linux, first determine which device your sd card shows up as. Then make sure to unmount that device completely. For example, if your device shows up mounted as /dev/sdc1, as root or using sudo, execute the following command:
unmount /dev/sdc1
You now know that the base device is /dev/sdc.
As root or using sudo, now issue the following command:
dd if=image-file of=/dev/sdc
After the dd command has completed, be sure to issue the sync command. Outerwise, there is the possibility that the data has not been flushed to the device. Do not remove the SD card until after you have synced.
How do I mount the /system partition as read-write?
Using adb, the command is:
./adb mount -o remount rw /system
From a terminal emulator on the NOOKcolor, the commands are:
su
mount -o remount rw /system
My [n]Gig sd card is only showing up as 39M! What do I do?
Power your NOOKcolor up WITHOUT the SD card inserted. After it has completed booting, insert the SD card. Then launch "Settings". Click on "Device Info". Click on "SD Card". Click on "Unmount SD card". After the SD card is unmounted, the "Format SD card" option will be available. Click on "Format SD card." Your SD card will now show up as its full capacity.
(a)My youtube has stopped working. How do I fix it?
(b)How do I uninstall/reinstall youtube?
Connect your NOOKcolor to your computer. Verify that it is seen by ADB.
Using ADB, execute the following commands from the directory where your adb binary is located:
./adb pull /data/app/com.google.android.youtube.apk
./adb uninstall com.google.android.youtube.apk
./adb install com.google.android.youtube.apk
What you just did was pull a copy of the youtube APK to your computer, uninstall youtube from your NOOKcolor and then reinstalled youtube to your NOOKcolor. It is not necessary (and not recommended) that you log into youtube from the youtube app after this.
(a)How do I install ADB on my computer?
(b)ADB isn't working on my computer!
(c)I can't find the adb binary in the android SDK! Help!
From r08 forward, the Android SDK does not include the adb binary. I have archived the last version of the Android SDK that did include the adb binary. This version is for x86 Linux and is what I personally use under Ubuntu 10.04 LTS.
You can download it from:
http://www.op-sec.us/adb-archive/android-sdk_r07-linux_x86.tgz?attredirects=0
You will also need adb_usb.ini which can be found at:
http://www.op-sec.us/adb-archive/adb_usb.ini?attredirects=0
Under Linux, you can use the following commands to get a functional copy of adb running.
cd ~
mkdir .android
cd .android
wget http://www.op-sec.us/adb-archive/adb_usb.ini?attredirects=0
cd ~
wget http://www.op-sec.us/adb-archive/android-sdk_r07-linux_x86.tgz?attredirects=0
tar -zxf android-sdk_r07-linux_x86.tgz
cd ~/android-sdk-linux_x86/tools/
Plug your rooted (nootered/auto-nootered/supernootered) NOOKcolor into your computer.
From within the ~/android-sdk-linux_x86/tools/ directory, issue the following commands:
./adb kill-server
./adb devices
When you run the second command, you should see output that looks very similar to the following:
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
1234567890123456 device
The number in the output will be the actual serial number of your NOOKcolor.
You now have a functional copy of adb located in ~/android-sdk-linux_x86/tools/
(a)How do I reset my NOOKcolor back to factory?
(b)How do I unroot my NOOKcolor?
(c)Help! I bricked my NOOKcolor!!!
Putting your NOOKcolor back to factory state is a two-step process.
Step-1: reflash
If you for some reason think you bricked your NOOKcolor or otherwise want to get back to factory fresh just like when you unboxed your NOOKcolor, follow these steps:
If your NOOKcolor will not boot completely and/or you can't get ADB access to it, just keep powering it on until you see the splash screen and then hold the power button until the NOOKcolor powers off. You must do this eight times in a row. After eight unsuccessful boot attempts, the NOOKcolor will automatically reflash itself.
If you have ADB access to your NOOKcolor, it is easier to do the following:
adb shell
echo -n -e "\x08\x00\x00\x00" > /rom/devconf/BootCnt
reboot
Step-2: wipe /data
With your NOOKcolor completely powered off, hold the "n" button (home button) while at the same time holding the power button. As soon as you see "Touch the future of Reading" on the screen, release both buttons. Shortly after, you will see a Factory Reset screen. At this screen, press the "n" (Home) button to Factory Reset your NOOKcolor.
After completing these two steps, your NOOKcolor will be just as it was when you unboxed it.
I am not seeing any of my installed aps in Extras!
Apps you install will not show up in the "Extras" section until after a reboot. Simply reboot your NOOKcolor and your new apps will show up for you.
Alternatively, you can install an alternate launcher program. ADW Launcher and Zeam Launcger are two popular choices and are both available in the market.
How do I install an alternate keyboard?
The following will show you how to install the Droid-X multitouch keyboard on the NOOKcolor. Be sure to read through the thread and get the latest APK for the keyboard. I am personally running the one from http://forum.xda-developers.com/showpost.php?p=9837580&postcount=16
The instructions for install are in the first post of the thread at:
http://forum.xda-developers.com/showthread.php?t=872470
I'm only seeing a few apps in the Market! What gives?
If you are not running the latest Vending.apk, you will need to rotate to Landscape mode for scrolling in the market to cause it to load additional results.
(a)How do I get the NOOKcolor to connect to my ADHOC network?
(b)My NOOKcolor won't connect to the wifi tether on my phone!
The stock wpa_supplicant on the NOOKcolor does not support ADHOC mode. There is a version of wpa_supplicant that does support both ADHOC and Infrastructure (AP) modes at the same time. It does have one bug: You must reset the wifi (turn wifi off and then back on) if the NOOKcolor goes into sleep mode.
Here is a link to the procedure to install both versions of the wpa_supplicant file along with scripts that will allow you to switch between them. By default, the procedure activates the stock wpa_supplicant file that shipped with the NOOKcolor.
http://forum.xda-developers.com/showthread.php?t=872521
(a)How do I install system apps?
(b)How do I install APKs in /system/app?
http://forum.xda-developers.com/showthread.php?t=875797
How do I install VNC Server on the NOOKcolor
http://forum.xda-developers.com/showthread.php?t=876213
(a)How do I install system apps?
(b)How do I install APKs in /system/app?
http://forum.xda-developers.com/showthread.php?t=875797
Click to expand...
Click to collapse
link appears to be broken
(a)How do I install system apps?
(b)How do I install APKs in /system/app?
http://forum.xda-developers.com/showthread.php?t=875797
Can someone fix this link, pleezz!
How do I write the nooter/auto-nooter/super-nooter image to my sd card with Windows?
Download & use Win32diskimager to create the bootable sd card.
Really? Another thread like this? This is all in the wiki.
http://nookdevs.com/Portal:NookColor
Use it.
Question: I cannot register to my google account
I have a NC, 1.0.1. Rooted flawlessly yesterday. I yet had great problems to register with my Google account. The NC works a long while with signing in... and then says: can't establish a reliable data connection to the server. At the same time I could reach my Google account via the Web on the NC without difficulty, so there are no Wi-Fi problems obviously. Finally, after some hours, I managed it somehow, don't really remember what I did. Market etc, all worked.
This morning, when starting the NC it went to a reset by itself. After that, I had to setup the NC and register at B&N again, without problems, and then to connect to my Google account again. WHICH DOES NOT WORK THIS TIME AT ALL. But again, I can reach Google via the Web. But that does not help for setting up my account, or. Cannot reach Market and all this.
What shall I do? Root again?? Is this problem known?
Many thanks for any help,
wernerml1
can't register with market
wernerml1 said:
I have a NC, 1.0.1. Rooted flawlessly yesterday. I yet had great problems to register with my Google account. The NC works a long while with signing in... and then says: can't establish a reliable data connection to the server. At the same time I could reach my Google account via the Web on the NC without difficulty, so there are no Wi-Fi problems obviously. Finally, after some hours, I managed it somehow, don't really remember what I did. Market etc, all worked.
This morning, when starting the NC it went to a reset by itself. After that, I had to setup the NC and register at B&N again, without problems, and then to connect to my Google account again. WHICH DOES NOT WORK THIS TIME AT ALL. But again, I can reach Google via the Web. But that does not help for setting up my account, or. Cannot reach Market and all this.
What shall I do? Root again?? Is this problem known?
Many thanks for any help,
wernerml1
Click to expand...
Click to collapse
Having the same problem, except that I have not been able to connect to the market at all. No ideas yet.
I'm kind of become both numb and amused with all the suggestions for the problem "market isn't showing all apps" ends up being "get the new market, or rotate to landscape."
That's not my problem, I can scroll in portrait just fine, but I am using the latest version of the market app.
But I am most definitely NOT seeing all the apps. Free and paid, there are numerous apps that do not show up (and direct links give an error like "what, this doesn't exist at all, 404 dude", yet they show up normal on my Droid).
Getting to be a real bummer, I don't want to rely on backing up apps from my Droid... or worse, not seeing an app and basically just going on without ever knowing it exists.
Today my Tablet (Hyundai A7HD) with CM9 started behaving very strange.
It doesnt recognize my sd card, nor its own internal nand storage anymore.
I dont know what to do, since i cant even flash an update through CWM anymore without a functioning storage medium.
the sd card works fine on my pc and i cant format the internal storage through my tablet.
what else can i do to fix this?
I could really use some help, if someone knows a way to do it.
IndigoHD said:
I could really use some help, if someone knows a way to do it.
Click to expand...
Click to collapse
Supply more information. How do you know it's not detecting the internal storage? What are the symptoms? In my point of view, the device would be bricked in this case. Can it boot at all? Or is it fastboot complaining , trying to flash it? The internal memory, is it a MTD for /system plus an MMC for /data, or only an MTD? Only one MMC? Does the devices still exists or not? The partitions..?
Give us some more information, and we'll see if someone here can come with an intelligent suggestion.
Thank you for your reply!
The Device is an Hyundai A7HD and it says that what it calls "sdcard" but actually is its internal storage is damaged. Formatting doesnt work.
It still boots fine but cant access the internal storage, so nothing can be downloaded onto the device and such.
It has a special partition where applications are installed, but nothing can be saved there.
im guessing that something is wrong with the OS, and maybe i could fix it using ADB (if someone could explain to me how)?
Ok, so no /sdcard and /sdcard is supposed to be the phones internal memory, no /data partition, hence not able to download new apps, but the phone boots and so, i.e. system partitions works fine.
This sounds quite like this (confusing) thread to me. In summary, we are talking about three devices, the internal MTD device with /system, boot image, cache etc, the internal MMC device with /sdcard and /data plus an external sdcard named something like /sdcard/external_sd. The internal MMC broken beyond repair (hardware failure).
Still it may be something else only reassembling this.
If you believe your problem is due to some problem with your ROM I suggest you try to reinstall stock ROM using the vendors standard flash tools.
If this doesn't work, we can see if a solution similar to the one in the thread above may be applicable to you.
When i use Astro file manager to look at my phones storage the internal memory calls itself "sdcard" and my ACTUAL micro-sdhc calls itself "extsd" in a folder called "mnt".
the original flash tool doesnt seem to function anymore since i would normally hold down the "menu"-button, then plug the cable into my pc and while STILL holding menu id press power 7 to 10 times and then flashing would start automatically. but ever since installing cwm and a cm9 custom-rom, this doesnt seem to function anymore.
EDIT: in Clockwordmod recovery its called "emmc" for internal memory and "sdcard" for my actual sdcard.
Ok, this is consistent. Can you do a couple of shell commands?
# mount
and
# ls -l /dev/block
... and paste in the result here. As root or as shell user (or any other user) doesn't really matter.
when i plug the device into usb it says debugging enabled. so i open adb and type in "adb devices" and it starts listing devices. But no device is recognized.
EDIT: it recognizes my phone tho.
IndigoHD said:
when i plug the device into usb it says debugging enabled. so i open adb and type in "adb devices" and it starts listing devices. But no device is recognized.
Click to expand...
Click to collapse
Tricky. And not possible to install apps, so no ConnectBot or similar ...
Do you have a link to the CM9 you are using?
kuisma said:
Tricky. And not possible to install apps, so no ConnectBot or similar ...
Do you have a link to the CM9 you are using?
Click to expand...
Click to collapse
wait! i CAN install apps from the market!
and yes, one second.
http://www.slatedroid.com/topic/33373-rom-cm9-nightlies/
im using version 20120711
EDIT: Its an Allwinner A10 Device.
IndigoHD said:
wait! i CAN install apps from the market!
Click to expand...
Click to collapse
That makes all the difference!
So, what does "mount" say?
when i type "adb mount" it just gives me a long list of commands and explanations.
EDIT: there are many versions of connectbot. which one do we need?
IndigoHD said:
when i type "adb mount" it just gives me a long list of commands and explanations.
Click to expand...
Click to collapse
No, run mount from the command line using ConnectBot. ADB didn't work, you told me before.
$ mount
Click to expand...
Click to collapse
but which connectbot on the market is the right one? There are so many.
IndigoHD said:
but which connectbot on the market is the right one? There are so many.
Click to expand...
Click to collapse
Please. Show a little more effort.
https://play.google.com/store/apps/details?id=org.connectbot
i installed it and started it.
now it asks me to connect to a host.
i honestly dont know what im doing here.
IndigoHD said:
i installed it and started it.
now it asks me to connect to a host.
i honestly dont know what im doing here.
Click to expand...
Click to collapse
Select "local", give the session some name of you choice and connect. Now you are running a local shell in the same way as using "adb shell". You are familiar with "adb shell"..?
kuisma said:
Select "local", give the session some name of you choice and connect. Now you are running a local shell in the same way as using "adb shell". You are familiar with "adb shell"..?
Click to expand...
Click to collapse
isnt adb shell a terminal that accepts commands either locally or by usb connection?
EDIT: What should i do now on connectbot?
Can anyone help me, perhaps?
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
I've got a droid razr; rooted, stock rom
I broke the screen accidentally and now the screen isn't showing anything and touch isn't working.
I'd like to recover all the data off my device, but since it's locked, it won't budge. Drives won't mount when I plug it into my PC.
I've got a previous backup which is a little older, but i'm interested in backing up the actual databases (texts, call logs, etc) and system data too, along with my images and personal data.
Is there any way I can perform a whole backup while the system is locked like this?
I've already searched the forum for previous threads with similar issues, but I couldn't find one with a viable solution.
Any help is appreciated, thanks in advance.
Partial Update
Hey all-
I've partially solved my problem.
I was able to get ADB working miraculously. I downloaded the Motorola Device Manager and installed it, also downloaded the Android SDK/Java SDK;
Using the sdk manager i installed the google usb drivers (im not sure it helped any way, but just in case)
after that I ran through the process of adb
Code:
adb kill-server
adb start-server
**plug in device**
adb wait-for-device
adb get-serialno
From there I was able to use "adb shell" and navigate around the file system; used su, went to /data/system/ and did "mv gesture.key gesture.key.bak"
I then restarted my phone and did a repeat of wait-for-device, and get-serialno just to verify the phone was connecting properly.
I then browsed to my computer and amazingly, the drives mounted, my sdcard, and sdcard-ext as removable drives and I was able to view the contents.
-------
So now, I'm stuck here with a device that's NOT locked, I can view my files, and I can navigate the file system.
My end goal is to be able to copy everything from /data/ to /etc/ /system/ /root/ /sdcard*/ /vendor/ /xbin/ and any other system file that's not available through the mounted drives.
I'll keep this thread updated, and if anybody has any help or clue on how I'd do this, it'd be greatly appreciated.
So far I've tried variations on "adb pull" using / as a root dir; trying to find a way to use the shell to invoke scp, ssh, or some other file transfer, but I get no network connection. While in the adb shell and doing any file operations, I get an error stating that it's a read-only file system as well.
Fixed
I just wanted to let you all know that I've resolved my problem.
Let me state the issue again.
- Screen and touch broke.
- Device locked with pattern
- Rooted
- ICS - Stock Verizon ROM
- USB Mode was UMC, not PTP/MTP
- USB Debugging enabled
I used ADB to delete /data/system/gesture.key and rebooted, effectively removing the device lock, and allowing drives & data on my SD cards to show up in explorer after a reboot of the phone.
After futzing around for a bit, I realized the phone was tied to my Google account, and I remotely installed "Droid VNC Server" (app name org.onaips.vnc)
From there I found a way to activate the VNC server through the ADB command line
Source: android.stackexchange.com/a/31957
Code:
Application located in
/data/data/org.onaips.vnc/files
With a root shell, run this
chmod 766 /data/data/org.onaips.vnc/files/androidvncserver
Then you can execute the vnc server from the command line
/data/data/org.onaips.vnc/files/androidvncserver
Run this to forward the port
adb.exe forward tcp:5901 tcp:5901
On your VNC client, connect to localhost:5901
From there I was able to get access to my home screen and pulled the notification drop down and changed from USB Mass Storage to Camera/Media Mode
Rebooted the phone, started the vnc server again, connected to it and moved some files around to my SD Card
In another adb shell as root, I was able to copy files from /data/data/ (or anywhere else I wanted) and write them to anywhere on /sdcard-ext/
From there in another command shell, I ran adb pull /sdcard-ext/datafolderfile
=========================================================================
I believe this to be the overall gist of things, though I ran into hiccups along the way, while I was messing around, I changed some permissions which caused my su executable to break and only be allowed to run shortly after booting the phone; and also because of the broken screen, something would cause the phone to reboot every so often, breaking my connections, backups, file transfers, and etc
There's also a cool option in adb
Run
"adb backup" and it'll give you all the switches, you'll have to confirm the backup on your phone, so be sure to be running VNC and confirm it, but adb backup should be able to grab everything you need. Like I said it didn't work for me because my phone would reboot;
I hope everybody that sees this can benefit from it
Annafunny said:
So did you extract your data from your Razr with adb finally?
Click to expand...
Click to collapse
This thread is really old (4 years)... and the answer was provided.
To avoid further issues, closed.
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: