Hi!
I have kais130
I use "Froyo[2.2.2]: My Modified Fresh Froyo Release 20-2-2011" rom and have some issue with it: eventually (2-3 days after clean system install) many process like launcher, acore and many other just stop responding. Hot reboot or soft reset makes it worse, device just wont boot. And the same think happens with all of the roms I used. I have data and system installed on nand. Tried haret install, but i got some trouble with argument:
Mount: mounting/dev/block/mmcblk op1 on/ sdcard failed: invalid argument
/init line 334: mont_opt: not found sh: 2: unknown
............................................................................
Possibly non-existent or swap device?
I have 2 sd cards for nand install i used 1gb sd and for haret i used 16gb sdhc class 6 card.
If its necessary: i have panel type 1, used 2.6.25 kernel (because installing on 2.6.32 got some errors with bad blocks and failed to extract). Also i read on some post, that for the stable work don't use Rogue Tools (i use it).
While installing any rom on 2.6.25 kernel i have no errors but Fix permission on files:
Chown: data/app_s: No such file or directory (X2)
Chown: System/etc/bluez: No such file or directory (X4)
Chown: system/init: No such file or directory (X2)
and some errors while booting some thing with: data/sysfiles/su path don't exist and some no such file or directory( which i don't remember) + error no local ept for prog 02000031 replying anyway!
Is there some magical way to solve this problem?
Thanks for any reply!
Sorry for my English cause i m Russian.
I think I am having the same problem. I flashed the Eclair nbh file ant it gave me that error.
Related
Hello,
I flashed Squadzone's CM7.2 RC5.5 yesterday for first time I use any custom ROMs on my SGM.
Then I flashed GApps and Opened market to install my favorite apps, here I noticed that (SD-Card Normally supported) apps were installed in Internal Memory.
Finally, I installed Link2SD, moved and linked all application to SD-EXT partition .. so all applications linked to SD-EXT.
I tried to move them to Normal SD-Card via Settings => Applications, but it failed.
I tried to move them via Link2SD, but it failed with Error: "[INSTALL_FAILED_CONTAINER_ERROR]", but it succeeded one time to move Acrobat Reader then it failed.
I don't bother if they are installed on SD-Card or SD-EXT, but this problem causes to bigger problem. the Following Apps MUST be installed on SD-Card from Market or APK (as I think):
1. Voice Search
2. Archidroid
3. SpeedCar
4. Holy Quran
when I tried to install them from Market, they prompts an error: "couldn't install on USB Storage or SD Card"!
although the rest apps installed successfully!
Sorry for my bad English, I wish I explained the problem successfully.
Hello,
I searched here and there and I Found a way by removing a temp file in .android-secure but it failed.
I monitored the logcat and found this:
http://db.tt/JWKOb0wg
Edit: I removed smdl2tmp1.asec from /mnt/secure/asec but still can't install!
Edit 2: I fetched these commands:
$ export PATH=/data/local/bin:$PATH
$ su
# cd /mnt/sdcard/.android_secure
# ls
# rm smdl2tmp1.asec
rm: can't remove 'smdl2tmp1.asec': No such file or directory
# rmdir /mnt/sdcard/.android_secure
rmdir failed for /mnt/sdcard/.android_secure, Device or resource busy
Sent from my GT-S5570 using XDA App
Finally, I removed all system and application related folders from SD card via a computer. And wiped data and cash and started in a clean environment with English interface.
Then I succeeded, I discovered that the problem in Arabic interface so I tried many times to be sure!
Sent from my GT-S5570 using XDA App
Hello xda-kaiser-android community
My configuration is :
SDCARD with 4 partitions :
FAT16 with Haret, zimage, inird, default.txt
SYSTEM (ext2)
DATA (ext2)
swap
I've managed to launch Android, and the phones does work.
Unfortunately, at the moment, some other things does not work :
WIFI : fails when getting the IP (so I scan WIFI networks well, but there is a problemn when creating the network interface...)
Modem : does not work..
Camera : not very important for the moment, but can become more...
So, I wanted to dump log files and try, with the terminal, to guess what is happening, but I COULD NOT MANAGED to SU ROOT (as a Linux user, I don't feel comfortable when I cannont be root on my personnal machine)...
When launching the "SuperUser" program the Applist is empty ?
When I set suid and root:root ownership of /bin/su on the SYSTEM partition, when SD mounted on my computer, It is not preserved when used inside Android...
After some inspection of the init scripts (see here under), my question is :
WHY SYSTEM PARTITION IS NOT MOUNTED with ROOT privileges ??
WHY is it chowned to the user 1000:1000 ?
Code:
# mount and set perms
$BB mount -o noatime,nodiratime -t auto $PARTITION $SD_EXT_DIRECTORY;
if [ "$?" = 0 ];
then
$BB chown 1000:1000 $SD_EXT_DIRECTORY;
$BB chmod 771 $SD_EXT_DIRECTORY;
log -p i -t mountsd "$SD_EXT_DIRECTORY successfully mounted";
Thank you for your comments, any help will be appreciated
Regards
Bernie
I overpost myself : My problem probably comes from the way I extracted the Froyo tarball to the SYSTEM partition...
I'll try again and inform you of my mistake.
Regards
why don't you try FAT32 instead of FAT16
bernie.discale said:
I overpost myself : My problem probably comes from the way I extracted the Froyo tarball to the SYSTEM partition...
I'll try again and inform you of my mistake.
Regards
Click to expand...
Click to collapse
Don't extract the froyo tarball. Just place androidinstall.tgz and androidupdate.tgz into the SDCARD andboot folder. Then, after you boot linux, touch and hold the center of the screen, and an install menu will appear. Then select your partitions, install system (and format data partition), install updates, and fix permissions, then exit. Android should start. Be sure your kernel (zImage) and drivers (androidupdate.tgz) match, and it also helps for the initrd.lzma to match. When wifi doesn't work, that usually means the driver is mismatched.
Hi Guys
Thnk you for your answers.
I got a more urgent issue than porting my kaiser to android : I've been forced to move my laptop back to windows again ...
So I must know workaround to dual boot linux (and, believe me, this install of windows is not the standard one)..
But A soon as I can, I will try the install stuff.
thank you again
Heydiho !
Things get better...
I caught eu-froyo-odex and installed it as is after entering the installation menu (launched by init ?)... The su command is now working. I have to tackle a few things now :
Wifi works even worse (now I clealry see an error, where, with the other distro, it was probably a permission issue)
Screen has still odd behaviors
Keymap issue with Keyboard arrows does not work in terminal
And camera to be confirmed
I'll dig the forum for topics on these subjects and get back if I'm really stuck
Best regards
Bernie
Hello
Things goes in the good direction :
Wifi is now ok (was not working with panel 1.. can this be correlated ?)
Screen works better with panel 2, but I'am still not sure if mine is 2 or 3)
Keymap Fixed : was only a matter of using bash insted of default busybox's shell
camera is not working
GPRS modem not working
Battery consumption is high with system on sdcard
Stay tuned !
I am working on a couple of things, specifically a "build.prop" mod and adding a "gps.conf" file to /system/etc, which is just a list of AGPS servers and to fix some GPS issues.
The modded build.prop that I have reworked adds some dalvik cache lines and "sleep mode" lines, as our Kaisers don't have a sleep mode implemented.
Camera and GPRS can be associated with the radio rom installed. I found that on my specific device, radio 1.70.19.09 allowed GPS and data to work smoothly, but I would lose the phone after the first call and camera had just a dark green screen. 1.65.16.25 dropped GPRS but improved data speeds and allowed the phone to work as well as the camera.
YMMV but I would say wipe any trace of WM from that phone (support is ending this May) and go directly with Android via NAND install.
Hello guys
@PoXFreak
I still have some habbits on my WM (freeOTFE encryption, contacts and some other stuffs) that are still working well on WM, and I don't feel very comfortable in switching on full Android (I mean on NAND) while I'am not very used to use Android... I would have definitely preferred to have a working platform booting from sdcard before flashing the NAND, but you confirmed that some issues may be linked to the SDCARD install...
I'm stuck since the beginning of march with the GPRS modem, and I don't clearly understand what are you talking about (have to check what you mean by radio).
My problem is, at the moment, that I don't have any mean to debug : is there a way to activate logs for users spaces programs ? Where to find em ?
If there is a better way to debug, what is it ?
As always, thank you, in advance, for any answer.
I'll try by myself a soon as I can (and, during the last weeks, it was not the case).
Best regards
I will add, moreover, that I'am still not sure of my panel (2 or 3 !!!)
Regards
Hello, I have been going through the process for setting up a swap space on my SDcard for Webtop on my Bionic. Everything has gone well as far as using Webtop2SD, paritioning my SDcard for the swap space, and getting terminal and synaptic package manager to run in Webtop mode. However the next step is to go into PartitionManager and navigate to the swap space but everytime I attempt to launch PartitionManager is get this error:
/usr/bin/partitionmanager-bin: error while loading shared libraries: libparted.so.0: cannot open shared object file: No such file or directory
I went back to ADB and did the following to eliminate this potential problem:
adb shell
su
mount -o remount, rw /
That has still not resolved this. I have gone back into Syanptic and did a complete uninstall and then a new install and this also hasnt cleared it up. Is anyone else having this issue? I would appreciate any help that can be offered.
I am having this same problem. I will let you know if I can resolve it.
I don't think either GParted or Partition Manager can be run from Webtop. GParted can be run from ADB Shell through Windows and the thread: http://forum.xda-developers.com/showthread.php?t=1309712 has instructions to avoid using Partition Manager when creating a swap file for WebTop2SD.
Hi,
I've just installed fresh CM10 ICS Nightly on my LG Optimus 2x. The original __EXTERNAL_SD folder in my Home was suddenly empty, so I thought the mount point of External SD has changed. I found it in /storage/sdcard1. However, Applications don't recognize that, because they obviously expect __EXTERNAL_SD simlink/folder (or whatever it is) in my home. So I decided to delete it and create a new one to new location. Deletion was successful,but I'm not able to create a new symlink.
Code:
[email protected]: /sdcard # ln -s /storage/sdcard1 __EXTERNAL_SD
link failed Operation not permitted
[email protected]: /sdcard #
This is what I get.
Furthermore, since I deleted original file, every time I start Apollo (music player) I get error Unfortunately, Apollo has stopped. That's kinda weird, because it acts like it requires working __EXTERNAL_SD, but I'm not 100% sure.
Can you please explain me how to create such a symlink? Thanks!
Have You tried with superuser?
Sure, sign # means I have root access. Anyway, the problem is not longer relevant for me, bacause I've reinstalled whole system from the bottom using factory reset.
I'm newbie to Android, and It's litte suprising for me that root can not create a simple symilnk, that shoul work every time (as in Linux).
[Q] encryption, ext2/4, and "filesystem too large to mount safely" error fix?
Hello again,
With my Droid 3 (thanks to Minimoto) again working great, I've turned my attention back to encrypting some of my data on the external SD card. I had used "LUKS Manager" some time ago so that seemed the logical place to start.
Okay, the short *short* version is: What does the error message (from dmesg output) "EXT4-fs (dm-4): filesystem too large to mount safely on this system" mean and how do I fix it or work around it?
The details:
I have a 32 GB SD card with a normal ~20 GB FAT partition that Android sees and uses just fine. On my laptop I created an ext4 file system on the second partition (the remaining ~12 GB of space). Android does not see or use this, but from a terminal I *can* mount it without problems. I chose to mount /dev/block/mmcblk0p2 (external SD partition 2) at /mnt/sdcard-ext-p2. Just FYI, but I wrote a short script and put it at /etc/init.d/03mount_sdpart2 to mount this second partition at the correct mount point and it works fine. Even after a reboot the script runs without problems and now I always have my new ext4 file system present.
The reason for creating the ext4 file system is because FAT does not support files larger than 4 GB and therefore my encrypted volume cannot be larger than 4 GB *if* I create that volume on a FAT file system. With the new ext4 file system, now using the LUKS Manager app, I created a new volume at the above mount point with a size of approximately 11.25 GB. This worked fine, too. The last step, however, actually mounting this encrypted volume, keeps failing. It was supposed to be mounted at /mnt/sdcard/LUKS. Unfortunately, LUKS Manager did not produce much in the way of information about why it had failed.
A quick note about file sizes: If I use an app like "ES File Explorer" and go to /mnt/sdcard-ext-p2 where the large volume file exists, ES says the volume file has a size of -805306366 bytes, obviously wrong. Fortunately, if I use the terminal and look at the file size with "ls -l" it has the correct size. Furthermore, after I opened the volume below using lm.cryptsetup I can use its "status" command and after converting the values from sectors (each sector is 512 bytes) it also displays the correct size of the encrypted volume.
So, back to the terminal where I decided to do the steps manually and see where it failed. For the most part, I used different device and directory names than what LUKS Manager would have used, mostly to be sure I wouldn't accidentally conflict with another process/app. The 'lm.cryptsetup' binary is provided by LUKS Manager and placed in /system/bin. I have the version of busybox that, I assume, ships with Minimoto which is busybox v1.20.0. This is where the 'losetup' I am using comes from.
Concerning loopback devices: LUKS Manager defaults to using/creating high numbered loopback devices, 300 for the first volume created. On Android the loop devices are created in /dev/block, but some tools don't seem to look there. In particular, lm.cryptsetup complains about not being able to find a free loopback device and 'losetup -f' (which displays the next free/available loopback device) always refers to devices in /dev regardless of where they really are. Making symlinks such as "ln -s /dev/block/loop0 /dev/loop0" for each of the currently present loop devs (0 through 7, and 300) fixes both of these problems. That said, whatever manner LUKS Manager uses to execute the underlying tools works properly with the loop devs being located in /dev/block. This can be verified by using "lm.cryptsetup status <crypt_dev>" and the status output shows that it is correctly attached to, for example, /dev/block/loop300. Making these symlinks is more of a convenience/fix for when one is working directly on the command line.
Where, before, 'losetup -f' indicated that /dev/loop0 was free (even though it did not exist), after making the symlinks the same command indicates that /dev/loop4 is the next free loop. On my phone, at that moment in time, that was the correct answer. loop4 also makes sense because I have four apps that I have "moved to SD" and for each app that you do this one loopback device is used (so loop0 - loop3 were used by apps "moved" from main internal storage). Creating these symlinks also made lm.cryptsetup stop complaining/erroring about not being able to find a free loop dev. Finally, running "losetup" without arguments is supposed to list the used loop devs and what is using them. Before making the symlinks is produced no output, and now, after the symlinks, it displays:
Code:
/dev/loop0: 0 /mnt/secure/asec/blah_appA.asec
/dev/loop1: 0 /mnt/secure/asec/blah_appB.asec
/dev/loop2: 0 /mnt/secure/asec/blah_appC.asec
/dev/loop3: 0 /mnt/secure/asec/blah_appD.asec
/dev/loop5: 0 /ss/safestrap/rom-slot2/cache.img
/dev/loop6: 0 /ss/safestrap/rom-slot2/userdata.img
/dev/loop7: 0 /ss/safestrap/rom-slot2/system.img
As you can see, loop4 is missing/available. Also, rom-slot2 is correct as it is where I opted to install Minimoto, rom-slot1 currently containing CM 10.1.
With the loop device issues taken care of, the steps I performed are as follows:
Code:
$ su
# lm.cryptsetup luksOpen /mnt/sdcard-ext-p2/MyCrypto.vol MyCrypto
<type in passphrase>
# ls /dev/mapper
MyCrypto control
# mkdir /mnt/sdcard/luks-tst
# mount /dev/mapper/MyCrypto /mnt/sdcard/luks-tst
mount: mounting /dev/mapper/MyCrypto of /mnt/sdcard/luks-tst failed: File too large
# dmesg | tail -2
[20665.748504] EXT4-fs (dm-4): filesystem too large to mount safely on this system
[20665.750732] EXT4-fs (dm-4): filesystem too large to mount safely on this system
You can see from the above block my commands and the output, especially errors, that followed. Clearly, the file is "too large"... but how? The whole point of this extra partition and ext4 file system stuff was specifically to get around the FAT 4GB file size limitation. Unfortunately, while these errors tell me that something is too large, what *part* is too large? Is the 11.25 GB volume *container* too large, or the ext2/4 file system that exists inside the volume? And if either is too large, what is the maximum size I can make them? I did try adding "-t ext2" and "-t ext4" to the mount command, but neither one changed the outcome nor did they change the messages that were output.
The 'mount' binary (like most others) is provided by busybox, so it could possibly be part of the problem. However, the last two errors above come from the kernel log (via dmesg) which means that at least part of the issue is the kernel, maybe the file system modules. I also checked the logcat output, just in case, but it did not contain anything related or useful. Minimoto 1.7 is using kernel version 2.6.35.7 and perhaps it has some maximum size issues I am unaware of. With the exception of my Droid 3, I haven't used a 2.6.x Linux kernel in a very long time.
I've searched around here as well as the fairly small LUKS Manager message board and the Net at large, but I haven't been able to find the answers I'm looking for. Any ideas as to what I might have done wrong, or something I haven't done but should? I'm not sure how to proceed. Just to be perfectly safe, I did try rebooting but it made no difference.
--John Gruenenfelder
Re: [Q] encryption, ext2/4, and "filesystem too large to mount safely" error fix?
Could it be that your mount point is within the FAT fs, what about creating a new mount point at say /mnt/LUKS
Sent from my XT860 using xda premium
Re: [Q] encryption, ext2/4, and "filesystem too large to mount safely" error fix?
I tried using /mnt/LUKS (instead of the previous /mnt/sdcard/LUKS) as the mount point, but nothing changed. The "filesystem is too large..." messages still appeared.
I don't know why there are two such messages separated by about 2/1000th of a second in the dmesg output even though I issued just one command. It was the same way in my first post.
If I recall, the original reason for putting the mount point under /mnt/sdcard was so that most apps could see/use the new area without having any extra knowledge.
--Sent from my DROID3 using xda app-developers app