So I just installed Ubuntu 10.10 on my PC and I'm really digging it. But when I try to mount my sdcard from the phone, it doesn't show up under my places menu. I'm running GSB 1.8.1. I don't have a problem mounting it under windows XP, and also have no problem using the wired tether function. Is there anything I can change on the phone or in Ubuntu to fix this?
I am running Ubuntu 10.04 LTS - inside a Virtual Machine - and I can mount the drive from inside the VM. (Believe me, that's even trickier than what you are trying).
But, 10.10 might have had some changes, and I wouldn't be surprised if your result depended on which desktop you are running; so maybe you need to mount the thing manually.
Try this:
With the phone unplugged, type
$ sudo /bin/bash
# tail -f /var/log/messages
This will continue to show you various kernel messages as they appear. Next, plug in the phone.
Hopefully, you will see some lines scroll by that mention USB.
Next, mount the SD to the PC from the phone. If all goes well, you should now see some mention of "SCSI" devices /dev/sdX, where X is probably "a", "b" "c" "d". Probably you will also see mention of the first partition on the device, such as "/dev/sdb1". Make a note of this drive device name.
Cancel the "tail" command (Ctrl-C) and do a
# mount | grep sdb1
( note device name "sdb1" ; use whatever you saw previously )
This will show you if the device is already mounted somewhere.
If the device has not been mounted, you can manually mount it, as in:
# mkdir -p /mnt/Eris_SD
# mount -o rw /dev/sdb1 /mnt/Eris_SD
( Again, note device name "sdb1" - use whatever you saw previously. If it doesn't recognize the file system, use "mount -o rw -t vfat /dev/sdb1 /mnt/Eris_SD" )
Hopefully that will do it. Don't forget to "umount /mnt/Eris_SD" when you are done.
If the device never shows up in the /var/log/messages file, then you have some other problems.
If you don't see anything in the log file indicating USB activity, well - you ought to investigate what is going on at the USB port.
Right now my phone is booted into Amon_RA; if I issue the "lsusb" command, I see:
Code:
Bus 001 Device 031: ID 0bb4:0c98 High Tech Computer Corp.
BTW, on my VM, it seems like I need to unplug the USB cable after I dismount the drive, or the next time I export the SD card to the PC, the kernel recognizes it, but the automounter doesn't automatically mount it.
Another thing that you might try to make things more automatic is the instructions in "Step #5" of this XDA post. This is meant for allowing an unprivileged user on your Ubuntu box to use ADB or fastboot without needing to "sudo" to root. I did this on my VM - I don't think that's the reason that the phone automounts into the SD drive, but perhaps it is related - the same "Vendor_ID" is in use when the phone is in "Composite ADB mode".
When you get to the part in these instructions about restarting the "udev" subsystem, unplug your USB cable first - and then see what you get when you plug it in and fire up the SD export from the phone.
hope that helps.
bftb0 said:
BTW, on my VM, it seems like I need to unplug the USB cable after I dismount the drive, or the next time I export the SD card to the PC, the kernel recognizes it, but the automounter doesn't automatically mount it.
Click to expand...
Click to collapse
I noticed this on my desktop with a full install of Ubuntu. I knew it was connected because the charge led was lit, but I would have to unplug the usb and plug it back in almost every time just to get it to mount or connect to the internet with wired tether. I never messed with it BUT it did seem to fix itself once I started doing the system updates on Ubuntu.
bftb0 said:
$ sudo /bin/bash
# tail -f /var/log/messages
This will continue to show you various kernel messages as they appear. Next, plug in the phone.
Hopefully, you will see some lines scroll by that mention USB.
Next, mount the SD to the PC from the phone. If all goes well, you should now see some mention of "SCSI" devices /dev/sdX, where X is probably "a", "b" "c" "d". Probably you will also see mention of the first partition on the device, such as "/dev/sdb1". Make a note of this drive device name.
Click to expand...
Click to collapse
When I got to this step, the log didn't show anything when I mounted the sdcard from the phone. On a whim I tried rebooting the phone into the recovery (AmonRA 1.6.2) and then the log showed it as /sdc. If I turn on USB Mass Storage from the recovery, Ubuntu recognizes it then. On a side note, I'd been having trouble getting ADB to recognize my phone until I did this. But shouldn't this also work with the phone fully booted? Maybe it's GSB?
EDIT: I flashed the Stock Sense 2.1 rom to see if everything worked and it did. I rerooted and restored a backup I made this morning to GSB, and Ubuntu recognizes my sdcard when I mount it, and ADB now works. Thanks for your help.
prsguitaruser said:
When I got to this step, the log didn't show anything when I mounted the sdcard from the phone. On a whim I tried rebooting the phone into the recovery (AmonRA 1.6.2) and then the log showed it as /sdc. If I turn on USB Mass Storage from the recovery, Ubuntu recognizes it then. On a side note, I'd been having trouble getting ADB to recognize my phone until I did this. But shouldn't this also work with the phone fully booted? Maybe it's GSB?
EDIT: I flashed the Stock Sense 2.1 rom to see if everything worked and it did. I rerooted and restored a backup I made this morning to GSB, and Ubuntu recognizes my sdcard when I mount it, and ADB now works. Thanks for your help.
Click to expand...
Click to collapse
In case this helps, GSB mounts the SD card through USB just fine with Windows. Don't take my comment as a Windows versus Ubuntu, thing, however. Just for whatever it's worth.
prsguitaruser said:
I flashed the Stock Sense 2.1 rom to see if everything worked and it did. I rerooted and restored a backup I made this morning to GSB, and Ubuntu recognizes my sdcard when I mount it, and ADB now works. Thanks for your help.
Click to expand...
Click to collapse
Glad to here you got this fixed
prsguitaruser said:
When I got to this step, the log didn't show anything when I mounted the sdcard from the phone. On a whim I tried rebooting the phone into the recovery (AmonRA 1.6.2) and then the log showed it as /sdc. If I turn on USB Mass Storage from the recovery, Ubuntu recognizes it then. On a side note, I'd been having trouble getting ADB to recognize my phone until I did this. But shouldn't this also work with the phone fully booted? Maybe it's GSB?
EDIT: I flashed the Stock Sense 2.1 rom to see if everything worked and it did. I rerooted and restored a backup I made this morning to GSB, and Ubuntu recognizes my sdcard when I mount it, and ADB now works. Thanks for your help.
Click to expand...
Click to collapse
Great news! I don't know how I missed your edit since I quoted it in my last response. I must've had this thread open in my browser from before, and went to respond to it after your edit.
OK, so I went back to GSB and had the problem again. I found out that ADB works and the sdcard mounts until I turn on wired tether, then if I turn wired tethering off, my sdcard still won't mount, nor will ADB recognize my phone, until I reboot the phone. Every time I've tried to mount the sdcard, I've made sure to turn tethering off. But it seems like tethering is what kills it.
prsguitaruser said:
OK, so I went back to GSB and had the problem again. I found out that ADB works and the sdcard mounts until I turn on wired tether, then if I turn wired tethering off, my sdcard still won't mount, nor will ADB recognize my phone, until I reboot the phone. Every time I've tried to mount the sdcard, I've made sure to turn tethering off. But it seems like tethering is what kills it.
Click to expand...
Click to collapse
Are you using the tethering abilities built into CM7 (for wired you have to use the Tether Widget from the market, but that's it), or are you using the "for root" apps? IMHO, the "for root" apps are redundant and don't work as well as the native tethering in CM6 and CM7.
roirraW "edor" ehT said:
IMHO, the "for root" apps are redundant and don't work as well as the native tethering in CM6 and CM7.
Click to expand...
Click to collapse
Really? Because I have never been able to get "native" tethering to work. They appear to be working but there not allowing data to pass through.
Also I only use the ones posted on Google's source page.
I believe there may be an issue here that isn't faulted by the phone or the tethering apps. I think it has something to do with the way Ubuntu reacts to the change between allowing data inbound and when it goes back to remounting the phone and its SD card. Honestly if you can I would say allow your Ubuntu to do its system updates then see what happens.
@ roirraW "edor" ehT, no harm intended at the top of my post. Just my personal observation of how these things generally work out for me. Heh.
Powered by: GSB CM7
wildstang83 said:
Really? Because I have never been able to get "native" tethering to work. They appear to be working but there not allowing data to pass through.
Also I only use the ones posted on Google's source page.
I believe there may be an issue here that isn't faulted by the phone or the tethering apps. I think it has something to do with the way Ubuntu reacts to the change between allowing data inbound and when it goes back to remounting the phone and its SD card. Honestly if you can I would say allow your Ubuntu to do its system updates then see what happens.
@ roirraW "edor" ehT, no harm intended at the top of my post. Just my personal observation of how these things generally work out for me. Heh.
Powered by: GSB CM7
Click to expand...
Click to collapse
Just curious, did you have the opportunity to try the native tethering under Froyo/CM6 as well, or did you only try it under CM7? I haven't needed the tethering since before I started to try CM7, so I actually don't know from personal experience if Cyanogen has made the tethering work correctly under it yet. I didn't have any trouble with it under CM6, besides the usual occasional semi-random tethering failures.
My ubuntu 10.10 install handles native tethering just fine. However, that stupid bug where the Eris loses data connection randomly. while natively tethered kicks in.
The only solution I've found is to use AziLink (seems to solve the random disconnect as well as pdanet does.)
Sent from my Eris using XDA App
adaneshade said:
My ubuntu 10.10 install handles native tethering just fine. However, that stupid bug where the Eris loses data connection randomly. while natively tethered kicks in.
The only solution I've found is to use AziLink (seems to solve the random disconnect as well as pdanet does.)
Sent from my Eris using XDA App
Click to expand...
Click to collapse
Thanks, I'll keep them both in mind. I tried PDANet a long time ago and it didn't keep the tethering from failing, but maybe they improved it.
Related
Hellol everyone, i have read thru the forums and i still have not gotten the answer i was looking for. I am trying to download android sdk.
I can install it and all, but once i click the SDK manager, a black cmd prompt pops up and then vanishes. Also i cant install a drive for my erissince everytime i try to locate the file (and i do), it says that it couldnt locate the folder.
I have read thru the website's guide and installed jdk. Im on a 32bit Vista. Droid eris phone.
ilikeyoumore said:
Hellol everyone, i have read thru the forums and i still have not gotten the answer i was looking for. I am trying to download android sdk.
I can install it and all, but once i click the SDK manager, a black cmd prompt pops up and then vanishes. Also i cant install a drive for my erissince everytime i try to locate the file (and i do), it says that it couldnt locate the folder.
I have read thru the website's guide and installed jdk. Im on a 32bit Vista. Droid eris phone.
Click to expand...
Click to collapse
What do you mean, you can't install a drive? Do you mean you can't mount the SD card? Have you tried installing HTC Sync for the Eris from HTC's website? I know the SDK is supposed to have the drivers necessary, too, but just a thought.
After the Command Prompt vanishes, can you use the SDK Manager then? Have you selected any Available Packages to download and install from the SDK (if you need anything besides the tools).
Also, I see that they changed the organization of the SDK sub-folders as of v8. aapt.exe and adb.exe, and some other files are now in the platform-tools sub-folder now instead of the tools sub-folder.
roirraW "edor" ehT said:
What do you mean, you can't install a drive? Do you mean you can't mount the SD card? Have you tried installing HTC Sync for the Eris from HTC's website? I know the SDK is supposed to have the drivers necessary, too, but just a thought.
After the Command Prompt vanishes, can you use the SDK Manager then? Have you selected any Available Packages to download and install from the SDK (if you need anything besides the tools).
Also, I see that they changed the organization of the SDK sub-folders as of v8. aapt.exe and adb.exe, and some other files are now in the platform-tools sub-folder now instead of the tools sub-folder.
Click to expand...
Click to collapse
I can mount it, but every time i plug it in, it asks me to install a drive. I have tried to direct it to the sdk folder but it wont connect. I have also tried HTC sync and i cant get the drivers intalled either becuase it wont recognize my phone.
After the cmd promt vanishes nothgin happens; its like i didn't click it at all.
No, i have not installed any additional packages. By the way, i do not have a platform-tools folder, just add-ons, platforms, tools, sdk manager(which doesn't work), read me and uninstall.
ilikeyoumore said:
I can mount it, but every time i plug it in, it asks me to install a drive. I have tried to direct it to the sdk folder but it wont connect. I have also tried HTC sync and i cant get the drivers intalled either becuase it wont recognize my phone.
After the cmd promt vanishes nothgin happens; its like i didn't click it at all.
No, i have not installed any additional packages. By the way, i do not have a platform-tools folder, just add-ons, platforms, tools, sdk manager(which doesn't work), read me and uninstall.
Click to expand...
Click to collapse
Well let's take one step at a time. I'm concerned that you say you can't get HTC Sync's drivers to install. Are you sure you've tried the right one (meant for the Eris)? It should be version 2.0.33 and apparently it's dated 4/23/2010. Download it again from the link on this page http://www.htc.com/us/support/droid-eris-verizon/downloads/, unplug your phone, install HTC Sync completely, then plug your phone in. Wait for Windows to install all the drivers, it may take a few minutes to finish.
What method are you trying to use to mount your SD card to the computer? Meaning, are you using the official method from the phone to mount it from the notifications menu, for instance, and which dismounts the SD card from the phone as long as it's mounted to the computer?
Does everything else in Windows Vista work right? Are you able to plug USB flash drives and/or external hard drives in and have them work?
I forget the circumstances, but in the past (not right now), maybe when I'm not using my phone for tethering, Windows gave me a drive letter for my phone as long as it was plugged in, even when I didn't choose to mount the SD card. Trying to view the contents of the drive letter results in an error until you actually tell the phone to mount the SD card as USB storage.
roirraW "edor" ehT said:
Well let's take one step at a time. I'm concerned that you say you can't get HTC Sync's drivers to install. Are you sure you've tried the right one (meant for the Eris)? It should be version 2.0.33 and apparently it's dated 4/23/2010. Download it again from the link on this page http://www.htc.com/us/support/droid-eris-verizon/downloads/, unplug your phone, install HTC Sync completely, then plug your phone in. Wait for Windows to install all the drivers, it may take a few minutes to finish.
Click to expand...
Click to collapse
Done, nothing much happened. when i open HTC sync it says disconnected and i cannot find my phone for phone monitor options, nor sync (it's plugged in).
roirraW "edor" ehT said:
What method are you trying to use to mount your SD card to the computer? Meaning, are you using the official method from the phone to mount it from the notifications menu, for instance, and which dismounts the SD card from the phone as long as it's mounted to the computer?
Click to expand...
Click to collapse
Yes the notification method. I use the same method to dismount it. I have KaosFroyo v38 ROM.
roirraW "edor" ehT said:
Does everything else in Windows Vista work right? Are you able to plug USB flash drives and/or external hard drives in and have them work?
Click to expand...
Click to collapse
Yes, everything works fine.
roirraW "edor" ehT said:
I forget the circumstances, but in the past (not right now), maybe when I'm not using my phone for tethering, Windows gave me a drive letter for my phone as long as it was plugged in, even when I didn't choose to mount the SD card. Trying to view the contents of the drive letter results in an error until you actually tell the phone to mount the SD card as USB storage.
Click to expand...
Click to collapse
wut?
ilikeyoumore said:
Done, nothing much happened. when i open HTC sync it says disconnected and i cannot find my phone for phone monitor options, nor sync (it's plugged in).
Click to expand...
Click to collapse
If you're trying to actually use HTC Sync to sync (not just for the drivers), you have to be running a stock ROM like xtrSENSE, xtrROM or others. Or a Sense-based Froyo ROM, but those aren't really ready for day to day use yet.
Then when you plug your phone in you get three options instead of two:
1. Charge only
2. Mount USB
3. HTC Sync
And it has to be in HTC Sync mode for the HTC Sync program to see it.
Yes the notification method. I use the same method to dismount it. I have KaosFroyo v38 ROM.
Click to expand...
Click to collapse
Have you tried rebooting both the phone and the computer (with the phone disconnected)? Only reconnect it after both are fully loaded.
wut?
Click to expand...
Click to collapse
In other words, with some ROMs when I plug my phone into my USB cable on my computer, the computer immediately shows a drive letter for it. It won't be accessible, though, until I choose the mount USB option on the phone.
There are other alternatives for mounting the SD card through USB, maybe you should try them.
There's a widget on the market that isn't free called Dual Mount SD. Personally I use it, it allows mounting the SD card without dismounting it from the phone. Given the problems you're having, though, perhaps this wouldn't work for you either.
There's a free program called QtADB you can find a link to in a thread on here. Google for QtADB XDA and you'll find it, and it'll link to the website for the program. You can even set it up to do this wirelessly if you have a wireless network/router. When I had real internet (not tethering like now) I tried it and it worked great. It uses something free called Wireless ADB or something like that.
You can do many things with this program, and you have to have the Android SDK installed to use it, but you can see what's on the SD card and copy files to and from it with it.
The only other alternative would be to use a Micro SD card to USB adapter, but then you'd have to turn your phone off every time you want to access you SD card on your computer.
I use DropBox (free) to upload files from my computer and download them to my phone all the time.
So after an incident saturday, my Thunderbolt screen is in a trillion pieces. The phone still boots up fine, receives text messages (much to my chagrin) and receives calls. In fact, it's still paired with my bluetooth in my car so I can make and receive calls when in my vehicle.
However, my replacement should be here tomorrow. I missed several important text messages (the source of its destruction).
Unfortunately, I did not have the phone in PC Mode prior to its destruction, so I cannot see it with adb devices. Is there a way to get it into PC Mode without seeing the screen? As in, a certain key press on bootup that would allow the PC to see it properly?
Upon that, I could use ddms to capture the screen, or download the text database (it is rooted).
On the other hand, the Verizon tech at the corporate store says they can transfer texts as well as contacts (I have Exchange so that's not an issue) if the phone boots. I am very skeptical that this is the case, but she insisted. If they can, then this isn't a big issue to me.
Thanks!
I *think* I might have solved part of the problem.
This is a new PC and I never installed the HTC drivers.
Before I installed them, nothing showed up in adb devices.
Now, my device is listed... but it says "offline" or "error: device offline" when trying to use adb shell.
ddms also doesn't allow me to get a screen shot.
Did you not have USB Debugging checked? That's all you need for ADB to work. It doesn't have to be in PC mode if that's checked.
I'm positive I did have USB Debugging checked as I rooted the phone and did a lot of hacking. Good to know I don't have to put it in PC mode though.
However, I can't seem to get by the "offline" message I get with adb devices or "error: device offline" when I do an adb shell. doing a kill-server and start-server has no effect.
I think I might be on the right track.
I was able to boot into recovery somehow by using power and vol down.
Then I hit something (Power I think) and it vibrated.
Now adb devices lists my device, followed by recovery.
I can connect via adb and list the directory, but only the recovery partition is mounted.
I was able to mount the system via mount -t ext3 /dev/block/mmcblk0p25 /system, but I don't know what the mmcblk is for the data partition.
GOT IT!
Using ddms, I was able to see that I had booted into Clockwork. I then was able to navigate to the mount section and mount /data.
From there, I was able to use adb pull to get the mmssms.db file and use Root Explorer on my Xoom to view those text messages. Then I was able to see why I threw my phone in the first place
Phew, it's amazing what you can do in the Android world.
Bodero said:
Then I was able to see why I threw my phone in the first place
Phew, it's amazing what you can do in the Android world.
Click to expand...
Click to collapse
lol funniest thing i heard all day... maybe there is an android app to fix those anger issues!!
So since cm7 is so close, I decided to try the flashable cwm from indirect. Unfortunately, after that all that happens is my nook tries to boot, I see the white screen with the package, and then it turns off. If I have it plugged in, it will just loop.
I have partitioned a 4gb sandisk with a 50mb FAT 32 partition as the primary, and have given it the lba and boot flags in gparted from my ubuntu laptop. I never could get it to boot off the sd card.
So now I must ask, where do I go from here. I've searched and crawled this forum, but with the boot loop and not being able to boot off of SD, I am unsure where to go next.
Any tips? To me, it looks like it just keeps trying to boot from the recovery. N + Power yields same results as above. Could really use some help with this head scratcher
So you cant access to CWM at all, if not somehow you must make the sdcard method to work in order to apply the fix posted by Indirect, that is the only way im afraid.
~ Veronica
http://forum.xda-developers.com/showthread.php?p=21785424 there's a link to indirects fix for broken recovery.
_______sig starts here______
Even you were a beginner once
If this post helped click the thanks button!
remember QTIP - Quit Taking It Personal
Okay, I get that. I have two questions though,
1: Does this mean I have to do the recovery method vs the bootable sd card?
2: How am I supposed to run commands to a device that keeps rebooting and doesn't give windows time to communicate with it, or will it send commands to it even though its rebooting?
cleverghost said:
Okay, I get that. I have two questions though,
1: Does this mean I have to do the recovery method vs the bootable sd card?
2: How am I supposed to run commands to a device that keeps rebooting and doesn't give windows time to communicate with it, or will it send commands to it even though its rebooting?
Click to expand...
Click to collapse
To apply Indirect's fix first you need to use Goncezilla's CWM sdcard method to boot into CWM once in CWM basically you use adb tools to fix it, use the link posted below by @dodgepot and read the OP carefully to understand the process.
~ Veronica
Thank you for the replies....
So I've gone through and tried once again to get my nook to boot from SD, and still I can't get it to boot. There is a way to do it using DISKPART in windows, I've made the 50mb fat partition, and set it to active. Have there been any other issues with getting it to work?
Poked around the CM7 thread again, apparently CelticWebSolutions was having a problem booting from an sd card.
Anyone know what he did exactly?
It works! Installing android sdk now
cleverghost said:
It works! Installing android sdk now
Click to expand...
Click to collapse
If you are on windows there is no need of SDK it will just give you troubles with the drivers, you should already have the drivers and adb if you rooted your nook tablet before. The adb drivers came in the zip provided for root and should be in C:\ntroot folder.
~ Veronica
I had access to a xp laptop when I did it on before. Using a win 7 64 bit right now, and indirect's batch file stops part of the way through. I had problems in 64 bit before, using the usb drivers from snowball's mod. Guess its a 64 bit problem. (have used usbdeview and I have verified it sets up as an android composite device.)
cleverghost said:
I had access to a xp laptop when I did it on before. Using a win 7 64 bit right now, and indirect's batch file stops part of the way through. I had problems in 64 bit before, using the usb drivers from snowball's mod. Guess its a 64 bit problem. (have used usbdeview and I have verified it sets up as an android composite device.)
Click to expand...
Click to collapse
i have a windows x64 bits too and when i rooted did not have any problem, do not install sdk it is not necessary, run the runmefirst.bat the one that comes in the .zip with the root files not the one that comes in the drivers.zip from Indirect's root. Snowball uses the same drivers as Indirect.
~ Veronica
I did everything stated above ... still a no go.
I tried indirect's driver half a dozen times and can never seem to get it working on x64. I decided to format my laptop and put xp on it. Like I said, last time I used XP, no problems at all.
Edit: Okay, so I tried it on another x64 machine, and I still run into the same issue!
1. run runmefirst.bat
2. Plug in nook
3. Right click nook device with /!\ and update drivers from c:\ntroot
4. Open up bat from indirect's thread
5. Y, Enter
6. Program starts abd..... locks up right after it states it, I waited a good 10 mins for results.
7. Use USBDeview and delete all references to usb mass storage, nook, and android devices. Unplug nook.
8. Plug in nook and repeat 3-6
9. Bang head against wall lol.
It's probably something stupid I overlooked. Feel free to flame away, I'll take it like a man XD. I started with a nook color, but this is pretty much my first tablet experience. You guys have a lot of experience, and I just want to make sure I am not missing something obvious. (I guess I just don't want to seem like a noob, more like a half noob )
Truth be told, I don't know if this is an issue... but I am runing W7x64 Ultimate N
Alright, so adb devices lists my device as "recovery".
I run the script and it still seems to just stop.
Uhmmm the steps you've done are right, I run a windows professional no N edition but that shouldn't be a problem. Maybe try disabling firewall, antivirus if any also Use ccleaner to clean your registries and cache of your machine, reboot and then try again, I want to repeat do not install SDK (just making sure).
~ Veronica
Sent from XDA premium using my Nook Tablet
okay great! Then I do understand the steps.
Yep, no SDK.
Edit: Going to crash now, ill wake up in a bit and take another crack at it. Thanks for your help so far
Alrighty. I woke up again and decided to give it a try from step one. Still a no go. Going to try wiping my drivers again. I've also disabled all antivirus/antimalware....
Looks like its going to be a fun day heh.
ok keep us updated on how you doing.
~ Veronica
Should I see the nook and sd drives mounting in Windows? Right now, I see the drives, but I can't access them. I don't know if that matters or not.....
Also, when I do an adb devices, mine shows as:
Code:
<String of numbers> recovery
Thats correct?
I also took a look at the batch file and might try to run the first few commands to see if I can find where the problem is manually. I have a feeling it's stopping at:
Code:
adb wait-for-device
We'll see though.
EDIT: Unless when you run the command it's supposed to not do anything, then yes. It's hanging.
Alright. Here is what I've found out.
I've done some forum crawling, and I happened upon a post by Loglug where he says to run the following commands:
Code:
adb shell mount -t vfat /dev/block/mmcblk0p6 /data
adb shell dd if=/dev/zero of=/data/BCB bs=1 count=1088
adb shell dd if=/dev/zero of=/data/BootCnt bs=1 count=1
adb reboot
All of the commands work except the second one. It basically echos back and tells me how to use the command. Now, I read a little further into his post and it says that if you do not get the BN recovery after 8 reboots, your recovery partition might be messed up. Could this be what is preventing me from recovering?
EDIT: NEVERMIND! I am up. Sorry, I feel pretty stupid now lol. I just ran the second command wrong -_-. Sorry, my answer was in the forums, just couldn't find it!
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?
Hello all, longtime reader first time poster. I've got the Galaxy Player 4.0 (YP-G1US), and I'm in a "bootloop" situation similar to the others I've seen around here. It seems that the device can't mount the /data partition (mmcblk0p2), and I've tried flashing the stock ROM using Odin in Windoze, Heimdall in both Windoze and Ubuntu 12.04 and 12.10 (not that that I expected a difference) and Terra Silent ROM as well. I flashed using the files from zaclimon's post (http://forum.xda-developers.com/showthread.php?t=1531850), using the pit (with repartition), param, cache, dbdata, factoryfs and zImage. None of that worked, so, I've resigned myself to the fact that my internal memory must have been damaged.
I stumbled on this post http://forum.xda-developers.com/showthread.php?t=1861294 to try to format my external SD as the /data partition. I realize this isn't for the YP-G1US, but I thought I would try anyway (and the first steps should be agnostic of device.) I made two partitions, one in vfat, the other in ReiserFS, flashed stock ROM using all the files I mentioned above, but still got the bootloop. To monitor the situation, I installed google's SDK tools, but can't get ADB to work with my device. When I am in recovery mode for Terra Silent ROM, I am in USB debugging mode automatically, but ADB shows that my device is offline (specifically, the command 'adb devices' returns '????????? offline' ) I understand this is because my device can't authenticate the RSA key from my computer, which would be a handy feature if my device actually worked (you know, to prevent someone from taking my information.) But, since my device won't boot and I've wiped out all the data it had, this is an unnecessary annoyance that prevents me from diagnosing my problem.
Here are my questions:
1.) Do you know how to restore my device to some sort of working order (which most likely involves mounting the external SD as the internal SD in some manner.)
2.) If you don't know how to do 1.), could you at least tell me how to get ADB to recognize my device so I can figure out what my problem is? Maybe some method of moving the RSA key from my computer to the device, or some other way to run ADB on a device that can boot to recovery or download but not all the way so that I can transfer the key normally?
Thanks very much,
Eric
ewgrashorn said:
Hello all, longtime reader first time poster. I've got the Galaxy Player 4.0 (YP-G1US), and I'm in a "bootloop" situation similar to the others I've seen around here. It seems that the device can't mount the /data partition (mmcblk0p2), and I've tried flashing the stock ROM using Odin in Windoze, Heimdall in both Windoze and Ubuntu 12.04 and 12.10 (not that that I expected a difference) and Terra Silent ROM as well. I flashed using the files from zaclimon's post (http://forum.xda-developers.com/showthread.php?t=1531850), using the pit (with repartition), param, cache, dbdata, factoryfs and zImage. None of that worked, so, I've resigned myself to the fact that my internal memory must have been damaged.
I stumbled on this post http://forum.xda-developers.com/showthread.php?t=1861294 to try to format my external SD as the /data partition. I realize this isn't for the YP-G1US, but I thought I would try anyway (and the first steps should be agnostic of device.) I made two partitions, one in vfat, the other in ReiserFS, flashed stock ROM using all the files I mentioned above, but still got the bootloop. To monitor the situation, I installed google's SDK tools, but can't get ADB to work with my device. When I am in recovery mode for Terra Silent ROM, I am in USB debugging mode automatically, but ADB shows that my device is offline (specifically, the command 'adb devices' returns '????????? offline' ) I understand this is because my device can't authenticate the RSA key from my computer, which would be a handy feature if my device actually worked (you know, to prevent someone from taking my information.) But, since my device won't boot and I've wiped out all the data it had, this is an unnecessary annoyance that prevents me from diagnosing my problem.
Here are my questions:
1.) Do you know how to restore my device to some sort of working order (which most likely involves mounting the external SD as the internal SD in some manner.)
2.) If you don't know how to do 1.), could you at least tell me how to get ADB to recognize my device so I can figure out what my problem is? Maybe some method of moving the RSA key from my computer to the device, or some other way to run ADB on a device that can boot to recovery or download but not all the way so that I can transfer the key normally?
Thanks very much,
Eric
Click to expand...
Click to collapse
Are you using adb on Ubuntu? You have to run adb start-server as root.
Mevordel said:
Are you using adb on Ubuntu? You have to run adb start-server as root.
Click to expand...
Click to collapse
I am (technically Kubuntu, 12.10), but whether or not you need to be root to use adb depends on where you installed it. At any rate, if it were a root user priviliges issue, I'd be seeing "?????????? No Permissions". I did run adb as root, just to be sure, and got the same response as described in the original post.
I know that the issue is the RSA key authentication (whitelist) "feature" that google introduced with more recent versions of adb, which is fine if you can actually boot your device and click "yes" on the popup that asks to verify that you want the connected computer to access your device. The problem I have has arisen because I can't boot normally (I can only get to recovery) and so can't authorize my computer to connect to my Galaxy player (and so can't transfer the RSA key from my computer to my Galaxy.) So again, I ask, is there a workaround?
Thanks,
eric
ewgrashorn said:
I am (technically Kubuntu, 12.10), but whether or not you need to be root to use adb depends on where you installed it. At any rate, if it were a root user priviliges issue, I'd be seeing "?????????? No Permissions". I did run adb as root, just to be sure, and got the same response as described in the original post.
I know that the issue is the RSA key authentication (whitelist) "feature" that google introduced with more recent versions of adb, which is fine if you can actually boot your device and click "yes" on the popup that asks to verify that you want the connected computer to access your device. The problem I have has arisen because I can't boot normally (I can only get to recovery) and so can't authorize my computer to connect to my Galaxy player (and so can't transfer the RSA key from my computer to my Galaxy.) So again, I ask, is there a workaround?
Thanks,
eric
Click to expand...
Click to collapse
The build property ro.adb.secure=0 will override that. You can try putting it in build.prop, but if it doesn't work, you'll have to put it in /default.prop, which requires modifying the kernel ramdisk. While you're at it, ro.secure=0 will give you an automatic root shell.