Related
This thread is obsolete and the method is buggy. I've created a new post with a simple script that does the job. Please find it here:
http://forum.xda-developers.com/showthread.php?p=12827697
Hello,
In this guide I will show you how to enable Darktremor's a2sd (i.e. extending your internal memory using SD card, so you can install more applications easily). This method has been tested on a rooted Galaxy ACE running Android 2.2.1.
This guide assumes that your phone is rooted, and you have a basic knowledge in Linux.
REMEMBER: The steps below will not extend your phone's internal memory, you still have to install a2sd (link provided below) to complete the job.
1- Backup all data, both on your phone and your SD card.
Click to expand...
Click to collapse
2- Partition your SD card as following: 1st partition FAT32, 2nd partition ext2. I'm not sure about the optimal partition size of ext2, but you can start with 1-2 GB. Make sure that you use ext2 only, as ext3 and ext4 are not supported by the kernel. Here's a good guide to help you out.
Click to expand...
Click to collapse
3- Insert your SD card and make sure that your phone recognizes it correctly.
Click to expand...
Click to collapse
4- Connect your phone through USB and login to ADB shell as root:
Code:
> adb shell
su
_
Click to expand...
Click to collapse
5- Try mounting the second partition to confirm that everything is going fine:
Code:
mount -o remount,rw /dev/stl12 /system
mkdir /system/sd
mount -t ext2 /dev/block/mmcblk0p2 /system/sd
df
Click to expand...
Click to collapse
6- Applying the commands above should bring an output similar to the following, make sure that you have something similar to the line in red below:
Code:
/dev: 142220K total, 12K used, 142208K available (block size 4096)
/mnt/asec: 142220K total, 0K used, 142220K available (block size 4096)
/cache: 25656K total, 12K used, 25644K available (block size 4096)
/data: 185240K total, 36768K used, 148472K available (block size 4096)
/system: 213376K total, 211520K used, 1856K available (block size 4096)
[B][COLOR="Red"]/system/sd: 1032088K total, 38512K used, 993576K available (block size 4096)[/COLOR][/B]
/mnt/sdcard: 6783016K total, 190356K used, 6592660K available (block size 4096)
/mnt/secure/asec: 6783016K total, 190356K used, 6592660K available (block size 4096)
Click to expand...
Click to collapse
7- So far you have successfully mounted your ext2 partition. Now you need to enable mounting it at boot time, and enable a2sd boot scripts, as following:
Code:
mount -o remount,rw /dev/stl12 /system
cd /system/etc
mv install-recovery.sh install-recovery.sh.bak
echo "#!/system/bin/sh" > install-recovery.sh
echo "/system/bin/mount -t ext2 /dev/block/mmcblk0p2 /system/sd" >> install-recovery.sh
echo "/system/bin/sh /system/etc/init.d/dtapp" >> install-recovery.sh
echo "/system/bin/sh /system/etc/init.d/99complete" >> install-recovery.sh
Don't worry if you get complains about "install-recovery.sh doesn't exist"
Click to expand...
Click to collapse
8- To check that everything went well, reboot your phone and login again as root through adb, then run the following command, and find the highlighted line in the output below:
Code:
su
df
Output
Code:
/dev: 142220K total, 12K used, 142208K available (block size 4096)
/mnt/asec: 142220K total, 0K used, 142220K available (block size 4096)
/cache: 25656K total, 12K used, 25644K available (block size 4096)
/data: 185240K total, 36768K used, 148472K available (block size 4096)
/system: 213376K total, 211520K used, 1856K available (block size 4096)
[B][COLOR="Red"]/system/sd: 1032088K total, 38512K used, 993576K available (block size 4096)[/COLOR][/B]
/mnt/sdcard: 6783016K total, 190356K used, 6592660K available (block size 4096)
/mnt/secure/asec: 6783016K total, 190356K used, 6592660K available (block size 4096)
Click to expand...
Click to collapse
9- Now you're good to go. Follow the directions as described in Darktremor's thread here:
http://forum.xda-developers.com/showthread.php?t=715116
Click to expand...
Click to collapse
10- IMPORTANT: If your internal memory is still the same after installing a2sd and rebooting, then type the following commands in adb shell:
Code:
su
a2sd install
Click to expand...
Click to collapse
11- BONUS: To move dalvik-cache from internal memory to ext2 partition, type the following commands in adb shell:
Code:
su
a2sd cachesd
Click to expand...
Click to collapse
Please feel free to comment and share your experience.
Note for the experts:
I think we can easily enable init.d scripts at boot using the /system/etc/install-recovery.sh. I didn't have the time to test this, but I think busybox run-parts is the way to start.
wow...this is a very helpful thread !!!!!!
thanks n the step is very easy...
need to flash custom recovery ROM b4 start ur step ???
Any performance issue after implement this?
cheehing said:
need to flash custom recovery ROM b4 start ur step ???
Click to expand...
Click to collapse
Nope, you don't have to. Just follow the steps exactly as stated above
mynewuser said:
Any performance issue after implement this?
Click to expand...
Click to collapse
4 days and no problems at all. Performance is great. I'm using a stock Nokia SD card (8 GB taken from Nokia 5800) - not sure which class it is, but I'm sure it's not super.
Why you do not use Move2SD Enabler? I think it is more easily for every one.
What is the difference between your method and using Move2SD Enabler in practic?
One more easy way to free some space at main memory with out any scripts:
Link2sd
Lovetz said:
Why you do not use Move2SD Enabler? I think it is more easily for every one.
What is the difference between your method and using Move2SD Enabler in practic?
Click to expand...
Click to collapse
First of all, it's not my method. Credits go to Darktremor for his contribution. All I did was enabling it to work on Galaxy ACE.
Move2SD moves applications to the FAT partition, which does not play well with many apps. Moreover, if you plugged your device as mass storage, these applications will not be available until you release it. Ofcourse, dalvik-cache can't be moved. Please refer to the original post for more details:
http://forum.xda-developers.com/showthread.php?t=720739
Lovetz said:
One more easy way to free some space at main memory with out any scripts:
Link2sd
Click to expand...
Click to collapse
This does the same job as a2sd, with the exception that you have to manually select apps to move to ext partition. This is not a disadvantage, but personally, I don't like it. Plus, it failed to move my dalvik-cache on SGA.
Just like you said, Move2SD and Link2SD are much easier and save you the hassle. A2SD in the other hand is more adventurous and sexy
Anyways, thank you for pointing this out, might help a couple of noobs finding easier alternatives.
just follow all the steps u provided...no need to refer to Darktremor's thread right ??? the a2sd from Darktremor is for what?
but i cant find install-recovery.sh in /system/etc
sorry for many noob Q
cheehing said:
just follow all the steps u provided...no need to refer to Darktremor's thread right ??? the a2sd from Darktremor is for what?
but i cant find install-recovery.sh in /system/etc
sorry for many noob Q
Click to expand...
Click to collapse
Actually you do have to follow Darktremor's guide to complete the process.
Regarding the install-recovery.sh, it doesn't have to be there. The 7th step above will create it if it doesn't exist (and back it up if it already exists).
majedev said:
Actually you do have to follow Darktremor's guide to complete the process.
Regarding the install-recovery.sh, it doesn't have to be there. The 7th step above will create it if it doesn't exist (and back it up if it already exists).
Click to expand...
Click to collapse
the a2sd from Darktremor is for what? need to download in install b4 starting the mount steps?
cheehing said:
the a2sd from Darktremor is for what? need to download in install b4 starting the mount steps?
Click to expand...
Click to collapse
The steps I provided are only to mount the ext2 partition at device boot time, so applying them will not extend your phone internal memory by any means.
Darktremor's A2SD does the magic by moving your installed applications to ext2 partition, so you have to install it after following my guide.
majedev said:
The steps I provided are only to mount the ext2 partition at device boot time, so applying them will not extend your phone internal memory by any means.
Darktremor's A2SD does the magic by moving your installed applications to ext2 partition, so you have to install it after following my guide.
Click to expand...
Click to collapse
thanks....only install it after ur steps right ??
meaning after download the Darktremor's A2SD and save it at the SD card, boot into recovery mode and select "apply sdcard:update.zip" from the menu right?
Do u did any backup ?
urs also original samsung recovery rom ?
mine is root by using the SuperOneClick....is that possible to do all this ??
cheehing said:
thanks....only install it after ur steps right ??
Click to expand...
Click to collapse
Yes
cheehing said:
meaning after download the Darktremor's A2SD and save it at the SD card, boot into recovery mode and select "apply sdcard:update.zip" from the menu right?
Click to expand...
Click to collapse
Yes
cheehing said:
Do u did any backup ?
Click to expand...
Click to collapse
Yes, backed up may data and apps, but I couldn't backup the firmware, so I took the risk
cheehing said:
urs also original samsung recovery rom ?
Click to expand...
Click to collapse
Yes
cheehing said:
mine is root by using the SuperOneClick....is that possible to do all this ??
Click to expand...
Click to collapse
Yes
thank you so much !!
to play save must back up the ROM right ?
anyway to do it, pls give some suggestion...
thanks
cheehing said:
thank you so much !!
to play save must back up the ROM right ?
anyway to do it, pls give some suggestion...
thanks
Click to expand...
Click to collapse
Everyone tried to backup the ROM using RomManager reported that phone was bricked. So I don't know how to back it up.
You can find stock firmware ROM online, but again, I can't help you here too.
majedev said:
Everyone tried to backup the ROM using RomManager reported that phone was bricked. So I don't know how to back it up.
You can find stock firmware ROM online, but again, I can't help you here too.
Click to expand...
Click to collapse
ya, I read many comment about the ROM manager brick the phone so need to find out other way....
hard to get the stock firmware
HELP!!
I have successfully installed a2sd but when I type command a2sd darktremor check there is a problem that is not run at boot even though I have follow step 7 before installing darktremor
and another problem when I type command a2sd cachesd all applications does not show and could not run so i factory format and back to normal again
how a2sd can run normal on my ace ??? i still have this problem 3 times
How bout this...this isn't app2sd by darktremor, i've played with a script a little bit. Hope you will like it. I've posted a screenshot of my internal and a benchmark result here.
xdah said:
I have successfully installed a2sd but when I type command a2sd darktremor check there is a problem that is not run at boot even though I have follow step 7 before installing darktremor
and another problem when I type command a2sd cachesd all applications does not show and could not run so i factory format and back to normal again
how a2sd can run normal on my ace ??? i still have this problem 3 times
Click to expand...
Click to collapse
Hmm, I get your point, although a2sd cachesd is running fine for me without enabling a2sd at boot. Anyways, here's how you do it. Open adb shell, and execute the following:
Code:
su
mount -r remount, rw /dev/stl12 /system
echo "/system/bin/sh /system/etc/init.d/dtapp" >> install-recovery.sh
echo "/system/bin/sh /system/etc/init.d/99complete" >> install-recovery.sh
Reboot and type a2sd check, make sure it doesn't complain about booting.
Edit: I've added this to the main guide. Thanx for pointing this out
Hello everyone,
I have a Desire HD (Telus) rooted with Android Revolution 5.2.6 installed and 4ext recovery mod.
Overnight my phone locked up and then after popping the battery I could get maybe 30 seconds of use before it would crawl to a halt and lock up again.
I decided to try to wipe the phone and reinstall. Except all of the processes don't complete now. I'll either get (Error 1) or (Error 255) when trying to use the SuperWipe, install the ROM or use the "Wipe all partitions" option.
Right now it's in the 4ext recovery mod and since I've tried all of the wipe options is it safe to try to reboot (back into recovery) or have I wiped 4ext off as well? I have googled this and can't find an answer.
I've noticed that there is a new version of 4ext available (I have 4.1.3 RC2) but apparently the only way to update is via the app store - which obviously I can't do right now.
When trying to format system partition the screen goes blank for a few minutes and eventually returns to the main menu with no info other than a bunch of "E: Can't mount /cache/recovery" messages. The partition list shows system/data/cache as ext4 with only "iB" in the free column.
I'm not sure what to do. Can anyone offer some suggestions?
Here are some recovery log snips:
Code:
==============================================
| Wiping Script |
| This operation will remove all your data |
| You have 10 seconds to remove the battery |
| to cancel this procedure |
==============================================
unmount of /cache failed; no such volume
about to run program [/sbin/erase_image] with 2 args
1. Erasing & formatting EXT4 *CACHE* partitionCreating filesystem with parameters:
Size: 314572288
Block size: 4096
Blocks per group: 32768
Inodes per group: 6400
Inode size: 256
Journal blocks: 1200
Label:
Blocks: 76799
Block groups: 3
Reserved block group size: 23
Created filesystem with 11/19200 inodes and 2459/76799 blocks
(cache is unmounted already)
error: file_write: write: I/O error
E:Error in /sdcard/Android_Revolution_HD_Super_Wipe.zip
(Status 1)
Installation aborted.
MD5s are valid for the super wipe and the new rom:
Code:
Checking md5sum..
md5sum for this file:
89ad0a12c631e28d34d24ee3ea3d64c8
Checking md5sum..
md5sum for this file:
59531c9715527f5725cbd716dfae4549
Here's what happens when I try to flash the ROM:
Code:
===============================================
| Android Revolution HD |
Creating filesystem with parameters:
Size: 585104896
Block size: 4096
Blocks per group: 32768
Inodes per group: 7143
Inode size: 256
Journal blocks: 2232
Label:
Blocks: 142847
Block groups: 5
Reserved block group size: 39
Created filesystem with 11/35715 inodes and 4603/142847 blocks
| by mike1986 |
| Be patient - 1st boot may take a while |
===============================================
>>> Formatting partitions
error: file_write: write: I/O error
E:Error in /sdcard/Android_Revolution_HD-4G_5.2.6.zip
(Status 1)
Installation aborted.
W:failed to mount /dev/block/mmcblk0p27 (Invalid argument)
W:failed to mount /dev/block/mmcblk0p27 (Invalid argument)
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
W:failed to mount /dev/block/mmcblk0p27 (Invalid argument)
W:failed to mount /dev/block/mmcblk0p27 (Invalid argument)
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
W:failed to mount /dev/block/mmcblk0p27 (Invalid argument)
W:failed to mount /dev/block/mmcblk0p27 (Invalid argument)
W:Can't unlink /cache/recovery/command
-- Formatting boot...
Formatting /boot...
I:Formatting unknown device.
-- Formatting system...
Formatting /system...
Creating filesystem with parameters:
Size: 585104896
Block size: 4096
Blocks per group: 32768
Inodes per group: 7143
Inode size: 256
Journal blocks: 2232
Label:
Blocks: 142847
Block groups: 5
Reserved block group size: 39
Created filesystem with 11/35715 inodes and 4603/142847 blocks
error: file_write: write: I/O error
This is out of my league really technically. Is the rom zip OK? I see the error starts with that file. If all else fails I would try to put another rom file onto the SD Card and flash that in case it's just a bad file. (or bad SD Card)
In my experience I've only ever done any or all of the following:
wipe data/factory reset
wipe cache
wipe dalvik cache
wipe battery stats
format system
format data
(I've never done or wiped or formatted anything else.)
Hopefully a more technically experienced person can help.
I'm really uncomfortable formatting partitions, so I never touch them. I'm not sure of the state of yours. You could try to flash the smallest rom file you can. ie. the smallest rom zip size.
Thanks for the reply - I did upload another ROM and it failed in the same way. The logs are clearly indicating something wrong with the Flash filesystem on the device.
I don't know if I can shut down to swap the card and boot back into the 4EXT recovery - does "Wipe all partitions" remove 4EXT as well?
I have tried formatting partitions as EXT3 as well and no dice - here's the recovery log:
Code:
Formatting /system...
I:Formatting unknown device.
I:Formatting ext3 device.
Warning: 256-byte inodes not usable on older systems
Warning: could not read block 0: Attempt to read block from filesystem resulted in short read
/sbin/tune2fs: Attempt to read block from filesystem resulted in short read while trying to open /dev/block/mmcblk0p25
Couldn't find valid filesystem superblock.
tune2fs 1.41.6 (30-May-2009)
Formatting system completed.
Formatting /data...
I:Formatting unknown device.
I:Formatting ext3 device.
Warning: 256-byte inodes not usable on older systems
Warning: could not read block 0: Attempt to read block from filesystem resulted in short read
/sbin/tune2fs: Attempt to read block from filesystem resulted in short read while trying to open /dev/block/mmcblk0p26
Couldn't find valid filesystem superblock.
tune2fs 1.41.6 (30-May-2009)
Formatting data completed.
Formatting /cache...
I:Formatting unknown device.
I:Formatting ext3 device.
Warning: could not read block 0: Attempt to read block from filesystem resulted in short read
ext2fs_mkdir: Attempt to read block from filesystem resulted in short read while creating root dir
Formatting cache completed.
partition | fs | capacity | free
mount: mounting /dev/block/mmcblk0p25 on /system failed: Invalid argument
df: /system: can't find mount point
umount: can't umount /system: Invalid argument
system ext3 558 MiB iB
mount: mounting /dev/block/mmcblk0p26 on /data failed: Invalid argument
df: /data: can't find mount point
umount: can't umount /data: Invalid argument
data ext3 1175 MiB iB
mount: mounting /dev/block/mmcblk0p27 on /cache failed: Invalid argument
df: /cache: can't find mount point
cache ext3 300 MiB iB
mount: mounting /dev/block/mmcblk1p1 on /sdcard failed: Device or resource busy
sdcard fat32 1945 MiB 1.3GiB
I use amon ra recovery but it seems to me that your partition is somehow damaged, you should copy everything thats on ur sd card onto your computer and try formatting the sd card on the computer, see if that reformats the entire sd card and gets rid of the ext4 partition. If it does, then copy the recovery zip on there and try to reflash the recovery. Then try to repartition.
Sent from my PC36100 using xda premium
Synergies14 said:
I use amon ra recovery but it seems to me that your partition is somehow damaged, you should copy everything thats on ur sd card onto your computer and try formatting the sd card on the computer, see if that reformats the entire sd card and gets rid of the ext4 partition. If it does, then copy the recovery zip on there and try to reflash the recovery. Then try to repartition.
Sent from my PC36100 using xda premium
Click to expand...
Click to collapse
Thanks for the reply. The problem isn't the SD card itself it's the internal flash memory. 4EXT can read and calculate the correct MD5 sums of the images on the SD card. It fails when trying to format the internal flash.
Telek said:
Thanks for the reply. The problem isn't the SD card itself it's the internal flash memory. 4EXT can read and calculate the correct MD5 sums of the images on the SD card. It fails when trying to format the internal flash.
Click to expand...
Click to collapse
Is there a way you can remove your sdcard and then boot into recovery and try to do a factory reset/restore?, maybe try flashing a stock rom. I know this may not be abit of help but i would like to try and think of all possible things to do.
Synergies14 said:
Is there a way you can remove your sdcard and then boot into recovery and try to do a factory reset/restore?, maybe try flashing a stock rom. I know this may not be abit of help but i would like to try and think of all possible things to do.
Click to expand...
Click to collapse
I've tried the factory reset/restore and it didn't work. I'm worried about powering off right now because I don't know enough about how recovery is setup. Since all partitions have been wiped will I be able to boot back into 4EXT recovery?
Edit: thought you had a Desire not a desire hd, sorry
Telek said:
I've tried the factory reset/restore and it didn't work. I'm worried about powering off right now because I don't know enough about how recovery is setup. Since all partitions have been wiped will I be able to boot back into 4EXT recovery?
Click to expand...
Click to collapse
try downloading a stock released rom, not a custom rom and rename it to pd98img.zip and place it on your sd card. turn off your phone and go into the bootloader menu and it should auto detect the pd98img.zip file and it will ask you if you want to update. Choose yes and see if it installs. Thats installs the rom bypassing the recovery mod telling it to install on the partition.
madmaxx82 said:
Edit: thought you had a Desire not a desire hd, sorry
Click to expand...
Click to collapse
The ext3 format was a desperate attempt to get something to work. The installer before (check the top logs) was formatting as ext4.
I currently have 4.1.3 RC2 installed.
Synergies14 said:
try downloading a stock released rom, not a custom rom and rename it to pd98img.zip and place it on your sd card. turn off your phone and go into the bootloader menu and it should auto detect the pd98img.zip file and it will ask you if you want to update. Choose yes and see if it installs. Thats installs the rom bypassing the recovery mod telling it to install on the partition.
Click to expand...
Click to collapse
OK I'll give that a try. I have the PD98IMG.zip file from when I rooted my phone - that should work?
Telek said:
The ext3 format was a desperate attempt to get something to work. The installer before (check the top logs) was formatting as ext4.
I currently have 4.1.3 RC2 installed.
OK I'll give that a try. I have the PD98IMG.zip file from when I rooted my phone - that should work?
Click to expand...
Click to collapse
I got a shock when I saw ext3 since you had posted in the Desire forum's 4ext thread! The Desire has yaffs2 partitions after all
I really hope you get your phone working after flashing the ruu!
Telek said:
OK I'll give that a try. I have the PD98IMG.zip file from when I rooted my phone - that should work?
Click to expand...
Click to collapse
I'm not exactly sure. You can take anything and rename it as PD98IMG.zip and flash it. Chances are, the file you have is the recovery program. Im not sure where you can get a stock rom for your phone at. but if you find one, make sure its legit and the download is correct and use the method i mentioned. Let us know what happens.
madmaxx82 said:
I got a shock when I saw ext3 since you had posted in the Desire forum's 4ext thread! The Desire has yaffs2 partitions after all
I really hope you get your phone working after flashing the ruu!
Click to expand...
Click to collapse
Yeah my bad - I didn't even notice it was the wrong thread.
Ok so is there a PB99IMG.zip that will work for the Desire HD?
Telek said:
Yeah my bad - I didn't even notice it was the wrong thread.
Ok so is there a PB99IMG.zip that will work for the Desire HD?
Click to expand...
Click to collapse
NP
Is there no shipped roms thread for the Desire HD? Get an official RUU like Synergies14 suggested
---------- Post added at 05:29 AM ---------- Previous post was at 05:17 AM ----------
If you want I can package you a recovery you can flash from inside recovery.
I said it wasn't possible because I thought you had a desire. Now that this has changed it's no problem.
But I really don't think it could solve the problem.
Maybe the best would be to really flash an official ruu so you know if your device is ok or not ok.
If the ruu doesn't boot/flashing fails (not because of cid errors, but during flashing), then you really should send it in..
madmaxx82 said:
NP
Is there no shipped roms thread for the Desire HD? Get an official RUU like Synergies14 suggested
---------- Post added at 05:29 AM ---------- Previous post was at 05:17 AM ----------
If you want I can package you a recovery you can flash from inside recovery.
I said it wasn't possible because I thought you had a desire. Now that this has changed it's no problem.
But I really don't think it could solve the problem.
Maybe the best would be to really flash an official ruu so you know if your device is ok or not ok.
If the ruu doesn't boot/flashing fails (not because of cid errors, but during flashing), then you really should send it in..
Click to expand...
Click to collapse
I agree - I'm trying to find a stock ROM.
Does this one look good?
http://forum.xda-developers.com/showthread.php?t=1145397&page=2
I don't know what ACE means.
Telek said:
I agree - I'm trying to find a stock ROM.
Does this one look good?
http://forum.xda-developers.com/showthread.php?t=1145397&page=2
I don't know what ACE means.
Click to expand...
Click to collapse
BTW: How did you get s-off?
Do you have supercid?
I'm not so familiar with the desire hd I must admit.
---------- Post added at 05:33 AM ---------- Previous post was at 05:32 AM ----------
Ace is the name of the Desire HD.
madmaxx82 said:
BTW: How did you get s-off?
Do you have supercid?
Click to expand...
Click to collapse
The one I just linked is
RUU_Ace_Gingerbread_S_TELUS_WWE_2.43.661.1_R_Radio _12.56.60.25_26.10.04.03_M
I should be able flash that and then go back to Revolution?
I followed these guides to root and s-off. I think I supercid'd as well but honestly can't remember. How do I check?
http://www.addictivetips.com/mobile/how-to-root-telus-htc-desire-hd/
EDIT: Yes, I believe that does SuperCID as well.
Telek said:
The one I just linked is
RUU_Ace_Gingerbread_S_TELUS_WWE_2.43.661.1_R_Radio _12.56.60.25_26.10.04.03_M
I should be able flash that and then go back to Revolution?
I followed these guides to root and s-off. I think I supercid'd as well but honestly can't remember. How do I check?
http://www.addictivetips.com/mobile/how-to-root-telus-htc-desire-hd/
EDIT: Yes, I believe that does SuperCID as well.
Click to expand...
Click to collapse
Oh I see so you really have telus desire hd I suppose?
Then I think you should just use the rom zip linked in the rooting guide again.
madmaxx82 said:
Oh I see so you really have telus desire hd I suppose?
Then I think you should just use the rom zip linked in the rooting guide again.
Click to expand...
Click to collapse
Yes I do have Telus DHD - and I was just posting that I was going to use that ROM from the rooting guide since I'll have to use it again anyway in order to re-root my phone
Is it possible to make a PB99IMG.zip with the latest 4EXT before I go this route? I'd rather give that one quick try before I have to re-root the phone.
Thanks!
Hi xda community,
I've an issue with my Defy. My actual Rom is the last stable MIUI 2.3.7a.
The error is that the /data partition is always in read-only.
Code:
/dev/block/mmcblk1p25 on /data type ext3 (ro,relatime,errors=continue,data=ordered)
So I can't use any applications. ( lot of crash due to read only partition )
I have some errors like this one in the log :
Code:
Buffer I/O error on device mmcblk1p25, logical block 86151
lost page write due to I/O error on mmcblk1p25
I already try to re-install the rom and other roms included stock rom. And I always have this kind of error.
I have no idea on how to resolve this.
Can I move the /data to sdcard ? or use tools like fsck ? Or perhaps the defy internal memory is dead.
Thank you for help or advise.
Did you try full flash via RSD lite?
buruss said:
Did you try full flash via RSD lite?
Click to expand...
Click to collapse
I'm late in my answer but this topic is always open in my mind.
Yes I try this several times, The flash work. But after a little time of utilisation (with stock rom or miui or cyanogen, the error occurs again.
I think that I have bad block on internal memory, my goal is now to create a partition on sdcard and use symbolic link to this one in order to bypass the internal memory. Or an easy way is to mount /data on the sdcard.
Actually I'm not familiar with Android, but I'm very familiar with Linux. In theory it should work if I can mount the sdcard early in the boot process.
Anyone have already try this ?
bipbip61083 said:
... I think that I have bad block on internal memory, my goal is now to create a partition on sdcard and use symbolic link to this one in order to bypass the internal memory. Or an easy way is to mount /data on the sdcard.
Actually I'm not familiar with Android, but I'm very familiar with Linux. In theory it should work if I can mount the sdcard early in the boot process.
Anyone have already try this ?
Click to expand...
Click to collapse
Hi,
Sorry to revival your post.
I have a similar problem (details in this thread). For some reason my Defy will not mount the /dev/block/mmcblk1p25 and I guess that's the reason why after each reboot all my settings are lost.
I've already try to Fix Permissions (under Recovery Menu > Advanced), but it didn't help.
I was hoping to learn with your experience. Did you could manage to fix your problem creating a symlink or something else?
Merci.
hi,
my chienese zte blade has:
162mb /data
13,74gb /mnt/sdcard
0,98gb /data/sdext2
220mb /system
162mb /cache/donwload
is there a way to customize these size, especially /data?
tnx
db
take a look at this: http://www.modaco.com/topic/352666-info-tpt-on-my-zte-blade-v880-chinaunicom/#entry2000976
tnx matt4321,
that topic was mine. But nobody has given a sure reply. all i've understand is that by tpt my chinese zte blade, maybe, i will brick it.
I'd like to be sure that i can't damage my phone and then i'm looking for somebody who has experience about tpt chinese blade.
sorry for my poor english.
bye
db
Hello!
Can anyone explain how can i change file system ext4 to f2fs?
i've tried so many ways but none works which recovery use?? there is a global steps to do that? i always got a few errors... like: unable to mount internal storage... failed to mount '/data' (no such device), unable to recreate /data/media folder... etc
i'm on stock rom atm.. what are the steps to change ext4 to f2fs without any error?
thank you in advance
After changing ext4 to f2fs I needed an extra zip file to flash on my mi8..after installing a custom rom...I reed nothing about it on xda forems...for the mi a1....so who has the answers?