Hello,
I would like to post this in void. rom but I don't have enough post count.
I install void. delta as per instruction, and create directory on the following order: kernel, a2sd, gingerbread, gapps, one reboot for one directory. Then after installing Launcher Pro I realize I only have 138MB left on internal memory. I tried installing all my previous application and now got only 62MB left.
I partitioned the sd card as instructed, 0 for swap, 512 for ext, convert to ext3 then ext4, wipe everything, and after flashing it is all the same: apps still resided in internal memory.
I wonder what's wrong. Here the output for command a2sd check:
Code:
# a2sd check
[ ] Launching Darktremor A2SD
Starting Darktremor A2SD version 2.7 Update 3r1
[ ] Mounting /system as read-write
[ ] Starting A2SD in check mode
[ ] Running A2SD Check Program.
[ ] Searching for Mount Point...
[*] Mount point /system/sd located.
[ ] Checking for ext partition
[X] Ext partition found, but not mounted.
Your rom may not be setup to run A2SD.
Check with your rom developer if the boot image
is programmed to run A2SD.
[ ] Setting File System Ready property to 1.
[ ] Remounting /system to read-only.
Here the output for command a2sd remove:
Code:
# a2sd remove
[ ] Launching Darktremor A2SD
Starting Darktremor A2SD version 2.7 Update 3r1
[ ] Mounting /system as read-write
[ ] Starting A2SD in remove mode
[ ] Running A2SD Setup Program.
[ ] Searching for Mount Point...
[!] Mount point found..no further action required.
[ ] Remounting /system to read-write
[ ] Checking for ext partition
[!] Ext partition found, but not mounted.
[ ] Mounting ext partitions
mount: mounting /dev/block/mmcblk0p2 on /system/sd failed: Invalid argument
[X] Mounting ext partition failed.
[X] Can't continue script...aborting.
[ ] Remounting /system to read-only.
[ ] Setting File System Ready property to 1.
[ ] Remounting /system to read-only.
Here the output for command a2sd install:
Code:
# a2sd install
[ ] Launching Darktremor A2SD
Starting Darktremor A2SD version 2.7 Update 3r1
[ ] Mounting /system as read-write
[ ] Starting A2SD in install mode
[ ] Running A2SD Setup Program.
[ ] Searching for Mount Point...
[!] Mount point found..no further action required.
[ ] Remounting /system to read-write
[ ] Checking for ext partition
[!] Ext partition found, but not mounted.
[ ] Mounting ext partitions
mount: mounting /dev/block/mmcblk0p2 on /system/sd failed: Invalid argument
[X] Mounting ext partition failed.
[X] Can't continue script...aborting.
[ ] Remounting /system to read-only.
[ ] Setting File System Ready property to 1.
[ ] Remounting /system to read-only.
And the last command a2sd repair show (perhaps) some info:
Code:
# a2sd repair
[ ] Launching Darktremor A2SD
Starting Darktremor A2SD version 2.7 Update 3r1
[ ] Mounting /system as read-write
[ ] Starting A2SD in repair mode
[ ] Running A2SD Repair Program.
[ ] Searching for Mount Point...
[!] Mount point found..no further action required.
[ ] Remounting /system to read-write
[ ] Checking for ext partition
[!] Ext partition found, but not mounted.
[ ] Checking Ext partition...
e2fsck 1.40.8 (13-Mar-2008)
/dev/block/mmcblk0p2 has unsupported feature(s): extents gdt_checksum
e2fsck: Get a newer version of e2fsck!
[ ] Mounting ext partitions
mount: mounting /dev/block/mmcblk0p2 on /system/sd failed: Invalid argument
[X] Mounting ext partition failed.
[X] Can't continue script...aborting.
[ ] Remounting /system as read-only.
[ ] Setting File System Ready property to 1.
[ ] Remounting /system to read-only.
I tried searching the forum but cannot find the suitable solution.
Thank you very much for your time.
UPDATE:
After several re-flash I got app2sd working. Here is what I did:
- reboot into recovery
- wipe everything
- partition micro sd: swap => 0, ext => 1024
- convert ext2 to ext3
- convert ext3 to ext4
- enable usb storage
- copy rom file
- and while the storage is connected, format the ext partition (/dev/sdb2 if on Linux) as ext4 using GNOME's Disk Utility
- disable usb storage
- flash zip
- reboot
- first boot, check free space: 165 MB
- create directory kernel
- reboot
- check free space: 165 MB
- create directory a2sd
- reboot
- check free space: 178 MB
- dont' do anything, just reboot
- check free space: 193 MB
And a2sd check command give me these:
Code:
# a2sd check
[ ] Launching Darktremor A2SD
Starting Darktremor A2SD version 2.7 Update 3r1
[ ] Mounting /system as read-write
[ ] Starting A2SD in check mode
[ ] Running A2SD Check Program.
[ ] Searching for Mount Point...
[*] Mount point /system/sd located.
[ ] Checking for ext partition
/dev/block/mmcblk0p2 /system/sd ext4 rw,noatime,nodiratime,barrier=1,data=ordered 0 0
[*] Ext partition is mounted.
[ ] Checking A2SD links.
A2SD Status Report
===============================================================
Apps - [-] Linked to SD Card.
[-] File .noa2sd not found.
[*] Programs run from SD card
To run from internal storage, type a2sd remove
Private Apps - [-] Linked to SD Card.
[-] File .noa2sd not found.
[*] Private Programs run from SD card
To run from internal storage, type a2sd remove
Dalvik Cache - [-] Symbolically Linked.
[-] File .dalvikcache found.
[*] Dalvik runs from SD card
To run from internal storage, type a2sd nocache
To run from /cache partition, type a2sd cachepart
Swap - [!] Partition not present.
[!] Swap does not start.
ZipAlign - [!] Not running at boot.
Property Patch - [-] File System Ready property
found.
[*] Boot image init.rc patched.
[ ] Setting File System Ready property to 1.
[ ] Remounting /system to read-only.
Thank you guys for your time. Have a nice weekend.
Try to convert ext2 to ext 3,then ext3 to ext4.I worked for me!
Had the same problem. I did as TheError said; i just wiped everything then repartitioned sd and it worked after reflashing
rosuvladut said:
Try to convert ext2 to ext 3,then ext3 to ext4.I worked for me!
Click to expand...
Click to collapse
Have done that too, but still not working.
kite86 said:
Had the same problem. I did as TheError said; i just wiped everything then repartitioned sd and it worked after reflashing
Click to expand...
Click to collapse
I notice you do wiping before partitioning. Will try that for next time flashing, might work for me.
UPDATE:
Done that too and still not working, but I can get it working now, will update the first post.
Hey one question.I'm using megatron and as the ROM said,it has apps to sd and dalvik to sd. But I feel I'm actually running out of space still.I would like to try out all this ext 3 ext 4 thing but I'm kinda stuck! Any suggestions???
AsherChua said:
Hey one question.I'm using megatron and as the ROM said,it has apps to sd and dalvik to sd. But I feel I'm actually running out of space still.I would like to try out all this ext 3 ext 4 thing but I'm kinda stuck! Any suggestions???
Click to expand...
Click to collapse
To check whether your a2sd working or not run this command on terminal emulator or adb shell:
Code:
a2sd check
If it working it should be output similar to mine in the first post.
export PATH=/data/local/bin:$PATH
sh-3.2$ export PATH=/data/local/bin:$PATH
sh-3.2$ a2sd check
rm: cannot remove '/data/dta2sd.lg2': Permission denied
cp: cannot create '/data/dta2sd.lg2': File exists
rm: cannot remove '/data/dta2sd.lg1': Permission denied
cp: cannot create '/data/dta2sd.lg1': File exists
rm: cannot remove '/data/dta2sd.log': Permission denied
[ ] Apps2SD is launching...
/system/bin/a2sd: line 22: /data/dta2sd.log: Permission denied
/system/bin/a2sd: line 23: /data/dta2sd.log: Permission denied
/system/bin/a2sd: line 24: /data/dta2sd.log: Permission denied
/system/bin/a2sd: line 31: /data/dta2sd.log: Permission denied
/system/bin/a2sd: line 35: /data/dta2sd.log: Permission denied
/system/bin/a2sd: line 36: /data/dta2sd.log: Permission denied
/system/bin/a2sd: line 37: /data/dta2sd.log: Permission denied
/system/bin/a2sd: line 38: /data/dta2sd.log: Permission denied
/system/bin/a2sd: line 39: /data/dta2sd.log: Permission denied
grep: /init.rc: Permission denied
tee: /data/dta2sd.log: Permission denied
__ _____
tee: /data/dta2sd.log: Permission denied
| \ |
tee: /data/dta2sd.log: Permission denied
| | |
tee: /data/dta2sd.log: Permission denied
|__/ | Darktremor Apps2SD 2.7.5.2 (2010-09-30)
tee: /data/dta2sd.log: Permission denied
/system/bin/launcha2sd: line 117: /data/dta2sd.log: Permission denied
[ ] GetProp Command = /system/bin/toolbox getprop
[ ] SetProp Command = /system/bin/toolbox setprop
[ ] Mount Point = /system/sd
tee: /data/dta2sd.log: Permission denied
[ ] Creating /cache/dc
tee: /data/dta2sd.log: Permission denied
mkdir: can't create directory '/cache/dc': Permission denied
tee: /data/dta2sd.log: Permission denied
chmod: /cache/dc: Permission denied
[ ] Symlinking /cache/dalvik-cache to /data/dalvik-cache
tee: /data/dta2sd.log: Permission denied
rm: can't stat '/cache/dalvik-cache': Permission denied
ln: /cache/dalvik-cache: Permission denied
tee: /data/dta2sd.log: Permission denied
/system/bin/launcha2sd: line 273: /data/dta2sd.log: Permission denied
[ ] Starting Apps2SD Check Program.
/system/bin/chka2sd: line 7: /data/dta2sd.log: Permission denied
grep: /init.rc: Permission denied
grep: /init.rc: Permission denied
tee: /data/dta2sd.log: Permission denied
[ ] Checking for ext partition
tee: /data/dta2sd.log: Permission denied
[X] Ext partition found, but not mounted.
tee: /data/dta2sd.log: Permission denied
Your rom may not be setup to run Apps2SD.
tee: /data/dta2sd.log: Permission denied
Check with your rom developer if the boot image
tee: /data/dta2sd.log: Permission denied
is programmed to run Apps2SD.
tee: /data/dta2sd.log: Permission denied
tee: /data/dta2sd.log: Permission denied
Your partition may be using an EXT4 partition,
tee: /data/dta2sd.log: Permission denied
but your rom may not support EXT4. Repartition
tee: /data/dta2sd.log: Permission denied
your SD card to use EXT2 or EXT3.
tee: /data/dta2sd.log: Permission denied
/system/bin/chka2sd: line 96: /data/dta2sd.log: Permission denied
/system/bin/launcha2sd: line 276: /data/dta2sd.log: Permission denied
/system/bin/launcha2sd: line 277: /data/dta2sd.log: Permission denied
/system/bin/a2sd: line 41: /data/dta2sd.log: Permission denied
sh-3.2$
This is what I got.So is it working? The permission denied shows me something is not right.
Try running the command as superuser. Enter su first, allow permission if requested, then execute a2sd check.
export PATH=/data/local/bin:$PATH
sh-3.2$ export PATH=/data/local/bin:$PATH
sh-3.2$ su
sh-3.2# a2sd check
[ ] Apps2SD is launching...
__ _____
| \ |
| | |
|__/ | Darktremor Apps2SD 2.7.5.2 (2010-09-30)
[ ] GetProp Command = /system/bin/toolbox getprop
[ ] SetProp Command = /system/bin/toolbox setprop
[ ] Mount Point = /system/sd
[ ] Creating /cache/dc
[ ] Symlinking /cache/dalvik-cache to /data/dalvik-cache
[ ] Starting Apps2SD Check Program.
[ ] Checking for ext partition
[X] Ext partition found, but not mounted.
Your rom may not be setup to run Apps2SD.
Check with your rom developer if the boot image
is programmed to run Apps2SD.
Your partition may be using an EXT4 partition,
but your rom may not support EXT4. Repartition
your SD card to use EXT2 or EXT3.
sh-3.2#
Now I got this.Looks to me like I have the apps2sd?
Yes, you got a2sd installed, but it has problem mounting ext partition. This problem was similar to mine.
You may want to try formatting ext partition using computer. No need to re-flash, just format the (supposedly) ext partition with ext4 using computer, reboot your phone and the a2sd should have no problem anymore.
You can also check the first post for how I do it.
Alright! I'm not very good with the 'computer and phone' way! Is there a way to do this just by using the phone? And after doing that,will I lose all my data on phone or sd card?
AsherChua said:
Alright! I'm not very good with the 'computer and phone' way! Is there a way to do this just by using the phone? And after doing that,will I lose all my data on phone or sd card?
Click to expand...
Click to collapse
You can try formatting using recovery mode, see if it's working for the second time.
I tried re-wiping, re-partitioning and re-flashing about three time until I finally decide to format manually using computer.
Yes on sd card, if you decide to re-partitioning again. Yes on the phone, if you decide to flashing again.
But always do backup before any attempt.
Alright! I'll try to figure this out. What good will it do me once I finish this?
fixed
I had the same exact problem but managed to figure out a way to fix it
The problem was that the ext was ext4 and not ext3 so a2sd could not detect it, which didnt make sense because I had backed up my entire phone using clockwork mod touch and it was restoring as ext4
So I booted into parted magic and put the microsd card in a usb reader, it would not detect it properly with the phone
Then I backed up all the files on the ext4 partition (right click mount), then look for disk under file manager
Next I reformatted the ext4 as ext3
Lastly I copied all the files I had backed up to the ext3 partition.
When I booted back into my phone, all my apps were there and it was working fine.
For some reason when I use the restore sd-ext in clockworkmod it changes the partition to ext4
That was giving me the issues with the lost apps and the mounting ext partition error.
Hallo,
i tryed to get root permission on my x10 mini pro using the rooted.sh script.
distro ubuntu 10.04
this is the output...
I also tryed to run the script with sudo user... but it's the same...
any help?
/ROOTer-Linux-v3$ sh ROOTer.sh
ROOTer for Linux by react2409.
Requirements and credits are listed in the README.txt file.
Please make sure requirements are met before continuing.
Remember by using this you understand the risks involved with doing so.
Is your phone already rooted? (y/n)n
Do you wish to continue with the ROOTing? (y/n)y
Is USB Debugging enabled on your phone? (y/n)y
Great lets start the process.
Starting ADB server.
ROOTer.sh: 49: ./adb/adb: Permission denied
Wait for phone to be ready.
ROOTer.sh: 53: ./adb/adb: Permission denied
Push the exploit to the phone.
ROOTer.sh: 57: ./adb/adb: Permission denied
ROOTer.sh: 58: ./adb/adb: Permission denied
Run the exploit. There may be a delay whilst this is happening.
ROOTer.sh: 62: ./adb/adb: Permission denied
ROOTer.sh: 63: ./adb/adb: Permission denied
Mount system as R/W.
ROOTer.sh: 67: ./adb/adb: Permission denied
Push su to phone.
ROOTer.sh: 71: ./adb/adb: Permission denied
Push Superuser.apk to phone.
ROOTer.sh: 73: ./adb/adb: Permission denied
Push busybox to phone.
ROOTer.sh: 75: ./adb/adb: Permission denied
Setting permissions for su.
ROOTer.sh: 79: ./adb/adb: Permission denied
Setting permissions for busybox.
ROOTer.sh: 81: ./adb/adb: Permission denied
Reboot phone.
ROOTer.sh: 85: ./adb/adb: Permission denied
Stopping ADB Server.
ROOTer.sh: 89: ./adb/adb: Permission denied
Your phone should now be ROOTed.
Hey sorry for my bad englisch ......
I rooted my galaxy s5 and installed busy box ... now i downloaded Linux Deploy and try to install kali linux ... failed ......
Here code:
[15:25:37] Updating configuration file ... done
[15:25:38] >>> begin: install
[15:25:38] Checking mount points ... /data/data/ru.meefik.linuxdeploy/linux/bin/linuxdeploy: line 1575: grep: Permission denied
[15:25:38] /data/data/ru.meefik.linuxdeploy/linux/bin/linuxdeploy: line 1575: cat: Permission denied
[15:25:38] done
[15:25:38] Checking installation path ... done
[15:25:38] /data/data/ru.meefik.linuxdeploy/linux/bin/linuxdeploy: line 1575: dirname: Permission denied
[15:25:38] /data/data/ru.meefik.linuxdeploy/linux/bin/linuxdeploy: line 1575: stat: Permission denied
[15:25:38] /data/data/ru.meefik.linuxdeploy/linux/bin/linuxdeploy: line 1575: stat: Permission denied
[15:25:38] Making new disk image (512 MB) ... /data/data/ru.meefik.linuxdeploy/linux/bin/linuxdeploy: let: line 1575: arithmetic syntax error
[15:25:38] /data/data/ru.meefik.linuxdeploy/linux/bin/linuxdeploy: let: line 1575: arithmetic syntax error
[15:25:38] /data/data/ru.meefik.linuxdeploy/linux/bin/linuxdeploy: line 1575: dd: Permission denied
[15:25:38] fail
[15:25:38] <<< end: install
[15:25:38] /data/data/ru.meefik.linuxdeploy/linux/bin/linuxdeploy: line 1575: dd: Permission denied
Can someone help me?
You can't with selinux on enforce, flash a permissive selinux kernel and try again
Hi Developers,
I want to set/get the GPU and DDR frequencies using devfreq object by changing governor.
i need to run the following command in adb shell.
HWBKL:/ $ echo performance > /sys/class/devfreq/ddrfreq/governor
But i am not able to access below things.
HWBKL:/sys/class/devfreq/ddrfreq $ ls
ls: ./trans_stat: Permission denied
ls: ./target_freq: Permission denied
ls: ./available_governors: Permission denied
ls: ./cur_freq: Permission denied
ls: ./max_freq: Permission denied
ls: ./min_freq: Permission denied
ls: ./uevent: Permission denied
ls: ./ddr_bandwidth: Permission denied
ls: ./bd_utilization: Permission denied
ls: ./available_frequencies: Permission denied
ls: ./governor: Permission denied
ls: ./polling_interval: Permission denied
device power subsystem
-> i tried $adb root
adbd cannot run as root in production builds.
->i tried HWBKL:/ $ su
/system/bin/sh: su: not found
Please let me know is there any possibility.
Thanks
ashokkatha said:
Hi Developers,
I want to set/get the GPU and DDR frequencies using devfreq object by changing governor.
i need to run the following command in adb shell.
HWBKL:/ $ echo performance > /sys/class/devfreq/ddrfreq/governor
But i am not able to access below things.
HWBKL:/sys/class/devfreq/ddrfreq $ ls
ls: ./trans_stat: Permission denied
ls: ./target_freq: Permission denied
ls: ./available_governors: Permission denied
ls: ./cur_freq: Permission denied
ls: ./max_freq: Permission denied
ls: ./min_freq: Permission denied
ls: ./uevent: Permission denied
ls: ./ddr_bandwidth: Permission denied
ls: ./bd_utilization: Permission denied
ls: ./available_frequencies: Permission denied
ls: ./governor: Permission denied
ls: ./polling_interval: Permission denied
device power subsystem
-> i tried $adb root
adbd cannot run as root in production builds.
->i tried HWBKL:/ $ su
/system/bin/sh: su: not found
Please let me know is there any possibility.
Thanks
Click to expand...
Click to collapse
There is no way you can run adb shell as root without rooting. Rooting your phone installs the su binary in your phone. That is needed to run root for any apps.
mohhaxs said:
There is no way you can run adb shell as root without rooting. Rooting your phone installs the su binary in your phone. That is needed to run root for any apps.
Click to expand...
Click to collapse
Thank you mohhaxs.
i didn't tried rooting a phone before. Do you know any rooting procedure for Honor View 10 (BKL-L09)
Long story short, I tried to install Company Portal app and failed, which left my phone on 'pixel is starting' screen. I'm fine with resetting the phone, but have some files I would like to transfer first.
The phone is on Android 10 (QQ1A.200105.002), unrooted but debugged. I ran adb on my pc, adb shell ls returns the following:
Code:
ls: ./init.zygote64_32.rc: Permission denied
ls: ./init.rc: Permission denied
ls: ./init.usb.rc: Permission denied
ls: ./ueventd.rc: Permission denied
ls: ./init.zygote32.rc: Permission denied
ls: ./init: Permission denied
ls: ./cache: Permission denied
ls: ./init.environ.rc: Permission denied
ls: ./postinstall: Permission denied
ls: ./init.usb.configfs.rc: Permission denied
ls: ./metadata: Permission denied
acct
apex
bin
bugreports
charger
config
d
data
debug_ramdisk
default.prop
dev
dsp
etc
lost+found
mnt
odm
oem
persist
proc
product
product_services
res
sbin
sdcard
storage
sys
system
vendor
But when I run pull sdcard, which is listed above, it shows that the file does not exist.
Code:
sdcard: No such file or directory
I turned on 'file transfer' in 'USB preference', which still doesn't help.
Any suggestions would be appreciated. I need to get the files off the phone before I could reset and use it again.
I had the same problem when I was un-able to boot.
I researched every possible reason that I would get that "sdcard: No such file..." error, but I wasn't able to fix it. Despite having the bootloader unlocked and being rooted, I still had to wipe it.
You cant pull anything unless phone is decrypted. Which happens after you unlock lockscreen after boot.