yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Mini General] jacques_xda:
Hi,

I closed the phone and took off the SD card without any problem.

I made an image of the content with ext2explore.

I then use MiniTool Partiton to try to extend the ext4 partition. The problem is there: MiniTool Partition cannot handle the job!

On the SD card, I have one FAT32 Partition and one ext4 linux patition. MiniTool can resize the FAT32 partition, leaving an unallocated space between the FAT32 and the ext4 partition, but it cannot resize the ext4 partition to take advantage of the unallocated space! I can move the ext4 partition closer to the FAT32, leaving the unallocated space at the end; that is all I can do with MiniTool.

Of course I could delete the ext4 partition and create a new one, using all the unallocated space. But then , will I be able to load the ext4 image I created before in that new partition, since it is not the same size? When ext2explore create an image, does it make a clone of the partition (content, size, etc...) there is no explanation or help on that product!

I will try with Gparted to see what it does and try to simply copy the content of the ext4 partition instead of creating an image.

Thank again for helping.

Jacques :)
[Galaxy S III Mini General] Warre101:
Hello Jacques,

That's odd. I did almost exactly the same thing you described here (except for using ext2 rather than ext4) and was able to resize my ext2 partition using Partition Wizard. I first shrunk the FAT32 partition, then moved and resized the ext2 to use all the unallocated space. Have you tried first pressing apply after you shrink the fat32 and move the ext4? In any case, GParted should also work.

I can't help you with ext2explore as I have no direct experience with that program. You might be able to get some help in other parts of this forum.

If you want to try deleting that ext4 partition and creating a new one, you may be able to do this by first unlinking your apps back to your internal memory in Link2SD (as I suggested in an earlier post), re-partitioning and then re-linking with Link2SD.
[Galaxy S III Mini General] jacques_xda:
Hi,

It is realy odd! I created that ext partition with the same tool! Now I can move it, but not resize it....I will try with Gparted with my old computer running Linux (Ubuntu)...later on, expecting it will work fine.

Thanks again,

Jacques :)
[Galaxy S III Mini General] ankit gaur:
I rooted my moto e 2nd gen 4g phone and made partition on my 16gb sd card using ext4 FAT32. After partioning sd card then i inserted it in my phone to use link2sd but when i try to recreate mount script an error pop up every time showing " mount script cannot be created. No such file or directory" please help me. If any solution you know.:(
[Galaxy S III Mini General] jacques_xda:
Hi,

Try to mount with ext2 instead of ext4. I had the same problem trying to mount with ext2; I then try with ext4 and it worked|

Regards,

Jacques
[Galaxy S III Mini General] Warre101:
That looks exactly like the problem I had. I suggest you first try Jacques' idea (changing ext2 into ext4 or vice versa) and if that doesn't work, use the method I put in the very first post. Let us know if you have any problems with that...
[Galaxy S III Mini General] FinalFreeze:
Been trying to get link2sd to work for awhile now

My init-link2sd.sh file looks a bit different though. For me, it looks like:

set +e

echo "$(date) mounting..." >$LOG

sleep4

mount-t vfat-o

rw,uid=1000,gid=1000,unmask=133,dmask=0002 /

dev/block/vold/179:34/data/sdext2 1>>$LOG 2>>

$LOG

mount -t vfat-o

rw,uid=1000,gid=1000,unmask=133,dmask=0002 /

dev/block/mmcblk1p2 /data/ sdext2 1>>$LOG 2>>

$LOG

Mount >> $LOG

echo "$(date) mount finished" >> $LOG

chmod 773 /data/dalvik-cache

Whenever I try to use Link2SD, it gies me the "mount: No such file or directory error," would you be able to help me?
[Galaxy S III Mini General] Warre101:
A couple of things stand out to me; I'll go through the script you posted step by step:

A space is missing between "sleep" and "4". Was it lost in copy-pasting?

I expected this to be on a single line like this:

mount-t [B]vfat[/B]-o rw,uid=1000,gid=1000,unmask=133,dmask=0002 /dev/block/vold/179:34/data/sdext2 1>>$LOG 2>>$LOG

Is it like that in your file?

Anyway, I notice the second argument in the mount command is "vfat". If you use the "recreate mount scripts" in Link2SD, which option do you use for the file system? Does it correspond to the way your SD card is partitioned? I used EXT2.

This is the information you would need to follow the tutorial that I posted. You could try putting the following in an init.d script:

#!/system/bin/sh
sleep 4
mount -t [B]ext2[/B] -o rw,uid=1000,gid=1000,unmask=133,dmask=0002 /dev/block/mmcblk1p2 /data/sdext2

Note that I'm assuming here that your SD card uses an EXT2 partition, as shown in bold.

The last line (starting with chmod) is something I haven't seen before. If you create your own init.d script, you may need to add the same line.
[Galaxy S III Mini General] Stabbey:
Mount script error

Mount Script cannot be created

Moun Invalid arguement

I've been at this every day for a week i inserted the txt file with ur script rebooted and nothing same old bs script error. PLEASE tell me som1 knows A REAL WORKING FIX.

I've tried fat32/ext2 fat32/ext4 fat32/fat32 The mount DOES NOT EXIST. i have int.d support How do I create the mount? Not just a file directory?
[Galaxy S III Mini General] mikeroku:
Hi, I have tried the script, but at restart seems not to run because no mount is done, so no partition.

I use CM13. Any ideas? Thank you.
[Galaxy S III Mini General] Warre101:
That's difficult to tell based on the information you provided. Can you look for this file:

/data/data/com.buak.Link2SD/files/init-link2sd.sh

and post the contents please?
[Galaxy S III Mini General] psantos1091:
Hey...my problem is mounting the second partition...I've been literally trying since yesterday....no luck using the mini tool to format any of the ext's and lost a lot of time trying different fixes....typing in "cannot mount 2nd partition" on google leaves me with so many results that don't have actual fixes...any help?
[Galaxy S III Mini General] Warre101:
Hey guys,

Some time ago my phone started having the exact same problem that Stabbey describes: mounting the second partition no longer works, manually mounting the second partition results in the "Invalid argument" error when running this command in a terminal emulator:

mount -t ext2 -o rw /dev/block/mmcblk1p2 /data/sdext2

This started happening after I installed an update for busybox and some other apps and then rebooted. Something might have changed in the mount applet of busybox with that update, and that might have broken the mount command. Right now I don't know for sure if this is the case; I haven't figured out how to roll back the busybox update yet. In any case, if I can't manually mount, it certainly won't work on startup with init.d, so I'm stuck for now.

I'm sorry I can't give any of you a solution right now. If anyone else wants to take a crack at it, my problems started after installing busybox 1.25.1, so a version *before* that might work.
[Galaxy S III Mini General] yanmingwuyu:
大神你好：

这是个非常厉害的好办法！您帮我解决了这个疑难杂症！让我手机重新获得新生，而且问题分析得非常准确。

致敬！

机油
[Galaxy S III Mini General] Warre101:
It looks like your mount script works and link2sd can correctly access the partition once mounted, but either init.d is not running your script or the mount command isn't working at the time that init.d runs. I have no experience with android 6 so I don't know for sure what the problem is from what you're posting.

Can you test if the 11link2sd.txt script actually runs at boot? There are a couple of reasons why it might not be running: a problem with the file permissions or maybe Android doesn't like that ".txt" extension. Can you add a line to that script that writes a simple log file with the echo command?
[Galaxy S III Mini General] dededefix:
Hi Warre101, I deeply apologised for my very late answer, I had some personal issues, and then as I needed my phone I re-did the merge proposed by Android and forgot to answer you. ?

I think the issue was in the order of booting: I mean the script did run at boot, but after another thing which had as a result the partition mounted (I could see it) but not writable (like you can see but not touch). But, as I needed my phone to be working, I reflashed my ROM, and reinstalled everything, then did again themerge proposed by Android, and it seems to be fine. I say seem because sometime I still have the error message "no more space", when it is quite empty in reality, but let's say it's working enough for my current use, and I will probably look for a solution when it will be a critical issue again ? Anyway, thanks a lot for your answer and having taken the time to think about it !
[Galaxy S III Mini General] Warre101:
No worries, good to see it's working for you! If the problem is that the partition isn't writable, you might possibly be able to solve the problem by re-mounting it with write permission. I've never done this myself however...
[Galaxy S III Mini General] Medeon:
Thanks for the effort of posting this solution. I've tested this on my phone but it is still not working unfortunatly. How or in what directory do I find the init-link2sd.sh file?
[Galaxy S III Mini General] Warre101:
On my phone, it was located in:

/data/data/com.buak.Link2SD/files/init-link2sd.sh

which is the data folder of the Link2SD app. This was a long time ago on an old device though, so it may be different in your case.
[Galaxy S III Mini General] torres1948:
It's great, but my device has no path such as /system/etc/init.d/ ? So, what I can do?

Yours, torres1948.
[Galaxy S III Mini General] Warre101:
I'm assuming you have a newer device than the Galaxy S3 mini that I tested this on, with a more recent version of Android. It's possible that the location of init.d has changed. Unfortunately I can't try this out on my current device, it's not rooted. Also, considering how long ago I wrote this guide, a lot of things in it will probably not work or require a different approach. Please be careful not to break anything!
[Galaxy S III Mini General] torres1948:
Dear Sir, I found several facts:

1. I must use ext4 for formatting second partition of my SD card - Have done it.

2. blkid command shows both devices:

/dev/block/mmcblk1p2 UUID="..." TYPE="ext4"

/dev/block/mmcblk1p1 UUID="..." TYPE="vfat"

3. link2sd asks which format used for second partition and modifies script to use partition type (ext4) for mounting the /dev/block/mmcblk1p2 as /data/sdext2

4. I tried in terminal this command and I saw the result of mounting ...

So I understood the script doesn't run after booting.

I should place the script so that it will run after boot. My knowledge of Android not enough to determine where I should insert it.

Techniсal descriptions:

tablet - Lenovo Tab 3 8 Plus (TB-8703X)

OS - Android MarshMallow v 6.0.1.

Root - Magisk v 24.3

I looked several articles about using user script as boot-script, but places where I can insert our scripts do not exist on my device. The only way is using Magisk guide ref:

Magisk/docs/guides.md at master · topjohnwu/Magisk

The Magic Mask for Android. Contribute to topjohnwu/Magisk development by creating an account on GitHub.

github.com

May you help me to manage with this task or can you advice me to whom I may address?

Yours,

torres1948
[Galaxy S III Mini General] Warre101:
Indeed, what's still missing is a way to run terminal commands automatically at boot. In my original guide I linked to another guide with a method to add init.d support to achieve this. But reading further down in that guide, it seems that this method no longer works on more recent versions of android such as yours. However...

Magisk might give you a different opportunity to run commands at boot. If I read this correctly:

https://xdaforums.com/t/mod-apk-scr...-need-of-custom-kernels.1933849/post-76592455

There's a way to run commands at boot included with Magisk, using a file called post-fs-data.d located in /magisk/.core/

I'm not able to test this myself so there's no guarantee this will work but you could try adding your commands to that file.
[Galaxy S III Mini General] torres1948:
Dear Sir;

I 've wrote small script (just one string 'echo "$(date) boot-check inside..." >/storage/FFD3-CAA2/txt.txt ' and test it inserting in

/data/adb/post-fs-data.d,

/system/etc/init.lct.bootcheck.sh

and found: none of these places work on start. I guess adb and lct defines on which event the script is called. Test shows theese event doesn't happen.

So, I failed seeking somewhat like init.d as you mentioned. If you have init.d may you send me a sample, I want to seek file whitch contains specially selected string in your init.d. I reckon I might find some common fragment?

Yours,

torres1948.
[Galaxy S III Mini General] Warre101:
Do you have a directory /magisk/.core on your device? From what I read, post-fs-data.d should be in that folder
[Galaxy S III Mini General] torres1948:
No, there is not the /magisk/.core, first o all no folder /magisk. I have the folder /data/adb/post-fs-data.d, I suppose it works if adb demon start, really I don't know the schedule of starting processes... .

Yours, Radmir
[Galaxy S III Mini General] Warre101:
Unfortunately I won't be able to help you any further then, as I'm not familiar with Magisk myself. Possibly you will have more luck in a subforum that deals with Magisk specifically. Sorry...
[Galaxy S III Mini General] torres1948:
Dear Sir,

I afraid the magisk offers does not work. Now I find the script /system/etc/init.qcom.post_boot.sh. It really is calling after boot. In the end of it I added call of my own script:

sh /storage/FFD3-CAA2/boot-chk.sh

It contains next commands:

echo "blkid:">>/storage/FFD3-CAA2/txt.txt

blkid>>/storage/FFD3-CAA2/txt.txt

echo "mount:">>/storage/FFD3-CAA2/txt.txt

mount >>/storage/FFD3-CAA2/txt.txt

I reboot and found:

Script worked, but blkid output was empty

Output of mount contains:

/dev/block/vold/public:179,65 /mnt/media_rw/FFD3-CAA2 vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1023,gid=1023,fmask=0007,dmask=0007,allow_utime=0020,codepage=437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0

this is the first partition of external SD.

The second must have dev/block/vold/public:179,66.

Blkid shows there are not both of /dev/block/mmcblk1p1, /dev/block/mmcblk1p2

So the script generated by Link2SD failed cause the necessary devices absent.

My intention is to insert command which make necessary devices visible to blkid.

Do you know what is the name of such command and its syntax?

Excuse me for bothering you of my routine problems. If you have no time you may leave me no answer. I will stop the communication.

Yours,

torres1948.
[Galaxy S III Mini General] Warre101:
Rest assured that your questions aren't bothering me, but I'm in way over my head here - it's been years since I last worked with a rooted phone and a lot of things have changed since then. There's a lot I don't understand anymore! I'm not even sure Link2SD works at all on a device as recent as yours, even if you get the mount working at boot...

Just off the top of my head, here are a couple of things that could be going wrong (but I don't know how to fix any of it):

- your script might be correctly running at boot, but too late, after link2sd has already started

- the syntax of the mount command could be wrong, causing it to fail or produce incorrect results

- link2sd might be looking in the wromg place for the mounted partition, or be entirely incompatible with your version of Android
[Galaxy S III Mini General] torres1948:
O, no! It seems, I found my mistakes. First of all the mount point /data/sdext2 exists and is accessible for read and write. The script generated successfully. The difference from starting is changing type of second partition on ext4, that's all. Now I got a Failure[-6] during moving the app to SD card. If you know where I can get the description of Error -6, let me know. The module link2sd_b is executable, but I don't know what is it's target. So I decided to search other ways to solve my problem.

Regards,

torres1948
[Galaxy S III Mini General] torres1948:
Additionally:

Dear Sir, I agree with you my Android Marshmallow has no init.d module and none of versions of Link2sd will work on it.

I tested about 30 apps from Google Play. Most of then transfers files from internal memory to SD card, not apps. Some of them transfers apps if their OS allows to transfer, really it exploits the OS ability to transfer, my OS has no. And part of remaining use the init.d module.

AppMgrIII only transfers small part of apps (I saw only 8 apps from 193 able to transfer, among them Titanium Backup, but after process of moving my device begin work abnormal, I forced to restore device from TWRP copy. Additionally the moved 8 apps uses only 364 MB from 59 GB and prevents other using it. . That is ridiculous!

I am thinking about flashing my ROM with custom firmware, such as Lineage OS, Pixel, Havoc; but I don't know if they have init.d.

Thank your for advices and help, I understand I should to buy more better tablet.

Yours,

torres1948.
[Galaxy S III Mini General] victorcastillab:
Hi All

I have similar troubles with my Huawei P8 Lite 2017, running with Lineage Os 18.1 Android 11:

- Warning about mounting

- Move to Sd - get "Failure -6"

- Link Dalv. Cache and libr. - get failure "can't statt data/app/ etc

- Link App works, but it's not enough due to small free space

As didn't see Init.d I tried with Post's Link and seems to work fine (verified it by the app); but still receive Mount's warning and I can't move to SD card, only alink apps but not the rest.

Link2sd shows the two partitions, but it sems that system doesn't mount SD correctly at the beginin, so that the Warning / Advice. (I've tried by all formats but didn't work)

Init.d file exists but is not the same as posted, and I don't know a lot about programmierumg to correct it.

Please find attached some images, they could help you, and I'll be very greatfull for your help.

In case of I couldn't solve it, I'm thinking to use SD as internal storage, but I do not want to do that.

Million Thanks in advance for your help!
[Galaxy S III Mini General] victorcastillab:
(By mistake my post were duplicated, but don't find an option to delete it!)
[Android Q&A, Help & Troubleshooting] AndroidAsker:
Hey guys,

I want to install an Android Recovery System to a totally empty android device. After I want to install a stock Android OS. How can I do it?

Thanks,

An Asker
[Android Q&A, Help & Troubleshooting] asif.malick:
Which phone do u have? Variant? Or simply flash stock rom of your phone.
[Android Q&A, Help & Troubleshooting] AndroidAsker:
I think it's a Lenovo A3500-FL, but I haven't OS and Recovery System on it, so I want to install these.
[XDA Assist] sandbsess:
I have a Kindle Fire 5th Generation, os 5.1.1, 7". I have been trying to find a script to root it, but all I can find is for os 5.0.1. According to what I have found, the script for 5.0.1 does not work for 5.1.1. I have a linux computer. Anyone know if I will be able to root this? I would really like to root it so I can get more use out of it.

sandb
[XDA Assist] v7:
Hello,

Thanks for using XDA Assist.

Refer this thread to root your device ->>Amazon Fire 5th Gen [SuperTool] Root, Google play install, block ota updates and more

___

v7

XDA Assist
[Galaxy Note II Q&A, Help & Troubleshooting] amitchawat:
How to get LTE on Samsung Note 2 N7100 in India
[Galaxy Note II Q&A, Help & Troubleshooting] R0B3RTF1SH3R:
you cant
[Galaxy Note II Q&A, Help & Troubleshooting] Trafalgar Square:
LOL. You must buy a N7105 for LTE.
[Galaxy Note II Q&A, Help & Troubleshooting] lilliput222:
I have Lte variant , if u want we can exchange .. Im from New delhi
[Galaxy Note II Q&A, Help & Troubleshooting] Nakul The Great:
Note 2 Ltd dosent work on Indian Networks

You need note 4 I guess as frequencies don't match with note 2 nor with note 3 lte
[Galaxy Note II Q&A, Help & Troubleshooting] variravitejareddy:
group play no video share any solution
[P8lite Q&A, Help & Troubleshooting] klsystem1:
Hi

I have a p8 lite single sim B181. I want to flash to B170 dual sim. Can anyone tell me the steps? ADB flashing or SD flash is OK.

I already flashed another p8 from B133 to B170 with several steps. Is this possible heute too? Direct flashing would be much easier.

Thanks for help.
[P8lite Q&A, Help & Troubleshooting] electrical.mon:
Will u plz help me to go Dual sim version from B133??
[P8lite Q&A, Help & Troubleshooting] klsystem1:
Same AS going from B181. B041c than b052 and ota 170. b041c with ADB flash. B052 SD flash
[P8lite Q&A, Help & Troubleshooting] dereppsteiner:
show this thread and go from step 1 to step 4 update 188 and you have dual sim firmware.

------> http://xdaforums.com/p8lite/general/huawei-p8-lite-android-6-0-marshmallow-t3309796
[Nexus 6P Q&A, Help & Troubleshooting] sjandroiddeveloper:
Need help here

So just purchased my nexus 6p and after reading the index by Heisenberg, I came to know that I have four updates to install.So downloaded all serialwise

But the problem is when I boot into stock recovery and select apply update from SD card it says sdcard not mounted. So how to solve this

Second thing after mounting can I apply all updates serialwise one by one and then reboot or do I have to apply an update and then boot then apply the second one and so on

Thanks
[Nexus 6P Q&A, Help & Troubleshooting] SlimSnoopOS:
Just download MMB29Q from the Google factory image website and fastboot flash the files using your computer. That is the February OTA. Don't bother with older OTAs.
[Nexus 6P Q&A, Help & Troubleshooting] Heisenberg:
It's probably easier just to flash the latest factory images, I have instructions here:

http://xdaforums.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
[Nexus 6P Q&A, Help & Troubleshooting] GuestD0701:
If you use windows you can download factory image and execute the flash all bat file and it flashes it all for you in about 3 minutes via fastboot. Super easy. :)

Here's a how to install fastboot and adb. Literally tales a 20-30 seconds and works great. Fastboot and adb are mandatory for Nexus IMO. http://xdaforums.com/showthread.php?t=2588979
[Nexus 6P Q&A, Help & Troubleshooting] Heisenberg:
Might want to point out that the flash-all.bat wipes the whole devices, this isn't apparent to those who aren't in the know.
[Nexus 6P Q&A, Help & Troubleshooting] sjandroiddeveloper:
the flashall bat also flashes the user data partition right?
[Nexus 6P Q&A, Help & Troubleshooting] GuestD0701:
Yes and that's what wipes data. You can easily flash them separately and do not need user data. I wipe my phone often so I don't care. :)
[Nexus 6P Q&A, Help & Troubleshooting] sjandroiddeveloper:
Well I have the 64 gb variant, so flashing the user data will allocate only 32 gb of space in my phone ( thanks to guide by heisenberg)
[Nexus 6P Q&A, Help & Troubleshooting] GuestD0701:
Don't flash user data. Its not mandatory. :)