[Q] First Rom ready! How i can upload it? - Galaxy S II Q&A, Help & Troubleshooting

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.

Related

[Q] Wrong Partition Type

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...

[Q] change internal memory and adb logcat

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.

Online Android Backup **DO BACKUP WHILE YOUR PHONE STILL ON**

ANNOUNCEMENT:
Official version that support most (including our) device has been released. See HERE
Hi All.
Here are the modified version of Online Android Backup from ORIGINAL THREAD. I've changed some codes to make it works for our HTC Legend.
How To Install:
Through CWM
1. Download from attachment onandroidv3.7_cwm.zip
2. Copy it to your sdcard
3. Reboot into recovery
4. Flash the file
Manual
1. Extract onandroid.zip attached and use adb/root explorer to push/copy the file onandroid to your /system/bin
2. change permission to rwxr-xr-x
How To use:
From PC:
1. Open terminal/command prompt
2. type adb shell
- if using CM9, type su to gain root access after step 2.
3. type onandroid
From your phone:
1. open terminal emulator, type su
2. type onandroid
UPDATE:
If you use ogo2's ROM HERE, please download SENSE_fix_tool.zip from attachment and flash it. Mediafire link are HERE
Changes:
12.06.2012: Initial modification from original version
13.06.2012: Power checking corrected
14.06.2012: Added CWM flashable file
20.06.2012: Update v3.7 from original developer. confirm to work in cm9
Changelogs from original developer:
:: Latest onandroid fixes from v3.7
:: Made "dd" not spit results.
:: Added partition detection for boot and recovery partitions.
02.07.2012: Fix for sense ROM
screenshots and file are attached.
Credits:
ameer1234567890 Original Developer
good morning my friend. is it possible to install this using the method described in original thread ?
1. Download and copy zip file to SD card
2. Reboot into recovery
3. Choose install zip from SD card, select zip and flash .
4. Reboot!
congruts on your work!
vriz27 said:
good morning my friend. is it possible to install this using the method described in original thread ?
1. Download and copy zip file to SD card
2. Reboot into recovery
3. Choose install zip from SD card, select zip and flash .
4. Reboot!
congruts on your work!
Click to expand...
Click to collapse
Yes, download the file from attachment (onandroid_CWM.zip)
This is absolutely great! Used this to do a nandroid backup while charging, saves sooo much time Haven't tried restoring yet but I'm sure it'll work.
smithchipz said:
This is absolutely great! Used this to do a nandroid backup while charging, saves sooo much time Haven't tried restoring yet but I'm sure it'll work.
Click to expand...
Click to collapse
Thanks. I just do some simple modification to the original version, praise to ameer1234567890 for the great tools.
Restoring is working fine with me but make sure you check the backup folder after onandroid is finish running and check if all required files is there especially if you do something else during the backup process.
Fix for sense ROM attached in 1st post.
feed3 said:
Fix for sense ROM attached in 1st post.
Click to expand...
Click to collapse
Hello,
when I try to Download it, I only get
404 - Not Found ,
can you check your upload again?
alligator_asl said:
Hello,
when I try to Download it, I only get
404 - Not Found ,
can you check your upload again?
Click to expand...
Click to collapse
That is due to an issue in XDA (one of the servers crashed). Should be fixed in a couple of days!
Sense fix
Sense fix tool uploaded to mediafire. Link in the post #1.
Hello,
I can confirm, that onandroid works now with a sense rom, but it did'nt find the sd-ext-partition.
Here is the output from "busybox mount":
Code:
# busybox mount
busybox mount
rootfs on / type rootfs (ro,relatime)
tmpfs on /dev type tmpfs (rw,relatime,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
none on /acct type cgroup (rw,relatime,cpuacct)
tmpfs on /mnt/asec type tmpfs (rw,relatime,mode=755,gid=1000)
none on /dev/cpuctl type cgroup (rw,relatime,cpu)
/dev/block/mtdblock3 on /system type yaffs2 (ro,relatime)
/dev/block/mtdblock5 on /data type yaffs2 (rw,nosuid,nodev,noatime,nodiratime)
/dev/block/mtdblock4 on /cache type yaffs2 (rw,nosuid,nodev,noatime,nodiratime)
/dev/block/mmcblk0p2 on /mnt/asec/sd type ext3 (rw,nodev,noatime,nodiratime,errors=continue,commit=30,nobh,data=writeback)
/dev/block/vold/179:1 on /mnt/sdcard type 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)
/dev/block/vold/179:1 on /mnt/secure/asec type 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)
tmpfs on /mnt/sdcard/.android_secure type tmpfs (ro,relatime,size=0k,mode=000)
/dev/block/dm-0 on /mnt/asec/com.quoord.tapatalkxda.activity-1 type vfat (ro,dirsync,nosuid,nodev,noexec,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
/dev/block/dm-1 on /mnt/asec/nadsoft.physicscheatsheetsfree-1 type vfat (ro,dirsync,nosuid,nodev,noexec,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
/dev/block/dm-2 on /mnt/asec/jwtc.android.chess-1 type vfat (ro,dirsync,nosuid,nodev,noexec,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
#
alligator_asl said:
Hello,
I can confirm, that onandroid works now with a sense rom, but it did'nt find the sd-ext-partition.
Click to expand...
Click to collapse
Can you post a screenshot or a log (copy and paste text) from terminal emulator, of the below commands:
Code:
mount
ameer1234567890 said:
Can you post a screenshot or a log (copy and paste text) from terminal emulator, of the below commands:
Code:
mount
Click to expand...
Click to collapse
Here is it:
Code:
# mount
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
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mtdblock3 /system yaffs2 ro,relatime 0 0
/dev/block/mtdblock5 /data yaffs2 rw,nosuid,nodev,noatime,nodiratime 0 0
/dev/block/mtdblock4 /cache yaffs2 rw,nosuid,nodev,noatime,nodiratime 0 0
/dev/block/mmcblk0p2 /mnt/asec/sd ext3 rw,nodev,noatime,nodiratime,errors=continue,commit=30,nobh,data=writeback 0 0
/dev/block/vold/179:1 /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:1 /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.quoord.tapatalkxda.activity-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/nadsoft.physicscheatsheetsfree-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-2 /mnt/asec/jwtc.android.chess-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
#
How did you partition your sdcard? Which app2sd or link2sd version do you use?
Also, post output from below command!
Code:
echo $SD_EXT_DIREECTORY
I formated my sdcard according this guide http://forum.xda-developers.com/showthread.php?t=907436 with a fat32- and a ext3-partition.
I use the a2sd-script, which is integrated in this rom http://forum.xda-developers.com/showthread.php?t=866849 .
And there is no output:
Code:
# echo $SD_EXT_DIREECTORY
echo $SD_EXT_DIREECTORY
# echo $SD_EXT_DIRECTORY
echo $SD_EXT_DIRECTORY
#
alligator_asl said:
I formated my sdcard according this guide http://forum.xda-developers.com/showthread.php?t=907436 with a fat32- and a ext3-partition.
I use the a2sd-script, which is integrated in this rom http://forum.xda-developers.com/showthread.php?t=866849 .
And there is no output:
Code:
# echo $SD_EXT_DIREECTORY
echo $SD_EXT_DIREECTORY
# echo $SD_EXT_DIRECTORY
echo $SD_EXT_DIRECTORY
#
Click to expand...
Click to collapse
Thank you for the information. I am working on a fix.
alligator_asl said:
Hello,
I can confirm, that onandroid works now with a sense rom, but it did'nt find the sd-ext-partition.
Here is the output from "busybox mount":
Code:
# busybox mount
busybox mount
rootfs on / type rootfs (ro,relatime)
tmpfs on /dev type tmpfs (rw,relatime,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
none on /acct type cgroup (rw,relatime,cpuacct)
tmpfs on /mnt/asec type tmpfs (rw,relatime,mode=755,gid=1000)
none on /dev/cpuctl type cgroup (rw,relatime,cpu)
/dev/block/mtdblock3 on /system type yaffs2 (ro,relatime)
/dev/block/mtdblock5 on /data type yaffs2 (rw,nosuid,nodev,noatime,nodiratime)
/dev/block/mtdblock4 on /cache type yaffs2 (rw,nosuid,nodev,noatime,nodiratime)
/dev/block/mmcblk0p2 on /mnt/asec/sd type ext3 (rw,nodev,noatime,nodiratime,errors=continue,commit=30,nobh,data=writeback)
/dev/block/vold/179:1 on /mnt/sdcard type 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)
/dev/block/vold/179:1 on /mnt/secure/asec type 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)
tmpfs on /mnt/sdcard/.android_secure type tmpfs (ro,relatime,size=0k,mode=000)
/dev/block/dm-0 on /mnt/asec/com.quoord.tapatalkxda.activity-1 type vfat (ro,dirsync,nosuid,nodev,noexec,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
/dev/block/dm-1 on /mnt/asec/nadsoft.physicscheatsheetsfree-1 type vfat (ro,dirsync,nosuid,nodev,noexec,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
/dev/block/dm-2 on /mnt/asec/jwtc.android.chess-1 type vfat (ro,dirsync,nosuid,nodev,noexec,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
#
Click to expand...
Click to collapse
Seldom using sense ROM so didn't realize that problem occur in sense as in other ROM (cm7,cm9,miui) it is just okay and i didn't have/use sd-ext anymore so can't help testing/troubleshooting on that.. Sorry..
feed3 said:
Seldom using sense ROM so didn't realize that problem occur in sense as in other ROM (cm7,cm9,miui) it is just okay and i didn't have/use sd-ext anymore so can't help testing/troubleshooting on that.. Sorry..
Click to expand...
Click to collapse
I have fixed this in the next version. Shall be releasing soon.
ameer1234567890 said:
I have fixed this in the next version. Shall be releasing soon.
Click to expand...
Click to collapse
Thanks ameer..

[Q] Unable to mount system to RW

Hi,
No matter what I do, I can't remount "/system" and "/" to RW. :crying:
Does anyone know how to resolve this issue?
I am running on KK 4.4.2 version 14.3.A.0.757.
My Current File System Status
[email protected]:/ # mount
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,seclabel,relatime,mode=600 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,seclabel,relatime 0 0
selinuxfs /sys/fs/selinux selinuxfs rw,relatime 0 0
debugfs /sys/kernel/debug debugfs rw,relatime 0 0
none /sys/fs/cgroup tmpfs rw,seclabel,relatime,mode=750,gid=1000 0 0
securityfs /sys/kernel/security securityfs rw,nosuid,nodev,noexec,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
tmpfs /tmp tmpfs rw,seclabel,nosuid,relatime,mode=755 0 0
/dev/block/platform/msm_sdcc.1/by-name/system /system ext4 ro,seclabel,relatime,discard,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/userdata /data ext4 rw,seclabel,nosuid,nodev,relatime,discard,noauto_da_alloc,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/cache /cache ext4 rw,seclabel,nosuid,nodev,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/apps_log /mnt/idd ext4 rw,seclabel,nosuid,nodev,noexec,noatime,discard,nobarrier,data=ordered 0 0
tmpfs /storage/remote tmpfs rw,seclabel,relatime,size=1024k,nr_inodes=256,mode=750,gid=1028 0 0
/dev/block/platform/msm_sdcc.1/by-name/LTALabel /lta-label ext4 ro,seclabel,nosuid,nodev,noexec,noatime,nobarrier,data=ordered 0 0
/dev/fuse /mnt/shell/emulated fuse rw,nosuid,nodev,noexec,relatime,user_id=1023,group_id=1023,default_permissions,allow_other,allow_utime_grp 0 0
/dev/fuse /storage/sdcard1 fuse rw,nosuid,nodev,noexec,relatime,user_id=1023,group_id=1023,default_permissions,allow_other,allow_utime_grp 0 0
tmpfs /storage/emulated tmpfs rw,seclabel,nosuid,nodev,relatime,mode=050,gid=1028 0 0
/dev/block/vold/179:65 /mnt/media_rw/sdcard1 vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1023,gid=1023,fmask=0007,dmask=0007,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/fuse /storage/emulated/0 fuse rw,nosuid,nodev,noexec,relatime,user_id=1023,group_id=1023,default_permissions,allow_other,allow_utime_grp 0 0
/dev/fuse /storage/emulated/0/Android/obb fuse rw,nosuid,nodev,noexec,relatime,user_id=1023,group_id=1023,default_permissions,allow_other,allow_utime_grp 0 0
/dev/fuse /storage/emulated/legacy fuse rw,nosuid,nodev,noexec,relatime,user_id=1023,group_id=1023,default_permissions,allow_other,allow_utime_grp 0 0
/dev/fuse /storage/emulated/legacy/Android/obb fuse rw,nosuid,nodev,noexec,relatime,user_id=1023,group_id=1023,default_permissions,allow_other,allow_utime_grp 0 0
[email protected]:/ #
You obviously do not have the permission to do that, so the question is, are you rooted, and if so root again and be sure to have the latest SuperSU installed with updated binaries.
Sent from my Z Ultra
LordManhattan said:
You obviously do not have the permission to do that, so the question is, are you rooted, and if so root again and be sure to have the latest SuperSU installed with updated binaries.
Sent from my Z Ultra
Click to expand...
Click to collapse
Yes, I am able to gain root access but unable to boot into recovery
Sent from my C6833 using XDA Premium 4 mobile app
[email protected] said:
Yes, I am able to gain root access but unable to boot into recovery
Sent from my C6833 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
What kernel are you on?
How did you get root?
Bootloader unlocked?
blueether said:
What kernel are you on?
How did you get root?
Bootloader unlocked?
Click to expand...
Click to collapse
My kernel version is 3.40-perf [email protected] #1 and bootloader is unlocked.
I gained root by downgrading my firmware to .532 version and install rooting using a program called Root_with_Restore_by_Bin4ry_v33. After rooting is successful, install dualrecovery and upgrade my firmware to .757 version by flashing a specific zip file via recovery followed by flash FTF with Flashtool.
Am I doing it correctly? Is there a better way to do it?
[email protected] said:
My kernel version is 3.40-perf [email protected] #1 and bootloader is unlocked.
I gained root by downgrading my firmware to .532 version and install rooting using a program called Root_with_Restore_by_Bin4ry_v33. After rooting is successful, install dualrecovery and upgrade my firmware to .757 version by flashing a specific zip file via recovery followed by flash FTF with Flashtool.
Am I doing it correctly? Is there a better way to do it?
Click to expand...
Click to collapse
I would try to reflash supersu and see if that fixes it
I'm not sure. I'm having the same issue, sort of. I can mount /system to read write easily but can't mount back to read only. Getting "resource busy" message. Running a 4.4.2 LG G2 ROM. Could it have anything to do with how /system is formatted within TWRP recovery? Idk.. Luckily not being able to mount as read only isn't exactly an issue but more of a nuisance.
Edit:: Found a solution minutes after posting.
Code:
su
mount -o remount,rw /system # works fine
mount -o remount,ro /system # resource busy error
mount -o remount ro /system # works fine without comma
With this knowledge I can go through and fix a few scripts that have the comma between remount and ro. Not sure why this is as it's always worked fine ever since my OG DROID.
Any updates ??
EvilMember said:
Any updates ??
Click to expand...
Click to collapse
Strange I'm using this rom: http://forum.xda-developers.com/xpe...14-4-0-118-t2859660/post56113642#post56113642
And I can't mount system to RW, had same issue before on stock but Super SU reflash fixed it...now no way to moint system to RW
MidnightHarvester said:
I'm not sure. I'm having the same issue, sort of. I can mount /system to read write easily but can't mount back to read only. Getting "resource busy" message. Running a 4.4.2 LG G2 ROM. Could it have anything to do with how /system is formatted within TWRP recovery? Idk.. Luckily not being able to mount as read only isn't exactly an issue but more of a nuisance.
Edit:: Found a solution minutes after posting.
Code:
su
mount -o remount,rw /system # works fine
mount -o remount,ro /system # resource busy error
mount -o remount ro /system # works fine without comma
With this knowledge I can go through and fix a few scripts that have the comma between remount and ro. Not sure why this is as it's always worked fine ever since my OG DROID.
Click to expand...
Click to collapse
FAIL:
this doing nothing.
mount -o remount ro /system
[email protected]:/ # mount | grep /system
mount | grep /system
/dev/block/platform/msm_sdcc.1/by-name/system on /system type ext4 (rw,noatime,nodiratime,noauto_da_alloc,data=ordered)
dmesg
<6>EXT4-fs (mmcblk0p30): re-mounted. Opts: (null)
kernel ignoring your command. problem is with some service open file for writing in /system and not letting go.
find the service! kill it, mount as RO.

YP G70 read only??

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?

Categories

Resources