Related
I'm running JF ADP1.5 and followed these instructions to get my apps to SD. For normal apps this works fine, but as far as I can tell protected apps (such as Abduction World Attack or Calorie Counter) get messed up. Installation seems to be working fine, but the apps have no icons, are called au.com.phil.abduction (or similar names) and forceclose on startup.
I don't believe I did something wrong with the apps2sd process, the symlinks are looking good:
Code:
# ls -al /data
drwxrwx--x 1 1000 1000 2048 May 3 11:19 .
drwxr-xr-x 12 0 0 0 May 7 10:36 ..
drwxrwxrwx 1 1000 1000 2048 May 3 11:20 anr
lrwxrwxrwx 1 0 0 14 May 3 11:33 app -> /system/sd/app
lrwxrwxrwx 1 0 0 22 May 3 11:33 app-private -> /system/sd/app-private
drwxrwx--x 1 1000 1000 2048 May 3 11:19 dalvik-cache
drwxrwx--x 1 1000 1000 2048 May 3 11:19 data
drwxrwx--x 1 2000 2000 2048 May 3 11:19 local
drwxrwx--- 1 0 0 2048 May 3 11:19 lost+found
drwxrwx--t 1 1000 9998 2048 May 3 11:19 misc
drwx------ 1 0 0 2048 May 3 11:19 property
drwxrwxr-x 1 1000 1000 2048 May 3 11:20 system
system/sd/app contains various apps, /system/sd/app-private is empty.
Does anyone here have a clue what's going wrong?
Could be a bad sdcard because I'm running that same exact paid app with no problem.
Try to reformat SD card, I've had some problems with my old card this is what I did:
killed all partitions
remake parts, formatted, still problems.
killed all partitions again, made one big part
dd if=/dev/zero of=/dev/sdcard1
remake 2 parts
mkfs.vfat /dev/sdcard1
mkfs.ext2 /dev/sdcard2
filled it up again.
I had the same problem when I got apps2sd, but wat I did was went to the market and all my paid apps said "update availabe", so I "updated" them even though they were already updated, but yea try that
I was wrecking my head all night cause I had the same problem. I lastly decided to format the old ext2 partition, refilled sdcard and presto, I did my happy dance.
Hi,
Go into apps on your phone and uninstall each paid app.
Then go to the market and reinstall.
They should work fine now.
That fixed this problem for me.
Apps on SD and ADP 1.5update
bsander said:
I'm running JF ADP1.5 and followed these instructions to get my apps to SD. For normal apps this works fine, but as far as I can tell protected apps (such as Abduction World Attack or Calorie Counter) get messed up. Installation seems to be working fine, but the apps have no icons, are called au.com.phil.abduction (or similar names) and forceclose on startup.
I don't believe I did something wrong with the apps2sd process, the symlinks are looking good:
Code:
# ls -al /data
drwxrwx--x 1 1000 1000 2048 May 3 11:19 .
drwxr-xr-x 12 0 0 0 May 7 10:36 ..
drwxrwxrwx 1 1000 1000 2048 May 3 11:20 anr
lrwxrwxrwx 1 0 0 14 May 3 11:33 app -> /system/sd/app
lrwxrwxrwx 1 0 0 22 May 3 11:33 app-private -> /system/sd/app-private
drwxrwx--x 1 1000 1000 2048 May 3 11:19 dalvik-cache
drwxrwx--x 1 1000 1000 2048 May 3 11:19 data
drwxrwx--x 1 2000 2000 2048 May 3 11:19 local
drwxrwx--- 1 0 0 2048 May 3 11:19 lost+found
drwxrwx--t 1 1000 9998 2048 May 3 11:19 misc
drwx------ 1 0 0 2048 May 3 11:19 property
drwxrwxr-x 1 1000 1000 2048 May 3 11:20 system
system/sd/app contains various apps, /system/sd/app-private is empty.
Does anyone here have a clue what's going wrong?
Click to expand...
Click to collapse
After I did the update I had a similar problem. I would install apps but no icons would appear. They would show up in settings as installed and I could uninstall them but no matter what I tried the icons would not show up. If I tried running them through settings, they would force close or say they weren't installed.
I copied everything off my fat32 partition onto my pc and used the trial version of Paragon Partition Manager to reformat the fat32 and ext2 partitions. Once reformatted, I used Lucidrem's 1.5 update as he had nice simple scripts for the apps2sd stuff. Copied that over to the fat32 partition, put it back into the phone and before applying the update I did a wipe Alt W and then did the update.
After the update I used terminal to enter the scripts (the apps2sd scripts) and started re-installing all my apps. True it was a bit of a pain to start over but the phone has been running great with virtually zero problems. Apps that were giving problems are running fine now.
The update over 1.42 or 1.43 seems to cause this for some of us. Who knows why it happens but it does. One advantage to "re-doing" everything is that you can get rid of all those apps that you never use anyway. Trying to figure out why your having the problem will probably take longer than simply starting from scratch.
Good Luck!
I finally got around to doing this. Pulled the app/ directory from the ext2 partition, first reformatted the whole sd card to one big partition (probably unnecessary but wth), then back to ext2/fat32 and cp -p'd the app/ dir back. All seems to work great now, and no need for a wipe! Thanks guys!
Hi Guys
I recently tried to upgrade my radio and SPL to use Cursors32A rom. It update failed and cannot seem to get the SD card to mount in recovery mode again
When i try to mount/use the card it come up with the following error
Code:
mount: mounting /dev/block/mmcblk0p1 on /sdcard failed: No such file or director
y
mount: mounting /dev/block/mmcblk0p2 on /system/sd failed: No such file or direc
tory
Now ive been going through the forums over the last two days trying to fix it. The one method that stands out to me is the gold card method..but i cant seem to obtain the CID.
Now my knowledge of the andriod/unix enviroment is limited(i was brain washed my M$)
anyway please help a n00b
Thanks
Kyle
Hi,
What is your current SPL?
Does fastboot works ?
a command like fastboot boot recovery-RA-sapphire-v1.5.2H.img works ?
Cedric
Fastboot won't work for him, no eng spl. Did you try another SD card? I know it's a simple question but double check if it's working. I remember another command available that helps mount your SD card but I forgot the command. Try searching the forums more, I'm sure you'll be able to find it.
If I remember correctly, your SPL + Radio don't match up. I've never seen that together before. Lucky it isn't bricked yet
The command is fastboot oem enableqxdm 0
the prompt returns 'OKAY'.
Hey guys
i tried 6 different sdcards
d_ced, when i run the below command i get
Code:
c:\android\android-sdk-windows\tools>fastboot oem enableqxdm 0
... INFO[ERR] Command error !!!
OKAY
ill post my ls -l for reference
Code:
drwxrwxrwx 1 0 0 2048 Sep 6 1980 cache
drwxr-xr-x 2 1000 1000 0 Jan 1 1970 data
-rwxr-xr-x 1 1000 1000 2733 Jan 1 1970 default.prop
drwxr-xr-x 11 0 0 1300 Jan 6 00:07 dev
drwxr-xr-x 2 1000 1000 0 Jan 1 1970 etc
-rwxr-xr-x 1 1000 1000 106764 Jan 1 1970 init
-rwxr-xr-x 1 1000 1000 1677 Jan 1 1970 init.goldfish.rc
-rwxr-xr-x 1 1000 1000 2781 Jan 1 1970 init.hero.rc
-rwxr-xr-x 1 1000 1000 598 Jan 1 1970 init.rc
dr-xr-xr-x 42 0 0 0 Jan 1 1970 proc
drwxr-xr-x 3 1000 1000 0 Jan 1 1970 res
drwx------ 2 0 0 0 Jan 1 1970 root
drwxr-x--- 2 1000 1000 0 Jan 6 00:07 sbin
drwxr-xr-x 2 0 0 0 Jan 6 00:07 sdcard
drwxr-xr-x 15 0 0 0 Jan 1 1970 sys
drwxr-xr-x 3 1000 1000 0 Jan 1 1970 system
drwxr-xr-x 2 1000 1000 0 Jan 6 00:07 tmp/CODE]
also i have not tried the goldcard method but i cannot get the CID of the device
thanks in advance guys!
Thanks
Kyle
well guys i tried following the instructions of /forum.xda-developers.com/showthread.php?t=639107&page=5 and i bricked it...it just sits at the HTC magic screen :/
oh well thanks in advance!
APP development page has moved to http://forum.xda-developers.com/and...esharing-server-android-t2803452/post53869540
This thread is kept fir reference as it contains valuable information for manual modifications.
hey there I was lookin for similar feature , its not exactly the sme well it is , but anyways , Estrong Explorer does the job for what you are tryin to do , ( ESexplorer) free inmarket . as long as phone is reg on network it will access your share
Hi, I just got Samba server (2.2.12) working on my HTC Hero. The daemons smbd+nmbd take up just under 4Mb memory when running (and opening a shared folder on the phone from a computer on the network will launch another smbd daemon, which is about 2.5Mb).
The main problem I'm having is slow xfer rates - seems to max out at 600 - 700Kb/s. Its the same if i SCP files though, so I dont think its a problem is with samba specifically...
I can provide a tarball with the files if you want to try it out (install & configuration is through a root shell, its all pretty basic at the moment).
- Jimmy
By all means, I'd like to try it on my Nexus. Just finished a thread about changing Nexus One's hostname from default "localhost", and understood that besides my router, I can't do much with it on Windows network w/o DNS
Please post the files & instructions.
Have attached a zip file containing the samba files + README.txt with basic install instructions. Access the phone shared folder via Windows network browsing, or with \\IPaddress of the phone.
** See a later post by me in this thread that has a newer version of Samba attached which includes automated install/uninstall script.
Hi,
I've checked the most recent version and the one before it, on Nexus.
Both exhibit the same behavior.
1) When trying to unzip to SD card, everything's ok and the default file attributes are preserved. When extracting to /data/local, no matter which way is used, "executable" attributes aren't preserved - only RW attributes. chmod +rwx samba/bin/* doesn't help, and when trying to execute "samba-rc start" via Terminal on the phone, it shows: "ash: can't find samba-rc" (I'm using ash). Using "su samba-rc start" also doesn't help, it shows "permission denied".
2) Trying to execute smbpasswd - it asks for a new password and confirmation, and crashes with segmentation fault.
3) Trying to execute samba-rc from ADB SHELL didn't throw any error messages, but it didn't work either.
I've tried both running from the phone's terminal emulator and by adb shell (I don't open the shell continuously, I run each command separately - adb shell "command", this way I can dump the output to PC by adding > in the end).
/data/local/samba/bin/nmbd -i -d 99
Looks like it's working, both from phone's terminal emulator and from adb shell. I see the Nexus being discovered by Windows 7 workstation on network scan (I've personalized the name - read my thread in Nexus development section on how to do that). nmbd_log attached, to check that everything's ok.
/data/local/samba/bin/smbd -i -d 99
Here the things start getting more interesting.
1) If I try to connect, after some time the smbd stops by itself - looks like after 5 failed attempts the server auto-stops itself. That's not a good behavior, especially considering that while Windows prompts you for username and password to connect, it also keeps trying to auto-connect using the default username (that's where 5 attempts come from). The server shouldn't stop itself. smbd_log1 attached.
2) If I write the user on time, smbd crashes while trying to compare passwords. smbd_log2 attached.
All the logs are zipped.
Thanks for the info Jack.
With the shell script, can you try running it like:
sh -c "/data/local/samba/bin/samba-rc restart"
if that still doesnt work, as a further test, open two root sessions via adb shell, in one run the nmbd command, in the other run the smbd (both with same options as before) then try browsing again from your computer.
Note: dont let your phone go into sleep mode (keep the screen active so the display stays on).
- JC
I had a chance to play with both versions some more.
1) using su and no shell (not running ash) I can run samba-rc, and it executes correctly. Both processes (nmbd and smbd) show up in ps. To achieve that, I needed to chmod +rwx /samba/bin/* after unzipping.
2) nmbd works well, and the phone shows up on Windows network.
3) It still doesn't allow logging into it, and I believe the problem lies in smbpasswd executable, which still shows erroneous behavior:
Tried to login using default user bogan: "network resource not available" message coming from Windows upon entering login credentials. Phone stays on the network and can be accessed again, but login is still impossible.
Tried to change default user's password: smbpasswd asks for new password twice (without asking for the old one - which is wrong behavior!) and crashes with segmentation fault.
Tried removing /samba/private/smbpasswd file and creating a new one, using smbpasswd -add username. Worked, but no password was asked for the user.
Tried to change password for new username. The same as before - asked for new password twice, then crashed with segmentation fault.
When tried to login with the new user, it didn't show "network resource not available", but it kept asking for password (the dialog where username is already there, and only the password needs to be retyped). I didn't know the default password that smbpasswd creates, if any. Tried nothing, tried several basic options (root, same as username, etc), none worked.
I believe the problem might be smbpasswd not working correctly on Android 2.1.
ich started samba via chroot debian. i can read and write the filesystem.. except mapped /sdcard... i cannot delete files... any ideas how to set permissions? the user is 1000 and group is 1015
Played some more with it, and I can definitely point at authentication as the source of the problems. I got it to work. Not too well - because it lacks any security whatsoever - but at least it works.
First, about the problems:
When mistyping the password one of the times, smbpasswd shows correct error message and gracefully exits.
When doing everything correctly, it crashes - but writes /private/smbpasswd file before that.
I've tried to run it with debug level = 9, it showed lots of info when starting, and after changing passwords - just the regular "Segmentation fault" crash.
in smb.conf, setting password encryption = off causes the Windows to throw "this user isn't authorized to login from this station" error instead of asking for username.
But, how I got things to work?
Well, since I was certain that it's the authentication mechanisms that prevent it from working, I prevented those authentication mechanisms from functioning. At first I wanted to ask Jimmy for a test version that would ignore user/password checking, but then I thought that I might do it in smb.conf file. So here is what I did:
[global]
security = SHARE # instead of USER
[sdcard]
guest ok = yes # instead of no
With these settings, I get no password prompts and Samba works! I see SD card share, and can copy to/from it.
Notes:
* The main script (samba-rc) works well in killing all the smbd processes on stop/restart.
* Server still runs when the phone is in sleep mode, just much slower.
Jimmy, could you please test smbpasswd compilation to find out why it crashes on 2.1 (I'm running Cyanogen 5.0.6)? Once it's done, I believe that this will work anywhere.
Also, something could probably be done to make it speed up CPU / network on demand when the phone is sleeping, or to prevent the phone from sleeping while it's running - and a GUI can be made for controlling it, since it'll be fully functional.
can you delete from the sdcard share?
DocMAX said:
can you delete from the sdcard share?
Click to expand...
Click to collapse
Yes, tried and deleted a directory with files.
Hi Jack,
Nice work with your testing
I'd like to take a look at all the file permissions samba unzip'd with and compare them to what they should be - could you post output of
ls -laR /data/local/samba
smbpasswd probs: could you delete /data/local/samba/private/smbpasswd and add a user with bin/smpasswd using '-a' rather than '-add', like
/data/local/samba/bin/smbpasswd -a jack
then re-enable authentication in the config file and see how it goes?
I'll see what the options might be for the sleep mode network speed slow down (I do want to package it all up with GUI config and control options etc eventually, i suspect the sleep mode stuff will be easier to control this way too).
- JC
DocMAX said:
ich started samba via chroot debian. i can read and write the filesystem.. except mapped /sdcard... i cannot delete files... any ideas how to set permissions? the user is 1000 and group is 1015
Click to expand...
Click to collapse
So you're doing a chroot to somewhere else on the phone filesystem before starting samba, if i understand correctly?
Have you tested it without chroot to see if the problem still happens? Is there any indication of a permission problem reported in /data/local/samba/var/log.smbd ?
Is 1000 / 1015 the user/group of the files on the sdcard you are trying to delete, or the user / group you've set in samba.conf?
- JC
JimmyChingala said:
Hi Jack,
Nice work with your testing
Click to expand...
Click to collapse
Thanks
JimmyChingala said:
I'd like to take a look at all the file permissions samba unzip'd with and compare them to what they should be - could you post output of
ls -laR /data/local/samba
Click to expand...
Click to collapse
Please remember that I've changed the /bin/* permissions from 666 to 777, and it shows in the list below.
Here:
/data/local/samba:
drwxrwxrwx 1 root root 2048 May 17 00:20 .
drwxrwx--x 1 shell shell 2048 May 17 00:20 ..
-rw-rw-rw- 1 root root 4178 May 17 00:20 README.txt
drwxrwxrwx 1 root root 2048 May 17 00:20 bin
drwxrwxrwx 1 root root 2048 May 24 17:05 lib
drwxrwxrwx 1 root root 2048 May 19 20:10 private
drwxrwxrwx 1 root root 2048 May 17 00:23 var
/data/local/samba/bin:
drwxrwxrwx 1 root root 2048 May 17 00:20 .
drwxrwxrwx 1 root root 2048 May 17 00:20 ..
-rwxrwxrwx 1 root root 457952 May 17 00:20 killsamba
-rwxrwxrwx 1 root root 870592 May 17 00:20 nmbd
-rwxrwxrwx 1 root root 396 May 17 00:20 samba-rc
-rwxrwxrwx 1 root root 1839404 May 17 00:20 smbd
-rwxrwxrwx 1 root root 948992 May 17 00:20 smbpasswd
/data/local/samba/lib:
drwxrwxrwx 1 root root 2048 May 24 17:05 .
drwxrwxrwx 1 root root 2048 May 17 00:20 ..
drwxrwxrwx 1 root root 2048 May 17 00:20 codepages
----rwxr-x 1 root root 708 May 24 17:05 smb.conf
/data/local/samba/lib/codepages:
drwxrwxrwx 1 root root 2048 May 17 00:20 .
drwxrwxrwx 1 root root 2048 May 24 17:05 ..
-rw-rw-rw- 1 root root 588 May 17 00:20 codepage.1125
-rw-rw-rw- 1 root root 140 May 17 00:20 codepage.1251
-rw-rw-rw- 1 root root 196 May 17 00:20 codepage.437
-rw-rw-rw- 1 root root 148 May 17 00:20 codepage.737
-rw-rw-rw- 1 root root 388 May 17 00:20 codepage.775
-rw-rw-rw- 1 root root 132 May 17 00:20 codepage.850
-rw-rw-rw- 1 root root 172 May 17 00:20 codepage.852
-rw-rw-rw- 1 root root 132 May 17 00:20 codepage.857
-rw-rw-rw- 1 root root 460 May 17 00:20 codepage.861
-rw-rw-rw- 1 root root 588 May 17 00:20 codepage.866
-rw-rw-rw- 1 root root 8 May 17 00:20 codepage.932
-rw-rw-rw- 1 root root 8 May 17 00:20 codepage.936
-rw-rw-rw- 1 root root 8 May 17 00:20 codepage.949
-rw-rw-rw- 1 root root 8 May 17 00:20 codepage.950
-rw-rw-rw- 1 root root 131614 May 17 00:20 unicode_map.1125
-rw-rw-rw- 1 root root 131614 May 17 00:20 unicode_map.1251
-rw-rw-rw- 1 root root 131614 May 17 00:20 unicode_map.437
-rw-rw-rw- 1 root root 131614 May 17 00:20 unicode_map.737
-rw-rw-rw- 1 root root 131614 May 17 00:20 unicode_map.775
-rw-rw-rw- 1 root root 131614 May 17 00:20 unicode_map.850
-rw-rw-rw- 1 root root 131614 May 17 00:20 unicode_map.852
-rw-rw-rw- 1 root root 131614 May 17 00:20 unicode_map.857
-rw-rw-rw- 1 root root 131614 May 17 00:20 unicode_map.861
-rw-rw-rw- 1 root root 131614 May 17 00:20 unicode_map.866
-rw-rw-rw- 1 root root 262174 May 17 00:20 unicode_map.932
-rw-rw-rw- 1 root root 262174 May 17 00:20 unicode_map.936
-rw-rw-rw- 1 root root 262174 May 17 00:20 unicode_map.949
-rw-rw-rw- 1 root root 262174 May 17 00:20 unicode_map.950
-rw-rw-rw- 1 root root 131614 May 17 00:20 unicode_map.ISO8859-1
-rw-rw-rw- 1 root root 131614 May 17 00:20 unicode_map.ISO8859-13
-rw-rw-rw- 1 root root 131614 May 17 00:20 unicode_map.ISO8859-15
-rw-rw-rw- 1 root root 131614 May 17 00:20 unicode_map.ISO8859-2
-rw-rw-rw- 1 root root 131614 May 17 00:20 unicode_map.ISO8859-5
-rw-rw-rw- 1 root root 131614 May 17 00:20 unicode_map.ISO8859-7
-rw-rw-rw- 1 root root 131614 May 17 00:20 unicode_map.ISO8859-9
-rw-rw-rw- 1 root root 131614 May 17 00:20 unicode_map.KOI8-R
-rw-rw-rw- 1 root root 131614 May 17 00:20 unicode_map.KOI8-U
/data/local/samba/private:
drwxrwxrwx 1 root root 2048 May 19 20:10 .
drwxrwxrwx 1 root root 2048 May 17 00:20 ..
-rw------- 1 root root 8192 May 26 14:08 secrets.tdb
-rw------- 1 root root 101 May 19 20:10 smbpasswd
/data/local/samba/var:
drwxrwxrwx 1 root root 2048 May 17 00:23 .
drwxrwxrwx 1 root root 2048 May 17 00:20 ..
drwxrwxrwx 1 root root 2048 May 26 14:08 locks
-rw-r--r-- 1 root root 23957 May 26 14:08 log.nmbd
-rw-r--r-- 1 root root 37485 May 26 14:08 log.smbd
drwxrwxrwx 1 root root 2048 May 17 00:20 tmp
/data/local/samba/var/locks:
drwxrwxrwx 1 root root 2048 May 26 14:08 .
drwxrwxrwx 1 root root 2048 May 17 00:23 ..
-rw-r--r-- 1 root root 696 May 24 18:06 brlock.tdb
-rw-r--r-- 1 root root 154 May 24 18:06 browse.dat
-rw-r--r-- 1 root root 8192 May 26 14:08 connections.tdb
-rw-r--r-- 1 root root 696 May 24 18:06 locking.tdb
-rw------- 1 root root 696 May 26 14:08 messages.tdb
-rw-r--r-- 1 root root 20 May 26 14:08 nmbd.pid
-rw------- 1 root root 8192 May 24 18:06 ntdrivers.tdb
-rw------- 1 root root 696 May 24 18:06 ntforms.tdb
-rw------- 1 root root 8192 May 24 18:06 ntprinters.tdb
-rw------- 1 root root 8192 May 24 18:06 printing.tdb
-rw------- 1 root root 8192 May 24 18:06 share_info.tdb
-rw-r--r-- 1 root root 20 May 26 14:08 smbd.pid
-rw-r--r-- 1 root root 16384 May 24 18:08 unexpected.tdb
/data/local/samba/var/tmp:
drwxrwxrwx 1 root root 2048 May 17 00:20 .
drwxrwxrwx 1 root root 2048 May 17 00:23 ..
JimmyChingala said:
smbpasswd probs: could you delete /data/local/samba/private/smbpasswd and add a user with bin/smpasswd using '-a' rather than '-add', like
/data/local/samba/bin/smbpasswd -a jackthen re-enable authentication in the config file and see how it goes?
Click to expand...
Click to collapse
Did so. It didn't work, but it helped me better understand one more symptom.
1) When adding with "-a", it accepted the new password and didn't crash.
2) I still couldn't login with the user.
3) I tried using debug options ("-i -d 99") and got it exiting after login attempts (login still failed).
4) I created a Samba user with the same name as Windows user, and tried to log in. This time it searched and found the password, but then crashed with the following error (this is the end of the log file):
[000] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ........ ........
[010] 00 00 00 00 00 00 00 00 51 97 2D 64 E2 C4 1E 10 ........ Q.-d....
[020] C2 C0 E9 19 DB 64 5B 98 01 01 00 00 00 00 00 00 .....d[. ........
[030] 0F A7 B4 B3 DF FD CA 01 D0 DE 19 BB 42 22 52 CA ........ ....B"R.
[040] 00 00 00 00 02 00 12 00 57 00 4F 00 52 00 4B 00 ........ W.O.R.K.
[050] 47 00 52 00 4F 00 55 00 50 00 00 00 00 00 00 00 G.R.O.U. P.......
[060] 00 00 4B 69 73 75 6C 79 61 00 4B 69 73 75 6C 79 ..Kisuly a.Kisuly
[070] 61 2D 50 43 00 00 00 a-PC...
switch message SMBsesssetupX (pid 1988)
created /data/local/samba/var/tmp/SMBsesssetupX.8.req len 220
setting sec ctx (0, 0) - sec_ctx_stack_ndx = 0
change_to_root_user: now uid=(0,0) gid=(0,0)
passlen1=24, passlen2=74
Domain=[Kisulya-PC] NativeOS=[] NativeLanMan=[]
sesssetupX:name=[Kisulya]
lp_file_list_changed()
file /data/local/samba/lib/smb.conf -> /data/local/samba/lib/smb.conf last mod_time: Thu May 27 20:36:57 2010
pass_check: Checking password for user kisulya (l=74)
NT Password did not match for user 'kisulya'!
Defaulting to Lanman password for kisulya
pdb_getsampwnam: search by name: kisulya
startsmbfilepwent_internal: opening file /data/local/samba/private/smbpasswd
getsmbfilepwent: returning passwd entry for user jack, uid 0
getsmbfilepwent: returning passwd entry for user kisulya, uid 0
endsmbfilepwent_internal: closed password file.
pdb_getsampwnam: found by name: kisulya
===============================================================
INTERNAL ERROR: Signal 11 in pid 1988 (2.2.12 Android build (JimmyChingala))
Please read the file BUGS.txt in the distribution
===============================================================
PANIC: internal error
I guess I'll ask you for a debug version of the build, that logs every step in the password checking under debug mode. "Signal 11" isn't too clear
Hi Jack, your file permissions look mostly ok - ive assembled the sambaArchive differently now, should hopefully avoid the permission probs you saw.
Tracked down the cause of smbd crashing in debug mode too, so we should be able to get some proper debug info about whats happening to authentication.
The bin/smbpasswd segfaults are fixed - adding/removing users, changing passwords seems to work ok.
Have attached the updated archive sambaAndroid-0.3.zip to my other post in this thread.
- JC
Great work, Jimmy. Tested, and everything looks functional.
Adding user works.
Removing user works.
Authentication works - also tested with non-default user.
Things left:
Auto-detect local network interface on start / on install.
Prevent slowdown in sleep mode.
Thanks a lot for making it work!
Damn, just got home and tested on my system. I guess it was too fast to declare it's fully functional.
Jimmy, I suppose you're testing it on Windows XP? Because it definitely works on XP, as I wrote earlier. But the problem is that once I start using Windows 7, the authentication mechanism changes somehow (my guess, it also could be the protocol - I didn't save the logs so I didn't note the difference, and I don't have XP at home) - and I can't login anymore. I've logged the server output and it looks like no matter what username is provided - Win7 uses its current logged in user to connect to the sharing device (user-level login to the system before logging in to the share itself - this is how Samba is configured), which ultimately results in login failure.
I'll record a successful XP log and an unsuccessful Win7 log tomorrow and post them, but I'm not sure that something can be deduced from them, since they just show different passwords (and Win7 log also shows server exiting when trying to log in with correct user/password, something that doesn't happen on XP - but at least this time it's graceful logged exit, thanks to your fix).
I suggest you test logging in from Vista or Win7 machine with a username that isn't the logged in Windows user.
Thanks for your testing and feedback, Jack!
I'm testing with Vista and XP - no Win7 yet.
A couple of things to double check:
- If the phone has been in sleep mode for an extended period, or wifi switched off, then on again, and if a "samba-rc restart" has not been done, strange auth problems will happen. (This shouldnt be a problem if using the dhcp hook script to auto-restart samba).
- Cached session credentials on the client or server can also play havoc with authentication - check "net use" in a cmd shell on your Win client to see if there is cached session info for the phone, and if there is, do a "net use /delete \\phoneIP\IPC$" to delete it. (On the server side, cached information is deleted each time the samba is started).
Manually running "/data/local/samba/bin/samba-rc restart" in adb or ssh root shell on your phone (when not in sleep mode) should fix the above two issues on the server side.
Otherwise take a look at
http://www.builderau.com.au/blogs/codemonkeybusiness/viewblogpost.htm?p=339270746
And see what your 'LAN Manager authentication level' defaults to. On my Vista system, its already set to "Send LM & NTLM - use NTLMv2 session security if negotiated". I dont remember changing this, I think it was the default on my Vista install - maybe i did change it, up late and half asleep one night .
Anyway, samba2 doesnt support NTLMv2 authentication but i think the workaround in the above URL will address this - if its the problem.. (I'm already working on porting a version of Samba3 that has NTLMv2 auth, but the code is significantly different that i cand just edit the same files and change the same blocks of code ).
- JC
Hello,
I'm using a rooted wildfire with original HTC rom.
I have installed Droid Explorer; I can explore my HTC without problems, but I cannot enter /data folder for example (I can "cd" to it if using adb directly).
Opening debug console , I can see that Droid Explorer sends the correct command and it gets the correct output, but IT doesn't publish it in the explorer window.
Why? Is someone using Droid explorer? thank you.
debug console output:
[CommandRunner] adb.exe -s HT079xxxxxx shell busybox ls -lF --color=never "/data/"
[CommandRunner] total 34
drwxrwxrwx 1 0 0 2048 Jan 6 1980 DxDrm/
drwxrwx--x 1 1000 1000 2048 Nov 15 11:00 anr/
drwxrwx--x 1 1000 1000 2048 Jan 6 1980 app/
drwxrwx--x 1 1000 1000 2048 Jan 6 1980 app-private/
drwx------ 1 1000 1000 2048 Jan 6 1980 backup/
drwxrwx--x 1 1000 1000 2048 Jan 6 1980 dalvik-cache/
drwxrwx--x 1 1000 1000 2048 Jan 6 1980 data/
drwxr-x--- 1 0 1007 2048 Jan 6 1980 dontpanic/
lrwxrwxrwx 1 0 0 11 Jan 6 1980 drm -> /data/local/
prw-r--r-- 1 1000 1000 2048 Aug 24 15:21 gps_nmea_fifo|
-rw-rw-rw- 1 1013 1000 0 Aug 24 15:01 http_proxy
srwxrwxrwx 1 0 1002 2048 Nov 11 13:15 inc_data_path=
drwxrwx--x 1 2000 2000 2048 Jan 6 1980 local/
drwxrwx--- 1 0 0 2048 Jan 6 1980 lost+found/
drwxrwx--t 1 1000 9998 2048 Jan 6 1980 misc/
drwx------ 1 0 0 2048 Nov 15 10:58 property/
-rw-rw-rw- 1 1013 1000 2 Nov 15 12:18 pvcodec.txt
-rw-rw-rw- 1 0 2000 161 Aug 29 20:05 reboot.chk
-rw-rw-rw- 1 1013 1000 0 Aug 24 15:01 rtsp_proxy
drwxrwxr-x 1 1000 1000 2048 Nov 15 12:27 system/
drwxr-xr-x 1 1000 1000 2048 Oct 1 20:53 tombstones/
[Program] Impossibile confrontare due elementi nella matrice. - System.InvalidOperationException: Impossibile confrontare due elementi nella matrice. ---> System.NullReferenceException: Riferimento a un oggetto non impostato su un'istanza di oggetto.
in DroidExplorer.Components.FileSystemInfoComparer.CompareFileSystemInfo x, FileSystemInfo y in s:\projects\csharp\DroidExplorer\trunk\DroidExplorer\DroidExplorer.Core\Components\FileSystemInfoComparer.cs:riga 8
in System.Collections.Generic.ArraySortHelper`1.SwapIfGreaterWithItemsT[] keys, IComparer`1 comparer, Int32 a, Int32 b
in System.Collections.Generic.ArraySortHelper`1.QuickSortT[] keys, Int32 left, Int32 right, IComparer`1 comparer
in System.Collections.Generic.ArraySortHelper`1.SortT[] keys, Int32 index, Int32 length, IComparer`1 comparer
--- Fine dell'analisi dello stack dell'eccezione interna ---
in System.Collections.Generic.ArraySortHelper`1.SortT[] keys, Int32 index, Int32 length, IComparer`1 comparer
in System.Array.Sort[T]T[] array, Int32 index, Int32 length, IComparer`1 comparer
in System.Collections.Generic.List`1.SortInt32 index, Int32 count, IComparer`1 comparer
in System.Collections.Generic.List`1.SortIComparer`1 comparer
in DroidExplorer.Core.CommandRunner.GetDirectoryContentsString device, String path in s:\projects\csharp\DroidExplorer\trunk\DroidExplorer\DroidExplorer.Core\CommandRunner.cs:riga 1534
in DroidExplorer.Core.CommandRunner.GetDirectoryContentsString path in s:\projects\csharp\DroidExplorer\trunk\DroidExplorer\DroidExplorer.Core\CommandRunner.cs:riga 1522
in DroidExplorer.Core.UI.Components.DirectoryTreeNode.OnAfterSelectCommandRunner runner in s:\projects\csharp\DroidExplorer\trunk\DroidExplorer\DroidExplorer.Core.UI\Components\DirectoryTreeNode.cs:riga 39
in DroidExplorer.UI.MainForm.NavigateToPathLinuxDirectoryInfo path, Boolean addHistory
in DroidExplorer.UI.MainForm.directoryTree_AfterSelectObject sender, TreeViewEventArgs e
in System.Windows.Forms.TreeView.OnAfterSelectTreeViewEventArgs e
in System.Windows.Forms.TreeView.TvnSelectedNMTREEVIEW* nmtv
in System.Windows.Forms.TreeView.WmNotifyMessage& m
in System.Windows.Forms.TreeView.WndProcMessage& m
in System.Windows.Forms.Control.ControlNativeWindow.OnMessageMessage& m
in System.Windows.Forms.Control.ControlNativeWindow.WndProcMessage& m
in System.Windows.Forms.NativeWindow.CallbackIntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam
Hi guys, Total Noob here.
I've been reading through the forums over the last week and am still at a total loss. Despite trying numerous things, nothing I've tried has worked.. If anything, I'm afraid I've made things worse.
The back story: The NC we have is a newer one purchased *just* over a year ago, given to my 10yr old daughter as a bday gift. It's never been rooted or modded in anyway whatsoever. Two weeks ago while she was playing a game on it, it locked up, and wouldn't power off. We let it sit for a couple of days for the battery to drain. After that, the battery wouldn't charge, the NC would not boot and the cable indicator stayed orange. So I purchased, and replaced the battery. I let it sit overnight after replacing the battery, and we got a green light. On boot up, it would hang at the 'N Screen', and do nothing more.
I tried running the NC recovery, but that only resulted in an "INSTALL FAILED" error message, and that was the last sign of life to have been seen coming out of the NC.
At this point, it will only boot off the SD card, (currently using an 8gb with CWR 6.0.1.2), I no longer get even the 'N screen' anymore. I've tried leapinlars partitioning and formatting .zips, I've tried every stock image I could find, but the result is always the same. No partitions are mounted, and nothing but errors are generated.
I've tried connecting through ADB, but 'ADB DEVICES" only returns:
Code:
C:\android-sdk-windows\platform-tools>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
0000000000000000 recovery
...and nothing more.
Since this NC is for my daughters use, I'm really not interested in rooting or opening up android for her, I'd really like it to be nothing more than stock, but at this point I'd be grateful just to see some sign of life come out of this thing. All help would be greatly appreciated.
I hope I've provided enough info, anybody have a clue whats going on here?
Some other screen grabs from adb:
Code:
C:\android-sdk-windows\platform-tools>adb shell
~ # ls -l
ls -l
drwxr-xr-x 2 root root 0 Jan 9 05:40 boot
drwxr-xr-x 2 root root 0 Jan 9 05:40 cache
drwxr-xr-x 2 root root 0 Jan 1 1970 data
drwxr-xr-x 2 root root 0 Jan 9 05:40 datadata
-rw-r--r-- 1 root root 2553 Jan 1 1970 default.prop
drwxr-xr-x 10 root root 2440 Jan 9 05:40 dev
drwxr-xr-x 2 root root 0 Jan 9 05:40 emmc
drwxr-xr-x 2 root root 0 Jan 9 05:40 etc
-rwxr-x--- 1 root root 98756 Jan 1 1970 init
-rwxr-x--- 1 root root 1415 Jan 1 1970 init.rc
dr-xr-xr-x 64 root root 0 Jan 1 1970 proc
drwxr-xr-x 3 root root 0 Jan 1 1970 res
drwxrwxrwx 2 root root 0 Jan 9 05:40 rom
drwx------ 2 root root 0 Sep 21 2011 root
drwxr-x--- 2 root root 0 Jan 1 1970 sbin
drwxr-xr-x 2 root root 0 Jan 9 05:40 sd-ext
drwxr-xr-x 2 root root 0 Jan 9 05:40 sdcard
drwxr-xr-x 12 root root 0 Jan 1 1970 sys
drwxr-xr-x 3 root root 0 Jan 1 1970 system
drwxr-xr-x 2 root root 0 Jan 9 05:40 tmp
-rw-r--r-- 1 root root 32 Jan 1 1970 ueventd.encore.rc
-rw-r--r-- 1 root root 272 Jan 1 1970 ueventd.goldfish.rc
-rw-r--r-- 1 root root 3825 Jan 1 1970 ueventd.rc
~ #
and
Code:
fdisk -l
returns nothing except for the command 'fdisk -l' being echoed back to the screen.
Even though I can boot with CWM; when booting CWM, it displays the following error messages
Code:
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
When trying to install "NookColor-emmc-repair-partitions-1-4-5-6-7-8.zip", I get:
Code:
-- Installing: /sdcard/NookColor-emmc-repair-partitions-1-4-5-6-7-8.zip
E:Can't mount /cache/recovery/last_install
E:failed to open last_install: No such file or directory
Finding update package...
Opening update package...
Installing update...
Repartition /boot, /system, /data (1GB), /cache and /media
Repartitioning internal memory - be patient this may take a while
Done. YOU MUST REBOOT TO RELOAD THE PARTITION TABLE
Install from sdcard complete.
Then, rebooting and installing "NookColor-emmc-format-partitions-5-6-7-8.zip" generates the following output instantly, with absolutely no delay when the formatting should be occuring:
Code:
-- Installing: /sdcard/NookColor-emmc-format-partitions-5-6-7-8.zip
E:Can't mount /cache/recovery/last_install
E:failed to open last_install: No such file or directory
Finding update package...
Opening update package...
Installing update...
Reformatting /system, /data, /cache, and /media
Reformatting /system (0p5)
This may take some time, please be patient
Reformatting /data (0p6)
This may take some time, please be patient
Reformatting /cache (0p7)
This may take some time, please be patient
Reformatting /media (0p8)
This may take some time, please be patient
Done.
Install from sdcard complete.
Trying "NookColor-emmc-repair-partition-2.zip", ends with:
Code:
-- Installing: /sdcard/NookColor-emmc-repair-partition-2.zip
E:Can't mount /cache/recovery/last_install
E:failed to open last_install: No such file or directory
Finding update package...
Opening update package...
Installing update...
Repair /rom partition (P2)
Checking for /factory - if not found will return error message and repair will be aborted.
assert failed: mount("ext2", "EMMC", "/dev/block/mmcblk0p3", "/factory") == "/factory"
E:Error in /sdcard/NookColor-emmc-repair-partition-2.zip
(Status 7)
Installation aborted.
and then after not making progress with those; trying "NookColor-emmc-stockrecovery-CWM6012asAlt.zip" returns:
Code:
-- Installing: /sdcard/NookColor-emmc-stockrecovery-CWM6012asAlt.zip
E:Can't mount /cache/recovery/last_install
E:failed to open last_install: No such file or directory
Finding update package...
Opening update package...
Installing update...
Installing Stock Recovery to EMMC with CWM 6.0.1.2 as Alternate
-----------------------------------------
Done
Install from sdcard complete.
, ...with still no recovery process being possible.
MaGoober said:
Some other screen grabs from adb:
Code:
C:\android-sdk-windows\platform-tools>adb shell
~ # ls -l
ls -l
drwxr-xr-x 2 root root 0 Jan 9 05:40 boot
drwxr-xr-x 2 root root 0 Jan 9 05:40 cache
drwxr-xr-x 2 root root 0 Jan 1 1970 data
drwxr-xr-x 2 root root 0 Jan 9 05:40 datadata
-rw-r--r-- 1 root root 2553 Jan 1 1970 default.prop
drwxr-xr-x 10 root root 2440 Jan 9 05:40 dev
drwxr-xr-x 2 root root 0 Jan 9 05:40 emmc
drwxr-xr-x 2 root root 0 Jan 9 05:40 etc
-rwxr-x--- 1 root root 98756 Jan 1 1970 init
-rwxr-x--- 1 root root 1415 Jan 1 1970 init.rc
dr-xr-xr-x 64 root root 0 Jan 1 1970 proc
drwxr-xr-x 3 root root 0 Jan 1 1970 res
drwxrwxrwx 2 root root 0 Jan 9 05:40 rom
drwx------ 2 root root 0 Sep 21 2011 root
drwxr-x--- 2 root root 0 Jan 1 1970 sbin
drwxr-xr-x 2 root root 0 Jan 9 05:40 sd-ext
drwxr-xr-x 2 root root 0 Jan 9 05:40 sdcard
drwxr-xr-x 12 root root 0 Jan 1 1970 sys
drwxr-xr-x 3 root root 0 Jan 1 1970 system
drwxr-xr-x 2 root root 0 Jan 9 05:40 tmp
-rw-r--r-- 1 root root 32 Jan 1 1970 ueventd.encore.rc
-rw-r--r-- 1 root root 272 Jan 1 1970 ueventd.goldfish.rc
-rw-r--r-- 1 root root 3825 Jan 1 1970 ueventd.rc
~ #
and
Code:
fdisk -l
returns nothing except for the command 'fdisk -l' being echoed back to the screen.
Even though I can boot with CWM; when booting CWM, it displays the following error messages
Code:
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
When trying to install "NookColor-emmc-repair-partitions-1-4-5-6-7-8.zip", I get:
Code:
-- Installing: /sdcard/NookColor-emmc-repair-partitions-1-4-5-6-7-8.zip
E:Can't mount /cache/recovery/last_install
E:failed to open last_install: No such file or directory
Finding update package...
Opening update package...
Installing update...
Repartition /boot, /system, /data (1GB), /cache and /media
Repartitioning internal memory - be patient this may take a while
Done. YOU MUST REBOOT TO RELOAD THE PARTITION TABLE
Install from sdcard complete.
Then, rebooting and installing "NookColor-emmc-format-partitions-5-6-7-8.zip" generates the following output instantly, with absolutely no delay when the formatting should be occuring:
Code:
-- Installing: /sdcard/NookColor-emmc-format-partitions-5-6-7-8.zip
E:Can't mount /cache/recovery/last_install
E:failed to open last_install: No such file or directory
Finding update package...
Opening update package...
Installing update...
Reformatting /system, /data, /cache, and /media
Reformatting /system (0p5)
This may take some time, please be patient
Reformatting /data (0p6)
This may take some time, please be patient
Reformatting /cache (0p7)
This may take some time, please be patient
Reformatting /media (0p8)
This may take some time, please be patient
Done.
Install from sdcard complete.
Trying "NookColor-emmc-repair-partition-2.zip", ends with:
Code:
-- Installing: /sdcard/NookColor-emmc-repair-partition-2.zip
E:Can't mount /cache/recovery/last_install
E:failed to open last_install: No such file or directory
Finding update package...
Opening update package...
Installing update...
Repair /rom partition (P2)
Checking for /factory - if not found will return error message and repair will be aborted.
assert failed: mount("ext2", "EMMC", "/dev/block/mmcblk0p3", "/factory") == "/factory"
E:Error in /sdcard/NookColor-emmc-repair-partition-2.zip
(Status 7)
Installation aborted.
and then after not making progress with those; trying "NookColor-emmc-stockrecovery-CWM6012asAlt.zip" returns:
Code:
-- Installing: /sdcard/NookColor-emmc-stockrecovery-CWM6012asAlt.zip
E:Can't mount /cache/recovery/last_install
E:failed to open last_install: No such file or directory
Finding update package...
Opening update package...
Installing update...
Installing Stock Recovery to EMMC with CWM 6.0.1.2 as Alternate
-----------------------------------------
Done
Install from sdcard complete.
, ...with still no recovery process being possible.
Click to expand...
Click to collapse
You need to type
fdisk -l /dev/block/mmcblk0
in ADB. That will show you the partition structure of emmc. I suspect your cylinder/head/sector count is messed up. That is why my zips appear to work, but do not.
Report here the output of the command.
Sent from my Galaxy Tab 2 using XDA Premium
leapinlar said:
You need to type
fdisk -l /dev/block/mmcblk0
in ADB. That will show you the partition structure of emmc. I suspect your cylinder/head/sector count is messed up. That is why my zips appear to work, but do not.
Report here the output of the command.
Sent from my Galaxy Tab 2 using XDA Premium
Click to expand...
Click to collapse
Thanks for the suggestion leapinlar, I assumed fdisk -l would show all disk info by default if a specific disk wasnt specified. For some reason when I plugged the NC into the USB port today, My Win7 box did not recognize it or want to reload the drivers the same way it did last night, and I was unable to connect to the NC through ADB.
I will try to figure out that later on, or try to use ADB through my Fedora box when I get a chance. In the meantime, I once again tried your repair-partions.zip and copied CWM's error log, which is pasted below. Hopefully this gives some insight:
Starting recovery on Sun Jan 9 18:13:58 2000
framebuffer: fd 4 (1024 x 600)
CWM-based Recovery v6.0.1.2
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null) 0
1 /boot vfat /dev/block/mmcblk0p1 (null) 0
2 /system ext4 /dev/block/mmcblk0p5 (null) 0
3 /data ext4 /dev/block/mmcblk0p6 (null) 0
4 /cache ext4 /dev/block/mmcblk0p7 (null) 0
5 /emmc vfat /dev/block/mmcblk0p8 (null) 0
6 /sdcard vfat /dev/block/mmcblk1p1 (null) 0
7 /sd-ext ext4 /dev/block/mmcblk1p8 (null) 0
W:Unable to get recovery.fstab info for /datadata during fstab generation!
I:Completed outputting fstab.
Irocessing arguments.
W:failed to mount /dev/block/mmcblk0p7 (No such file or directory)
E:Can't mount /cache/recovery/command
I:Checking arguments.
I:device_recovery_start()
Command: "/sbin/recovery"
ro.secure=0
ro.allow.mock.location=0
ro.debuggable=1
persist.sys.usb.config=mtp,adb
ro.build.id=IMM76D
ro.build.display.id=IMM76D
ro.build.version.incremental=eng.larry.20121021.181637
ro.build.version.sdk=15
ro.build.version.codename=REL
ro.build.version.release=4.0.4
ro.build.date=Sun Oct 21 18:17:05 PDT 2012
ro.build.date.utc=0
ro.build.type=userdebug
ro.build.user=larry
ro.build.host=larry-HP-Pavilion-dm4-Ubuntu
ro.build.tags=test-keys
ro.product.model=NookColor
ro.product.brand=bn
ro.product.name=encore
ro.product.device=encore
ro.product.board=encore
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=bn
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=omap3
ro.build.product=encore
ro.build.description=encore-user 4.0.4 IMM76D 228551 release-keys
ro.build.fingerprint=bn/bn_encore/encore:4.0.4/IMM76D/228551:user/release-keys
ro.build.characteristics=tablet
ro.cm.device=encore
wifi.interface=tiwlan0
wifi.supplicant_scan_interval=30
ro.additionalmounts=/mnt/emmc;/mnt/usbdisk
ro.vold.switchablepair=/mnt/sdcard,/mnt/emmc
ro.pm.awake_on_usb=1
ro.cwm.forbid_format=/boot
ro.sf.hwrotation=270
ro.emmc=1
com.ti.omap_compat=true
ro.magic.optimization=ZOMG
ro.com.android.dateformat=MM-dd-yyyy
dalvik.vm.heapstartsize=5m
dalvik.vm.heapgrowthlimit=48m
dalvik.vm.heapsize=256m
alsa.mixer.playback.master=default
alsa.mixer.capture.master=Analog
ro.opengles.version=131072
ro.rommanager.developerid=cyanogenmod
keyguard.no_require_sim=true
ro.url.legal=(link removed)
ro.url.legal.android_privacy=(link removed)
ro.com.google.clientidbase=android-google
ro.com.android.wifi-watchlist=GoogleGuest
ro.setupwizard.enterprise_mode=1
ro.com.android.dataroaming=false
ro.cm.version=9-20121022-UNOFFICIAL-encore
ro.modversion=9-20121022-UNOFFICIAL-encore
ro.config.ringtone=CyanTone.ogg
ro.config.notification_sound=CyanMessage.ogg
ro.config.alarm_alert=CyanAlarm.ogg
dalvik.vm.lockprof.threshold=500
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
net.change=net.bt.name
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.factorytest=0
ro.serialno=
ro.bootmode=unknown
ro.baseband=unknown
ro.carrier=unknown
ro.bootloader=unknown
ro.hardware=encore
ro.revision=5
init.svc.recovery=running
service.adb.root=1
init.svc.adbd=running
I:Checking for extendedcommand...
I:Skipping execution of extendedcommand, file not found...
W:failed to mount /dev/block/mmcblk0p7 (No such file or directory)
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
W:failed to mount /dev/block/mmcblk0p7 (No such file or directory)
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
W:failed to mount /dev/block/mmcblk0p7 (No such file or directory)
W:Can't unlink /cache/recovery/command
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
-- Installing: /sdcard/NookColor-emmc-repair-partitions-1-4-5-6-7-8.zip
W:failed to mount /dev/block/mmcblk0p7 (No such file or directory)
E:Can't mount /cache/recovery/last_install
E:failed to open last_install: No such file or directory
Finding update package...
I:Update location: /sdcard/NookColor-emmc-repair-partitions-1-4-5-6-7-8.zip
Opening update package...
Installing update...
Repartition /boot, /system, /data (1GB), /cache and /media
Repartitioning internal memory - be patient this may take a whileabout to run program [/tmp/repartition.sh] with 1 args
Archive: /tmp/boot.zip
inflating: boot.img
144522+0 records in
144522+0 records out
73995264 bytes (70.6MB) copied, 1.259857 seconds, 56.0MB/s
Device contains neither a valid DOS partition table, nor Sun, SGI or OSF disklabel
Building a new DOS disklabel. Changes will remain in memory only,
until you decide to write them. After that the previous content
won't be recoverable.
The number of cylinders for this disk is set to 236032.
There is nothing wrong with that, but this is larger than 1024,
and could in certain setups cause problems with:
1) software that runs at boot time (e.g., old versions of LILO)
2) booting and partitioning software from other OSs
(e.g., DOS FDISK, OS/2 FDISK)
Command (m for help): No partition is defined yet!
Command (m for help): 4: unknown command
Command Action
a toggle a bootable flag
b edit bsd disklabel
c toggle the dos compatibility flag
d delete a partition
l list known partition types
n add a new partition
o create a new empty DOS partition table
p print the partition table
q quit without saving changes
s create a new empty Sun disklabel
t change a partition's system id
u change display/entry units
v verify the partition table
w write table to disk and exit
x extra functionality (experts only)
Command (m for help): Command action
e extended
p primary partition (1-4)
Partition number (1-4): Value is out of range
Partition number (1-4): Value is out of range
Partition number (1-4): Partition number (1-4): Value is out of range
Partition number (1-4): Value is out of range
Partition number (1-4): Partition number (1-4): Value is out of range
Partition number (1-4): Value is out of range
Partition number (1-4): Partition number (1-4): Value is out of range
Partition number (1-4): Value is out of range
Partition number (1-4): Partition number (1-4): Value is out of range
Partition number (1-4): Value is out of range
Partition number (1-4): Partition number (1-4): Value is out of range
Partition number (1-4): Partition number (1-4): Partition number (1-4): script result was [Done. You MUST REBOOT TO RELOAD THE PARTITION TABLE]
Done. You MUST REBOOT TO RELOAD THE PARTITION TABLE
Install from sdcard complete.
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
W:failed to mount /dev/block/mmcblk0p7 (No such file or directory)
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
W:failed to mount /dev/block/mmcblk0p7 (No such file or directory)
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
W:failed to mount /dev/block/mmcblk0p7 (No such file or directory)
W:Can't unlink /cache/recovery/command
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
I:Can't partition unsafe device: /dev/block/mmcblk1p1
I:Can't format unknown volume: /external_sd
I:Can't partition unsafe device: /dev/block/mmcblk0p8
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
Click to expand...
Click to collapse
leapinlar said:
You need to type
fdisk -l /dev/block/mmcblk0
....
Click to expand...
Click to collapse
Okay, got adb working again. Here's the result:
Code:
fdisk -l /dev/block/mmcblk0
Disk /dev/block/mmcblk0: 7734 MB, 7734296576 bytes
4 heads, 16 sectors/track, 236032 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/mmcblk0 doesn't contain a valid partition table
~ #
Well now, isnt that special?
So that got me curious and I took a look/see in the /dev/block folder:
Code:
/dev/block # ls
ls
loop0 loop4 mmcblk0 ram1 ram13 ram3 ram7
loop1 loop5 mmcblk0p1 ram10 ram14 ram4 ram8
loop2 loop6 platform ram11 ram15 ram5 ram9
loop3 loop7 ram0 ram12 ram2 ram6
/dev/block # ls -l
ls -l
brw------- 1 root root 7, 0 Jan 9 18:13 loop0
brw------- 1 root root 7, 1 Jan 9 18:13 loop1
brw------- 1 root root 7, 2 Jan 9 18:13 loop2
brw------- 1 root root 7, 3 Jan 9 18:13 loop3
brw------- 1 root root 7, 4 Jan 9 18:13 loop4
brw------- 1 root root 7, 5 Jan 9 18:13 loop5
brw------- 1 root root 7, 6 Jan 9 18:13 loop6
brw------- 1 root root 7, 7 Jan 9 18:13 loop7
brw------- 1 root root 179, 0 Jan 9 18:13 mmcblk0
-rw-rw-rw- 1 root root 73995264 Jan 9 18:14 mmcblk0p1
drwxr-xr-x 4 root root 80 Jan 9 18:13 platform
brw------- 1 root root 1, 0 Jan 9 18:13 ram0
brw------- 1 root root 1, 1 Jan 9 18:13 ram1
brw------- 1 root root 1, 10 Jan 9 18:13 ram10
brw------- 1 root root 1, 11 Jan 9 18:13 ram11
brw------- 1 root root 1, 12 Jan 9 18:13 ram12
brw------- 1 root root 1, 13 Jan 9 18:13 ram13
brw------- 1 root root 1, 14 Jan 9 18:13 ram14
brw------- 1 root root 1, 15 Jan 9 18:13 ram15
brw------- 1 root root 1, 2 Jan 9 18:13 ram2
brw------- 1 root root 1, 3 Jan 9 18:13 ram3
brw------- 1 root root 1, 4 Jan 9 18:13 ram4
brw------- 1 root root 1, 5 Jan 9 18:13 ram5
brw------- 1 root root 1, 6 Jan 9 18:13 ram6
brw------- 1 root root 1, 7 Jan 9 18:13 ram7
brw------- 1 root root 1, 8 Jan 9 18:13 ram8
brw------- 1 root root 1, 9 Jan 9 18:13 ram9
/dev/block # fdisk -l /dev/block/mmcblk0
fdisk -l /dev/block/mmcblk0
Disk /dev/block/mmcblk0: 7734 MB, 7734296576 bytes
4 heads, 16 sectors/track, 236032 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/mmcblk0 doesn't contain a valid partition table
/dev/block # fdisk -l /dev/block/mmcblk0p1
fdisk -l /dev/block/mmcblk0p1
Disk /dev/block/mmcblk0p1: 73 MB, 73995264 bytes
255 heads, 63 sectors/track, 8 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/block #
Strange, today when I opened adb, it appears that some of the entries in /dev/block have changed. mmcblk0p1 is gone and replaced with mmcblk1p1.
Yesterday I saw this
Code:
/dev/block # ls
ls
loop0 loop4 mmcblk0 ram1 ram13 ram3 ram7
loop1 loop5 mmcblk0p1 ram10 ram14 ram4 ram8
loop2 loop6 platform ram11 ram15 ram5 ram9
loop3 loop7 ram0 ram12 ram2 ram6
This is what I see today:
Code:
/dev/block # ls
ls
loop0 loop4 mmcblk0 ram0 ram12 ram2 ram6
loop1 loop5 mmcblk1 ram1 ram13 ram3 ram7
loop2 loop6 mmcblk1p1 ram10 ram14 ram4 ram8
loop3 loop7 platform ram11 ram15 ram5 ram9
/dev/block #
If my understanding is correct (and it's usually not) the "P1" indicates that this is "partition one" on the "mmcblock one" device. (or 'disk'). I'm further assuming that of the two devices shown (mmcblk0, and mmcblk1) one of them is my 8gb microsd card, and the other is the NC's internal 8gb memory. Which makes me wonder why yesterday's "ls" did not show both devices. Also makes me wonder what the 'p1' partition is, which disk it's really on, and why it appears to have moved.
I took a look at the geometries of the disks and the partition using fdisk again, I dont know what I should be looking for here, and dont know whats relevant and what isn't. I can see I have two disks of slightly different sizes, and a mystery partition of some sort that doesnt seem like it should fit on either of the two disks.
Code:
/dev/block # fdisk -l /dev/block/mmcblk0
fdisk -l /dev/block/mmcblk0
Disk /dev/block/mmcblk0: 7734 MB, 7734296576 bytes
4 heads, 16 sectors/track, 236032 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/mmcblk0 doesn't contain a valid partition table
/dev/block # fdisk -l /dev/block/mmcblk1
fdisk -l /dev/block/mmcblk1
Disk /dev/block/mmcblk1: 7948 MB, 7948206080 bytes
255 heads, 63 sectors/track, 966 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk1p1 * 1 38 305203+ b Win95 FAT32
/dev/block # fdisk -l /dev/block/mmcblk1p1
fdisk -l /dev/block/mmcblk1p1
Disk /dev/block/mmcblk1p1: 312 MB, 312528384 bytes
4 heads, 16 sectors/track, 9537 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Device Boot Start End Blocks Id System
/dev/block #
Ok. I feel real stupid, obviously the mmcblk1 device is the sdcard and the p1 partition on it is the fat32 partition on it. Still leaves me wondering what happened to the geometry on the internal memory. CHS looks way off. shouldn't it be more like that of my sdcard?
*** Second Update***
I'm pulling my hair out here. I tried to correct the CHS values...no love there, even after rebooting it remains unchanged.
Code:
~ # fdisk -C 965 -H 255 -S 63 /dev/block/mmcblk0
fdisk -C 965 -H 255 -S 63 /dev/block/mmcblk0
Device contains neither a valid DOS partition table, nor Sun, SGI, OSF or GPT disklabel
Building a new DOS disklabel. Changes will remain in memory only,
until you decide to write them. After that the previous content
won't be recoverable.
Command (m for help): w
w
The partition table has been altered.
Calling ioctl() to re-read partition table
~ # fdisk -l /dev/block/mmcblk0
fdisk -l /dev/block/mmcblk0
Disk /dev/block/mmcblk0: 7734 MB, 7734296576 bytes
4 heads, 16 sectors/track, 236032 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/mmcblk0 doesn't contain a valid partition table
After trying to fix the geometry several times, and failing. I said Eff this, and tried living with the incorrect values and creating the partitions anyway. I keep getting fdisk: short write, when creating partition 8.
Anway....from start to finish here - notice the # of cylinders as I progress.
Code:
~ # fdisk -l /dev/block/mmcblk0
fdisk -l /dev/block/mmcblk0
Disk /dev/block/mmcblk0: 7734 MB, 7734296576 bytes
4 heads, 16 sectors/track, 236032 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/mmcblk0 doesn't contain a valid partition table
~ # fdisk -C 965 -H 255 -S 63 /dev/block/mmcblk0
fdisk -C 965 -H 255 -S 63 /dev/block/mmcblk0
Device contains neither a valid DOS partition table, nor Sun, SGI, OSF or GPT disklabel
Building a new DOS disklabel. Changes will remain in memory only,
until you decide to write them. After that the previous content
won't be recoverable.
Command (m for help): n
n
Command action
e extended
p primary partition (1-4)
p
p
Partition number (1-4):
Value is out of range
Partition number (1-4): 1
1
First cylinder (1-940, default 1):
Using default value 1
Last cylinder or +size or +sizeM or +sizeK (1-940, default 940): 9
9
Command (m for help): n
n
Command action
e extended
p primary partition (1-4)
p
p
Partition number (1-4): 2
2
First cylinder (10-940, default 10):
Using default value 10
Last cylinder or +size or +sizeM or +sizeK (10-940, default 940): 18
18
Command (m for help): n
n
Command action
e extended
p primary partition (1-4)
p
p
Partition number (1-4): 3
3
First cylinder (19-940, default 19):
Using default value 19
Last cylinder or +size or +sizeM or +sizeK (19-940, default 940): 56
56
Command (m for help): n
n
Command action
e extended
p primary partition (1-4)
e
e
Selected partition 4
First cylinder (57-940, default 57):
Using default value 57
Last cylinder or +size or +sizeM or +sizeK (57-940, default 940):
Using default value 940
Command (m for help): n
n
First cylinder (57-940, default 57):
Using default value 57
Last cylinder or +size or +sizeM or +sizeK (57-940, default 940): 114
114
Command (m for help): n
n
First cylinder (115-940, default 115):
Using default value 115
Last cylinder or +size or +sizeM or +sizeK (115-940, default 940): 236
236
Command (m for help): n
n
First cylinder (237-940, default 237):
Using default value 237
Last cylinder or +size or +sizeM or +sizeK (237-940, default 940): 281
281
Command (m for help):
at this point, I'll stop and review the changes before I commit (w) them to disk...
Code:
Command (m for help): p
p
Disk /dev/block/mmcblk0: 7734 MB, 7734296576 bytes
255 heads, 63 sectors/track, 940 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 1 9 72261 83 Linux
/dev/block/mmcblk0p2 10 18 72292+ 83 Linux
/dev/block/mmcblk0p3 19 56 305235 83 Linux
/dev/block/mmcblk0p4 57 940 7100730 5 Extended
/dev/block/mmcblk0p5 57 114 465853+ 83 Linux
/dev/block/mmcblk0p6 115 236 979933+ 83 Linux
/dev/block/mmcblk0p7 237 281 361431 83 Linux
Okay, Now the number of cylinders originally being reported was 236032, I specified 965 using the -C switch, and somehow ended up with a value of 940 - still leaving the geometry out of whack. Before I go any further I will commit and (w) the pending partition table here ...
Code:
Command (m for help): w
w
The partition table has been altered.
Calling ioctl() to re-read partition table
~ # fdisk -l /dev/block/mmcblk0
fdisk -l /dev/block/mmcblk0
Disk /dev/block/mmcblk0: 7734 MB, 7734296576 bytes
255 heads, 63 sectors/track, 940 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 1 9 72261 83 Linux
/dev/block/mmcblk0p2 10 18 72292+ 83 Linux
/dev/block/mmcblk0p3 19 56 305235 83 Linux
/dev/block/mmcblk0p4 57 940 7100730 5 Extended
/dev/block/mmcblk0p5 57 114 465853+ 83 Linux
/dev/block/mmcblk0p6 115 236 979933+ 83 Linux
/dev/block/mmcblk0p7 237 281 361431 83 Linux
~ #
So it appears my partition table has been written successfully. I just need to create partition 8. ... before I do that, I will reboot the NC to make sure the partition table is persistent...
Code:
fdisk -l /dev/block/mmcblk0
Disk /dev/block/mmcblk0: 7734 MB, 7734296576 bytes
4 heads, 16 sectors/track, 236032 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/mmcblk0 doesn't contain a valid partition table
...and that's a big fat fail.
At this point, It looks like my only option to ever use this NC again, is to have a stand alone bootable sd card. If anybody has a suggestion, please throw it my way.
Do either of these things indicate anything of importance that could potentially be of help?
1) 'adb devices' lists the Device ID as "RECOVERY"
2) The internal memory seems to be in a 'read only' mode of some sort.
The last time this NC did power up under its own free will, was when the stock recovery was being attempted - and crashed.
MaGoober said:
Do either of these things indicate anything of importance that could potentially be of help?
1) 'adb devices' lists the Device ID as "RECOVERY"
2) The internal memory seems to be in a 'read only' mode of some sort.
The last time this NC did power up under its own free will, was when the stock recovery was being attempted - and crashed.
Click to expand...
Click to collapse
Your CHS (cylinder, head, sector) settings are wrong. It should be 255 heads, 63 sectors/track and 965 cylinders. You need to run fdisk CHS to fix it. You need to type the following command in ADB shell.
fdisk -C 965 -H 255 -S 63 /dev/block/mmcblk0
Then do an
fdisk -l /dev/block/mmcblk0
to see what you get.
If the CHS is right you can do my 145678 repair and format. I don't know if the p2 repair will work though. If not, I may be able to help.
Sent from my Galaxy Tab 2 using XDA Premium
leapinlar said:
Your CHS (cylinder, head, sector) settings are wrong. It should be 255 heads, 63 sectors/track and 965 cylinders. You need to run fdisk CHS to fix it. You need to type the following command in ADB shell.
fdisk -C 965 -H 255 -S 63 /dev/block/mmcblk0
Then do an
fdisk -l /dev/block/mmcblk0
to see what you get.
If the CHS is right you can do my 145678 repair and format. I don't know if the p2 repair will work though. If not, I may be able to help.
Sent from my Galaxy Tab 2 using XDA Premium
Click to expand...
Click to collapse
Here's the result - as before, it just doesn't 'stick'.
Code:
C:\android-sdk-windows\platform-tools>adb shell
~ # fdisk -C 965 -H 255 -S 63 /dev/block/mmcblk0
fdisk -C 965 -H 255 -S 63 /dev/block/mmcblk0
Device contains neither a valid DOS partition table, nor Sun, SGI, OSF or GPT disklabel
Building a new DOS disklabel. Changes will remain in memory only,
until you decide to write them. After that the previous content
won't be recoverable.
Command (m for help): w
w
The partition table has been altered.
Calling ioctl() to re-read partition table
~ # fdisk -l /dev/block/mmcblk0
fdisk -l /dev/block/mmcblk0
Disk /dev/block/mmcblk0: 7734 MB, 7734296576 bytes
4 heads, 16 sectors/track, 236032 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/mmcblk0 doesn't contain a valid partition table
~ #
Thanks for your help, I really do appreciate it.
I may be crazy here, but what are the odds my NC does not have the same emmc chip? This thing sure acts like its fallen victim to the 'brick bug'. I cant seem to write anything at all, Tried creating new partitions with parted, no go. Even tried overwriting the mbr with dd if=/dev/zero of=/dev/block/mmcblk0 bs=512 count=1 and it didnt even touch it.
MaGoober said:
I may be crazy here, but what are the odds my NC does not have the same emmc chip? This thing sure acts like its fallen victim to the 'brick bug'. I cant seem to write anything at all, Tried creating new partitions with parted, no go. Even tried overwriting the mbr with dd if=/dev/zero of=/dev/block/mmcblk0 bs=512 count=1 and it didnt even touch it.
Click to expand...
Click to collapse
I have had SD chips that became ready only by some mysterious means. It is possible that your emmc has done the same. In fact, one other user said that happened to his emmc.
Sent from my Galaxy Tab 2 using XDA Premium
Alrighty then, I confirmed this much at least:
with
Code:
dmesg | grep mmc0
The emmc chip in my NC is the Samsung M8G2FA, which is prone to the "Brick Bug", and from the little I've read on it so far, the bug is brought on merely by wiping the cache partitions clean. I got me some more reading up to do...
Today, I called BN tech support for the second time in a week, after visiting the local store to see if anybody there could offer up assistance. Long story short, because our NC was just out of warranty (by three weeks) they did offer to exchange it with a 'certified pre-owned' . When that comes in, the very first thing I'm going to do is see what memory chip it has in it, Evidently just trying to do a 'hard reset' and run the stock recovery bricks the M8G2FA EMMC. However, I still don't know what caused our NC to lock up in the first place. I guess at this point, that's moot.
leapinlar, I've read through many of your posts, although I couldn't fix my problems, you were instrumental in keeping me sane. ... well, depending on how loosely you define sane,