FLASH STOCK ROM then overcome kernel 3.1.0
it works
Sent from my GT-I9100 using XDA App
serious , how you make it work ? ?
Edit : i was kidding with ya ... perhaps , i don't know what i say ..
compare eur jq1 initramfs with jp8 just little different
it just works
Sent from my GT-I9100 using XDA App
owh that is so new !!!!!!
screen capture
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
we need "Microscope" to look at it .. btw what you posted is not new !!!! perhaps for some other ppl ...
simple howto - no guarantee. try at your own risks
Get P1000ZTJP8 ## http://www.samfirmware.com/WEBPROTECT-p1000.htm
Unrar the file downloaded and get the gt-p1000_mr.pit and P1000ZTJP8_P1000ZTJP5_P1000BRIJP8_HOME.tar inside
flash stock rom with re-partition using Odin3 (repeat once more if you install http://forum.xda-developers.com/showthread.php?t=1074759 Overcome ROM v2.0.1 Hermes before to make it really clean)
download Overcome Kernel V3.1.0 http://overcome.mimzo.com/wp-content/plugins/download-monitor/download.php?id=4
Heimdall flash the zImage inside. Be patient but there are some voice telling you the progress and it can take few minutes
Cons:
Try at your own risks and no guarantee
As expected most Overcome features will not work
Pros:
Has Superuser
Quandrant rating is 1567
ext4 mount
Code:
$ mount
rootfs / rootfs ro,relatime 0 0
proc /proc proc rw,relatime 0 0
sys /sys sysfs rw,relatime 0 0
/dev/block/stl9 /system ext4 ro,relatime,barrier=0,data=writeback,noauto_da_alloc 0 0
/dev/block/stl11 /cache ext4 rw,noatime,barrier=0,data=writeback,noauto_da_alloc 0 0
/dev/block/stl10 /dbdata ext4 rw,noatime,barrier=0,nodelalloc,data=ordered,noauto_da_alloc 0 0
/dev/block/mmcblk0p2 /data ext4 rw,noatime,barrier=1,data=ordered,noauto_da_alloc 0 0
tmpfs /dev tmpfs rw,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
/dev/block/stl6 /mnt/.lfs j4fs rw,relatime 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 /app-cache tmpfs rw,relatime,size=12288k 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mmcblk0p3 /preload vfat ro,nodev,noatime,nodiratime,fmask=0133,dmask=0022,codepage=cp437,
iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/stl3 /efs rfs rw,nosuid,nodev,relatime,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0
/dev/block/vold/179:1 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,uid=1000,gi
d=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf
8,errors=remount-ro 0 0
/dev/block/vold/179:9 /mnt/sdcard/external_sd vfat rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime
,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortna
me=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:9 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,uid=10
00,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixe
d,utf8,errors=remount-ro 0 0
tmpfs /mnt/sdcard/external_sd/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
some hard work . really
Related
Taken from http://forums.hardwarezone.com.sg/showthread.php?t=2806456
For those that do not want to download Kies, here is the driver. I did not try others except I know it works on Win7 x64
http://db.tt/ErGVyE
deckcard said:
Galaxy S Meminfo
Code:
MemTotal: 333416 kB
MemFree: 28220 kB
Buffers: 5700 kB
Cached: 112080 kB
SwapCached: 0 kB
Active: 92292 kB
Inactive: 165804 kB
Active(anon): 48956 kB
Inactive(anon): 92160 kB
Active(file): 43336 kB
Inactive(file): 73644 kB
SwapTotal: 0 kB
SwapFree: 0 kB
Dirty: 4 kB
Writeback: 0 kB
AnonPages: 140336 kB
Mapped: 55228 kB
Slab: 13220 kB
SReclaimable: 3240 kB
SUnreclaim: 9980 kB
PageTables: 11976 kB
NFS_Unstable: 0 kB
Bounce: 0 kB
WritebackTmp: 0 kB
CommitLimit: 166708 kB
Committed_AS: 7187348 kB
VmallocTotal: 286720 kB
VmallocUsed: 78580 kB
VmallocChunk: 154628 kB
Click to expand...
Click to collapse
deckcard said:
Galaxy S mountpoints
Code:
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 rw,vfat,llw,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/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
Click to expand...
Click to collapse
/dev/block/stl9 /system rfs rw,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8
huh !?!?! /system mount in rw mode ? does this mean that no need to root?
worldicez said:
/dev/block/stl9 /system rfs rw,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8
huh !?!?! /system mount in rw mode ? does this mean that no need to root?
Click to expand...
Click to collapse
born to be RW !? wow!
That link just tells me they don't have a revision history for the file?
If I use the original link, I just don't see how where I get an actual download link!?!?
Please help
some mirrors:
http://www.multiupload.com/A3VUGCKIIJ
u can find the drivers here:
http://forums.hardwarezone.com.sg/showthread.php?t=2812085
hmmm.. or you can extract the contents of the latest Kies application from the Samsung website using 7zip and save it on your computer.
..check the folders and you will see there a folder which contains the "USB driver".. copy that folder and save it someone.. as for the rest you can safely delete them.
.. that is what I did before.. Kies is to laggy for me and takes a long time to respond/load.. "drag and drop" works wonders for me.
**note: you must enable "show hidden.." from folder options so that you will be able to see the Appdata.. haven't tried directly typing on the adrress bar the direct location.. "C:\Users\<user account name>\AppData\Local\Temp\Samsung\"..
**oh yeah.. this is for Windows 7.. should be the same for Vista i guess.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
SAMSUNG_USB_Driver_for_Mobile_Phones_v1.3.1600.0.exe
http://www.multiupload.com/ZQIEJHSRSI
this is from the samsung kies_win.exe package released on 2010/11/11
works with Win7 x64
Thank you, fixed my [nearly] bricked Captivate!
My brother and I are curious as to what is up with the File System in these phones involving the internal Memory and SD Card. He has a different GS and his file system is soo much stranger. However I'm more interested in how this Fascinate works
It claims 2gb internal memory But where in the file system is this internal memory? Where is the A2SD Memory? Where is all this stuff, say in like Root Explorer?
Here's a screen shot of the Fascinate with a 8gb SD Card
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
It shows the SD Card, which I get that, in Root Explorer its /sdcard/. However where is the 191mb that is completely empty of A2SD? Where is the 1.53gb of Internal Storage?
I know on my Inc, Internal memory is /emmc/ and sd is /sdcard/
Not one person on this forum knows how this phones file system is setup?
Its RFS file system, voodoo converts it to ext4. Apparently ext4 is more efficient/effective, specifically write operations. I'm no programmer so that's the extent of my knowledge.
Sent from my SCH-I500
nFiniti said:
It shows the SD Card, which I get that, in Root Explorer its /sdcard/. However where is the 191mb that is completely empty of A2SD? Where is the 1.53gb of Internal Storage?
Click to expand...
Click to collapse
I think Internal storage is /data, System storage is /system, System cache is /cache, and A2SD storage is /mnt/asec.
skreeves said:
I think Internal storage is /data, System storage is /system, System cache is /cache, and A2SD storage is /mnt/asec.
Click to expand...
Click to collapse
Thanks. Stupid Verizon claiming 2gb internal storage but there isn't any real internal storage. You must have a SD Card to do anything on the phone.
mrodsunshine said:
Its RFS file system, voodoo converts it to ext4. Apparently ext4 is more efficient/effective, specifically write operations. I'm no programmer so that's the extent of my knowledge.
Sent from my SCH-I500
Click to expand...
Click to collapse
Its slower, but more efficient and safer. But not what I was asking. I was asking for some kinda Diagram of the Storage Locations and what not like
IE: /mnt/sdcard = External SD Card.
No, there is internal storage. Take your microSD out and see if it still works... It might be an internal permanent SD card for all I know but it's there. Some of the other Galaxy S phones have both internal 16GB SD and an empty slot though which would have been nice to have.
I'm pretty sure RFS is not safer and definitely not more efficient... but by the way, most mount points are on the internal storage. Only /mnt/sdcard is on the sd card (big surprise).
If you want exact mount points for everything, run mount in a terminal emulator.
nFiniti said:
Thanks. Stupid Verizon claiming 2gb internal storage but there isn't any real internal storage. You must have a SD Card to do anything on the phone.
Click to expand...
Click to collapse
Yeah. There totally is internal storage. It's 2GB NAND flash storage. Totally not removeable.
Sent from my SCH-I500 using XDA App
here is eb16 with voodoo:
Code:
# mount
rootfs / rootfs rw 0 0
proc /proc proc rw,relatime 0 0
sys /sys sysfs rw,relatime 0 0
/dev/block/stl9 /system ext4 rw,noatime,barrier=0,data=writeback,noauto_da_alloc 0 0
/dev/block/stl11 /cache ext4 rw,noatime,barrier=0,data=writeback,noauto_da_alloc 0 0
/dev/block/stl10 /dbdata ext4 rw,noatime,barrier=0,nodelalloc,data=ordered,noauto_da_alloc 0 0
/dev/block/mmcblk0p1 /data ext4 rw,noatime,barrier=1,data=ordered,noauto_da_alloc 0 0
tmpfs /dev tmpfs rw,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
/dev/block/stl6 /mnt/.lfs j4fs rw,relatime 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /sqlite_stmt_journals tmpfs rw,relatime,size=4096k 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mmcblk0p2 /data/fota rfs rw,nosuid,nodev,relatime,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0
/dev/block/mmcblk0p3 /preinstall rfs rw,nosuid,nodev,relatime,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0
/dev/block/vold/179:9 /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 0 0
/dev/block/vold/179:9 /mnt/secure/asec 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 0 0
tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
nFiniti said:
Thanks. Stupid Verizon claiming 2gb internal storage but there isn't any real internal storage. You must have a SD Card to do anything on the phone.
Click to expand...
Click to collapse
If there wasn't any internal storage, where would everything be stored? Can't store apps on the SD card on 2.1...
Yeah I was testing out Dharam's battery saver rom but when I go to restore data from cwm it says unable to mount stl7 and here is what i get when i do adb shell mount
rootfs / rootfs rw 0 0
proc /proc proc rw,relatime 0 0
sys /sys sysfs rw,relatime 0 0
tmpfs /dev tmpfs rw,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 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/stl6 /system rfs ro,nodev,noatime,nodiratime,vfat,log_off,check=no,gi
d/uid/rwx,iocharset=cp437 0 0
/dev/block/stl7 /data rfs rw,nosuid,nodev,noatime,nodiratime,vfat,llw,check=no,g
id/uid/rwx,iocharset=cp437 0 0
/dev/block/stl8 /cache rfs rw,nosuid,nodev,noatime,nodiratime,vfat,llw,check=no,
gid/uid/rwx,iocharset=cp437 0 0
/dev/block/stl4 /efs rfs rw,nosuid,nodev,relatime,vfat,llw,check=no,gid/uid/rwx,
iocharset=cp437 0 0
/dev/block/vold/179:1 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,u
id=1000,gid=1015,fmask=0002,dmask=0002,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,relat
ime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,ioch
arset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
EDIT: I see that when i go to the mount and storage menu in CWM it says
E: can't mount /dev/block/stl7
(invalid argument)
Error mounting DATA:!
E: can't mount /dev/block/stl7
(invalid argument)
Error mounting DATA:!
I tried reflashing cwm and everything but still nothing :S
Thanks in advance
Galaxy Tab 10.1 GT-P7510 32GB, stock, not yet rooted
kernel: #1 SMP PREEMPT Mon Jun 6 08:59:10 KST 2011
PDA: KF3, phone: KF3; CSC: KF3 (XAB)
Starting down the path to root the phone, I encounter an issue that I haven't seen on the fora.
If I boot to recovery, I get to menu about "reboot system now", "apply update from /sdcard" and so on, but if I pick "apply update from /sdcard" it can't find what I've put in /sdcard. I get an error "E: unknown volume for path [/sdcard]".
While in this recovery state, if I adb shell, do "mount", I see that nothing is mounted on /mnt/sdcard:
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,nosuid,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
tmpfs /tmp tmpfs rw,relatime 0 0
/dev/block/mmcblk0p4 /system ext4 rw,relatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p5 /cache ext4 rw,nodev,noatime,nodiratime,barrier=1,data=ordered 0 0
In normal running state, if I adb shell "mount" I get:
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,nosuid,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
debugfs /sys/kernel/debug debugfs 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/mmcblk0p4 /system ext4 ro,relatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p5 /cache ext4 rw,nosuid,nodev,noatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p8 /data 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
/dev/fuse /mnt/sdcard fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
I'm quite surprised that /mnt/sdcard is not mounted in a mode where it's supposed to be able to do update.zip things from there.
Am I being stupid? (No surprise if that turns out to be the case.)
--bogoid
I am having the exact same issue with my Galaxy Tab 10.1. Anyone help would be greatly appreciated.
Adam
Ditto - have you guys found a fix yet?
Good Day. This is a known issue with the Retail Boatloaders.
If and only if your Devices is Unlocked (padlock at the bottom of the screen during regular boot up is evidence of an unlocked device) you can use the attached thread to flash a IO boatloader then a CWM compatible one and then root.
http://forum.xda-developers.com/showthread.php?t=1130574
For other questions take a walk over to the Development thread.
PLEASE READ COMPLETELY BEFORE TRYING ANYTHING
msm903 said:
Good Day. This is a known issue with the Retail Boatloaders.
If and only if your Devices is Unlocked (padlock at the bottom of the screen during regular boot up is evidence of an unlocked device) you can use the attached thread to flash a IO boatloader then a CWM compatible one and then root.
http://forum.xda-developers.com/showthread.php?t=1130574
For other questions take a walk over to the Development thread.
PLEASE READ COMPLETELY BEFORE TRYING ANYTHING
Click to expand...
Click to collapse
That did the trick! Thank you!
I am rooted (finally) and am trying to flash custom recovery and then ROM to my phone. Whenever I reboot after flashing, my phone starts the reboot process, but never gets past the LG screen (it is not bricked as I can take battery out and reboot it normally after the attempts). It will never actually fully reboot and make the change.
mount | grep system gives me this:
/dev/block/mmcblk0p14 /system ext4 rw,relatime,barrier=1,data=ordered 0 0
and then cat /proc/mounts gives me this:
rootfs / rootfs ro,noatime 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/extasec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/extobb tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mmcblk0p14 /system ext4 rw,relatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p21 /data ext4 rw,nosuid,nodev,noatime,errors=continue,barrier=1,data=ordered,noauto_da_alloc 0 0
/dev/block/mmcblk0p15 /persist ext4 rw,nosuid,nodev,relatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p16 /cache ext4 rw,nosuid,nodev,relatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p18 /drm ext4 rw,nosuid,nodev,relatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p22 /mpt ext4 rw,nosuid,nodev,relatime,barrier=1,data=ordered 0 0
/dev/block/vold/179:20 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859
-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:20 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0002,dmask=0002,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/imoblife.toolbox.full-1 vfat ro,dirsync,nosuid,nodev,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.s0up.goomanager-1 vfat ro,dirsync,nosuid,nodev,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.grindrapp.android-1 vfat ro,dirsync,nosuid,nodev,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.koushikdutta.rommanager-1 vfat ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=
remount-ro 0 0
/dev/block/dm-4 /mnt/asec/cm.aptoide.pt-1 vfat ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=
remount-ro 0 0
/dev/block/dm-5 /mnt/asec/de.mkrtchyan.recoverytools-1 vfat ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=
remount-ro 0 0
/dev/block/dm-6 /mnt/asec/com.siriusapplications.quickboot-1 vfat ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=
remount-ro 0 0
/dev/block/dm-7 /mnt/asec/com.pandora.android-1 vfat ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=
remount-ro 0 0
/dev/block/dm-8 /mnt/asec/com.cgollner.flashify-1 vfat ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=
remount-ro 0 0
/dev/block/dm-9 /mnt/asec/com.jrummy.root.browserfree-1 vfat ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=
remount-ro 0 0
#
anyone have any insight? is it just that the root filesystem is read only? the help would be greatly appreciated!
wmt9905 said:
I am rooted (finally) and am trying to flash custom recovery and then ROM to my phone. Whenever I reboot after flashing, my phone starts the reboot process, but never gets past the LG screen (it is not bricked as I can take battery out and reboot it normally after the attempts). It will never actually fully reboot and make the change.
mount | grep system gives me this:
/dev/block/mmcblk0p14 /system ext4 rw,relatime,barrier=1,data=ordered 0 0
and then cat /proc/mounts gives me this:
rootfs / rootfs ro,noatime 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/extasec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/extobb tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mmcblk0p14 /system ext4 rw,relatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p21 /data ext4 rw,nosuid,nodev,noatime,errors=continue,barrier=1,data=ordered,noauto_da_alloc 0 0
/dev/block/mmcblk0p15 /persist ext4 rw,nosuid,nodev,relatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p16 /cache ext4 rw,nosuid,nodev,relatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p18 /drm ext4 rw,nosuid,nodev,relatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p22 /mpt ext4 rw,nosuid,nodev,relatime,barrier=1,data=ordered 0 0
/dev/block/vold/179:20 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859
-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:20 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0002,dmask=0002,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/imoblife.toolbox.full-1 vfat ro,dirsync,nosuid,nodev,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.s0up.goomanager-1 vfat ro,dirsync,nosuid,nodev,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.grindrapp.android-1 vfat ro,dirsync,nosuid,nodev,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.koushikdutta.rommanager-1 vfat ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=
remount-ro 0 0
/dev/block/dm-4 /mnt/asec/cm.aptoide.pt-1 vfat ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=
remount-ro 0 0
/dev/block/dm-5 /mnt/asec/de.mkrtchyan.recoverytools-1 vfat ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=
remount-ro 0 0
/dev/block/dm-6 /mnt/asec/com.siriusapplications.quickboot-1 vfat ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=
remount-ro 0 0
/dev/block/dm-7 /mnt/asec/com.pandora.android-1 vfat ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=
remount-ro 0 0
/dev/block/dm-8 /mnt/asec/com.cgollner.flashify-1 vfat ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=
remount-ro 0 0
/dev/block/dm-9 /mnt/asec/com.jrummy.root.browserfree-1 vfat ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=
remount-ro 0 0
#
anyone have any insight? is it just that the root filesystem is read only? the help would be greatly appreciated!
Click to expand...
Click to collapse
I didn't read your whole post...but i think i can help u...just do kdg first....it will flash firmware to ur l3..so that u can use ur phone again..then root it and then install rom manager from playstore,there u will find an option of flashing recovery to l3...its the most safest method...any problem,pm me:thumbup:
Sent from my LG-E400 using Tapatalk 2
aroop mishra said:
I didn't read your whole post...but i think i can help u...just do kdg first....it will flash firmware to ur l3..so that u can use ur phone again..then root it and then install rom manager from playstore,there u will find an option of flashing recovery to l3...its the most safest method...any problem,pm me:thumbup:
Sent from my LG-E400 using Tapatalk 2
Click to expand...
Click to collapse
I was never not able to use my phone. I've tried ROM Manager to flash. The flashing isn't the problem. It's getting my to hold on to it because it never fully boots after flashing.