i am using a2sd ,,, i am not able to configure which memory setting should i use,, from these,,, and give a little bit explaination,, help asap plzzz
Low Memory Killer Commands:
----------------------------------------------------
lowmem-moderate
Sets the internal memory killer to the following
settings:
Foreground Apps: 1536 pages / 6 MB
Visible Apps: 3072 pages / 12 MB
Secondary Server: 4096 pages / 16 MB
Hidden Apps: 7680 pages / 30 MB
Content Provider: 8960 pages / 35 MB
Empty App: 10240 pages / 40 MB
Create File: /data/.lmmoderate
Remove File: /data/.lmoptimum
/data/.lmstrict
/data/.lmaggressive
/data/.lmultimate
/data/.lmextreme
lowmem-optimum
Sets the internal memory killer to the following
settings:
Foreground Apps: 1536 pages / 6 MB
Visible Apps: 2048 pages / 8 MB
Secondary Server: 4096 pages / 16 MB
Hidden Apps: 10240 pages / 40 MB
Content Provider: 12800 pages / 50 MB
Empty App: 15360 pages / 60 MB
Create File: /data/.lmoptimum
Remove File: /data/.lmmoderate
/data/.lmstrict
/data/.lmaggressive
/data/.lmultimate
/data/.lmextreme
lowmem-strict
Sets the internal memory killer to the following
settings:
Foreground Apps: 1536 pages / 6 MB
Visible Apps: 2048 pages / 8 MB
Secondary Server: 4096 pages / 16 MB
Hidden Apps: 15360 pages / 60 MB
Content Provider: 17920 pages / 70 MB
Empty App: 20480 pages / 80 MB
Create File: /data/.lmstrict
Remove File: /data/.lmmoderate
/data/.lmoptimum
/data/.lmaggressive
/data/.lmultimate
/data/.lmextreme
lowmem-aggressive
Sets the internal memory killer to the following
settings:
Foreground Apps: 1536 pages / 6 MB
Visible Apps: 3072 pages / 12 MB
Secondary Server: 4096 pages / 16 MB
Hidden Apps: 21000 pages / 82 MB
Content Provider: 23000 pages / 90 MB
Empty App: 25000 pages / 98 MB
Create File: /data/.lmaggressive
Remove File: /data/.lmmoderate
/data/.lmoptimum
/data/.lmstrict
/data/.lmextreme
/data/.lmultimate
lowmem-extreme
Sets the internal memory killer to the following
settings:
Foreground Apps: 1536 pages / 6 MB
Visible Apps: 3072 pages / 12 MB
Secondary Server: 4096 pages / 16 MB
Hidden Apps: 38400 pages / 150 MB
Content Provider: 40960 pages / 160 MB
Empty App: 43520 pages / 170 MB
Create File: /data/.lmextreme
Remove File: /data/.lmmoderate
/data/.lmoptimum
/data/.lmstrict
/data/.lmaggressive
/data/.lmultimate
lowmem-ultimate
Sets the internal memory killer to the following
settings:
Foreground Apps: 1536 pages / 6 MB
Visible Apps: 3072 pages / 12 MB
Secondary Server: 4096 pages / 16 MB
Hidden Apps: 51200 pages / 200 MB
Content Provider: 57600 pages / 225 MB
Empty App: 64000 pages / 250 MB
Create File: /data/.lmultimate
Remove File: /data/.lmmoderate
/data/.lmoptimum
/data/.lmstrict
/data/.lmaggressive
/data/.lmextreme
lowmem-default
Sets the internal memory killer back to phone default
settings.
I have the same question !
panaali said:
I have the same question !
Click to expand...
Click to collapse
now a days i am using optimum lowmem settings they are good for me
Related
Try to add new DWORD value:
HKEY_LOCAL_MACHINE\System\StorageManager\FATFS
BufferSize=0x900 [that is 2304 decimal]
[add BufferSize, wait 30 seconds and reboot ]
Use value between 0x800 and 0xA00.
If buffer size is not defined default value is 0x20 [==32].
SPB benchmark told me, that some file operations could be faster:
Code:
Write 1MB file 0,39%
Read 1MB file 5,04%
Copy 1MB file -1,31%
Write 10KB x 100 files 12,23%
Read 10KB x 100 files 22,31%
Copy 10KB x 100 files 8,44%
Directory list of 2000 files 38,05%
Internal database read 2,50%
Don't use BufferSize>0xA00 - results are not so good [due to buffer management overhead].
BufferSize<0x800 - results are not so good, too.
BTW. Increasing CacheSize above 0x1000 [decimal 4096] doesn't increase file system performance.
I have a 16gb touchpad, and have only webos and CM9 installed. My sdcard's capacity is about 6.9GBs.
How much is yours? Because i think im missing few gigabytes.
on lvm,
with pvscan i can see a physical partition of about 14GB and with lvscan i can see a sum of about 10GB of logical partitions. If i run the command lvresize -L +90000M /store/media it wont increase it at all
Don't forget that WebOS has a set of other partitions it needs as well - /boot, the swap, the mojodb, update room, etc. A fresh install of WebOS from factory leaves yo with about 14 or so gigs of room on /media/card. Then, when you install CM9, it shrinks that down further by about another almost-2.
Don't forget, you also might have a few apps that have installed themselves to the SD Card, as well as nandroid backups, new flash able zips, ,movies / music / pictures etc from either of the two OS's. They share the SD card partition between them.
Hope it helps.
Sent from my HP Touchpad, using the XDA Premium app.
ve6ay said:
Don't forget, you also might have a few apps that have installed themselves to the SD Card, as well as nandroid backups, new flash able zips, ,movies / music / pictures etc from either of the two OS's. They share the SD card partition between them.
Click to expand...
Click to collapse
Yes but that shouldn't reduce the total space of the media partition but the free space :/
The stuff that's installed on there will lower the free space. The actual partition size is changed by installing any form of Android / Linux / anything except the actual WebOS.
What explorer are you using that shows it's only 7 GB in size ? Root Explorer shows that my SD Card has 3.75 used, 6.88 free (so 10.63 total). I have the 16GB Touchpad with just yesterday's official nightly installed. I connected my tablet while booted into WebOS, and by using lvm.static lvdisplay (and saving the result to a text file) I get the following:
Code:
--- Logical volume ---
LV Name /dev/store/root
VG Name store
LV UUID sila5d-dULD-b5A2-vaei-gVJL-HtoQ-wWgupV
LV Write Access read/write
LV Status available
# open 1
LV Size 568.00 MB
Current LE 71
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Persistent major 254
Persistent minor 0
Block device 254:0
--- Logical volume ---
LV Name /dev/store/var
VG Name store
LV UUID jy0sqK-iGmC-VzSM-3v1e-FsiT-MU6j-2LXF2A
LV Write Access read/write
LV Status available
# open 1
LV Size 64.00 MB
Current LE 8
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Persistent major 254
Persistent minor 1
Block device 254:1
--- Logical volume ---
LV Name /dev/store/update
VG Name store
LV UUID O0w4f2-4WTg-nQOk-Gzrx-3ZCt-HJsn-pzkWnl
LV Write Access read/write
LV Status available
# open 0
LV Size 16.00 MB
Current LE 2
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Persistent major 254
Persistent minor 2
Block device 254:2
--- Logical volume ---
LV Name /dev/store/log
VG Name store
LV UUID 0bAx4I-B16G-5h0T-ZuN1-0tXv-hOXz-2QVGY7
LV Write Access read/write
LV Status available
# open 1
LV Size 24.00 MB
Current LE 3
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Persistent major 254
Persistent minor 3
Block device 254:3
--- Logical volume ---
LV Name /dev/store/mojodb
VG Name store
LV UUID TRDKpT-jhpg-WiP5-jTmu-CqP8-LuHf-V79EZj
LV Write Access read/write
LV Status available
# open 1
LV Size 256.00 MB
Current LE 32
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Persistent major 254
Persistent minor 4
Block device 254:4
--- Logical volume ---
LV Name /dev/store/filecache
VG Name store
LV UUID hJRmQn-tynn-0wYy-A0pn-27En-iOLF-V3xwhd
LV Write Access read/write
LV Status available
# open 1
LV Size 136.00 MB
Current LE 17
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Persistent major 254
Persistent minor 5
Block device 254:5
--- Logical volume ---
LV Name /dev/store/media
VG Name store
LV UUID qF4wkF-DYew-lsgu-nZw2-X42W-mdRS-Dp3jOW
LV Write Access read/write
LV Status available
# open 1
LV Size 10.64 GB
Current LE 1362
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Persistent major 254
Persistent minor 6
Block device 254:6
--- Logical volume ---
LV Name /dev/store/swap
VG Name store
LV UUID bm5Tzx-sIg1-DHay-FDqg-so0o-JIl3-F0WMr4
LV Write Access read/write
LV Status available
# open 1
LV Size 512.00 MB
Current LE 64
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Persistent major 254
Persistent minor 7
Block device 254:7
--- Logical volume ---
LV Name /dev/store/cm-system
VG Name store
LV UUID Udkiug-8e79-r1ny-3KOC-v9os-HR14-T5trzY
LV Write Access read/write
LV Status available
# open 0
LV Size 304.00 MB
Current LE 38
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 254:8
--- Logical volume ---
LV Name /dev/store/cm-cache
VG Name store
LV UUID LSKR0O-ViBX-kAjw-HOVx-5eO1-DYqf-bJ1T0t
LV Write Access read/write
LV Status available
# open 0
LV Size 200.00 MB
Current LE 25
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 254:9
--- Logical volume ---
LV Name /dev/store/cm-data
VG Name store
LV UUID LXwDzu-ouay-ksUq-baho-57pu-c4AW-9AJbx6
LV Write Access read/write
LV Status available
# open 0
LV Size 1.50 GB
Current LE 192
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 254:10
So, boot up, run Novaterm, and issue the lvm.static command and read what it shows you for your /media/card partition. And check for anything that isn't in the list I just posted.
http://dl.dropbox.com/u/8367832/lvresize.txt
http://dl.dropbox.com/u/8367832/lvdisplay.txt
http://dl.dropbox.com/u/8367832/pvdisplay.txt
http://dl.dropbox.com/u/8367832/vgdisplay.txt
Nothing missing or extra from yours except my mojodb is smaller also:
--- Logical volume ---
LV Name /dev/store/media
VG Name store
LV UUID j9PK6T-zqfm-CP2C-vaPl-UpF7-u4zS-2sMOFa
LV Write Access read/write
LV Status available
# open 1
LV Size 6.75 GB
Current LE 864
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 254:6
Click to expand...
Click to collapse
I think the problem is here:
lvm> vgdisplay
--- Volume group ---
VG Name store
Format lvm2
VG Size 14.19 GB
Alloc PE / Size 1302 / 10.17 GB
Free PE / Size 514 / 4.02 GB
Click to expand...
Click to collapse
but not sure how to fix it
What I would do, if I were you, would be to do a nandroid backup of anything you value, then factory restore your touchpad like THIS THREAD tells you. It'll then allow you to get your partitions back the way they should be. And will give you your 10GB /media/card once you install CM9 again to it.
I got one of those original HP 16GB WIFI TouchPad. I had the famous too-discharged-won't-boot-anymore ( question-mark-battery-logo issue ) 3 times which I managed to resolve through usage of this forum ( Thank you! ) This time, I don't know what to do. Nothing on screen at all, I can only 'see' something through looking at what device the TouchPad appears as on the USB port:
Palm:
Product ID: 0x8070
Vendor ID: 0x0830 (Palm Inc.)
Version: 10.00
Speed: Up to 480 Mb/sec
Manufacturer: bootie
Location ID: 0xfa140000 / 6
Current Available (mA): 500
Current Required (mA): 500
The other mode I can start the TouchPad in is the 'QHSUSB_DLOAD'
QHSUSB_DLOAD:
Product ID: 0x9008
Vendor ID: 0x05c6 (Qualcomm, Inc)
Version: 0.00
Speed: Up to 480 Mb/sec
Manufacturer: Qualcomm CDMA Technologies MSM
Location ID: 0xfa140000 / 6
Current Available (mA): 500
Current Required (mA): 2
Taken from @jcsullins toolbox script, with the TouchPad booted in 'Palm' mode I can enter a few commands and eventually able to establish a SSH connection with my TouchPad.
$ dfu-util -d 0830:8070 -R -D ./tpdebrick-v004/moboot-dfu-v004
$ fastboot flash bootmem ./tpdebrick-v004/TPToolbox-Headless-v004
$ ssh -i ssh-key [email protected]
I can connect to the TouchPad, I have access to pretty all devices ( although screen is still blank ). I've even backed up the entire 16GB flash ( as it is now )
[email protected](none):/mnt# dd if=/dev/mmcblk0 | gzip -c | ssh [email protected] 'dd of=/Volumes/BACKUP_80GB/touchpad_full_image_backup20150124.gz'
Below is just ( for reference the list of the many parititions )
[email protected](none):/mnt# fdisk /dev/mmcblk0
Disk /dev/mmcblk0: 15.9 GB, 15923675136 bytes
1 heads, 16 sectors/track, 1943808 cylinders, total 31100928 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x6d6c6150
Device Boot Start End Blocks Id System
/dev/mmcblk0p1 1 204800 102400 c W95 FAT32 (LBA)
/dev/mmcblk0p2 * 204801 205800 500 4d QNX4.x
/dev/mmcblk0p3 205801 208800 1500 51 OnTrack DM6 Aux1
/dev/mmcblk0p4 208801 30969855 15380527+ 5 Extended
/dev/mmcblk0p5 262144 263143 500 47 Unknown
/dev/mmcblk0p6 393216 394715 750 45 Unknown
/dev/mmcblk0p7 524288 529287 2500 4c Unknown
/dev/mmcblk0p8 655360 675839 10240 48 Unknown
/dev/mmcblk0p9 786432 789431 1500 46 Unknown
/dev/mmcblk0p10 917504 923647 3072 4a Unknown
/dev/mmcblk0p11 1048576 1054719 3072 4b Unknown
/dev/mmcblk0p12 1054720 1062911 4096 f0 Linux/PA-RISC boot
/dev/mmcblk0p13 1062912 1128447 32768 83 Linux
/dev/mmcblk0p14 1179648 30969855 14895104 8e Linux LVM
That great! Now what?
Is my TouchPad really dead?
Can I use it still for Android?
How can I reflash or put back 'Web OS Recovery' ?
With all of the access I feel I have, do I need 'WebOS Recovery' at all?
Can't I just 'DD' one or more of the 14 partitions ?
Rastikan said:
I got one of those original HP 16GB WIFI TouchPad. I had the famous too-discharged-won't-boot-anymore ( question-mark-battery-logo issue ) 3 times which I managed to resolve through usage of this forum ( Thank you! ) This time, I don't know what to do. Nothing on screen at all, I can only 'see' something through looking at what device the TouchPad appears as on the USB port:
Palm:
Product ID: 0x8070
Vendor ID: 0x0830 (Palm Inc.)
Version: 10.00
Speed: Up to 480 Mb/sec
Manufacturer: bootie
Location ID: 0xfa140000 / 6
Current Available (mA): 500
Current Required (mA): 500
The other mode I can start the TouchPad in is the 'QHSUSB_DLOAD'
QHSUSB_DLOAD:
Product ID: 0x9008
Vendor ID: 0x05c6 (Qualcomm, Inc)
Version: 0.00
Speed: Up to 480 Mb/sec
Manufacturer: Qualcomm CDMA Technologies MSM
Location ID: 0xfa140000 / 6
Current Available (mA): 500
Current Required (mA): 2
Taken from @jcsullins toolbox script, with the TouchPad booted in 'Palm' mode I can enter a few commands and eventually able to establish a SSH connection with my TouchPad.
$ dfu-util -d 0830:8070 -R -D ./tpdebrick-v004/moboot-dfu-v004
$ fastboot flash bootmem ./tpdebrick-v004/TPToolbox-Headless-v004
$ ssh -i ssh-key [email protected]
I can connect to the TouchPad, I have access to pretty all devices ( although screen is still blank ). I've even backed up the entire 16GB flash ( as it is now )
[email protected](none):/mnt# dd if=/dev/mmcblk0 | gzip -c | ssh [email protected] 'dd of=/Volumes/BACKUP_80GB/touchpad_full_image_backup20150124.gz'
Below is just ( for reference the list of the many parititions )
[email protected](none):/mnt# fdisk /dev/mmcblk0
Disk /dev/mmcblk0: 15.9 GB, 15923675136 bytes
1 heads, 16 sectors/track, 1943808 cylinders, total 31100928 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x6d6c6150
Device Boot Start End Blocks Id System
/dev/mmcblk0p1 1 204800 102400 c W95 FAT32 (LBA)
/dev/mmcblk0p2 * 204801 205800 500 4d QNX4.x
/dev/mmcblk0p3 205801 208800 1500 51 OnTrack DM6 Aux1
/dev/mmcblk0p4 208801 30969855 15380527+ 5 Extended
/dev/mmcblk0p5 262144 263143 500 47 Unknown
/dev/mmcblk0p6 393216 394715 750 45 Unknown
/dev/mmcblk0p7 524288 529287 2500 4c Unknown
/dev/mmcblk0p8 655360 675839 10240 48 Unknown
/dev/mmcblk0p9 786432 789431 1500 46 Unknown
/dev/mmcblk0p10 917504 923647 3072 4a Unknown
/dev/mmcblk0p11 1048576 1054719 3072 4b Unknown
/dev/mmcblk0p12 1054720 1062911 4096 f0 Linux/PA-RISC boot
/dev/mmcblk0p13 1062912 1128447 32768 83 Linux
/dev/mmcblk0p14 1179648 30969855 14895104 8e Linux LVM
That great! Now what?
Is my TouchPad really dead?
Can I use it still for Android?
How can I reflash or put back 'Web OS Recovery' ?
With all of the access I feel I have, do I need 'WebOS Recovery' at all?
Can't I just 'DD' one or more of the 14 partitions ?
Click to expand...
Click to collapse
Try to (just) load this version of moboot-dfu instead:
https://goo.im/devs/jcsullins/tpdebrick/moboot-dfu-20150128
Do you see small text appear on the screen after loading it?
If so, are there two lines with "a6_test"? If so, what do they say. If not, what does it say on the screen.
If nothing appears on screen, does it show up when you run "fastboot devices" ?
If so, does it allow you to run "fastboot oem klogs 2>&1"? If so, upload the output and give link here.
jcsullins said:
Try to (just) load this version of moboot-dfu instead:
https://goo.im/devs/jcsullins/tpdebrick/moboot-dfu-20150128
Click to expand...
Click to collapse
Ok, from the 'Palm mode' ( POWER + HOME + VOLUME-UP ) for about 30 seconds ...
Code:
dfu-util -d 0830:8070 -R -D moboot-dfu-20150128
jcsullins said:
Do you see small text appear on the screen after loading it?
Click to expand...
Click to collapse
Yes!!! Thank you! I was beginning to think something was damaged as I didn't see anything on screen for long time ( although I was getting some access through SSH )
jcsullins said:
If so, are there two lines with "a6_test"? If so, what do they say. If not, what does it say on the screen.
Click to expand...
Click to collapse
Code:
(bootloader) [2100] a6_test: batt valid=1 percent=0 voltage=3225680
(bootloader) [2110] a6_test: batt temp=19 current=-312 coulombs=0
Although it does says 0 percent, I did let it charge the whole night ( as your tpdebrick tool suggests )
jcsullins said:
If nothing appears on screen, does it show up when you run "fastboot devices" ?
If so, does it allow you to run "fastboot oem klogs 2>&1"? If so, upload the output and give link here.
Click to expand...
Click to collapse
Yes, I see ( finally) stuff on the screen! Again, Thank you! I was beginning to think something was damaged as I didn't see anything on screen for long time.
http://forum.xda-developers.com/attachment.php?attachmentid=3139872&stc=1&d=1422547266
Now can I go ahead and load-up or run your full toolbox software and reformat/setup the entire flash device for Android ?
Hello,
When I try to build my ROM, I keep getting this error, despite setting Xxm to 2 gb. Does this need to be at least 4gb?
I'm running Kubuntu 16.04 on a 4gb ram system. Would it be safe to set it to 4gb while only running 4gb of ram (plus 3gb swap on usb)
Also, please see my original post here for more info:
Code:
hch tee tee pee colon slash slash w11.zetaboards dot com slash Pwnie_Express slash topic slash 30332348
Code:
Out of memory error (version 1.2-rc4 'Carnac' (298900 f95d7bdecfceb327f9d201a1348397ed8a843843 by [email protected])).
GC overhead limit exceeded.
Try increasing heap size with java option '-Xmx<size>'.
Warning: This may have produced partial or corrupted output.
######
echo $ANDROID_JACK_VM_ARGS
-Dfile.encoding=UTF-8 -XX:+TieredCompilation -Xmx2048m
total used free
Mem: 3140 803 1729
Swap: 3271 94 3177
Device: OnePlus 3t Rooted with magisk TWRP installed.
Android 8.0
BusyBox is installed
On PC I have Cygwin 64bit installed with util linux, pv, netcat packages installed, including platform tools.
I'm trying to get into my partition directory user data by-name as I want to make an image of my OnePlus Internal storage and copy it on PC.
I can view cat /proc/partitions
$ adb shell
OnePlus3T:/ # cat /proc/partitions
major minor #blocks name
8 0 119062528 sda
8 1 8 sda1
8 2 32768 sda2
8 3 262144 sda3
8 4 1024 sda4
8 5 512 sda5
8 6 128 sda6
8 7 128 sda7
8 8 512 sda8
8 9 10240 sda9
8 10 10240 sda10
8 11 1024 sda11
8 12 8096 sda12
8 13 16192 sda13
8 14 512 sda14
8 15 118718956 sda15
8 32 4096 sdc
8 33 4052 sdc1
8 64 4194304 sde
8 65 512 sde1
8 66 512 sde2
8 67 2048 sde3
8 68 2048 sde4
8 69 512 sde5
8 70 512 sde6
8 71 2048 sde7
8 72 16 sde8
8 73 512 sde9
8 74 512 sde10
8 75 97280 sde11
8 76 16384 sde12
8 77 1024 sde13
8 78 32768 sde14
8 79 8192 sde15
259 0 8192 sde16
259 1 16384 sde17
259 2 65536 sde18
259 3 65536 sde19
259 4 3080192 sde20
259 5 65536 sde21
259 6 4 sde22
259 7 1024 sde23
259 8 512 sde24
259 9 512 sde25
259 10 256 sde26
259 11 256 sde27
259 12 256 sde28
259 13 256 sde29
259 14 256 sde30
259 15 256 sde31
259 16 4 sde32
259 17 33424 sde33
259 18 2048 sde34
8 16 4096 sdb
8 17 4052 sdb1
8 80 1572864 sdf
8 81 2048 sdf1
8 82 2048 sdf2
8 83 4 sdf3
8 84 512 sdf4
8 48 131072 sdd
8 49 32 sdd1
8 50 4 sdd2
8 51 1024 sdd3
254 0 118718940 dm-0
Can anyone help me to find partition by-name lists on OnePlus 3t? I have also tried Diskinfo to find the details but it didn't helped me. I have also followed this https://forum.xda-developers.com/t/guide-internal-memory-data-deleted-files-recovery.3093292/ but it's getting hard for me to get into the b-name partition list of my device.
Or do you guys know any other alternatives on how to make an image of OnePlus internal storage to PC?
I'm stucked since days. Please need some help.
is there any genius who can help me on this matter?
Have a look at both of these commands:
Bash:
cat /proc/partitions
ls -l /dev/block/bootdevice/by-name
BillGoss said:
Have a look at both of these commands:
Bash:
cat /proc/partitions
ls -l /dev/block/bootdevice/by-name
Click to expand...
Click to collapse
after typing
ls -l /dev/block/bootdevice/by-name
it says system/bin/sh: 1s: not found.
I'm really stucked here.
Lol! The command is lower case L - ls. Not 1 - 1s.
BillGoss said:
Lol! The command is lower case L - ls. Not 1 - 1s.
Click to expand...
Click to collapse
thanks for the clarification bro..