Database Develop

Unable to mount any more

Not sure when or what happened but I'm unable to mount now. I'm able to use adb and everything but unable to mount AT ALL via adb nor drop down on the notification bar. Any ideas? Yes i've searched and had other members try n figure out why.

imbonez9 said:
Not sure when or what happened but I'm unable to mount now. I'm able to use adb and everything but unable to mount AT ALL via adb nor drop down on the notification bar. Any ideas? Yes i've searched and had other members try n figure out why.
Click to expand...
Click to collapse
If you have Cyan's 1.4 recovery, reboot into recovery, go to console and type
Code:
ums_enable
if it doesnt work, its hardware problem. Make sure its in right, pull it out, blow out any dust, put it back in.
If it does, its something wrong with your ROM install. Make sure its not your computer OS either
you have given absolutely no information on your set-up and its hard to diagnose anything if we don't know what you have

i have
jacXhero1.2
vista 32bit.
My thing is i can use adb with no problems at all, will register every time.

if you can use adb then it shouldn't matter if you can mount the phone, just adb push stuff to your phone if you need it, or pull it. you said you couldn't mount via adb so i guess that means you did "adb shell sdutil ums enable" and you still have ums enabled in your settings?

My whole thing is i want to be able to mount so i can put things on my SD Card and take things off like: music,pictures,videos.

did you try flashing your ROM again? when did it start happening

Go to Settings>Applications>Development and disable USB debugging, you can now mount on your computer to access files. Reenable when done.

SolemnWishing said:
Go to Settings>Applications>Development and disable USB debugging, you can now mount on your computer to access files. Reenable when done.
Click to expand...
Click to collapse
No i still can't thank you though.

imbonez9 said:
No i still can't thank you though.
Click to expand...
Click to collapse
Did you try it with a different card?

you don't NEED to mount to put things on your SD card, you can just do
Code:
adb push \users\me\music\file.mp3 \sdcard\music\file.mp3
or do the same thing to pull from the sdcard, as long as the phone is reading the sdcard then you can push/pull through adb to/from the sdcard

[Q] nc don't boot

i used this method to boot:http://forum.xda-developers.com/showthread.php?t=920347
first it worked but i powered my nc off and since it didn't boot even if a kept the n button pressed,when i plug it on my computer adb dont detect it and the light is orange in charge and on computer
plz help me
thx

cwr
i boot from cwr and used this method:http://forum.xda-developers.com/showthread.php?t=931720
but still doesn't boot

need help
please someone help me i don't know what to do

Does your NC totally not boot at all? If you followed instruction in this thread - http://forum.xda-developers.com/showthread.php?t=931720 basically you are booting from SD. In this case, it has nothing to do what's on your internal flash. Check whether your SD card is created correctly.

it boots
it only boots from CWR

i had the same problem you have. i booted into CWM using the 1 gig sdimage, put the stock boot.img and system.img (from here - http://forum.xda-developers.com/showthread.php?t=919353) and did the dd commands from adb as shown there and my system booted normally.
i had a problem with the stock B&N usb cable where it didn't detect through adb at all. i had to use a different usb cable and it worked good.

i'll try
thx i'll try it tonight,it 1 pm in france^^,tell you if it worked

i don't have any other cable,i ll try to see at virgin tomorrow ,if you have an easier way let me know

the only other way i can think of doing that is to use nookie froyo and wireless adb. the problem with this method was when i tried doing that, i had no market, so i couldn't get wireless adb. i didn't feel like doing a workaround to getting that apk on there. problem with this method is i didn't know if the partitions would look the same or even show off the nook as i was working off the sdcard for froyo, so i wouldn't be able to say if this would actually work.
using the stock B&N cable, i noticed that the device would show in adb, but not online. so reading around i found out if u used a different usb cable it might work, so i did and it did work lol.

Simply flash my repartition boot file...
Sent from my HTC Desire using XDA App

samuelhalff said:
Simply flash my repartition boot file...
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
i looked at sam's method before as well, but didn't try it since i had luck with my usb cable connection for ADB usage. just dd-ing system and boot seemed to work for me and allowed me to keep it how i had it before (with all my previous apps installed). my partitions are probably still shorter though. flashing the zip looks like it'll restore everything to stock.

i bought a new cable,still don't work with adb ,windows detect it but it says it's two different devices and i cant change the driver,sooner nc booted under nookie froyo i don't know how,i'll try to boot again with 2.2 and work with adb from here

were u able to adb in the first place? i used this link http://forum.xda-developers.com/showthread.php?t=882751 to get it working. i also went through the nookdev site to get adb working. i was assuming it was my cable at least since it was tweaking (connecting/disconnecting) with the stock B&N usb cable.

still no adb even over nookie froyo,i try with your method

i have adb usb ,now i don't know how to do cause i only have a 2gb card so i only can put boot but not system on it,i don't know how to enter the command ,is it in adb shell?

i went through CWM and mounted system, data and sdcard. u use adb shell to get into the shell in the nook. then adb'd and
dd if=/sdcard/boot.img of=/dev/block/mmcblk0p1
dd if=/sdcard/system.img of=/dev/block/mmcblk0p5
Click to expand...
Click to collapse
did that. i guess u can put one file and then another file after the first file is dd'd. i used adb to push those img files to the sdcard.

i try it,could you make me a kind of how to with steps and stuff plz?

petithor said:
i try it,could you make me a kind of how to with steps and stuff plz?
Click to expand...
Click to collapse
in your situation this is what i would do.
boot into cwm
mount system, boot and sdcard through the menus
without entering the shell (adb shell) type in: adb push <boot.img file location> /sdcard
now enter the nook's shell by type adb shell then enter
so you're in the nook's shell, and type "dd if=/sdcard/boot.img of=/dev/block/mmcblk0p1"
delete the boot.img file so you have enough space on for the system image by typing "rm boot.img" (make sure you're in the root of sdcard)
type exit to exit the nook's shell
now you're going to push the system.img to the sdcard: adb push <system.img file location> /sdcard
enter into the nook's shell again (adb shell)
type in "dd if=/sdcard/system.img of=/dev/block/mmcblk0p5"
once that is done reboot and everything should work just like before you ran that other script.
this is pretty much what i did. i'm on windows 7 x64 so i just dragged and dropped the files into the command prompt to get the file locations.
again: http://forum.xda-developers.com/showthread.php?t=919353 for more reference of what i was doing.

it worked thx very much ,you are a god besides the humans

[Q] Internal SD Card corrupted

My wife seems to have corrupted her internal SD card, absolutely no idea how. She was bone stock, not even rooted. I could not get stock to even boot past the boot animation, so I tried one of the GB 1 Clicks and boogs KJ3 kernel to get CWM, now I can boot to the launcher, but it bootloops from there. I don't want to format the internal SD until I can get her pictures from it if possible, so my question is: is there a way to get the pictures off, if they even still exist? I have tried mounting in CWM and all i get is a lost directory, now I can't even mount USB storage.

Boot into recovery, then use adb to pull from /mnt/sdcard
Don't need to mount with adb.

Just tried this, I get an empty directory. Tried using adb shell and still showing an empty directory. Any other thoughts, or am I going to have to reformat?

Ouch....I think a format is in order.
sorry man

Well I got it to boot with the kk4 1 click and it runs, but the gallery is empty, so I assume I'm hosed. Any thoughts on cause, she says that earlier she got a message in the notification area about removing her sd card (she has no external, just an internal)?

Try this
Set your screen timeout to the max. Reboot y your phone. Keep touching the screen, don't let it go to sleep. Keep doing that as you pull everything from the phone.
About adb
If you don't set a destination folder in your command, it won't pull. If she's on 2.1, you don't use the mnt part. Place a folder directly on your c drive, so that it's address path is c:\your folder name
This makes your adb command
adb pull \sdcard\ c:\your folder name
Do all of this without letting the phone go to sleep. Maybe it will work for you.

Adb pull /sdcard c:\your folder
Forward slash on phone, backslash on pc.

studacris said:
Adb pull /sdcard c:\your folder
Forward slash on phone, backslash on pc.
Click to expand...
Click to collapse
Yeah, your right.

Appreciate both of your input, but now adb won't even recognize that the phone is attached in the stock kk4 1 click, even in recovery. Like I said the gallery is totally empty and my USB storage on the about phone shows that all of the storage is available, so I'm gonna guess it's all gone. I'll try flashing one of the custom kernels for kk4 just to give it one last try, but I'm not holding out much hope here.

How are you trying to connect to your computer with adb? All you have to do is turn usb debugging on and plug in. open a command prompt terminal. Any of that sound familiar?

There should be a "my files" app you can explore the sdcard that way.
Pictures are in DCIM/camera folder.

the stock 1 click did not have a usb debugging option. Got it to work connecting with samurai 1.4.3, but the directories are showing empty or nonexistent.

Studacris,
You must have been posting while I replied. I've used the my files app and it shows dcim as empty. Now, my wife has decided she's gonna give up on the phone since this was her warranty replacement after her first 1 completely bricked after our daughter played with it. Never could get that one to even boot, although, I've found that this one won't boot to download with a jig, have to use the battery pull, vol +/vol -, insert usb cable method.
Thanks again for the attempts, but I think it's a lost cause, so I'm giving up.

Flash it back to stock and get it replaced again.

sd-card blues...

Hey guys I have a question for you all about sd-cards
I sbf'd
Installed ota 5.7.894 (because of no true .906 sbf I won't flash it)
Regained root
Installed busybox 1.20 (figured newer might be better)
Installed safestrap (tweaked of course 1.08f)
Now
My phone see's the internal/external sd-cards fine and mounts/formats/explores just fine
My laptop also see's internal/external sd-cards just fine
However
Rootbrowser cannot see the sd-card
Safestrap cannot find /sdcard
But
Root explorer can see the internal and external just fine
I have tried sbfing several times to see if it will fix it
I have tried not installing the ota,changing versions of busybox ect..
Why can my phone see and work with the sd-cards just fine but programs cannot?
Because safestrap cannot see the sd-card I cannot create backups..
Any help is greatly appreciated

I think Rick#2 acknowledged this in the safestrap 1.08f thread and had this advice for those experiencing the error:
(For the record, this change almost worked for me - safestrap would now access my external sdcard (/sdcard), but when I would select a zip to flash, it would just take me back to the menu. I dropped a reply with my results in that thread.)
Rick#2 said:
While you're in Safestrap, either go into the console or "adb shell" into your phone. (Remember that for adb to work properly in the recovery your phone has to boot up with the USB cable already connected).
If you type:
Code:
ls -l /dev/block | grep mmcblk0
what output does it provide? For me, it spits out "mmcblk0" but... I'm pretty sure that for those that aren't able to mount their external sdcards it will say mmcblk0p1. In which case, the fix is easy; I'll be sure to update my package, obviously, but for those of you who want to try a little DIY, copy the file /systemorig/etc/safestrap/recovery.zip onto your computer and unzip it. Inside, there's be a file called /etc/recovery.fstab; edit this and change the line corresponding to /sdcard (It ought to be on line 3, or the second line of actual text) to the following:
Code:
/sdcard vfat /dev/block/mmcblk0p1 /dev/block/mmcblk0
Click to expand...
Click to collapse
At this point, after copying the recovery.fstab back to my phone, I assumed I had to correct the permissions of the file, so I did. If I am wrong, someone please let me know!
continuing his reply...
Doesn't really matter how many spaces you have between; ideally you'll just need to hit tab each time.
Hopefully this is what the issue was. I remembered changing that line because I was getting random error messages about my external /sdcard and since I didn't see /dev/block/mmcblk0p1 in my /dev/block directory I assumed I must have made a typo and changed it... here's one tiny example of how easy it is to completely bork these things. Multiply it by a million and you have kernel development...
Click to expand...
Click to collapse

That might work if it was just safestrap having the issue..but its not
Even cwm cannot backup the apps on the sd-card as it cannot see it as well..
But root explorer and the stock file browser can see the internal/external sd-cards
And write on them just fine..and even mount/unmount and format...arrrggggg
This is killin me

Broken Screen, Not Rooted, Lockscreened.

SOLVED
(No success for me personally, but I'd still like to explain how I realised there's no hope left - description is at the bottom of this post)
Hi, not a regular poster in the S3 mini section, but a friend of mine has had his entire screen smashed. Somehow though, the phone is still breathing and can be turned on/off.
The problem is: My friend has asked me to extract his photos and similar media from the device's memory.
The device isn't rooted and I'm not sure if there's a default recovery mode or something like that built in the device.
I've tried connecting the device to my PC and it gets recognized and the drivers install themselves, but the device is empty. Moreover, I've downloaded KIES which also recognized the device, but says that there's a lockscreen and he can't go any further.
Any advices? Most of the other xda answers are for rooted phones so they haven't been very helpful, unfortunately.
There's a picture of the device in the attachments below, and KIES interface aswell.
<<EDIT>>
I'm using this http://forum.xda-developers.com/showthread.php?t=2339530 Recovery operation but it keeps saying "adb.exe" not found. I've installed ADB via the 15sec install ( http://forum.xda-developers.com/showthread.php?t=2588979 ) and entered the path correctly, but it still can't detect it. Any tips? perhaps i'm using the wrong ADB - I don't have c:\android\platform-tools folder - it's simply c:\adb\adb.exe.
SOLVED PROBLEM:
After messing with this for 2-3 days, I've decided to go with the simplest method - find a way to list all directories on the device and then see if there's anything in "sdcard" or a similar folder. To do this, after ADB recognizes your device, type : adb shell ls -R
adb shell ls -R will list a zillion directories so you may want to save the data into a .txt file. to do this, type adb shell ls -R > output.txt (or any other name).
After that, open the output.txt file and then use ctrl-f to find the sdcard folders and check if there's any data left in them.
IMPORTANT:
I've read that, without root permission, one cannot access the data or sdcard directories. The device I was working on had USB debugging OFF so there was no way I could root the phone in order to access the data directories.

Silly question, but did you use option 2 in RecoverData to change the path of ADB to c:\adb\?

aumedina said:
Silly question, but did you use option 2 in RecoverData to change the path of ADB to c:\adb\?
Click to expand...
Click to collapse
Yup, but it still can't find it. That's why I think the ADB-15sec install might be flawed.
There's a screencap of the Recovery + TotalCMD in the background in the attachments.
<EDIT>
Alright so I've followed an ADB tutorial (http://forum.xda-developers.com/showthread.php?t=2266638), installed all the SDK packages just to be sure.
ADB now recognizes the device after I've booted it into recovery mode. I've tried doing adb pull /data and it says 0 files pulled, 0 files skipped. Does this mean the device's internal memory is blank? No it doesn't, only the folder "data" is blank, other system data is present.
<EDIT 2> Can anyone please tell me the path to the internal camera storage folder? I may have fixed the problem if only I knew the correct path. SOLVED: The correct path is one of 4 combinations, usually these: /mnt/sdcard0/ /mnt/sdcard/ /storage/sdcard0/ /storage/sdcard/