Database Develop

Test if apps installed on SD?

Just installed cyanogens rom and started adding apps from an 'appmanager' folder on the SD card- but I cannot see them in a seperate folder on the SD - is it just running them in the 'appmanager' folder? Or is apps2sd not working and installing stuff on my internal memory?
( I have 3 partitions by the way, one ext2 /3 not sure which, the last one a 'swap' from early 'hero' install)
Thanks

you need an ext2/ext3 partition for apps2sd to work. if you have such a partition then cyanogen rom is installing apps there automatically.

open an adb shell and cd to /system/sd
if there are some folders, the apps2sd is running (the ext partition is mounted under /system/sd)
You can also run this in terminal but there you need to run the "su" command first

Sorry, noob!
Ok I opened 'terminal emulator', did 'su' allowed root and then
cd /system/sd
'ls' to see directory right? just shows 'placeholder' so somethings wrong?
Is there an easy fix and can I move all the apps I just installed over?
Thanks!

looks like no apps2sd(the partition might be there, but no apps were moved at this time)
just create an ext3 partition on your sd card and install your favourite rom. cyanogen will move all apps automatic (long long first boot).
on other roms you might have to run the apps2d.sh script to move the apps. just read the corresponding thread for your rom. you will find all information there.

FireFart - you mean cyanogen? That's the one I installed, before adding these apps!
If I flash it again won't it wipe all installed apps?
Is it worth trying to run this apps2d.sh script?

try this guide:
http://forum.xda-developers.com/showthread.php?t=535232
When you just flash another update.zip, your apps wont get deleted(with and without apps2sd).
When nothing works, wipe, delete the ext partition and make a fresh install
To delete the content on the ext partition:
rm -rf /system/sd/*

I would agree with the thread you linked, however the apps2sd section is not necessary. as already stated, cyanogen's rom does this automatically (most do now), and installing apps2sd will (i believe) implement an outdated/slower method of 'symlinks'.
in short: use the thread for a guide, but ignore the app2sd section. its a good guide for the partitioning of your sd card (this part IS necessary)
FireFart said:
try this guide:
http://forum.xda-developers.com/showthread.php?t=535232
When you just flash another update.zip, your apps wont get deleted(with and without apps2sd).
When nothing works, wipe, delete the ext partition and make a fresh install
To delete the content on the ext partition:
rm -rf /system/sd/*
Click to expand...
Click to collapse

Ok , tried reflashing, no effect it seems. ... from what I've seen the thread on partitioning was pretty much the same as the one I used.
FireFart said:
try this guide:
http://forum.xda-developers.com/showthread.php?t=535232
When nothing works, wipe, delete the ext partition and make a fresh install
To delete the content on the ext partition:
rm -rf /system/sd/*
Click to expand...
Click to collapse
you mean wipe it's contents right?

he means do a wipe on the recovery screen (ALT+W) AS WELL AS remove contents from ext partition.
the recovery console wont touch the ext partition when performing an ALT+W.
im not sure thats the issue though. just to verify, the order of your partitions on the SD is: FAT32/ext, correct? the FAT32 partition must be the first partition, and the ext the second.
EDIT: can u post the results of running a 'mount' cmd? you should have a line that reads something like:
Code:
/dev/block/mmcblk0p2 on /system/sd/ type ext3 (rw,noatime,nodiratime,barrier=1,data=ordered)
jomtones said:
Ok , tried reflashing, no effect it seems. ... from what I've seen the thread on partitioning was pretty much the same as the one I used.
you mean wipe it's contents right?
Click to expand...
Click to collapse

phantasm -sorry, noob, not sure what you mean!
partitions currently look like this (as JAC instructions)
http://i70.photobucket.com/albums/i120/jomtones/IMAGE_829.jpg
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Maybe having 3 parts is throwing it? confused!

[Solved] Can't flash ROM?

Hi, i try to flash Cyan's new rom v4.0.1, but i keep getting this error message in my recover console:
E:Can't mount /dev/block/mmcblk0p1 (or /dev/block/mmcblk0)
(No such file or directory)
E:Can't mount SDCARD:update.zip
Installation aborted.
After trying unsuccesfully to flash the rom, my sdcard can no longer be seen in my phone and it became write-protected, unable to move files into the sdcard. Appreciate your help....
Edit: Yeah solved this menacing but simple problem which i found out is my sd card fault. Since i couldn't access sdparted in the recovery console, i had to use Ubuntu to partition my sd card again. Sighs... now i have to replace everything back into phone. Thanks anyways for those who gave advice.

is your sdcard formatted to fat32? because /dev/block/mmcblk0p1 or /dev/block/mmcblk0 is referencing your first partition or your sdcard respectively.

you dont flash a rom in consol
you flash it from the recovery screen. you probably CAN flash it from consol, but its much easier to flash from the recovery screen. what recovery image do you have?

david1171 said:
is your sdcard formatted to fat32? because /dev/block/mmcblk0p1 or /dev/block/mmcblk0 is referencing your first partition or your sdcard respectively.
Click to expand...
Click to collapse
yes my sdcard is fat32(1st partition) and my 2nd partition is ext3 whilst the last is a linux-swap partition...

oshizzle1991 said:
you flash it from the recovery screen. you probably CAN flash it from consol, but its much easier to flash from the recovery screen. what recovery image do you have?
Click to expand...
Click to collapse
Using Cyan's Recover 1.4. How do you flash from the console? commands?

Scholesville said:
Using Cyan's Recover 1.4. How do you flash from the console? commands?
Click to expand...
Click to collapse
Have you tried using the CM Updater?

Scholesville said:
yes my sdcard is fat32 and my 1st partition is ext3.
Click to expand...
Click to collapse
Well I've Always had the best luck with my partitions in order as follows Fat32-Ext3-Linux-Swap(if you use it)
And if you still have problems this is what I do
Well I re-downloaded the update. and did this.
This is how I installed without any problems:
: rename to update.zip
: place in the root of sd card
: shut off device
: boot into recovery
: wipe (alt w)
: go to console (alt x) and hit enter
(enter)
# mount -o rw /dev/block/mmcblk0p2 /system/sd
# cd /system/sd
# rm -rf /system/sd/*
# reboot recovery
: now wipe again (alt w)
: run a filesystem check from the menu. If it tells you to run it manually,
drop to a console (alt+x) and run "e2fsck /dev/block/mmcblk0p2".
: flash
Enjoy!!
Hope this helps!!!

yourtravelboy said:
Well I've Always had the best luck with my partitions in order as follows Fat32-Ext3-Linux-Swap(if you use it)
And if you still have problems this is what I do
Well I re-downloaded the update. and did this.
This is how I installed without any problems:
: rename to update.zip
: place in the root of sd card
: shut off device
: boot into recovery
: wipe (alt w)
: go to console (alt x) and hit enter
(enter)
# mount -o rw /dev/block/mmcblk0p2 /system/sd
# cd /system/sd
Hope this helps!!!
Click to expand...
Click to collapse
The problem is i can't even mount mount my 2nd partition, and everytime i write the command > # mount -o rw /dev/block/mmcblk0p2 /system/sd < , it justs says no such file or directory found.
I also can't go into parted in the recovery console so the now the problem is i can't even reformat my card. I'm going to try Ubuntu and reformat my card and partition it again. Sighs...

please, can you tell me how did you solved it, did you use ubuntu to reformat the sdcard? thanks in advance..

q2box said:
please, can you tell me how did you solved it, did you use ubuntu to reformat the sdcard? thanks in advance..
Click to expand...
Click to collapse
Yes, since i was not able to access parted in the recovery console, my only choice was to use Ubuntu: Partition Editor. When i diagnose my sdcard, i manage to format only my ext3 partition so my fat32 remain unchanged. You need to go download Ubuntu OS, then try to install or LiveCD the Ubuntu. There is a thread under android development which will guide you on how to do this...

Tips for Increasing the internal memory (/data partition) to 1.5G

I had tried many ways including A2SD and stuffs. But the best way I found is mounting /dev/block/mmcblk0p2 -> /data. I had also modified some scripts and now my htc salsa is having huge internal memory over my sdcard. The methods are in my blog.
New URL: http://wiki.bluebert.info/index.php?title=HTC_Salsa_C510e_Rooting
Some of the details and images are from here and files too. The only difference is I am using the recovery method to alter some scripts and forever it will auto mount the second partition of my sdcard to /data and I will never ever worry about the internal memory issue for my htc salsa

Please update the link
hi,
Can you please update the link as i am not able to browse it.Thanks in advance

wiki.bluebert.info/index.php/HTC_Salsa_C510e_Rooting

If unable to view please let me know. Thanks.

Its nice Blog
Hi,
Thanks for updating the link.I read your blog and have few queries:-
What happens when you connect your device to PC. Memory card is unmounted.So your phone thinks that internal memory is unmounted?
Did you got my point?
Can you tell me what are these partitions?
/dev
/mnt/asec
/mnt/obb
These three partitions take 209mb individually.
What about the battery.How is your phone's battery backup?

chinu1984 said:
Hi,
Thanks for updating the link.I read your blog and have few queries:-
What happens when you connect your device to PC. Memory card is unmounted.So your phone thinks that internal memory is unmounted?
Did you got my point?
Can you tell me what are these partitions?
/dev
/mnt/asec
/mnt/obb
These three partitions take 209mb individually.
What about the battery.How is your phone's battery backup?
Click to expand...
Click to collapse
1. The memory card only will be unmounting the FAT32 partition but not the EXT3/EXT2 partition. It just thinks that is another disk Currently the latest file system I am using is ext3 instead of ext2.
2. /dev: is the folder that contains all the devices files and pointers.
/mnt/asec: is the mount point for the apps that had moved to SDCard. url: groups.google.com/group/android-porting/browse_thread/thread/38b1768ed6a5e1a8
/mnt/obb: StorageManager is the interface to the systems storage service. The storage manager handles storage-related items such as Opaque Binary Blobs (OBBs).
OBBs contain a filesystem that maybe be encrypted on disk and mounted on-demand from an application. OBBs are a good way of providing large amounts of binary assets without packaging them into APKs as they may be multiple gigabytes in size. However, due to their size, they're most likely stored in a shared storage pool accessible from all programs. The system does not guarantee the security of the OBB file itself: if any program modifies the OBB, there is no guarantee that a read from that OBB will produce the expected output.
What do you mean about the phone battery backup?
Basically, what I am doing is actually making sure that even I unplug my /data my phone still be able to start back and also I can have any size for my internal memory. Currently, I had migrated to a 16GB class 10 sdcard and it performs like a charm.
I had noticed on my 8GB class 4 SDCard a bit lagging. So try to get a high speed sdcard and it really helps on this case. So once you had done this mod and you still maintains the original HTC firmware yet you get a very large internal disk.
But remember, whatever you do on the phone, please backup the images using the ClockworkMod. It will save your life. Happy modding

Summarize of the increasing internal memory process...
1. Make sure S-OFF
2. Flash the recovery partition with the clockworkmod
3. Boot into clockworkmod recovery and backup the original /data /system and all the partitions using the clockworkmod recovery.
4. Install the root.zip using the clockworkmod for rooting it
5. If fails we still able to revert back to original firmware.
6. If everything good, you should be root now. Once you get the root, install busybox and superuser. This is needed for the partition process.
7. Reboot back to recovery and make another backup.
8. Make the new ext2 partitions using the busybox or you can do this on any linux terminals on your desktop pc.
9. Upload the modified htcfs and copy everything from /data -> new ext2 partition.
10. The htcfs will auto mount the /data before everything starts and there you go with your newly created partitions size. This is how you get the huge internal memory size on your sdcard.

2nd day of my usage of the /data on sdcard.
I had bought a 16GB class 10 SDCard and partitioned into 4GB for /data as ext3 and the rest for /sdcard as fat32. Currently, I am consuming only 342MB/3.6GB. Which I am quite happy with it.
Below are the things I had found out:
1. Sometimes when there are some heavy process on going it will be a bit slow. Especially when turning on the screen after the screen when to power saving mode. Not all the time but when it is heavily transferring something inside the /data which is the sdcard. This is why we need a high speed sdcard.
2. I am using ext3 instead of ext2. ext3 partition seems a bit stable than ext2. I am not sure yet but will keep on trying.
I will keep on posting and hopefully people out there can do the same on the phone for enjoying the huge internal data storage for the apps. Now I no longer need to remove my apps away from my phone anymore

this sounds like a fantastic idea
i have a questioned
i rooted my gf's phone,installed links2sd,created a ext2 partition and removed a whole bunch of bloat
would me using your method now cause problems or instability on her phone?
i'd love to try this out tonight if possible

vickyboicancan said:
this sounds like a fantastic idea
i have a questioned
i rooted my gf's phone,installed links2sd,created a ext2 partition and removed a whole bunch of bloat
would me using your method now cause problems or instability on her phone?
i'd love to try this out tonight if possible
Click to expand...
Click to collapse
It may unstable unless you are pretty clear what you are migrating and redo the softlink.
The best to try with a clean and possible a few important apps installed like the file expert, root checker, superuser and busybox then you copy the whole /data to the ext2 partition of the sdcard and mount it with my method.
Again, remember to back up everything before trying it.

http://www.facebook.com/pages/HTC-Android/265046560194954
This is my FB HTC page.

Found some minor bug but is repairable. As long as you do not eject the sdcard after power off the HTC (where I had already enabled the fastboot) then everything should be fine. But just in case, like my case I had switched off the phone then I eject my sdcard for copying some files and reinsert it back then power on the phone and all my apps become unstable and not usable. This is because I had enabled the fastboot and some files are reside in the memory.
What you can do is:
1. Do not panic. Let it starts. Everything still in the ext3 partition.
2. use the adb command and run as below:
# sudo adb shell
# /system/bin/fix_permissions
If you have encounter some cut command not found that is not a main issue. Is fixable. You just need to remount the /system folder as rw and softlink the busybox as cut. Something like below:
# su
# mount -o rw,remount dev/block/mtdblock3 /system
# cd /system/xbin/
# ln -s busybox cut
Once done, re-run the /system/bin/fix_permissions again.
3. Wait for the process the fix all the file permission issues.
4. Then reboot the phone again:
# adb reboot
What is the fix_permissions about? Below link is the details on it:
http://wiki.cyanogenmod.com/wiki/Fix_permissions

mount Internal to internal??
Hi,
In spite of mounting and external drive with ext-3 partition onto /data. cant me mount an internal drive may be /dev/obb onto /data?
What will be the advantages and disadvantages?

chinu1984 said:
Hi,
In spite of mounting and external drive with ext-3 partition onto /data. cant me mount an internal drive may be /dev/obb onto /data?
What will be the advantages and disadvantages?
Click to expand...
Click to collapse
Defeating the purpose. The reason why we need to mount to the sdcard is to get extra disk space. I am using this method to trick the system thinks that it have a very huge space and eventually all from the external sdcard partition.
The /dev/obb... is just a tmpfs. Try to do a mount command to get the output then you will get a clearer picture on this. For my case, is /mnt/obb and just a tmpfs which is useless.
tmpfs is a temporary file system where it will be gone after power off.

Hi,
Where can i get this XTC Clip to S-OFF??

chinu1984 said:
Hi,
Where can i get this XTC Clip to S-OFF??
Click to expand...
Click to collapse
Read my Facebook page on the last second post.

Below images are the screenshots from my HTC Salsa.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The above image is after the /data remounted to my sdcard. Originally was 150MB and now is 4GB.
After I had installed many apps I am still having lots of space.

I had simplified the process:
What I am intend to do is to extend the /data (internal memory) to sdcard.
1. Install Busybox.
2. Install Sudo Checker and all the sudo tools.
3. Once this done, we will need to partition the sdcard. Please be making sure all the data are backup. I am not going to be responsible on that
4. Use the hardware method by pressing the volume down and power button to enter the recovery mode or using the adb command "adb reboot recovery".
5. Use the recovery tool and backup the existing working image to the sdcard before proceeding next step. It will be useful to have the recovery image in hand. You will never know when you going to make the mistakes.
6. Once done, lets proceed with the adb command on the linux / windows terminal.
7. Before we start lets prepare some simple shell scripting. What we are trying to do here is to create a file and replaces the existing htcfs on the /system/bin/htcfs. I am not sure what is the use of mounting this htcfs on /data/htcfs and is empty. But I will put back this to my script in future. What I had done was move the original htcfs to htcfs.original and put my version of htcfs which it will auto starts every power off or reboot. Below are the codes:
Filename: htcfs
#!/system/bin/sh
/system/xbin/busybox mount -t ext2 /dev/block/vold/179:2 /data
/system/bin/htcfs.original $1 $2 $3 $4 $5 $6
8. Now lets rename the original htcfs in the phone before we copy our version into the phone. At the same time we do partitioning on the SDcard.
# adb shell
# mount -a
# cd /system/bin/
# busybox cp htcfs htcfs.original
# exit
# adb push htcfs /system/bin/
# adb shell
# cd /system/bin
# chmod 755 htcfs
# chown root.shell htcfs
# fdisk /dev/block/mmcblk0
# mkfs.ext2 -m 0 /dev/block/mmcblk0p2
# mount /dev/block/mmcblk0p2 /sd-ext
# cd /data
# busybox cp -a . /sd-ext
# sync
# cd /
# umount /sd-ext /sdcard /data /system
# exit
# adb reboot
The above steps are creating an EXT2 partition on the SDCard. My version I created a 1.5G as my /data space.
So, basically the htcfs is mounting the /data from my sdcard on every reboot before all the applications start up. There is a step to copy all existing /data to the sd-ext and that is the trick to make the phone thinks that is using the internal memory and we have no longer facing insufficient disk space on cheaper android phones or on some branded HTC phones with little amount of internal disk.
Remember, the above steps are only for rooted phones. My phone until now still working great and with 4GB internal memory (mounted from SDCard as ext3).
I am working on a Linux Terminal for the above steps.

I have problem to get XTC Clip.
Is it possible we can S-Off without using XTC Clip?

luxoriouz said:
I have problem to get XTC Clip.
Is it possible we can S-Off without using XTC Clip?
Click to expand...
Click to collapse
Not at the moment.

[MOD][AD2SDX] Increase Internal Memory without loosing Performance

I just came across this script "AD2SDX - AMARULLZ DATA TO SD-EXT" which is still in alpha stages it works fine on Arc. I tested today on my MIUI ROM.
WHAT IS IT??
This mod will move all Internal Memory (data) into sd-ext, "but not like data2ext", this mod will maintain the performance, because it still place dalvik-cache and system application data in Internal Memory.
Here is a screenshot of my "Manage Application" :
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Note: This script is still in alpha stages so users who are not sure please don't try it. It can potentially brick you SD or can cause bootloops. I don't know a method to uninstall this yet.
HOW IT WORK??
The script will do this in the first boot:
Move Mounting Internal Memory (/data) Into /sd-ext
Mount SDCard-Ext (mmcblk0p2) partition into /data
Create dalvik-cache directory in Internal Memory data (/sd-ext), and symlink it to mmcblk0p2 (/data)
Create data directory in mmcblk0p2 (/data) And symlink it into Internal Memory data (/sd-ext)
Create symlink of app, app-private, app_s and lib_s from mmcblk0p2 (/data) to Internal memory data (/sd-ext)
Create symlink for all non-symllink of Internal Memory data (/sd-ext) into mmcblk0p2 (/data)
After Initializing Setup (First Boot), reboot the system (Just reboot, don't go into recovery), the mod will automatically do this following:
Create data_s in Internal Memory data (/sd-ext)
Move All mmcblk0p2(/data)/data/com.htc* and com.android* into Internal Memory data(/sd-ext)/data_s
Create symlink all files/directory from Internal Memory data (/sd-ext)/data_s/* into mmcblk0p2(/data)/data/ So the System Application Data still read into Internal memory, but rest Application Data will read Into SDCard.
More Information and download:[MOD][AD2SDX][ALPHA02] New Data To SD-EXT Mod - AMARULLZ DATA TO SD-EXT

A lot of people has read your thread, but nobody has answered.
I tried to use it. I have an sd-ext partition, but I don't remember if it's ext2, 3 or 4. I tried anyway and out caused a boot loop. So I'm guessing I don't have my partition formatted as ext4. I don't have access to a computer right now, so I will have to wait to test it again.
Thank you for your link.
Fb

can this be used with the neo ? using inteks kernel (it doesn't have ext support yet) i.e can this add the ext support to that kernel ? thanks !

skyboyextreme said:
can this be used with the neo ? using inteks kernel (it doesn't have ext support yet) i.e can this add the ext support to that kernel ? thanks !
Click to expand...
Click to collapse
Your kernel need init.d support. Then I believe it should work.

ShyamSasi said:
I just came across this script "AD2SDX - AMARULLZ DATA TO SD-EXT" which is still in alpha stages it works fine on Arc. I tested today on my MIUI ROM.
WHAT IS IT??
This mod will move all Internal Memory (data) into sd-ext, "but not like data2ext", this mod will maintain the performance, because it still place dalvik-cache and system application data in Internal Memory.
Here is a screenshot of my "Manage Application" :
Note: This script is still in alpha stages so users who are not sure please don't try it. It can potentially brick you SD or can cause bootloops. I don't know a method to uninstall this yet.
HOW IT WORK??
The script will do this in the first boot:
Move Mounting Internal Memory (/data) Into /sd-ext
Mount SDCard-Ext (mmcblk0p2) partition into /data
Create dalvik-cache directory in Internal Memory data (/sd-ext), and symlink it to mmcblk0p2 (/data)
Create data directory in mmcblk0p2 (/data) And symlink it into Internal Memory data (/sd-ext)
Create symlink of app, app-private, app_s and lib_s from mmcblk0p2 (/data) to Internal memory data (/sd-ext)
Create symlink for all non-symllink of Internal Memory data (/sd-ext) into mmcblk0p2 (/data)
After Initializing Setup (First Boot), reboot the system (Just reboot, don't go into recovery), the mod will automatically do this following:
Create data_s in Internal Memory data (/sd-ext)
Move All mmcblk0p2(/data)/data/com.htc* and com.android* into Internal Memory data(/sd-ext)/data_s
Create symlink all files/directory from Internal Memory data (/sd-ext)/data_s/* into mmcblk0p2(/data)/data/ So the System Application Data still read into Internal memory, but rest Application Data will read Into SDCard.
More Information and download:[MOD][AD2SDX][ALPHA02] New Data To SD-EXT Mod - AMARULLZ DATA TO SD-EXT
Click to expand...
Click to collapse
how come ur internal storage is 2.2GB...

That's what this script does it Internet storage will be your ext partition

martin132014 said:
how come ur internal storage is 2.2GB...
Click to expand...
Click to collapse
because the script re-mounts the internal storage partition to sd/ext

does anyone else have try this method and work...please do tell. i really like to apply it to my arc...

martin132014 said:
does anyone else have try this method and work...please do tell. i really like to apply it to my arc...
Click to expand...
Click to collapse
Me.....

ShyamSasi said:
Me.....
Click to expand...
Click to collapse
how did you do to make it work??
Edit: do i need just to flash the file for the recovery? with Ext4?
i got stuck on the Sony white text with Ext3...
Edit2: nevermind, it works now.

martin132014 said:
does anyone else have try this method and work...please do tell. i really like to apply it to my arc...
Click to expand...
Click to collapse
Is working perfect on Arc. Just have patience at boot - it's a long start up session.

i guess this will only works with fresh flashing...

nujhum said:
i guess this will only works with fresh flashing...
Click to expand...
Click to collapse
No! I have even used the "old" App2SD which I just deleted in init.d and copied AD2SDX into same directory. Then reboot a after waiting it worked.

em, so i need to delete the init.d before flashing ad2sdx...
this is what i did and caused me to bootloop.
1. restoring my backup rom, and flash the ad2sdx.
2. did fresh install rom and flash ad2sd without rebooting.

nujhum said:
em, so i need to delete the init.d before flashing ad2sdx...
this is what i did and caused me to bootloop.
1. restoring my backup rom, and flash the ad2sdx.
2. did fresh install rom and flash ad2sd without rebooting.
Click to expand...
Click to collapse
No, you have to delete the contents of init.d, not the folder.
Sent from my LT15i using xda premium

harfot said:
No, you have to delete the contents of init.d, not the folder.
Sent from my LT15i using xda premium
Click to expand...
Click to collapse
no, didnt delete the folder. just the specified file.
btw, it works fine now.
hm, but there is too many program keep FC, and lags, seem its getting heavier... hm. booting take minutes to load.

ShyamSasi said:
Me.....
Click to expand...
Click to collapse
well....i know its u first, i mean someone else....anybody....

nujhum said:
hm, but there is too many program keep FC, and lags, seem its getting heavier... hm. booting take minutes to load.
Click to expand...
Click to collapse
You're right - I'll try to change from ext2 to ext4 and see what happens.

It works fine for me I'm using Ext3 it works fine so far with MIUI ROM, I don't use lot of application only few everyday apps and lot of widgets

Additional Info:
When I updated the ROM version I had to format the ext3 partition (Mini Partition Tool) then re-apply the script to get it to work. Otherwise I had boot loops.

How I Can Do Adoptable Storage On OREO[PRA-LX1]

I can do it on Android 7.0
adb shell
sm list-disks
sm partition disk:179:192 mixed 20
it's work 7.0 but doesnt work on 8.0
Please Help

hellp

https://preview.ibb.co/f5gRn8/2018_06_23_14_41_21.png
its error.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

same here, any updates?
would like to have a crDroid 4.3 ROM without Treble for my PRA-LX1....
migrate data works fine there

Solution
Copied this solution from another thread
Disable encryption to use Adoptable Storage (or just because you can)
open /vendor/etc/fstab.hi6250
make a backup just in case
find "/dev/block/bootdevice/by-name/userdata /data f2fs nosuid,nodev,noatime,discard,inlinedata,inlinexatt r wait,check,fileencryption=aes-256-xts:aes-256-cts"
remove ",fileencryption=aes-256-xts:aes-256-cts"
factory reset via stock recovery

mustafademiral said:
I can do it on Android 7.0
adb shell
sm list-disks
sm partition disk:179:192 mixed 20
it's work 7.0 but doesnt work on 8.0
Please Help
Click to expand...
Click to collapse
if its still on 7 remove sd card and do the update it carries over with not much issues
had it done successfully on my brothers device on mine i was too late since i tried to start fresh after doing the update. which clearly is blocked.
"Error: java.lang.IllegalStateException: command '15 volume partition disk:179:192 mixed 90' failed with '400 15 Command failed'"
i'm probably going to get my device rolled back to 7 and redo it now
i had to format my device since i only had about 2gb on my original internal storage so figured id sd partition as well start fresh with 90-10% instead of my 50/50 partition for this unexpected oreo update XP <( T_T)> regret after 3 hrs

Mister746 said:
Copied this solution from another thread
Disable encryption to use Adoptable Storage (or just because you can)
open /vendor/etc/fstab.hi6250
make a backup just in case
find "/dev/block/bootdevice/by-name/userdata /data f2fs nosuid,nodev,noatime,discard,inlinedata,inlinexatt r wait,check,fileencryption=aes-256-xts:aes-256-cts"
remove ",fileencryption=aes-256-xts:aes-256-cts"
factory reset via stock recovery
Click to expand...
Click to collapse
fstab.hi650 missing in my phone. im using stock firmware

Mister746 said:
Copied this solution from another thread
Disable encryption to use Adoptable Storage (or just because you can)
open /vendor/etc/fstab.hi6250
make a backup just in case
find "/dev/block/bootdevice/by-name/userdata /data f2fs nosuid,nodev,noatime,discard,inlinedata,inlinexatt r wait,check,fileencryption=aes-256-xts:aes-256-cts"
remove ",fileencryption=aes-256-xts:aes-256-cts"
factory reset via stock recovery
Click to expand...
Click to collapse
do you try this solution. is it work ?

Muratia4141 said:
do you try this solution. is it work ?
Click to expand...
Click to collapse
Yeah it worked.

Mister746 said:
Yeah it worked.
Click to expand...
Click to collapse
Noob request!
Could one give more details on the steps/tools needed to do this. More if some one could make a tutorial for the rest of the people dealing with this issue or just post the source maybe it will provide the needed info!

daniel.dobrea said:
Noob request!
Could one give more details on the steps/tools needed to do this. More if some one could make a tutorial for the rest of the people dealing with this issue or just post the source maybe it will provide the needed info!
Click to expand...
Click to collapse
Hi, @daniel.dobrea!
Noob to noob, I think you'll need to root your device - I myself will be using the regular root tutorial from here - after unlocking your bootloader. After going through all of this you'll be able to use root file explorer apps to navigate into /system/vendor/ and the likes. (I personally use ES File Explorer Pro, but only because I got it cheap. I recommend something like 'File Explorer' from the Play Store.
Thanks

XDA XILFY said:
Hi, @daniel.dobrea!
Noob to noob, I think you'll need to root your device - I myself will be using the regular root tutorial from here - after unlocking your bootloader. After going through all of this you'll be able to use root file explorer apps to navigate into /system/vendor/ and the likes. (I personally use ES File Explorer Pro, but only because I got it cheap. I recommend something like 'File Explorer' from the Play Store.
Thanks
Click to expand...
Click to collapse
Thanks XDA XILFY,
I'll give it a try... first rooting then the above steps!
Could some one confirm the need of factory reset!
Thanks Daniel

Hello,
I've tried the proposed solution.
As one can see below, there are now 2 files in my /vendor/etc, which are :
/vendor/etc/fstab.hi6250 : the updated file with the encryption related part removed.
/vendor/etc/fstab.hi6250.old : the original file that I copied just before I modified it.
After doing this, I boot into the recovery (the stock one), I asked to wipe the data, and after the various confirmation, the device rebooted in order to perform the wipe.
So I had approximately the same screen than when it's updating the ROM, but with a red title stating that I should not hold and press the power button to keep things Ok (I don't remeber exactly), but... it stayed at 0% for about 1 hour when I gave up.
I then had to restore the /vendor partition I had backup-ed before doing the work in order to restore things to normal.
So either there is some trick that is not mentionned, or I screwed up, but in both case I'd suggest you not to perform this action.
Now, if you want my guess : the stock recovery might expect a not encrypted partition according to the fstab, although it is, and therefore is unable to perform the wipe...
I'll give it a try with a special TWRP (if such exists) to perform the wipe (which consists in a specific rm -rf in order to keep Huawei drivers in /data)
If you had better luck, let me know!
Code:
HWPRA-H:/ # cat /vendor/etc/fstab.hi6250
# Android fstab file.
#<src> <mnt_point> <type> <mnt_flags and options> <fs_mgr_flags>
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK
/dev/block/bootdevice/by-name/system /system ext4 ro,barrier=1 wait,avb
/dev/block/bootdevice/by-name/vendor /vendor ext4 ro,barrier=1 wait,avb
/dev/block/bootdevice/by-name/product /product ext4 ro,barrier=1 wait
/dev/block/bootdevice/by-name/version /version ext4 ro,barrier=1 wait
/dev/block/bootdevice/by-name/cust /cust ext4 ro,barrier=1 wait
/dev/block/bootdevice/by-name/odm /odm ext4 ro,barrier=1 wait
/dev/block/bootdevice/by-name/patch /patch_hw ext4 ro wait,verify
/dev/block/bootdevice/by-name/splash2 /splash2 ext4 rw,nosuid,nodev,noatime,data=ordered,context=u:object_r:splash2_data_file:s0 wait,check
/devices/hi_mci.1/mmc_host/mmc1/* auto auto defaults voldmanaged=sdcard:auto,noemulatedsd
/devices/platform/hi_mci.1/mmc_host/mmc1/* auto auto defaults voldmanaged=sdcard:auto,noemulatedsd
/devices/hisi-usb-otg/usb1/* auto auto defaults voldmanaged=usbotg:auto
/dev/block/bootdevice/by-name/userdata /data f2fs nosuid,nodev,noatime,discard,inline_data,inline_xattr wait,check
/dev/block/bootdevice/by-name/cache /cache ext4 rw,nosuid,nodev,noatime,data=ordered wait,check
/dev/block/bootdevice/by-name/secure_storage /sec_storage ext4 rw,nosuid,nodev,noatime,discard,auto_da_alloc,mblk_io_submit,data=journal,context=u:object_r:teecd_data_file:s0 wait,check
/dev/block/bootdevice/by-name/misc /misc emmc defaults defaults
HWPRA-H:/ # cat /vendor/etc/fstab.hi6250.old
# Android fstab file.
#<src> <mnt_point> <type> <mnt_flags and options> <fs_mgr_flags>
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK
/dev/block/bootdevice/by-name/system /system ext4 ro,barrier=1 wait,avb
/dev/block/bootdevice/by-name/vendor /vendor ext4 ro,barrier=1 wait,avb
/dev/block/bootdevice/by-name/product /product ext4 ro,barrier=1 wait
/dev/block/bootdevice/by-name/version /version ext4 ro,barrier=1 wait
/dev/block/bootdevice/by-name/cust /cust ext4 ro,barrier=1 wait
/dev/block/bootdevice/by-name/odm /odm ext4 ro,barrier=1 wait
/dev/block/bootdevice/by-name/patch /patch_hw ext4 ro wait,verify
/dev/block/bootdevice/by-name/splash2 /splash2 ext4 rw,nosuid,nodev,noatime,data=ordered,context=u:object_r:splash2_data_file:s0 wait,check
/devices/hi_mci.1/mmc_host/mmc1/* auto auto defaults voldmanaged=sdcard:auto,noemulatedsd
/devices/platform/hi_mci.1/mmc_host/mmc1/* auto auto defaults voldmanaged=sdcard:auto,noemulatedsd
/devices/hisi-usb-otg/usb1/* auto auto defaults voldmanaged=usbotg:auto
/dev/block/bootdevice/by-name/userdata /data f2fs nosuid,nodev,noatime,discard,inline_data,inline_xattr wait,check,fileencryption=aes-256-xts:aes-256-cts
/dev/block/bootdevice/by-name/cache /cache ext4 rw,nosuid,nodev,noatime,data=ordered wait,check
/dev/block/bootdevice/by-name/secure_storage /sec_storage ext4 rw,nosuid,nodev,noatime,discard,auto_da_alloc,mblk_io_submit,data=journal,context=u:object_r:teecd_data_file:s0 wait,check
/dev/block/bootdevice/by-name/misc /misc emmc defaults defaults
HWPRA-H:/ # [email protected]: ~/android/essai_adb $>adb shell
daniel.dobrea said:
Thanks XDA XILFY,
I'll give it a try... first rooting then the above steps!
Could some one confirm the need of factory reset!
Thanks Daniel
Click to expand...
Click to collapse

Briked?bricked!XD said:
if its still on 7 remove sd card and do the update it carries over with not much issues
had it done successfully on my brothers device on mine i was too late since i tried to start fresh after doing the update. which clearly is blocked.
"Error: java.lang.IllegalStateException: command '15 volume partition disk:179:192 mixed 90' failed with '400 15 Command failed'"
i'm probably going to get my device rolled back to 7 and redo it now
i had to format my device since i only had about 2gb on my original internal storage so figured id sd partition as well start fresh with 90-10% instead of my 50/50 partition for this unexpected oreo update XP <( T_T)> regret after 3 hrs
Click to expand...
Click to collapse
Has this worked? Because I can't set my sd as adoptable storage (emui 8 android 8.0.0) because I have my disks encrypted.

Mister746 said:
Copied this solution from another thread
Disable encryption to use Adoptable Storage (or just because you can)
open /vendor/etc/fstab.hi6250
make a backup just in case
find "/dev/block/bootdevice/by-name/userdata /data f2fs nosuid,nodev,noatime,discard,inlinedata,inlinexatt r wait,check,fileencryption=aes-256-xts:aes-256-cts"
remove ",fileencryption=aes-256-xts:aes-256-cts"
factory reset via stock recovery
Click to expand...
Click to collapse
Hi,
I have found the file and the text to remove.
My phone isn't rooted so I can only open the file as read only at the moment.
Once I sort out how to update the file and rewrite it, am I correct in thinking that all I do is the deletion you detailed above and factory reset and that's it?
How do I then make my SDCard as internal storage?
Normally there is an option on the phone to do this, which involves a reformat of the SDCard.

is there an update to this thread same error here i have the same model. i hope to fix this problem without rooting i cant unlock my bootloader due to no unlock code. thank you

On oreo 8 i can't still?

Briked?bricked!XD said:
if its still on 7 remove sd card and do the update it carries over with not much issues
had it done successfully on my brothers device on mine i was too late since i tried to start fresh after doing the update. which clearly is blocked.
"Error: java.lang.IllegalStateException: command '15 volume partition disk:179:192 mixed 90' failed with '400 15 Command failed'"
i'm probably going to get my device rolled back to 7 and redo it now
i had to format my device since i only had about 2gb on my original internal storage so figured id sd partition as well start fresh with 90-10% instead of my 50/50 partition for this unexpected oreo update XP <( T_T)> regret after 3 hrs
Click to expand...
Click to collapse
Hi,
I did rollback to Android 7 and did adoptable storage on SD card and disabled OS upgrades. But your solution with removal of SD card and upgrade o Android 8 is interesting.
- Is this removal necessary only for first upgrade to version 8 or it need to be removed for all of them? (there are some security updates also)
- You say 'it carries over with not much issues'. I'm also interested what are those issues?

So I tried upgrade from default Android 7 to 8 and all is working fine. Adoptable storage working for me so far. There was no need to remove SD card from device or anything.