Related
This procedure is really dangerous so I have to warn that you can brick your phone. It directly modifies partition tables so if something goes wrong you may have a bricked phone. Do it at your own risk and I'm not responsible for any damage it may cause.
By following the procedure, you acknowledge and accept that the author is not liable for any loss, material or otherwise howsoever caused.
OK, you've been warned Now to the fun part.
This procedure does work but, please, follow it only if you are an advanced user or a developer.
It also has some unnecessary steps but I include them since they can help you to learn something.
Later, I might write an "update.zip" for cwm which automatically does all the work
This works only on top of the existing N4 8G conversion.
So if you're stock etc then you'll need to do N4 8G conversion first, that is to flash the tot listed in N4 conversion topic in LGNPST.
This is a link to the N4 conversion thread: http://forum.xda-developers.com/showthread.php?t=2099784
You also need cwm recovery installed. I did it in sk8's cwm touch recovery. So I suggest using it: http://forum.xda-developers.com/showthread.php?t=2010984
Also, you need an external sd card with at least 100MB(after doing all rom backups) of free space and I recommend to do a filesystem check of the sd card in windows/*nix/osx.
And another requirement is to have working adb and fastboot drivers for Nexus 4.
Before starting the procedure look through all the steps and please stop if you don't understand something. No rocket science here but it's just a dangerous thing to do.
- Download the following 3 files and copy them to your _external_ sd card root directory
Links:
Modified busybox dd : http://d-h.st/cFA
16G Primary GPT(includes MBR): http://d-h.st/yUQ
16G Secondary GPT: http://d-h.st/0dH
- if you care about the content of your internal sd card then back it up somewhere. After doing this conversion all your data and /sdcard will be purged.
- boot into cwm recovery.
- if you care about your current ROM/data do a backup to _external_ sd.
- connect the phone via USB to your pc and on your pc run 'adb shell'. Once in shell:
Code:
# cp /external_sd/dd /
# chmod 755 /dd
- Backup your existing partition tables. Make sure you put / in front of dd to use my modified dd
Code:
# /dd if=/dev/block/mmcblk0 of=/external_sd/pgpt8G.img bs=512 count=34
# /dd if=/dev/block/mmcblk0 of=/external_sd/sgpt8G.img bs=512 skip=30777311
- By default cwm mounts userdata and cache partitions. You need to unmount them
Code:
# umount /data
# umount /cache
- Make sure no partition from /dev/block/mmcblk0 is mounted. df should return only this with no extra rows:
Code:
# df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 911.7M 48.0K 911.6M 0% /dev
/dev/block/mmcblk1p1 59.4G 4.8G 54.6G 8% /external_sd
- Move content of DDR and grow partitions to their new locations. I doubt this step is required, but did it for safety. Seeking to the end of the mmc may take couple of minutes, don't freak out:
Code:
# /dd if=/dev/block/mmcblk0 of=/external_sd/DDR bs=512 skip=15267840 count=2015
# /dd if=/external_sd/DDR of=/dev/block/mmcblk0 bs=512 seek=30775296 conv=notrunc
- Install new partition tables. Seeking to the end of the mmc may take couple of minutes:
Code:
# /dd if=/external_sd/sgpt16G.img of=/dev/block/mmcblk0 bs=512 seek=30777311 conv=notrunc
# /dd if=/external_sd/pgpt16G.img of=/dev/block/mmcblk0 bs=512 seek=0 conv=notrunc
- At this point you have new partition tables installed. Verify this by running parted. You should see this:
Code:
# parted /dev/block/mmcblk0
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) p
p
Model: MMC 016G92 (sd/mmc)
Disk /dev/block/mmcblk0: 15.8GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 524kB 67.6MB 67.1MB fat16 modem
2 67.6MB 68.2MB 524kB sbl1
3 68.2MB 68.7MB 524kB sbl2
4 68.7MB 70.8MB 2097kB sbl3
5 70.8MB 71.3MB 524kB tz
6 71.3MB 94.4MB 23.1MB boot
7 94.4MB 117MB 23.1MB recovery
8 117MB 118MB 799kB m9kefs1
9 118MB 119MB 799kB m9kefs2
10 119MB 120MB 799kB m9kefs3
11 120MB 121MB 524kB rpm
12 121MB 121MB 524kB aboot
13 121MB 122MB 524kB sbl2b
14 122MB 124MB 2097kB sbl3b
15 124MB 124MB 524kB abootb
16 124MB 125MB 524kB rpmb
17 125MB 125MB 524kB tzb
18 125MB 126MB 524kB metadata
19 126MB 143MB 16.8MB misc
20 143MB 159MB 16.8MB ext4 persist
21 159MB 1040MB 881MB ext4 system
22 1040MB 1627MB 587MB ext4 cache
23 1627MB 15.8GB 14.1GB ext4 userdata
24 15.8GB 15.8GB 524kB DDR
25 15.8GB 15.8GB 507kB grow
(parted) quit
quit
Notice that userdata partition is 14.1GB in size
In case parted reports an error I suggest to return back to the old 8G partition tables, see below.
- Reboot the phone into bootloader: run reboot command and hold 'Up' button to enter bootloader menu
Code:
# reboot
- on your pc command line run:
Code:
fastboot erase userdata
fastboot -w
- In phone bootloader enter 'Recovery Mode' to load cwm
- In cwm restore your previous N4 rom from external sd or flash a new N4 rom
PS
In case parted reported an error, put the old 8G partition tables back. This should not happen but never say never:
Code:
# /dd if=/external_sd/sgpt8G.img of=/dev/block/mmcblk0 bs=512 seek=30777311 conv=notrunc
# /dd if=/external_sd/pgpt8G.img of=/dev/block/mmcblk0 bs=512 seek=0 conv=notrunc
reserved
Awww Look at the "community" sharing!!!
really easy process thank you!
This is the final straw for me, I'm gonna try the conversion tonight. Thanks a ton!
Damn, so was this the final problem with the conversion? Does this mean all the bugs have been worked out? If so, this is awfully tempting... haha
blenkows said:
Damn, so was this the final problem with the conversion? Does this mean all the bugs have been worked out? If so, this is awfully tempting... haha
Click to expand...
Click to collapse
For the most part, I think a few people still have issues with NFC, but I think that's just about ironed out too. Goodbye Quickmemo and Q-slide, I'll actually miss you!
Awesome work but I'll wait tell you make a update zip since I don't trust my computer have USB problems
Sent from my LG-E970 using xda premium
Right now I have the little voices in my head. The good guy is saying "NO DUDE! WAIT FOR AOSP! ITS JUST AROUND THE CORNER!". The other dude is saying "OMG JUST DO IT YOU WUSS!"
Mannnnnnn. Now I'm confused as to what I wanna do. Stock JB or convert? Great job. Looks good!
Sent from my LG Optimus G
Neroga said:
Mannnnnnn. Now I'm confused as to what I wanna do. Stock JB or convert? Great job. Looks good!
Sent from my LG Optimus G
Click to expand...
Click to collapse
More like Nexus 4 with SD card and LTE 4.2.2 or LGOG with 4.1.2?
xxgmon3yxx said:
More like Nexus 4 with SD card and LTE 4.2.2 or LGOG with 4.1.2?
Click to expand...
Click to collapse
You know, plus the millions of other possibilities that come along with a nexus.
C2fifield said:
You know, plus the millions of other possibilities that come along with a nexus.
Click to expand...
Click to collapse
No doubt... this phone will be supported for years to come! I'm never getting rid of it.
C2fifield said:
For the most part, I think a few people still have issues with NFC, but I think that's just about ironed out too. Goodbye Quickmemo and Q-slide, I'll actually miss you!
Click to expand...
Click to collapse
If NFC does not work for you, try to flash zip from the 'Notes' section of http://forum.xda-developers.com/showthread.php?p=37518694
Now can people accept the conversion lol so we can move on with our phones?
Sent from my LG-E970 using xda premium
blenkows said:
Right now I have the little voices in my head. The good guy is saying "NO DUDE! WAIT FOR AOSP! ITS JUST AROUND THE CORNER!". The other dude is saying "OMG JUST DO IT YOU WUSS!"
Click to expand...
Click to collapse
Haha, I feel you! I don't even trust myself with the conversion, though :/
But if a flash zip comes out, all hell might break loose!
Sent from my LG-E970 using xda app-developers app
TangoXray said:
Haha, I feel you! I don't even trust myself with the conversion, though :/
But if a flash zip comes out, all hell might break loose!
Sent from my LG-E970 using xda app-developers app
Click to expand...
Click to collapse
Just did it, it's all running smoothly, thanks again!
Seems to have worked here as well. Just restored my nandroid and its booting as we speak. And....... success. 12+ gigs of usable storage. Thanks a ton!!!!
thanks i just did it and works perfect
As I restore my backup, I have to wonder, why do we erase userdata and fastboot -w when a restore from backup works without a problem? Does the backup not look at the partition tables where booting straight up would and freeze up something?
Or is everything wiped from modifying the table and the fastboot part is just to make sure the partitions are empty?
So I am working on a Root Framework Tool used to create Android Root Applications. During this I found one strange issue. Whenever I attempt to output /proc/mounts from ProcessBuilder, I get it returned in reversed order. In the ADB shell there is no problem. Also 'df' bases it's output on a reversed /proc/mounts output when executed from within Java.
My question is if anyone has any idea why? This is the only file I have this problems with, other files in /proc like filesystems, devices, swaps etc get's returned in the same order as when using an ADB shell.
The issue is easy to fix as I can rearrange the output again, but only if can be sure that this is a constant thing which affects all devices, otherwise I will just create the issue on other devices. So far I have only been able to test this on two Android 4.2 devices, so I am not sure if this is a side affect of Android's new multi-user feature (Which uses some new mount features not used in older versions).
The problem with this is that the order of /proc/mounts decides which folder is attached to devices and which are bind mounted to other folders. A reversed list will give incorrect feedback about mount locations.
After checking further I saw that it is not a reversed list, it's more like an ordered list.
Original:
* /dev/block/mmcblk0p12 = /data
* /dev/block/mmcblk1p2 = /sd-ext
* /dev/block/mmcblk1p2 = /data/app
From Java:
* /dev/block/mmcblk0p12 = /data
* /dev/block/mmcblk1p2 = /data/app
* /dev/block/mmcblk1p2 = /sd-ext
It's like it has been ordered based on locations, which makes it even harder to create a fix for.
/proc/mounts is accessible without root, so can you just read it with a FileInputStream, can't you?
ramdroid77 said:
/proc/mounts is accessible without root, so can you just read it with a FileInputStream, can't you?
Click to expand...
Click to collapse
That gives the same result. It seams that each app process in general gets another version of the file.
Sent from my GT-I9300 using xda premium
dk_zero-cool said:
That gives the same result. It seams that each app process in general gets another version of the file.
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
oh well, that's really strange... Doesn't make any sense at all....
Hi.
Thanks to everyone who might give me some help.
I have a new quad-core phone with android 4.2.1, that is now useless. It can not boot, it freeze at second bootlogo, before animation.
It is rooted, and i have made some changes to build.prop. It worked fine, but after some time i realized the gallery and camera app was gone.
Then i did following:
Installed updated standard gallery+camera apk found online, both in the same app. from here http://forum.xda-developers.com/showthread.php?t=2341080
Works great, but i wanted to make it a system app, so did that with titanium backup.
After that, the camera app is gone. Gallery app is still working.
So i tried to change it back to user app, again with titanium, but did not stop working. After some time i took out the battery.
Now it freeze before boot animation.
I tried "wipe data/factory reset" and "wipe cache partition", in system recovery but still not booting!
I tried to backup user data from another phone, same model, and restore on this one but says "Error: checksum compare fail".
Do i need to flash a new rom to the phone with my pc? I have not tried this before, and i want to keep stock rom.
I have read this page:
http://www.chargeforums.com/forum/d...-flashing-roms-return-stock-odin-picture.html
But i can not get it in download mode, with those hotkeys?
If it is to any help, i have acces to other working phones of the same model.
Flashing new? It's look like this. How? I don't know because I have no information over ur phone.
Gesendet von meinem Xperia SP
joke19 said:
Flashing new? It's look like this. How? I don't know because I have no information over ur phone.
Gesendet von meinem Xperia SP
Click to expand...
Click to collapse
Its a noname phone imported from China.
The model is called A999M or Android Grand 1.
I can go in system recovery with volume up + power. But not helping. The only other boot menu i can acces, is only sometimes with volume down + power, i will get a menu but all en chinese.
I managed to get the bad build.prop file from the phone with adb, and see the error in it. But i can not get write acces to change/replace the file.
I compared the build.prop i modified on crashed phone, with working phone and the difference is following all changed to a OEM name (with Capial first letter, that gives problems):
ro.product.name=hexing89_we_jb2
ro.product.device=hexing89_we_jb2
ro.product.board=hexing89_we_jb2
ro.build.product=hexing89_we_jb2
"adb root" returns "adbd cannot run as root in production builds" and all other options like remount for r/w acces gives "remount failed: Operation not permitted"
The phone was rooted with framaroot:
http://forum.xda-developers.com/showthread.php?t=2130276
Would be very glad for some help. If you have the answer to fix it, i might even pay a little for your time.
So adb connects right?
Try this
adb shell
ls -l /dev/block/partitions
And from here keep searching and try to find by name (we are looking for system partition here)
If you can't find it from a shell try
cat /proc/partitions
Or just simply
Mount
If you find system then run this
adb shell
su
mount -o rw,remount /dev/block/mtdblock3 /system
Or whatever path to /system is
Then
You can simply push or use dd commands to push new build.prop and then chmod permissions to 644
Let me know what comes of this, as I know nothing about your phone but it sounds very fixable
Sent from my Nexus 4 using XDA Premium 4 mobile app
demkantor said:
So adb connects right?
Try this
adb shell
ls -l /dev/block/partitions
And from here keep searching and try to find by name (we are looking for system partition here)
If you can't find it from a shell try
cat /proc/partitions
Or just simply
Mount
If you find system then run this
adb shell
su
mount -o rw,remount /dev/block/mtdblock3 /system
Or whatever path to /system is
Then
You can simply push or use dd commands to push new build.prop and then chmod permissions to 644
Let me know what comes of this, as I know nothing about your phone but it sounds very fixable
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Hi.
I can not do that. First i already found the build.prop file. I can simply put "adb shell", and "cd /system", and "ls -all", and then i see the build.prop file.
I can also go youre way and do "mount -o rw,remount /dev/block/mmcblk0p5 /system", but it says "mount: Operation not permitted"
Remember i can not do adb root. I get "adbd cannot run as root in production builds".
I can also not do "su" inside adb shell. Everytime i do, prompt freezes. I think my phone is suposed to prompt me for Su acces, but shows nothing but the boot logo.
So for now, the problem is i have only read acces. No write acces.
Were not looking to list everything in system partition, rather trying to fin the block, I just wrote some random block that I'm sure is not yours unless you have some old mtd phone
In other words don't ls /system but rather /dev/block..... Until you find the block or use cat or mount or whatever to find it so you know what to mount
Also can you get to recovery and use adb there? If so I would recommend this as your system is already goofed up
Sent from my Nexus 7 using XDA Premium 4 mobile app
demkantor said:
Were not looking to list everything in system partition, rather trying to fin the block, I just wrote some random block that I'm sure is not yours unless you have some old mtd phone
In other words don't ls /system but rather /dev/block..... Until you find the block or use cat or mount or whatever to find it so you know what to mount
Also can you get to recovery and use adb there? If so I would recommend this as your system is already goofed up
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Hi.
If i just write "mount" i get:
/[email protected] /system ext4 ro,noatime,noauto_da_alloc,commit=1,data=ordered 0 0
/[email protected] /data ext4 rw,nosuid,nodev,noatime,discard,noauto_da_alloc,data=ordered 0 0
/[email protected] /cache ext4 rw,nosuid,nodev,noatime,discard,noauto_da_alloc,data=ordered 0 0
/dev/block/loop0 /mnt/cd-rom iso9660 ro,relatime 0 0
/[email protected]_f /protect_f ext4 rw,nosuid,nodev,noatime,nodelalloc,noauto_da_alloc,commit=1,data=ordered 0 0
/[email protected]_s /protect_s ext4 rw,nosuid,nodev,noatime,nodelalloc,noauto_da_alloc,commit=1,data=ordered 0 0
If i just write "ls -all" i get:
lrwxrwxrwx root root 1970-01-01 01:00 [email protected] -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-01-01 01:00 [email protected] -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-01-01 01:00 [email protected] -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-01-01 01:00 [email protected] -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-01-01 01:00 [email protected]_f -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-01-01 01:00 [email protected]_s -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-01-01 01:00 [email protected]_ro -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-01-01 01:00 [email protected] -> /dev/block/mmcblk0p7
I hope i got the info you wanted. What should i write next?
Well we know its ext4 file system but we still don't have the block location
Try
ls -l -a /dev/block/platform
And see what you get
Sent from my Nexus 7 using XDA Premium 4 mobile app
Not near a PC so just ran a terminal emulator so I can show you what we hope to find
If you have a by-name directory you're golden, if not we will keep looking
(Hit __ twice by accident in screen shot)
Sent from my Nexus 7 using XDA Premium 4 mobile app
demkantor said:
Well we know its ext4 file system but we still don't have the block location
Try
ls -l -a /dev/block/platform
And see what you get
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Inside "block" i get:
loop0
loop1
loop2
loop3
loop4
loop5
loop6
loop7
mmcblk0
mmcblk0boot0
mmcblk0boot1
mmcblk0p1
mmcblk0p2
mmcblk0p3
mmcblk0p4
mmcblk0p5
mmcblk0p6
mmcblk0p7
mmcblk0p8
mmcblk1
mmcblk1p1
platform
vold
Inside "platform" i get:
mtk-msdc.0
mtk-msdc.1
Inside "mtk-msdc.0" i get:
by-num
mmcblk0 -> /dev/block/mmcblk0
mmcblk0boot0 -> /dev/block/mmcblk0boot0
mmcblk0boot1 -> /dev/block/mmcblk0boot1
mmcblk0p1 -> /dev/block/mmcblk0p1
mmcblk0p2 -> /dev/block/mmcblk0p2
mmcblk0p3 -> /dev/block/mmcblk0p3
mmcblk0p4 -> /dev/block/mmcblk0p4
mmcblk0p5 -> /dev/block/mmcblk0p5
mmcblk0p6 -> /dev/block/mmcblk0p6
mmcblk0p7 -> /dev/block/mmcblk0p7
mmcblk0p8 -> /dev/block/mmcblk0p8
Inside "mtk-msdc.1" i get:
by-num
mmcblk1 -> /dev/block/mmcblk1
mmcblk1p1 -> /dev/block/mmcblk1p1
Sorry I'm blind, your mount showed /system is being called android, so you need to change the mount command from earlier to mmcblk0p5 from mtd....
Also did you try running adb from recovery mode?
Sent from my Nexus 7 using XDA Premium 4 mobile app
demkantor said:
Sorry I'm blind, your mount showed /system is being called android, so you need to change the mount command from earlier to mmcblk0p5 from mtd....
Also did you try running adb from recovery mode?
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I just tried:
[email protected]:/ $ mount -o rw,remount /dev/block/mmcblk0p5 /system
mount -o rw,remount /dev/block/mmcblk0p5 /system
mount: Operation not permitted
I think its because i can not do "su". Its just stops when i write it, and waiting on an empty line.
In system recovery i tried "wipe data/factory reset" and "wipe cache partition". But it does not help, since it will not recover system files like build.prop that is faulty. I also tried to "apply update" from zip and adb with the correct build.prop. But it can not apply it.
What recovery do you have? Stock? Custom?
Have you tried adb through recovery?
After you hit su does the prompt change from $ to # ?
Actually if you copy and paste all input/output from cmd/terminal when you try them out it is easier to help fix
Sent from my Nexus 7 using XDA Premium 4 mobile app
demkantor said:
What recovery do you have? Stock? Custom?
Have you tried adb through recovery?
After you hit su does the prompt change from $ to # ?
Actually if you copy and paste all input/output from cmd/terminal when you try them out it is easier to help fix
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I believe its just stock recovery. When im in recovery menu, i can not connect with adb.
C:\Users\Dennis>adb shell
[email protected]:/ $ su
su
-waiting on this empty line-
Mmm.... Does the oem have a website, often if you can find it there will be stock firmware/software with instructions on how to flash it. Like through fastboot or some download mode (maybe that Chinese writing screen - try getting a photo of it and see if someone will be nice and translate it for you)
Often there is some flash suite for these no-name devices like rockchips have as well as some well known OEMS
But without root access and no oem software this may be more difficult than I hoped, check around a bit and let me know what you find
Sent from my Nexus 7 using XDA Premium 4 mobile app
demkantor said:
Mmm.... Does the oem have a website, often if you can find it there will be stock firmware/software with instructions on how to flash it. Like through fastboot or some download mode (maybe that Chinese writing screen - try getting a photo of it and see if someone will be nice and translate it for you)
Often there is some flash suite for these no-name devices like rockchips have as well as some well known OEMS
But without root access and no oem software this may be more difficult than I hoped, check around a bit and let me know what you find
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Okay thank you. Im thinking if its possible to take a nandroid backup from a working phone (my girlfriend have one too), and recover on this one. But dont know if i can recover without root acces?
No worries, does your recovery have a nandroid backup and install function? If so then this would be ideal! The other option maybe to use dd commands to take her system.img and restore to yours through dd, but to me this is always a last resort as dd didn't get/the nickname disk destroyer for nothing! (_although it is safe so long as you don't mistype)
But start by looking for oem software and a flash mode if your recovery doesn't have backup restore options
Sent from my Nexus 7 using XDA Premium 4 mobile app
demkantor said:
No worries, does your recovery have a nandroid backup and install function? If so then this would be ideal! The other option maybe to use dd commands to take her system.img and restore to yours through dd, but to me this is always a last resort as dd didn't get/the nickname disk destroyer for nothing! (_although it is safe so long as you don't mistype)
But start by looking for oem software and a flash mode if your recovery doesn't have backup restore options
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
There is no oem software, i have to work it out myself. The stock recovery only have options to backup and restore "user date". Not the system. But still i already tried to restore a backup from another phone, but get checksum error. I tried a few workaround for this, but didnt help.
I think i need to learn how to do a full nandroid copy. But i just hoped it was possible to just copy the one file i need, and not everything.
...if its just data partition then this won't help. The only ways I know how to do a nandroid is with a custom recovery (you don't have)
Adb http://forum.xda-developers.com/showthread.php?t=1021625
But as you can see requires root
Some apps - you have no os
Utilities like android commander or droid explorer -_ need root
So this leaves dd commands, but maybe keep digging for stock website or getting someone to translate that screen for you (may be what you're after)
Best of luck!
Sent from my Nexus 7 using XDA Premium 4 mobile app
It's safe to enable this feature on a ext4 sdcard partition? I'm placing this script before link2sd mounts the partition:
#!/system/bin/sh
tune2fs -o journal_data_writeback /dev/block/mmcblk1p0
I should add other lines?
Thanks!
Sent from my WT19i using XDA Premium 4 mobile app
Hello!
I linked some apps to SD card second partition with Link2SD app.
After restarting my device the linked apps were missing.
I used the quick reboot feature, which fixed the problem temporary.
Do I really have to quick reboot my phone after every reboot to access the linked apps or is there a way to fix this problem?
write your own mount script.
aIecxs said:
write your own mount script.
Click to expand...
Click to collapse
I don't know how to, but I found the file which has the problem.
What should I make writeable: Group/Global?
Is it safe to change those settings?
Sorry, I'm a noob
get yourself a root explorer and find the /data/adb/service.d directory. there should be mount script for Link2SD. please show the contents of this file.
aIecxs said:
get yourself a root explorer and find the /data/adb/service.d directory. there should be mount script for Link2SD. please show the contents of this file.
Click to expand...
Click to collapse
I found the folder, but it's empty.
okay then create one. set permissions executable. replace mmcblk1p2 with proper partition.
/data/adb/service.d/40link2sd
Bash:
#!/system/bin/sh
test -d /data/sdext2 || exit 1
umount -l /data/sdext2
until grep -q /data/sdext2 /proc/mounts; do
mount -t ext4 -o rw,nosuid,nodev,noatime,nodiscard /dev/block/mmcblk1p2 /data/sdext2
sleep 1
done &
edit: fixed typo: grep (missing file name)
aIecxs said:
okay then create one. set permissions executable. replace mmcblk1p2 with proper partition.
/data/adb/service.d/40link2sd
Bash:
#!/system/bin/sh
test -d /data/sdext2 || exit 1
umount -l /data/sdext2
until grep -q /data/sdext2; do
mount -t ext4 -o rw,nosuid,nodev,noatime,nodiscard /dev/block/mmcblk1p2 /data/sdext2
sleep 1
done &
Click to expand...
Click to collapse
Thanks for your help, but as I said I'm a beginner so there are a few things I don't understand.
- What is the extension of the file?
- How to exactly set the RWX settings?
- Should I put a space after mmcblk1p2, then type ext4?
no suffix. like in your screenshot. spaces matter.
aIecxs said:
no suffix. like in your screenshot. spaces matter.
Click to expand...
Click to collapse
space matter. Like this?
/dev/block/mmcblk1p2 ext4/data/sdext2
no. exactly as in post #6
aIecxs said:
no. exactly as in post #6
Click to expand...
Click to collapse
you said replace mmcblk1p2. what does that mean? how to?
check cat /proc/partitions from terminal which is the 2nd partition of your MicroSD card. if you did not create 2nd partition yet, will tell you.
aIecxs said:
check 'cat /proc/partitions' which is the 2nd partition of your MicroSD card. if you did not create 2nd partition yet, will tell you.
Click to expand...
Click to collapse
i have the second partition, but what do you mean replace mmcblk1p2 ?
which is the block device name of your second partition?
aIecxs said:
which is the block device name of your second partition?
Click to expand...
Click to collapse
ext4? im not sure if you meant that
get a terminal emulator app (or connect phone to PC adb shell) and check the output of following command:
Code:
cat /proc/partitions
aIecxs said:
get a terminal emulator app (or connect phone to PC adb shell) and check the output of following command:
Code:
cat /proc/partitions
Click to expand...
Click to collapse
if your 2nd partition is mmcblk1p2 then just mount /dev/block/mmcblk1p2 as in post #6 (nothing to replace)
aIecxs said:
if your 2nd partition is mmcblk1p2 then just mount /dev/block/mmcblk1p2 as in post #6 (nothing to replace)
Click to expand...
Click to collapse
How can I check that? I dont understand the output of the command
you can double check first partition with grep /dev/block/vold /proc/mounts
Code:
:/ $ grep /dev/block/vold /proc/mounts
/dev/block/vold/public:179,129 /mnt/media_rw/8075-15FD vfat rw,dirsync,nosuid,nodev,noexec,noatime,uid=1023,gid=1023,fmask=0007,dmask=0007,allow_utime=0020,codepage=437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
in my case 1st partition is
179 129 1935608 mmcblk1p1
therefore next minor is 2nd partition
179 130 1935607 mmcblk1p2