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 all,
First of all I would like to say that this is purely not my work.All thanks goes to Fi***o(Guess him...).
Ok to the matter.You all know that most of the superbricks are caused because of the wipe done in recovery.It actually causes an I/O error which causes the /data partition in eMMC to get unrepairable.Even Odin,heimdall,shell....Nothin can fix it.And without /data partition your phone cannot boot.Since only the /data partition is damaged,you can use download mode and flash any kernel and even enter recovery sometimes.So explanation part is over.
Now to make our phone to boot up we must find a way to get /data partition working.But how can we?You know,there is a partition called /preload (hidden.img) which is always empty and almost not at all used and its size is 512 MB.So we are actually wasting 512 MB.A kernel only controlls where to mount what partition.So If we could make a kernel which would swap /data and /preload,/data will be mounted at /preload location and it will be fine and working and our phone will be able boot and run normally.
So does it only have advantages?Surely no.It has its own disadvantages too...
1.Your /data partition is shrinked to 512 MB
2.You should only stay on custom roms.You cannot flash a stock rom or anything through odin except kernels....
3.You can flash this kernel only through PC odin which means yellow triangle and increase counter.
But you can use CWM to flash any custom roms because it doesnt check for /preload but stock rom does....
And as I said earlier this is ain't my work but dont feel shy to press that thanks button if you like it....
I think it is Ficeto (DarkyROM kernel dev) who did this first. I remember someone posting something about this previously, but was probably missed.
EDIT: Worth it for people who don't have the $200 odd dollars in the meantime for a new MOBO
I actually do not recommend any custom ROMs! as they are all deodexed and that means that they store their odex(dex) files in /data/dalvik-cache which further uses more /data space.
What you can flash is: custom factoryfs.img(less apps and added CSC), empty hidden.img, custom zImage(that is made to swap /data and /preload) and boot loaders(boot.bin, Sbl.bin and param.lfs).
Do not flash stock cache.img or data.img!
With taking all that in consideration, my Note is now running LPF with LPY CSC
hkgrob said:
I think it is Ficeto (DarkyROM kernel dev) who did this first. I remember someone posting something about this previously, but was probably missed.
EDIT: Worth it for people who don't have the $200 odd dollars in the meantime for a new MOBO
Click to expand...
Click to collapse
I already gave a vague idea in someother thread.But I'm not use it was my post or not...
vijai2011 said:
Hi all,
First of all I would like to say that this is purely not my work.All thanks goes to Fi***o(Guess him...).
Ok to the matter.You all know that most of the superbricks are caused because of the wipe done in recovery.It actually causes an I/O error which causes the /data partition in eMMC to get unrepairable.Even Odin,heimdall,shell....Nothin can fix it.And without /data partition your phone cannot boot.Since only the /data partition is damaged,you can use download mode and flash any kernel and even enter recovery sometimes.So explanation part is over.
Now to make our phone to boot up we must find a way to get /data partition working.But how can we?You know,there is a partition called /preload (hidden.img) which is always empty and almost not at all used and its size is 512 MB.So we are actually wasting 512 MB.A kernel only controlls where to mount what partition.So If we could make a kernel which would swap /data and /preload,/data will be mounted at /preload location and it will be fine and working and our phone will be able boot and run normally.
So does it only have advantages?Surely no.It has its own disadvantages too...
1.Your /data partition is shrinked to 512 MB
2.You should only stay on custom roms.You cannot flash a stock rom or anything through odin except kernels....
3.You can flash this kernel only through PC odin which means yellow triangle and increase counter.
But you can use CWM to flash any custom roms because it doesnt check for /preload but stock rom does....
And as I said earlier this is ain't my work but dont feel shy to press that thanks button if you like it....
Click to expand...
Click to collapse
Hmmm I actually had a simillar idea couple of days ago ,but not the preload parttion ,I thought that someone could mount data and system partitions on any other partitions ,like internal sdcard (the user accessable space) and then move the actual user accessable Sdcard to external storage ?
but I don't think it's the kernel alone that can do this ,but rather a modified .pit file (to repartition the sdcard) along with a modified kernel?
just thinking out loud here and could be just mumbling and totally wrong ,but I hope it gives the devs a starting point to help those poor superbricked people.
MR.change said:
Hmmm I actually had a simillar idea couple of days ago ,but not the preload parttion ,I thought that someone could mount data and system partitions on any other partitions ,like internal sdcard (the user accessable space) and then move the actual user accessable Sdcard to external storage ?
but I don't think it's the kernel alone can do this ,but rather a modified .pit file along with a modified kernel?
just thinking out loud here , hope it gives the devs a starting point to help those poor superbricked people.
Click to expand...
Click to collapse
Do you ever use a pit file in flashing custom roms through CWM or when flashing kernel through PC odin???As I said earlier you cannot flash any rom through odin except a kernel I guess.I'm not a superbrick owner.
But yeah what you said should also work but its very time consuming and confusing.
MR.change said:
Hmmm I actually had a simillar idea couple of days ago ,but not the preload parttion ,I thought that someone could mount data and system partitions on any other partitions ,like internal sdcard (the user accessable space) and then move the actual user accessable Sdcard to external storage ?
but I don't think it's the kernel alone can do this ,but rather a modified .pit file along with a modified kernel?
just thinking out loud here , hope it gives the devs a starting point to help those poor superbricked people.
Click to expand...
Click to collapse
much simpler to just use /preload most is still as it should be and only 3 lines need changing in a stock kernel(initramfs) for it to work. cwm requires another line changed and that is it.
I can provide a working GGB and LPF kernels (no cwm in LPF)
its one of my ideas.. relocating the partition to be used...
vijai2011 said:
Do you ever use a pit file in flashing custom roms through CWM or when flashing kernel through PC odin???As I said earlier you cannot flash any rom through odin except a kernel I guess.I'm not a superbrick owner.
But yeah what you said should also work but its very time consuming and confusing.
Click to expand...
Click to collapse
No not through CWM but PC ODIN ,and yes many superbricked people could flash .pit file successfully from pc odin.
ficeto said:
much simpler to just use /preload most is still as it should be and only 3 lines need changing in a stock kernel(initramfs) for it to work. cwm requires another line changed and that is it.
I can provide a working GGB and LPF kernels (no cwm in LPF)
Click to expand...
Click to collapse
yes I understand that my method is much harder ,but like I said I'm no dev and this just an idea that I had couple of days ago.
but there is some methodology to my madness:
the preload partition is only 512 mb ,thus very small for some ROMs .
my method (if doable at all) should give users much larger ROM space ,as they can use the SDcard which is 12 GBs of space.
ficeto said:
much simpler to just use /preload most is still as it should be and only 3 lines need changing in a stock kernel(initramfs) for it to work. cwm requires another line changed and that is it.
I can provide a working GGB and LPF kernels (no cwm in LPF)
Click to expand...
Click to collapse
I don't have a bricked note, but that's worth a thanks for sure. If you could share, I am sure a bunch of people will be doing random cartwheels.
Then again, someone will probably asked if they can flash it here, or there, or everywhere!
hkgrob said:
I don't have a bricked note, but that's worth a thanks for sure. If you could share, I am sure a bunch of people will be doing random cartwheels.
Then again, someone will probably asked if they can flash it here, or there, or everywhere!
Click to expand...
Click to collapse
the problem is that that kernel should be used correctly.Its not like cf-root,abyss kernel.If you flash on a note in good condition,you might have some problems...
I thought /data has user data and ROM is flashed onto a different partition, no?
anilisanil said:
I thought /data has user data and ROM is flashed onto a different partition, no?
Click to expand...
Click to collapse
Yeah partially right.A rom requires both /system and /data.
Good work.
Once the bricked note is up nd running, and rooted, ain't it possible to write some lowlevel partition and format utility to repair the original /data portion of EMMC ?
friedje said:
Good work.
Once the bricked note is up nd running, and rooted, ain't it possible to write some lowlevel partition and format utility to repair the original /data portion of EMMC ?
Click to expand...
Click to collapse
Nope.Not at all possible.The partition becomes completely inaccessable.
Yes there are low level programs like parted - to repartition.
e2fsck to scan for bad sectors -like scandisk in windows.
format - should be possible -- I have to get help of forest1971 for this.
prabhu1980 said:
Yes there are low level programs like parted - to repartition.
e2fsck to scan for bad sectors -like scandisk in windows.
format - should be possible -- I have to get help of forest1971 for this.
Click to expand...
Click to collapse
Is this correct? I was under the impression that the emmc error was due to incorrect voltages being passed and therefor physically frying the chips, hence the only fix is to replace the chips/mobo?
Sent from my GT-N7000 using xda premium
Ofcourse there are no weird voltages applied. It's still the same chip being programmed by the same program delivering the same voltages.....
Actually the program doesn't set any voltages, it just tells the chipset to put the memory into the 'writing mode'
The most likely problem is that a wrong entry point is being written into the filesystem for the data partition.
I was not able to format it in any way and trust me I tried everything ....
Just found this on the net.
http://mobiletechvideos.mybigcommerce.com/samsung-galaxy-note-jtag-brick-repair/
expensive but less then 200 for a new mobo. maybe somebody wants to try.
So, my Defy had been stuck on the CM logo a few days ago I decided on doing a wipe data and cache but it seems somewhere along the way something went wrong and now for some reason the internal storage disappeared, it just shows, in the storage tab, to be of 0.00b of size and 51.75mb of space used.
I don't know if it means anything but I'm also getting this errors on the recovery mode:
E: Can't mount CACHE:recovery/command
E: Can't mount CACHE:recovery/caller
E: Can't mount CACHE:recovery/log
Any help will be gladly appreciated, thanks.
Hocevar said:
So, my Defy had been stuck on the CM logo a few days ago I decided on doing a wipe data and cache but it seems somewhere along the way something went wrong and now for some reason the internal storage disappeared, it just shows, in the storage tab, to be of 0.00b of size and 51.75mb of space used.
I don't know if it means anything but I'm also getting this errors on the recovery mode:
E: Can't mount CACHE:recovery/command
E: Can't mount CACHE:recovery/caller
E: Can't mount CACHE:recovery/log
Any help will be gladly appreciated, thanks.
Click to expand...
Click to collapse
Hi! I had encountered this (or a 99% similar) problem when I installed CM10 (which never worked ever...) and then it got bootloop, so after that I tried to revert back to CM9, and I got the Encryption Unsuccessful message, and when I tried to revert further more back, on CM7.x it just goes bootloop, no message. This problem WAS NOT caused by ext3/ext4 partition in my case, so it seemed that the ROM/CWM just lost it's permission to access the internal storage.
I solved the problem using the good old JORDN_U3_97.21.51.sbf which always did the trick. (You'll gotta go back to Éclair, than some tricky way to Froyo, what is known as the latest stock rom for Defy)
GL to revive your device!
i was having a partion on my sd card to store apps (using amarullz script)
in order to flash cm7.2, i flashed stock rom as it was recommended by OP
then flashed cm7.2 totoro
In Cm7.2,i again tried to increase my internal memory through that extra partion i already had on my sd card
ok here goes the problem
when i did the steps to increase my memory ... its not working ...everything goes well during installation (no force closes too) but after completion nothing happened
i just dont know whats happening ...
does that partition got deleted or what during installing stock rom (via odin) ????
please sum1 come up with a solution
Puru007 said:
i was having a partion on my sd card to store apps (using amarullz script)
in order to flash cm7.2, i flashed stock rom as it was recommended by OP
then flashed cm7.2 totoro
In Cm7.2,i again tried to increase my internal memory through that extra partion i already had on my sd card
ok here goes the problem
when i did the steps to increase my memory ... its not working ...everything goes well during installation (no force closes too) but after completion nothing happened
i just dont know whats happening ...
does that partition got deleted or what during installing stock rom (via odin) ????
please sum1 come up with a solution
Click to expand...
Click to collapse
What phone are you using?
shyamSGY said:
What phone are you using?
Click to expand...
Click to collapse
I hope a galaxy y seeing as he is using cm7 totoro
anyway @op
I dont know if that kernel supports that script
you could always use link2sd instead
marcussmith2626 said:
I hope a galaxy y seeing as he is using cm7 totoro
anyway @op
I dont know if that kernel supports that script
you could always use link2sd instead
Click to expand...
Click to collapse
man i know that....n even tried to use that link2sd method
but when go recreate mount scripts,,,, its says -
Mount script cannot be created.
mount: mounting/dev/block/void/79:2 on /data/sdext2 failed: invalid argument
any idea about this?
try ext3 or ext4
-CALIBAN666- said:
try ext3 or ext4
Click to expand...
Click to collapse
^+1 for that
yo man it worked ......
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?