I soft bricked my Vibrant after installing Bionix 1.4 w/Jacs OC/UV/Voodoo kernel. I used Odin to flash back to stock rom which was unsuccessful. It allowed me to boot to the samsung logo and then go black.
Grasping at straws I used clockwork recovery to do a nandroid restore to the vibrant9 rom I was running before (with the KingKlick kernel, but as I understand it nandroid doesnt backup or restore kernels). I thought maybe the kernel got switched back to the stock one but I'm lacking a ROM? Anyway, nandroid restored the system files but when going to restore data it gave me an error about not finding mmcblk0p2, when I go into adb shell and type mount, it tells me I have mmcblk0p3.
Is there any way for me to fix this so I can restore from my nandroid backups? I have everything in titanium and I can still access all the data on the sd card, but I'd really like to just have things back to how they were before installing the Bionix.
Thanks!
Here is a complete copy of what comes up when I hit mount if it helps. Could really use some assistance here, I try to do as much on my own as possible but I've hit a dead end.
Code:
$ mount
mount
rootfs / rootfs rw 0 0
tmpfs /dev tmpfs rw,mode=755 0 0
devpts /dev/pts devpts rw,mode=600 0 0
proc /proc proc rw 0 0
sysfs /sys sysfs rw 0 0
/dev/block/stl6 /mnt/.lfs j4fs rw 0 0
tmpfs /sqlite_stmt_journals tmpfs rw,size=4096k 0 0
none /dev/cpuctl cgroup rw,cpu 0 0
/dev/block/stl9 /system rfs rw,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0
/dev/block/mmcblk0p3 /data_tmo rfs rw,nosuid,nodev,vfat,llw,check=no,gid/uid/rwx
,iocharset=utf8 0 0
/dev/block/stl10 /dbdata rfs rw,nosuid,nodev,vfat,llw,check=no,gid/uid/rwx,iocha
rset=utf8 0 0
/dev/block/stl11 /cache rfs rw,nosuid,nodev,vfat,llw,check=no,gid/uid/rwx,iochar
set=utf8 0 0
/dev/block/stl3 /efs rfs rw,nosuid,nodev,vfat,llw,check=no,gid/uid/rwx,iocharset
=utf8 0 0
/dev/loop0 /data/data1 j4fs rw,noatime,nodiratime 0 0
/dev/block//vold/179:1 /sdcard vfat rw,dirsync,nosuid,nodev,noexec,uid=1000,gid=
1015,fmask=0102,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,s
hortname=mixed,utf8,errors=remount-ro 0 0
/dev/block//vold/179:9 /sdcard/sd vfat rw,dirsync,nosuid,nodev,noexec,uid=1000,g
id=1015,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-
1,shortname=mixed,utf8,errors=remount-ro 0 0
$ adb reboot recovery
Ok, thanks for all the help guys....
Anyway, for anyone who is having the same problem, I found my solution to be to get into download mode via instructions here: http://forum.xda-developers.com/showthread.php?t=741027&highlight=unbrick
And then follow the instructions in Fix 1 here: http://forum.xda-developers.com/showthread.php?t=782027
I had to upgrade to froyo then downgrade to get my file system back.
I'm now on stock Vibrant kernel and rom, but flashing Bionix 1.5 in a moment (NO VOODOO!!!)
Exact same thing
i had to do the exact same thing this morning. except mine would boot up fully. i couldnt get the internal memory to recognize at all so i couldnt disable the lagfix
blah blah blah... odin and fix 1 worked. i wished i had backups on my computer i should know better by now too. thats the stupid part. all that data lost.
Yea, I'm not new to this sort of thing, just this piece of hardware. I felt really confident after flashing a few ROM's and always read instructions for each new install, I was really surprised to find myself in that pickle. At least I learned something.
Going forward I'm being very dilligent about organizing a backup of my nandroid backups, different ROM's, everything needed to get back to stock, and most importantly the contents of my internal SD card! Nothing had ever messed with that partitioin before so I thought it would be fine, I also thought that nandroid or titanium would backup all my e-books since they were imported into Aldiko, WRONG-O!, it just saves the library index, gotta re-import over 600 books :O
Gotta love nothing ever being good enuf, now I'm off to fix what I broke on my car...
Related
Ok so I have a question about wiping the Dalvik Cache in Clockword Recovery. When I boot into recovery I go to Advanced > Wipe Dalvik Cache. Upon clicking this I am prompted with
E:Can't mount /dev/block/mmcblk1p2 <----IS THIS NORMAL?
(File exists)
Then it brings up the no,no,no, yes - wipe dalvik cache,no, no, no screen and I click yes and it says that everything went smooth.
I wiped the cache w/out disabling voodoo from clockwork and just want to make sure this is either A-normal or B-needs to be fixed. Voodoo has since been disabled and I then flashed to JFD Stock and then JI6 Stock and everything seems fine. I just remember reading that the "can't mount" is terrible news when coupled with Voodoo. Can anyone one confirm for me whether this is normal or not? Thanks!
Can someone help shed some light on this please? When I mount in terminal I get this back
$ export PATH=/data/local/bin:$PATH
$mount
rootfs / rootfs ro 0 0
tmpfs /dev tmpfs rw,mode=755 0 0
devpts /dev/pts devpts rw,mode=600 0 0
proc /proc proc rw 0 0
sysfs /sys sysfs rw 0 0
/dev/block/stl6 /mnt/.lfs j4fs rw 0 0
tmpfs /sqlite_stmt_journals tmpfs rw,size=4096k 0 0
none /dev/cpuctl cgroup rw,cpu 0 0
/dev/block/stl9 /system rfs ro,vfat,log_off,check=no,gid/uid/rwx,iocharset=utf8 0 0
/dev/block/mmcblk0p2 /data rfs rw,nosuid,nodev,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0
/dev/block/mmcblk0p3 /data_tmo rfs rw,nosuid,nodev,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0
/dev/block/stl10 /dbdata rfs rw,nosuid,nodev,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0
/dev/block/stl11 /cache rfs rw,nosuid,nodev,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0
/dev/block/stl3 /efs rfs rw,nosuid,nodev,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0
/dev/block//vold/179:1 /sdcard vfat rw,dirsync,nosuid,nodev,noexec,uid=1000,gid=1015,fmask=0102,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block//vold/179:9 /sdcard/sd vfat rw,dirsync,nosuid,nodev,noexec,uid=1000,gid=1015,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
$
I've done mount before and there is definitely something funny about this. I think it's that "/dev/block/stl6 /mnt/lfs j4fs" towards the top. Voodoo it's disabled so why does it still look off? Anyone?
Not sure but I am getting the same thing on my droid incredible. Same error, wonder if that is why some of my rom's are acting strange.
Seagrizzly said:
Not sure but I am getting the same thing on my droid incredible. Same error, wonder if that is why some of my rom's are acting strange.
Click to expand...
Click to collapse
I actually figured it out. The partition mmcblk1p2 is used for installing apps to your external SD card which is only present in froyo. So if you are running 2.1 Eclair then its normal for it not to be able to mount it, but if you are running froyo then there might be a prob...
Hello everyone,
I posted about this earlier but don't think I explained it well enough so let me try again. Last night I put Voodoo on my phone. Then this morning I was messing with some mods and I booted the phone into clockwork recovery. In there I cleared my cache and then i went to advanced>Wipe Dalvik Caceh and got this
E:Can't mount /dev/block/mmcblk1p2
(File exists)
I cleared the Dalvik Cache and it said it completed successfully. Then I remember that line showing up when you tried to flash something or perform a nandroid with voodoo enabled. So I booted up my phone and everything appears to be ok. I am able to download apps, everything seems to be working, ect. Then I go into Terminal and type "mount" and this is the what I get back
$mount
rootfs / rootfs ro 0 0
tmpfs /dev tmpfs rw,mode=755 0 0
devpts /dev/pts devpts rw,mode=600 0 0
proc /proc proc rw 0 0
sysfs /sys sysfs rw 0 0
/dev/block/stl6 /mnt/.lfs j4fs rw 0 0
tmpfs /sqlite_stmt_journals tmpfs rw,size=4096k 0 0
none /dev/cpuctl cgroup rw,cpu 0 0
/dev/block/stl9 /system rfs ro,vfat,log_off,check=no,gid/uid/rwx,iocharset=utf8 0 0
/dev/block/mmcblk0p2 /data rfs rw,nosuid,nodev,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0
/dev/block/mmcblk0p3 /data_tmo rfs rw,nosuid,nodev,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0
/dev/block/stl10 /dbdata rfs rw,nosuid,nodev,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0
/dev/block/stl11 /cache rfs rw,nosuid,nodev,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0
/dev/block/stl3 /efs rfs rw,nosuid,nodev,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0
/dev/block//vold/179:1 /sdcard vfat rw,dirsync,nosuid,nodev,noexec,uid=1000,gid=1015,f mask=0102,dmask=0002,allow_utime=0020,codepage=cp4 37,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block//vold/179:9 /sdcard/sd vfat rw,dirsync,nosuid,nodev,noexec,uid=1000,gid=1015,f mask=0000,dmask=0000,allow_utime=0022,codepage=cp4 37,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
$
I know from previously typing "mount" when confirming whether i am ext4 or rfs that this is very wrong looking. At the top where it says "/dev/block/stl6 /mnt/.lfs j4fs rw 0 0" it previously would say "/dev/block/mmcblk0p2 /data rfs rw" ... So what the heck does this mean? I have disabled voodoo and that did not change it. I have even downloaded the froyo that don't brick and downgraded back to 2.1 true stock and I am still getting this. I have this funny feeling that my cache is lost in limbo or something. Can anyone tell me whether this is normal or what it means? I just want to make sure that nothing is out of place or if something is wrong, what I need to do to fix it. Thanks in advance!
You won't be able to wipe dalvik-cache with voodoo enabled. It's located in the /data mount which Clockwork won't be able to access.
The mount you posted looks fine. Your /data is mounted at /dev/block/mmcblk0p2 as rfs. The /cache is mounted at /dev/block/stl11. Everything is where it's supposed to be. The order isn't important.
silow said:
You won't be able to wipe dalvik-cache with voodoo enabled. It's located in the /data mount which Clockwork won't be able to access.
The mount you posted looks fine. Your /data is mounted at /dev/block/mmcblk0p2 as rfs. The /cache is mounted at /dev/block/stl11. Everything is where it's supposed to be. The order isn't important.
Click to expand...
Click to collapse
Thanks for the reply. However, after reverting back to 100% stock (voodoo disabled) I have rooted, installed clockwork, and tried wiping the dalvik cache again. Everytime when I click advanced>wipe dalvik cache it still gives me the "can't mount... (file exists)" bit. Is that normal?
EDIT: So I think I may have figured this out. That partition is used to install apps to your sd card, which is only present in Froyo. Soooo it is normal to receive that error when running 2.1...
Hi all,
I just replace the internal memory with an 8 GB microSD, then I run the adb logcat and there is a message as follows:
EXT2-fs error (devices loop0): ext2_lookup:
deleted inode referenced: 20679
What does it mean? whether there are errors in the partition?
Hi, after you replaced the internal sdcard... i think you need a "new" Rom... flash... (Factory Reset?)
MfG
UKSheep
UKSheep said:
Hi, after you replaced the internal sdcard... i think you need a "new" Rom... flash... (Factory Reset?)
MfG
UKSheep
Click to expand...
Click to collapse
Yes, I already did flashing a new rom. But that doesnt fix it
hm, sorry...
i know no solution.
There is a thread over at MoDaCo that tells you how to do it. You will need to keep the partition sizes the same and use a modified boot.img file in order for your streak to recognise the bigger card.
I'm also pretty sure that there is the modified boot.img files for all versions of the streak roms on that thread for you to download.
I've often thought about doing it, but I'm not brave enough yet
I am intersted in this too but still no clarity, for me at least. Glad you are braver than some of us.
There is also a thread
http://android.modaco.com/content/d...6477/lcd-replacement-and-internal-sd-upgrade/
Keep us informed and I, for one, will follow. 32Gb Class 10 cards are no longer outrageous prices and that capacity will make the exercise worthwhile for me.
According to the other thread you can go to at least 4gig without any special files.
Btw, previously I have made 3 partitions for the internal memory card as follows:
-- Partition 1: 2GiB ext2
-- Partition 2: 1GiB ext3 (named cache)
-- Partition 3: 5 GiB ext4 (named Data)
Is there an error in setting up partition?
I use steve streak droid 1.7. And the system read 6,12GB for internal memory
Please help
Hello, the partitions you are showing seem to be ok...
what was the use for you to swap the internal sd ? speed, more space for apps ?
How did you manage to obtain those partitions ? did you followed the howto from modaco's forum ?
Could you provide me the output of a mount command ?
to finish, did you change the original boot.img to a modified one, provided in the same forum ?
I'm willing to help you, but you need to provide me those informations !
Good luck,
Boujou bien,
K.
kwenteen said:
Hello, the partitions you are showing seem to be ok...
what was the use for you to swap the internal sd ? speed, more space for apps ?
How did you manage to obtain those partitions ? did you followed the howto from modaco's forum ?
Could you provide me the output of a mount command ?
to finish, did you change the original boot.img to a modified one, provided in the same forum ?
I'm willing to help you, but you need to provide me those informations !
Good luck,
Boujou bien,
K.
Click to expand...
Click to collapse
Hi, my priority is the speed in running application. To obtain those partition i use gparted live via usb. honestly I didn't follow the howto from modaco forum and I didn't change the original boot.img.
What should I do now? Thanks for your support.
here is the output of mount command:
export PATH=/data/local/bin:$PATH
sh-4.1$ export PATH=/data/local/bin:$PATH
sh-4.1$ root
sh: root: command not found
sh-4.1$ su
sh-4.1# mount
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
/dev/block/mtdblock6 /system yaffs2 rw,relatime 0 0
/dev/block/mtdblock7 /firstboot yaffs2 rw,nosuid,nodev,relatime 0 0
/dev/block/innersd0p5 /cache ext3 rw,noatime,nodiratime,errors=continue,commit=99999,data=writeback 0 0
/dev/block/innersd0p6 /data ext3 rw,noatime,nodiratime,errors=continue, commit=99999,data=writeback 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
/dev/loop0 /mnt/asec/extdata ext2 rw,nosuid,nodev,noatime,nodiratime,errors=continue 0 0
/dev/block/vold/179:17 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:17 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
/dev/block/dm-0 /mnt/asec/com.ArtInGames.AirAttackHDLite-1 vfat ro,dirsync,nosuid,nodev,noexec,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/dm-1 /mnt/asec/com.agilesoftresource-2 vfat ro,dirsync,nosuid,nodev,noexec,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed, utf8,errors=remount-ro 0 0
/dev/block/dm-2 /mnt/asec/com.rovio.angrybirdsrio-1 vfat ro,dirsync,nosuid,nodev,noexec,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/dm-3 /mnt/asec/com.rovio.angrybirds-1 vfat ro,dirsync,nosuid,nodev,noexec,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
sh-4.1#
up up please help
/dev/block/innersd0p5 /cache ext3 rw,noatime,nodiratime,errors=continue,commit=99999 ,data=writeback 0 0
/dev/block/innersd0p6 /data ext3 rw,noatime,nodiratime,errors=continue, commit=99999,data=writeback 0 0
/dev/loop0 /mnt/asec/extdata ext2 rw,nosuid,nodev,noatime,nodiratime,errors=continue 0 0
apparently, your /data and /cache partitions seem to be found by your device, and well mounted... which is quite weird, because you didn't changed your boot.img.
I'm wondering if you're not using a mod made to speed up the rom, by using your external sd to be used for data ? That could be related to the loop line in your mount command, that may be related to the error you see in logcat...
what are the symptoms on your phone, besides the message ? can you install apps ?
I would advise you to try a modded boot.img, you will find the file for your streakdroid version on the modaco link that someone posted earlier... it won't delete your files, and should help ! use fastboot to flash it !
I think it should solve your problem !
good luck,
Boujou bien,
K.
kwenteen said:
I'm wondering if you're not using a mod made to speed up the rom, by using your external sd to be used for data ? That could be related to the loop line in your mount command, that may be related to the error you see in logcat...
what are the symptoms on your phone, besides the message ? can you install apps ?
I would advise you to try a modded boot.img, you will find the file for your streakdroid version on the modaco link that someone posted earlier... it won't delete your files, and should help ! use fastboot to flash it !
I think it should solve your problem !
good luck,
Boujou bien,
K.
Click to expand...
Click to collapse
so the setting is still using the external card for data? how do I move it to an internal card which is certainly faster (class 10 vs class 2)?
Apart from these error messages, no problems when using the handset. I also can install the application.
I've tried boot.img and it seems an error message is gone. I'm still wondered the use of data in the internal card, please guide.
Up ul about internal sd
normally by flashing the new boot.img, you should have a "normal" setup, meaning without the loop device...
just run once more the mount command, and see if you still have this loop mounted !
And if yes, I suggest you to flash a fresh rom, that doesn t have this option, like the streakdroid 190, and be sure to replace in the update.zip file the original boot.img with the alternate one available on modaco...
And beware of the option you select with this install, some of them are incompatible with the innersd mod !
good luck !
K.
I have done these works :
1. Removed full battery notification
2. Installed supercurio kernel
3. Removed touchwiz launcher (replaced with the stock gingerbread of the nexus s 9020)
4. Removed all Samsung stuff (unuseful) except voice commands and dlna.
Now i would share this with all the comunity, but how i can do this ?
(i can't do a nandroid backup because clockworkmod isn't avaible).
Please, help me, this phone it's terrible with all samsung customization!
Im pretty sure you can create an ODIN package.
I am not sure if the partitions are the same on SGS2 (dont own one yet) but take a look at this.
icezar1 said:
Im pretty sure you can create an ODIN package.
I am not sure if the partitions are the same on SGS2 (dont own one yet) but take a look at this.
Click to expand...
Click to collapse
Ok, i'll try now to pack my first worlwide rom!
kawa636r said:
I have done these works :
1. Removed full battery notification
2. Installed supercurio kernel
3. Removed touchwiz launcher (replaced with the stock gingerbread of the nexus s 9020)
4. Removed all Samsung stuff (unuseful) except voice commands and dlna.
Now i would share this with all the comunity, but how i can do this ?
(i can't do a nandroid backup because clockworkmod isn't avaible).
Please, help me, this phone it's terrible with all samsung customization!
Click to expand...
Click to collapse
thanks man
does the removal of the samsung bloatware resolve the android os battery issue>
winwiz said:
thanks man
does the removal of the samsung bloatware resolve the android os battery issue>
Click to expand...
Click to collapse
seems to be yes, because samsung apps stay forever in background.
I'm trying to take nexus s keyboard and port to s2, but where are keyboard files located?
****URGENT****
When trying to make odin flashable image, i have this error after these commands :
# su
# mount -o remount,rw /dev/block/stl9 /system
# dd if=/dev/block/stl9 of=/sdcard/factoryfs.rfs bs=4096
/dev/block/stl9: cannot open for read: No such file or directory
I have followed http://forum.xda-developers.com/showthread.php?t=960946 but seems to be not good for S2. I think that /dev/memory addressing it's different.
Who can help me?
In shell type mount and see on what stl is mounted /system. I DONT OWN A SGS 2! If you don't have some basic linux knowledge and dont know how the phone works, don't do this! I'm really serious!
But if you wanna go ahead you will need to find out your mount points. Is vital!
How i can see on what stl is mounted system? there isn't an fstab file?
kawa636r said:
****URGENT****
When trying to make odin flashable image, i have this error after these commands :
# su
# mount -o remount,rw /dev/block/stl9 /system
# dd if=/dev/block/stl9 of=/sdcard/factoryfs.rfs bs=4096
/dev/block/stl9: cannot open for read: No such file or directory
I have followed http://forum.xda-developers.com/showthread.php?t=960946 but seems to be not good for S2. I think that /dev/memory addressing it's different.
Who can help me?
Click to expand...
Click to collapse
SGS2 has different mount points. I see mention of RFS as well, which is wrong for the SGS2...
# mount
rootfs / rootfs rw,relatime 0 0
tmpfs /dev tmpfs rw,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/usb tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /app-cache tmpfs rw,relatime,size=7168k 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mmcblk0p9 /system ext4 rw,relatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p7 /cache ext4 rw,nosuid,nodev,noatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p1 /efs ext4 rw,nosuid,nodev,noatime,barrier=1,data=ordered 0 0
nil /sys/kernel/debug debugfs rw,relatime 0 0
/dev/block/mmcblk0p10 /data ext4 rw,nosuid,nodev,noatime,barrier=1,data=ordered,noauto_da_alloc,discard 0 0
/dev/block/mmcblk0p4 /mnt/.lfs j4fs rw,relatime 0 0
/dev/block/vold/179:11 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro,discard 0 0
Somebody can help me for the commands that i must do for creating a ROM?
kawa636r said:
Somebody can help me for the commands that i must do for creating a ROM?
Click to expand...
Click to collapse
Not got an SGS 2. Also, I hate working on ROMs from a dump of the device to be perfectly frank...
pulser_g2 said:
Not got an SGS 2. Also, I hate working on ROMs from a dump of the device to be perfectly frank...
Click to expand...
Click to collapse
from my response of mount command you can't help me?
kawa636r said:
from my response of mount command you can't help me?
Click to expand...
Click to collapse
Nope, sorry. I need the device to figure it out really, as I've not worked with a Samsung before. And I don't know about repackaging a ROM into a tar for ODIN based on a dump.
I wouldn't want to try and help either, as I need the device to actually check it properly, and wouldn't want you or someone else to have to try reflashing after messing something up...
Never looked at using a dump before - I prefer to take the stock ROM and modify it on my PC tbh
pulser_g2 said:
Never looked at using a dump before - I prefer to take the stock ROM and modify it on my PC tbh
Click to expand...
Click to collapse
Yes, but stock rom come with odin files format.
If i want to cook a rom i must start from sources, from a system dump, or from a zip rom (in nexus s i remember that rom are packaged in zip)....
Me too
I have the same problem, do you have find a solution?
I don't want to ruin your mojo, the more people interested in android, the better... but I'm a bit worried if inexperienced people give other inexperienced people things to flash with Odin. Since your ROM doesn't bring anything new (all other roms have this already), why not put some more time in it, polish it a bit, and maybe you will get some original ideas to add to it, instead of rushing it like this, and possibly brick some phones?
The probleme is that i have no time to do this, i have created a system and i have modivied the cyanogenmod to work with this system, the probleme is that i should to find a better methode to install the cyanogenmod rom from a pc, it is not for me is for other simple users.
Hi all
I have in my hands a Samsung YP G70 with this problem: I need to format it, clean it COMPLETELY.
I tried the following things:
1-Using the stock recovery, clean data and cache
2-Flash via Odin (different processes): his original firmware (same version), another firmware, a Kernel that should included the CWM Recovery
3-Root with Kingo
4-Tried to flash the TWRP flashable version into his stock recovery
5-Restore at factory default from the player
No one worked
After the reboot I will always have the same data (same accounts, same photos, same apps)
If I add a file, after a reboot, the file disappear; if I delete a file, after a reboot, the file re-appear.
So: how can I completely clean it? Or should I trash cause the memory allocator gone crazy?
Thanks a lot
GeniusJack said:
Hi all
I have in my hands a Samsung YP G70 with this problem: I need to format it, clean it COMPLETELY.
I tried the following things:
1-Using the stock recovery, clean data and cache
2-Flash via Odin (different processes): his original firmware (same version), another firmware, a Kernel that should included the CWM Recovery
3-Root with Kingo
4-Tried to flash the TWRP flashable version into his stock recovery
5-Restore at factory default from the player
No one worked
After the reboot I will always have the same data (same accounts, same photos, same apps)
If I add a file, after a reboot, the file disappear; if I delete a file, after a reboot, the file re-appear.
So: how can I completely clean it? Or should I trash cause the memory allocator gone crazy?
Thanks a lot
Click to expand...
Click to collapse
Please post the output of "mount" after a normal boot ( not in recovery )
You can do this in adb by doing:
adb shell
su
mount
or in a terminal app
su
mount
Then copy the output here or a screenshot with the info is fine...
$ su
su: not found
$ mount
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mmcblk0p13 /system rfs ro,relatime,vfat,log_off,check=no,gid/uid/rwx,
iocharset=utf8 0 0
/dev/block/mmcblk0p10 /efs rfs rw,nosuid,nodev,relatime,vfat,llw,check=no,gid/ui
d/rwx,iocharset=utf8 0 0
/dev/block/mmcblk0p16 /data rfs rw,nosuid,nodev,relatime,vfat,llw,check=no,gid/u
id/rwx,iocharset=utf8 0 0
/dev/block/mmcblk0p14 /dbdata rfs rw,nosuid,nodev,relatime,vfat,llw,check=no,gid
/uid/rwx,iocharset=utf8 0 0
/dev/block/mmcblk0p15 /cache rfs rw,nosuid,nodev,relatime,vfat,llw,check=no,gid/
uid/rwx,iocharset=utf8 0 0
/dev/block/mmcblk0p9 /mnt/.lfs j4fs rw,relatime 0 0
/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0
/dev/block/vold/259:9 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,noatime,no
diratime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437
,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
Is it ok?
GeniusJack said:
$ ...
Click to expand...
Click to collapse
If you have the USA variant try flashing this with Odin:
http://www.4shared.com/zip/hFJmoXTiba/YP-G70-UEKI8-Stock-USA-Meticul.html?
Flashed via Odin3 v1.87 into PDA but after the reboot I have the same data as before, so not worked...
GeniusJack said:
Flashed via Odin3 v1.87 into PDA but after the reboot I have the same data as before, so not worked...
Click to expand...
Click to collapse
Hmm.. Not sure whats goin' on.... When did this start???
I really don't know
A friend gave it to me asking for a check because he noticed that when installed an application, after a reboot the app disappears.. He thought about a virus so he asked to clean it...
GeniusJack said:
I really don't know
A friend gave it to me asking for a check because he noticed that when installed an application, after a reboot the app disappears.. He thought about a virus so he asked to clean it...
Click to expand...
Click to collapse
You could try the "getto lagfix":
This converts your file systems from rfs to ext4...
It's been a long time since I messed with stock GB so read and understand carefully before attempting...
http://forum.xda-developers.com/showthread.php?t=1445840&page=9
But I don't have a CWM, everything is stock, without root etc...
GeniusJack said:
But I don't have a CWM, everything is stock, without root etc...
Click to expand...
Click to collapse
So even if you flash a kernel it does not change?
Nope... Tried but not works... Same kernel after the reboot from Odin
GeniusJack said:
Nope... Tried but not works... Same kernel after the reboot from Odin
Click to expand...
Click to collapse
Seems like a hardware issue. Check dmesg/kmsg for errors...
Noob question coming.....
How?