Hello, at the moment my phone is in a bit weird state and I would really appreciate any help
this is what I have, it's a SHS bought in Europe
Model number: GT-I9000
Formware version: 2.2
Baseband version: I9000XXJPP
Kernel version: 2.6.32.9 [email protected] #Voodoo_stable_5.5
Build number: FROYO.XWJPF
I installed latest voodoo recently and it worked fine, quadrant was giving me about 1500 points so I'm sure it working and the phone was really fast
everything was fine until decided to root it to apply wifi timeout fix... since I have 3 button recovery mode I didn't think I was risking anything (MY MISTAKE!)
unfortunately, after 4 hours of reviving my phone I don't remember what program from market I used to root... anyway, I ended up having SuperUser app with ninja icon... and I lost all my other apps... now I know I should have converted the filesystem back before doing anything, but it was too late
at this point female voice was already saying "data partition /*something*/ system not available"
I decided to reset the phone from the recovery menu and it was giving me errors, it couldn't mount partition or do something with them, and it also wouldn't boot anymore
I started searching for solutions and found THIS, everything looked exactly as I had so I decided to follow those instructions, I think they can be summed up to this:
Now, we need to fix the partitions. This is assuming that the partitions are there, just the wrong format (which is what happened to me .. I accidentally made them FAT32 instead of ext). So, run the following: parted /dev/block/mmcblk0 mkfs ext2. It will ask if you want to continue, hit yes. When it asks for the partition number, enter 1. Next, when it asks for the format, enter ext2. Let it do its thing. Now, once it's done, run parted again. This time, enter partition 2 (everything else is the same).
Click to expand...
Click to collapse
I did what this said and my phone could boot and wipe data from recovery menu could also work
but it kept saying about "system not available"
I thought the problem could still be in the superuser ninja app, so I started looking how to remove it, and found THIS, which also worked and I got rid of it
but I still have female void saying "system not available" on boot
and for some reason, the phone can't connect by wifi to my router anymore, it gets stuck on obraining IP address, it could after all this, but after some restarts and resets it can't connect anymore
he's the voodoo logs that I have now:
2011-03-20 20:33:52 model detected: 8GB
2011-03-20 20:33:53 option: lagfix disabled
2011-03-20 20:33:53 option: lagfix is allowed to convert /system to Ext4
2011-03-20 20:33:53 option: debug mode enabled
2011-03-20 20:33:53 filesystem detection on system:
2011-03-20 20:33:53 Ext4 on /dev/block/stl9
2011-03-20 20:33:53 filesystem detection on dbdata:
2011-03-20 20:33:53 Ext4 on /dev/block/stl10
2011-03-20 20:33:53 filesystem detection on cache:
2011-03-20 20:33:53 Ext4 on /dev/block/stl11
2011-03-20 20:33:53 filesystem detection on data:
2011-03-20 20:33:53 RFS on /dev/block/mmcblk0p2
2011-03-20 20:33:53 battery level: 77%
2011-03-20 20:33:53 convert cache (/dev/block/stl11) from ext4 to rfs
2011-03-20 20:33:53 ERROR: unable to call the df command from system, cancel conversion
2011-03-20 20:33:53 Your Android system partition is empty or it is corrupt (Universal Lagfix /system corruption)
2011-03-20 20:33:53 You may flash a new factoryfs.rfs with Odin or try to it with the RFS fixer
2011-03-20 20:33:53 battery level: 77%
2011-03-20 20:33:53 convert dbdata (/dev/block/stl10) from ext4 to rfs
2011-03-20 20:33:53 ERROR: unable to call the df command from system, cancel conversion
2011-03-20 20:33:53 Your Android system partition is empty or it is corrupt (Universal Lagfix /system corruption)
2011-03-20 20:33:53 You may flash a new factoryfs.rfs with Odin or try to it with the RFS fixer
2011-03-20 20:33:53 no need to convert data
2011-03-20 20:33:53 battery level: 77%
2011-03-20 20:33:53 convert system (/dev/block/stl9) from ext4 to rfs
2011-03-20 20:33:56 ERROR: unable to call the df command from system, cancel conversion
2011-03-20 20:33:56 Your Android system partition is empty or it is corrupt (Universal Lagfix /system corruption)
2011-03-20 20:33:56 You may flash a new factoryfs.rfs with Odin or try to it with the RFS fixer
2011-03-20 20:33:58 manage fat.format in /system/bin
2011-03-20 20:33:58 fat.format wrapper already installed in /system/bin
2011-03-20 20:33:58 running extension: apk_cleaner.sh
2011-03-20 20:33:58 TouchWiz 3.0 Launcher already optimized
2011-03-20 20:33:58 running extension: install_bln.sh
2011-03-20 20:33:58 BackLightNotification improved liblights already installed
2011-03-20 20:33:58 running extension: install_su.sh
2011-03-20 20:33:58 secure su binary for Superuser apk already installed
2011-03-20 20:33:58 running extension: sdcard_cleaner.sh
2011-03-20 20:33:58 sdcard cleaned up
2011-03-20 20:33:58 running extension: update_vold.fstab.sh
2011-03-20 20:33:58 running init !
Click to expand...
Click to collapse
Quadrant gives me 1000 points now, so there's probably some different filesystem configuration at the moment... maybe it's because I followed the instructions and created ext2 partitions?
anyway, even though my phone has 3-button recovery and still boots it is still screwed at the moment, so I'm looking for a way to get back to stock firmware and then voodoo again
but should I somehow convert back to RFS first?
I don't care about my data, there's nothing important in it
I found this post, would it be safe to use any of those firmwares with the phone in this state? will Odin's re-partition feature dump everything that I have now and recreate normal filesystem?
and which stock firmware should I use? there's no I9000XXJPP version in that list, would it be safe to use any other European 2.2.1 version?
I appreciate any help
well what you need to do is download a firmware with all 3 files and PIT.
Go into odin and put the correct files in the correct section, then put your pit file in, and check the repartition box.
flash that thru odin and you should be ok, this will remove the ext 4 filesystem and replace back to stock rfs.
if you are having trouble finding a firmware with all 3 files. try darkys resurrection (odin version) with 512 pit.
Thanks, I'll try to install I9000XXJPY in the evening and see how it goes
I downloaded I9000XXJPY firmware from this thread and it's only 1 file inside - JPY_JPY_JPY.tar
inside it has:
cache.rfs
factoryfs.rfs
param.lfs
zImage
modem.bin
instructions say that I shouldn't check re-partition with 1 file installation, but as I understand, I need to re-partition my phone
will this 1 file firmware installation even work in my situation?
I think I found what I need: this post describes how to install 1 file firmware with repartitioning and rooting
following those instructions solved my problems
the only problem was with voodoo... I was surprised to see that even after installing new firmware my phone still remembered password for my wifi... so I had to reset it
and voodoo wouldn't work, because there was a disable-lagfix file on the internal sd card (which also wasn't erased), so I had to remove that
Thanks for the advice
Related
Is it possible convert the ext2 partition to rfs format? i have changed the /dev/block/stl3 to ext2 format by mistake, and could not find the way back to rfs, which cause all official ROM stop working properly, please kindly help.
Eddie
haoning said:
Is it possible convert the ext2 partition to rfs format? i have changed the /dev/block/stl3 to ext2 format by mistake, and could not find the way back to rfs, which cause all official ROM stop working properly, please kindly help.
Eddie
Click to expand...
Click to collapse
try newfs_msdos or fat.fotmat
wipe uses fat.format to new partitions
tried to use fat.format with -F 32 parameter, but got the error "too small partition" as this partition is only 6M, which parameter should be used to avoid this? and where can i find newfs_msdos?
someone help? urgent for help.
Did you try to tick "repartition" in Odin?
yes, but it doesn't help as odin will not touch this partition.
try this
Code:
fat.format -F 16 -S 512 -s 1 /dev/block/stl3
Hello all I have my first reoccurring issue. I have tried a complete reflash and only have this info to go on:
Running jvk simply honey rom with voodoo hack kernel. Last time I tried to convert to ext4 via voodoo hack on stock jvk it worked fine. On doc jvk deodexed it worked fine. Simply 3 rc2 not working BUT it seems odd that the rom would affect anything.
Voodoo log says something ominous:
Superuser apk already installed
2011-04-13 06:12:51 running extension: sdcard_cleaner.sh
2011-04-13 06:12:51 sdcard cleaned up
2011-04-13 06:12:51 running init !
2011-04-13 06:13:48 model detected: 16GB-bigger-movinand
2011-04-13 06:13:49 option: lagfix disabled
2011-04-13 06:13:49 option: lagfix will keep /system as RFS
2011-04-13 06:13:49 filesystem detection on system:
2011-04-13 06:13:49 RFS on /dev/block/stl9
2011-04-13 06:13:49 filesystem detection on dbdata:
2011-04-13 06:13:49 Ext4 on /dev/block/stl10
2011-04-13 06:13:49 filesystem detection on cache:
2011-04-13 06:13:49 Ext4 on /dev/block/stl11
2011-04-13 06:13:49 filesystem detection on data:
2011-04-13 06:13:49 RFS on /dev/block/mmcblk0p2
2011-04-13 06:13:49 battery level: %
2011-04-13 06:13:49 convert cache (/dev/block/stl11) from ext4 to rfs
2011-04-13 06:13:49 ERROR: unable to call the df command from system, cancel conversion
2011-04-13 06:13:49 Your Android system partition is empty or it is corrupt (Universal Lagfix /system corruption)
2011-04-13 06:13:49 You may flash a new factoryfs.rfs with Odin or try to it with the RFS fixer
2011-04-13 06:13:49 battery level: %
2011-04-13 06:13:49 convert dbdata (/dev/block/stl10) from ext4 to rfs
2011-04-13 06:13:49 ERROR: unable to call the df command from system, cancel conversion
2011-04-13 06:13:49 Your Android system partition is empty or it is corrupt (Universal Lagfix /system corruption)
2011-04-13 06:13:49 You may flash a new factoryfs.rfs with Odin or try to it with the RFS fixer
2011-04-13 06:13:49 no need to con
Also in CWM I can't seem to be able to unmount system... is this normal?
Could someone please help me sort this out if its fixable easily?
Oh and using root explorer any mount settings I apply to folders don't 'stick'
**Simply Honey 3.0, Voodoo GB hack, JVE modem**
rlorange said:
Hello all I have my first reoccurring issue. I have tried a complete reflash and only have this info to go on:
Running jvk simply honey rom with voodoo hack kernel. Last time I tried to convert to ext4 via voodoo hack on stock jvk it worked fine. On doc jvk deodexed it worked fine. Simply 3 rc2 not working BUT it seems odd that the rom would affect anything.
Voodoo log says something ominous:
Superuser apk already installed
2011-04-13 06:12:51 running extension: sdcard_cleaner.sh
2011-04-13 06:12:51 sdcard cleaned up
2011-04-13 06:12:51 running init !
2011-04-13 06:13:48 model detected: 16GB-bigger-movinand
2011-04-13 06:13:49 option: lagfix disabled
2011-04-13 06:13:49 option: lagfix will keep /system as RFS
2011-04-13 06:13:49 filesystem detection on system:
2011-04-13 06:13:49 RFS on /dev/block/stl9
2011-04-13 06:13:49 filesystem detection on dbdata:
2011-04-13 06:13:49 Ext4 on /dev/block/stl10
2011-04-13 06:13:49 filesystem detection on cache:
2011-04-13 06:13:49 Ext4 on /dev/block/stl11
2011-04-13 06:13:49 filesystem detection on data:
2011-04-13 06:13:49 RFS on /dev/block/mmcblk0p2
2011-04-13 06:13:49 battery level: %
2011-04-13 06:13:49 convert cache (/dev/block/stl11) from ext4 to rfs
2011-04-13 06:13:49 ERROR: unable to call the df command from system, cancel conversion
2011-04-13 06:13:49 Your Android system partition is empty or it is corrupt (Universal Lagfix /system corruption)
2011-04-13 06:13:49 You may flash a new factoryfs.rfs with Odin or try to it with the RFS fixer
2011-04-13 06:13:49 battery level: %
2011-04-13 06:13:49 convert dbdata (/dev/block/stl10) from ext4 to rfs
2011-04-13 06:13:49 ERROR: unable to call the df command from system, cancel conversion
2011-04-13 06:13:49 Your Android system partition is empty or it is corrupt (Universal Lagfix /system corruption)
2011-04-13 06:13:49 You may flash a new factoryfs.rfs with Odin or try to it with the RFS fixer
2011-04-13 06:13:49 no need to con
Also in CWM I can't seem to be able to unmount system... is this normal?
Could someone please help me sort this out if its fixable easily?
Oh and using root explorer any mount settings I apply to folders don't 'stick'
**Simply Honey 3.0, Voodoo GB hack, JVE modem**
Click to expand...
Click to collapse
I too have same issue. Previously ran Juwe's rom 3.2 with new CF kernel which used RFS. Decided to try Darky's rom which is using a Voodoo kernel. Have the exact same problem.
I'm on a fresh flash of continuum 6.1, and it seems as if my filesystem is stuck on ext4. Here's a voodoo log if it helps,
2011-07-18 05:56:29 model detected: 16GB
2011-07-18 05:56:29 option: lagfix disabled
2011-07-18 05:56:29 option: lagfix is allowed to convert /system to Ext4
2011-07-18 05:56:29 option: debug mode enabled
2011-07-18 05:56:29 filesystem detection on system:
2011-07-18 05:56:29 Ext4 on /dev/block/stl9
2011-07-18 05:56:29 filesystem detection on dbdata:
2011-07-18 05:56:29 Ext4 on /dev/block/stl10
2011-07-18 05:56:29 filesystem detection on cache:
2011-07-18 05:56:29 Ext4 on /dev/block/stl11
2011-07-18 05:56:29 filesystem detection on data:
2011-07-18 05:56:29 Ext4 on /dev/block/mmcblk0p2
2011-07-18 05:56:30 battery level: %
2011-07-18 05:56:30 convert cache (/dev/block/stl11) from ext4 to rfs
2011-07-18 05:56:30 ERROR: unable to call fat.format: cancel conversion
2011-07-18 05:56:30 battery level: %
2011-07-18 05:56:30 convert dbdata (/dev/block/stl10) from ext4 to rfs
2011-07-18 05:56:30 ERROR: unable to call fat.format: cancel conversion
2011-07-18 05:56:30 battery level: %
2011-07-18 05:56:30 convert data (/dev/block/mmcblk0p2) from ext4 to rfs
2011-07-18 05:56:30 ERROR: unable to call fat.format: cancel conversion
2011-07-18 05:56:30 battery level: %
2011-07-18 05:56:30 convert system (/dev/block/stl9) from ext4 to rfs
2011-07-18 05:56:30 ERROR: unable to call fat.format: cancel conversion
2011-07-18 05:56:30 manage fat.format in /sbin
2011-07-18 05:56:30 fat.format wrapper installed in /sbin
2011-07-18 05:56:30 running extension: apk_cleaner.sh
2011-07-18 05:56:30 running extension: install_bln.sh
2011-07-18 05:56:30 BackLightNotification improved liblights cannot be installed or is not supported
2011-07-18 05:56:30 running extension: install_su.sh
2011-07-18 05:56:30 secure su binary for Superuser apk cannot be installed
2011-07-18 05:56:30 running extension: sdcard_cleaner.sh
2011-07-18 05:56:30 sdcard cleaned up
2011-07-18 05:56:30 running init !
Click to expand...
Click to collapse
Sent from my SAMSUNG-SGH-I897 using Tapatalk
Same thing happening here. Running Apex w/ DarkCore at the moment. Just want to try RFS again, but cannot get there.
I have the same problem... I found a solution on the Vibrant forum but doesn't worked for me, you guys can try it, though
http://forum.xda-developers.com/showthread.php?t=875498
justmart said:
I have the same problem... I found a solution on the Vibrant forum but doesn't worked for me, you guys can try it, though
http://forum.xda-developers.com/showthread.php?t=875498
Click to expand...
Click to collapse
I can't try it right now but if it doesn't work for me then I would guess we need the stock gingerbread version. Theirs seem to be Froyo.
Sent from my SAMSUNG-SGH-I897 using Tapatalk
I tried it and it didn't work, but it's definitely a kernel problem. kodos96 (team member of the kernel I'm using, Talon) he gave me a custom built version of Talon that fixed my problems.
This post will interest many. a few days ago my internal memory is physically dead, the memory (16GB) is partitioned into two, /data (~ 2GB) and /sdcard (~ 14GB). Not having these partitions the phone can not save settings or user data.
Symptoms:
* Internal sd corrupt (http://forum.xda-developers.com/showthread.php?t=845708)
* (I/O) error in factory reset
* mmcblk0p1 y mmcblk0p2 does not appear in /dev/block/
* Boot loop
* E: can not mount /dev/block/mmcblk0p1 in recovery, or updating rom
* You can't install applications, since /data does not exist
Please I need your help to move the partition /data to external sd memory (/dev/block/mmcblk1p2).
I Create two partitions fat32 (/dev/block/mmcblk1p1) and ext4 (/dev/block/mmcblk1p2) and edit the fstab file and vold.fstab. the system now recognizes the FAT32 partition of the external memory as internal memory but the partition /data does not mount the second partition of external SD.
original:
---
/dev/block/stl11 /cache auto llw,check=no,nosuid,nodev
/dev/block/mmcblk0p2 /data auto llw,check=no,nosuid,nodev
/dev/block/stl10 /dbdata auto llw,check=no,nosuid,nodev
/dev/block/stl9 /system auto llw,check=no
/dev/block/mmcblk0p1 /mnt/sdcard vfat rw
(null) /sd-ext auto rw
---
edited:
---
/dev/block/stl11 /cache auto llw,check=no,nosuid,nodev
/dev/block/mmcblk1p2 /data auto llw,check=no,nosuid,nodev
/dev/block/stl10 /dbdata auto llw,check=no,nosuid,nodev
/dev/block/stl9 /system auto llw,check=no
/dev/block/mmcblk0p1 /sd-ext vfat rw
(null) /mnt/sdcard auto rw
---
The busybox df-h command shows that the first partition is mounted, but the second partition is not listed .
I've tried everything, and what I see is that it requires more knowledge. Not whether to build or edit the kernel or some file.
I appreciate your help, since many users have a higher Know-how on this topic.
* My English is very bad, I'm using the google translator.
I tried to edit the initramfs folder to edit files lpm.rc init.rc and fota.rc, i download many kernels to remove zImage and edit images and package them again, but does not work, not that I'm doing wrong.
Someone who has worked with the edition of the kernel can help me build or rebuild a file with the new changes.
I am new to Android, want to customize the system follow the tutorials, but found the Note is different to other Android phones:
for other phone, there will be a /proc/mtd and list all the partitions with mount point, but on Note I can only found /proc/fs, with 3 folders: ext4 jbd2 nfsd
and the mount table is like this:
rootfs on / type rootfs (ro,relatime)
...
/dev/block/mmcblk0p9 on /system type ext4
/dev/block/mmcblk0p7 on /cache type ext4
/dev/block/mmcblk0p1 on /efs type ext4
for other devices, e.g., HTC Wildfire, the partition will like below:
mtd1: recovery
mtd3: system"
...
I downloaded the CF-Root flasher, by Chainfire, found basiclly it's flashing a zImage into /dev/block/mmcblk0p5. I mount the partition before flash and seems there is only some picture files there. how can we know the machine will boot to this partition in recovery mode?
nobody knows? so far what I get seems that the phone do not use the /recovery partition, but use same kernel to handle the recovery state. during boot it will search for /system/etc/install-recovery.sh, maybe that will trigger the recovery process?
The Note, like many other Samsung phones, does not use or follow the mtd layout - at all.
Indeed there is a single kernel for both normal boot and recovery. Normal boot uses init.rc script, recovery boot uses recovery.rc script.
There is a "spare" partition that is both called recovery and available, but it isn't used.