So i followed the guide on how to unlock bootloader, flash twrp, all that stuff, and i try to flash the pixel experience rom then i get this error. I searched up some solutions, i found one that said to change the file system to ext4 but that didn't work so im out of ideas, hope someone here can help me with it.
just reboot to recovery from twrp
amrsy said:
So i followed the guide on how to unlock bootloader, flash twrp, all that stuff, and i try to flash the pixel experience rom then i get this error. I searched up some solutions, i found one that said to change the file system to ext4 but that didn't work so im out of ideas, hope someone here can help me with it.
Click to expand...
Click to collapse
Hi.
Did you fix it?
I've tried to install my first ROM on my Xiaomi MI5s but I did not get it.
I installed the TWRP and then followed the steps of installation in the Lineage website.
I tapped on "Format Data", but I found these messages:
"failed to mount data" and "device or resource busy".
Then I tried to reboot the device and go into TWRP again and it is not there anymore. Instead, it is the xiaomi recovery.
What am I doing wrong?
I have also tried to go to WIPE -> ADVANCED WIPE -> select 'DATA' -> REPAIR OR CHANGE FILESYSTEM -> CHANGE FILESYSTEM -> EXT4, but the same error
---------- Post added at 12:16 AM ---------- Previous post was at 12:15 AM ----------
febin92 said:
just reboot to recovery from twrp
Click to expand...
Click to collapse
Is that the solution?
I was getting issues like that when I was decrypting. I found that after every new step to reboot system.
For example.
Repair data, reboot system,
After format data, reboot system,
Then wipe data , reboot system,
Then do a restore, reboot system,
You need to remount as RW. This goes for Vendor/Data/System etc.
While in TWRP type:
Code:
adb shell
cat /proc/mounts
You will get something along these lines:
Code:
rootfs / rootfs rw,seclabel 0 0
tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,seclabel,relatime,mode=600 0 0
proc /proc proc rw,relatime,gid=3009,hidepid=2 0 0
sysfs /sys sysfs rw,seclabel,relatime 0 0
selinuxfs /sys/fs/selinux selinuxfs rw,relatime 0 0
tmpfs /mnt tmpfs rw,seclabel,nosuid,nodev,noexec,relatime,mode=755,gid=1000 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /tmp tmpfs rw,seclabel,relatime 0 0
none /config configfs rw,relatime 0 0
pstore /sys/fs/pstore pstore rw,seclabel,relatime 0 0
adb /dev/usb-ffs/adb functionfs rw,relatime 0 0
/dev/block/bootdevice/by-name/vendor_a /v ext4 ro,seclabel,relatime,block_validity,delalloc,barrier,user_xattr,errors=remount-ro 0 0
/dev/block/sda13 /data ext4 ro,seclabel,relatime,resgid=1065,stripe=2,data=ordered 0 0
/dev/block/sda13 /sdcard ext4 rw,seclabel,relatime,resgid=1065,stripe=2,data=ordered 0 0
In my case TWRP was saying:
Code:
TWRP failed to mount vendor device or resource busy
TWRP failed to mount data device or resource busy
Whatever your case is just remount the partition partition that's throwing errors as RW to fix the problem.
For example:
Code:
mount -o rw,remount /dev/block/bootdevice/by-name/vendor_a
mount -o rw,remount /dev/block/sda13
This remounted both vendor and data as RW and TWRP no longer gives errors. :good:
Related
Root Explorer is unable to re-mount /system in R/W. The button simply does nothing when I press it. I am also unable to update AdFree, which re-writes the hosts file in /system. Anything I can do to remedy this?
stupid question, but I have to ask: are you rooted?
o0beaner said:
Root Explorer is unable to re-mount /system in R/W. The button simply does nothing when I press it. I am also unable to update AdFree, which re-writes the hosts file in /system. Anything I can do to remedy this?
Click to expand...
Click to collapse
Try backing all the way out of the folder by pressing the (...) button at the top. Keep pressing that until you are at the root folder (it won't be there anymore). Now press the r/w button at the top. It should change, and will stay changed once you go back into the other folders.
Sorry, it was early, and my brain wasn't good for specifics. I am rooted, running SRE 1.2.
Root is mounted R/W, but /system will not change state. Is there anything I can try from the terminal?
Same problem here on my wife's Captivate. I used SRE 1.2.1a and noticed that I was still seeing ads. So I tried installing Adfree and updating the host file and ran into the same mounting error.
On my own Captivate, I had used 1-Click root before SRE came out and no problems updating there.
same here no ADFREE in SREv2b7. I tried R/W on Root explorer and even trying to change permissions on sys,system, data/data, and still get same error as you guys re-mount /system.
Let's see where /system is mounted:
Code:
C:\Program Files\android-sdk-windows\tools>adb shell
* daemon not running. starting it now *
* daemon started successfully *
$ mount
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
[COLOR="Red"]/dev/block/stl9 /system rfs rw,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0
[/COLOR]/dev/block/mmcblk0p2 /data rfs rw,nosuid,nodev,vfat,llw,check=no,gid/uid/rwx,ioc
harset=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/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
$
At this point, we can see that /system is mounted at /dev/block/stl9. With that knowledge:
Code:
$ su
# mount -o remount,rw /dev/block/stl9 /system
Now your free to do whatever it is you were trying to do. When you're done, don't forget to:
Code:
# mount -o remount,ro /dev/block/stl9 /system
# exit
$ exit
Thanx but that didnt work this are my setting
C:\AndroidSDK\tools>adb shell
$ mount
mount
rootfs / rootfs rw 0 0
proc /proc proc rw 0 0
sys /sys sysfs rw 0 0
/dev/block/mmcblk0p4 /data ext4 rw,barrier=1,data=ordered 0 0
tmpfs /dev tmpfs rw,mode=755 0 0
devpts /dev/pts devpts rw,mode=600 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/stl10 /dbdata rfs rw,nosuid,nodev,noatime,vfat,llw,check=no,gid/uid/r
wx,iocharset=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/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
$
IM STILL GETTING failed to remount system partition read-only
I can't update AdFree either.
shilob said:
Let's see where /system is mounted:
Code:
C:\Program Files\android-sdk-windows\tools>adb shell
* daemon not running. starting it now *
* daemon started successfully *
$ mount
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
[COLOR="Red"]/dev/block/stl9 /system rfs rw,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0
[/COLOR]/dev/block/mmcblk0p2 /data rfs rw,nosuid,nodev,vfat,llw,check=no,gid/uid/rwx,ioc
harset=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/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
$
At this point, we can see that /system is mounted at /dev/block/stl9. With that knowledge:
Code:
$ su
# mount -o remount,rw /dev/block/stl9 /system
Now your free to do whatever it is you were trying to do. When you're done, don't forget to:
Code:
# mount -o remount,ro /dev/block/stl9 /system
# exit
$ exit
Click to expand...
Click to collapse
Didn't work for me either--still got the "failed to mount read-only file system" or something like that. Also, when I tried the "-o remount,ro" adb said device or resource busy. I'm pretty sure this has been discussed in the SRE thread, but i really, really, want adree to work
Hey guys,
Here's a dump of /system from the Google I/O GT10.1. Let me know if there's anything else you're interested in.
http://www.mediafire.com/?hmjy4w04u9cb4j4
smaskell said:
Hey guys,
Here's a dump of /system from the Google I/O GT10.1. Let me know if there's anything else you're interested in.
http://www.mediafire.com/?hmjy4w04u9cb4j4
Click to expand...
Click to collapse
EDIT: Haha fail wasn't even thinking.....
Thanks mate. Can you dump boot and recovery as well? Not even sure if you can, but...
I could if I knew where they were. Someone more knowledgeable than I would probably know where they usually are. Unfortunately, I cannot search the device because most standard commands are not available(find, grep, etc.)
smaskell said:
I could if I knew where they were. Someone more knowledgeable than I would probably know where they usually are. Unfortunately, I cannot search the device because most standard commands are not available(find, grep, etc.)
Click to expand...
Click to collapse
Cool. Thanks.
Have you tried adding busybox? Im surprised that the root 'package' didn't include them. I think Titanium Backup will add it for you but not the symlinks AFAIK so you need to prefix each command with busybox. eg:
Code:
busybox chmod +x <file>
it won't let me create a link to /system/bin/ because it's stuck at read only. I created a thread about this already, but does anyone know how to remount /system? I've tried the standard ways and they don't seem to work
This worked for me:
mount -o remount,rw /system
If all else fails, use Root Explorer to remount /system
Just thinking "out loud" here, but would it be fair to say that if someone could extract the boot and recovery images from these google 10.1's that they could be flashed onto a 10.1v with Odin or fastboot and allow the 10.1v to be rooted in the same way as the 10.1g?
That's what I'm hoping
Sent from my GT-P7100 using XDA Premium App
ObsidianX said:
This worked for me:
mount -o remount,rw /system
Click to expand...
Click to collapse
wow, that was stupid of me. I was trying
mount -o remount,rw /dev/block/mmcblk0p4 /system
but obviously that isn't needed.
Thanks
alright, so I have busybox working
but all the tutorials I've found have said to use
cat /proc/mtd
to find out what to pull but for me, it just returns
dev: size erasesize name
also, they say to use
cat /dev/mtd/mtdX > /sdcard/mtdX.img
but /dev/mtd doesn't exist on this device
any ideas what I could be doing wrong?
smaskell said:
alright, so I have busybox working
but all the tutorials I've found have said to use
cat /proc/mtd
to find out what to pull but for me, it just returns
dev: size erasesize name
also, they say to use
cat /dev/mtd/mtdX > /sdcard/mtdX.img
but /dev/mtd doesn't exist on this device
any ideas what I could be doing wrong?
Click to expand...
Click to collapse
Stupid question, but you did do a
Code:
su
before running these commands?
Sometimes it's the simple things
it certainly wouldn't be the first time I'd missed something as blatantly obvious as that, but no I did remember this time. That's not to say that I'm not missing something else that should be completely obvious, but I did at least remember to run it as root.
smaskell said:
it certainly wouldn't be the first time I'd missed something as blatantly obvious as that, but no I did remember this time.
Click to expand...
Click to collapse
Haha - yeah, Ive certainly been stumped by simpler things than that. Usually success if followed by a facepalm
Really appreciate your persistence with this!
Could you possibly post the output of:
Code:
adb shell mount
and
Code:
adb shell su ls -l /cache
You should see from this output which device is mounted as /cache and how the /cache/recovery is mounted/linked.
certainly
Code:
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
Code:
drwxrwx--- root root 1969-12-31 16:00 lost+found
drwxrwx--- system cache 2011-05-11 23:38 recovery
in /cache/recovery/last_log, I see this(among other things)
Code:
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null) '(null)' 0000 '(null)' 0
1 /efs ext4 /dev/block/mmcblk0p1 (null) '(null)' 0000 '(null)' 0
2 /recovery emmc /dev/block/mmcblk0p2 (null) '(null)' 0000 '(null)' 0
3 /boot emmc /dev/block/mmcblk0p3 (null) '(null)' 0000 '(null)' 0
4 /system ext4 /dev/block/mmcblk0p4 (null) '(null)' 0000 '(null)' 0
5 /cache ext4 /dev/block/mmcblk0p5 (null) '(null)' 0000 '(null)' 0
6 /data ext4 /dev/block/mmcblk0p8 (null) '(null)' 0000 '(null)' -16384
I'll try pulling mmcblk0p2 and 3
Edit: here they are. Hopefully this is what you were looking for
or not.. I tried uploading twice and both times it appeared to succeed but they're not showing up. let's try again.
still not working. let's try mediafire
http://www.mediafire.com/file/r37q8vluzshkdu8/boot.img
http://www.mediafire.com/file/bhi4q2wrqgl2ms5/recovery.img
Fantastic! Thanks again.
Downloading now although I just discovered I have blown my 120Gb/month allowance in 14 days so it may take a while to download at 256k
EDIT: smaskell, you are truly a champ! Recovery works on the 10.1v so I now have root!
Will be posting a guide here and asking all to thank smaskell
http://forum.xda-developers.com/showthread.php?t=1079781
smaskell said:
or not.. I tried uploading twice and both times it appeared to succeed but they're not showing up. let's try again.
still not working. let's try mediafire
http://www.mediafire.com/file/r37q8vluzshkdu8/boot.img
http://www.mediafire.com/file/bhi4q2wrqgl2ms5/recovery.img
Click to expand...
Click to collapse
You need to zip them. XDA only accepts ZIPs and media files for upload. Only discovered this myself yesterday
excellent! just glad I could help =]
So I tried to disable Voodoo lagfix (from Voodoo app) and now I'm stuck in the boot screen. Somehow disabling lagfix in CWM isn't working either. I accidentally had my phone corded up to my PC and had internal memory propably mounted while I booted the phone and it tried to convert the filesystem. Not sure if mounting caused the problem.
Being in this situation, is it safe to flash stock rom with .PIT file in Odin while having lagfix enabled? What (I think) I'm trying to ask is does re-partition convert my filesystem back to RFS? If it doesn't work that way, what should I try next? Already backed up all necessary data and ready to wipe. I'm currently on Darky's 10.1 RE and thought about moving on to newer roms, first through stock rom.
I have limited experience in flashing roms. I've read numerous threads and seen one case in which flashing with .PIT file in Odin helped but I wish not to hesitate with this.
Thanks for reading.
EDIT: Here's my /proc/mounts:
Code:
adb shell cat /proc/mounts
rootfs / rootfs rw,relatime 0 0
proc /proc proc rw,relatime 0 0
sys /sys sysfs rw,relatime 0 0
/dev/block/stl11 /cache ext4 rw,noatime,barrier=0,data=writeback,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 /tmp tmpfs rw,relatime 0 0
/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0
/dev/block/mmcblk0p1 /sdcard vfat rw,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/stl9 /system rfs rw,relatime,vfat,llw,gid/uid/rwx,iocharset=utf8 0 0
/dev/block/mmcblk0p2 /data ext4 rw,noatime,barrier=1,data=ordered,noauto_da_alloc 0 0
/dev/block/stl10 /datadata ext4 rw,noatime,barrier=0,nodelalloc,data=ordered,noauto_da_alloc 0 0
Everytime I plug it to charger, missus Voodoo robot says "convert /data partition".
EDIT 2: Flashed with .PIT + repartition in Odin and the system boots great! It all worked out!
Well as the title says, while installing twrp I erased cache. Now recovery loops, so how do I rebuild my cache? Does anyone know? I'm rooted, S-off, running stock KK up to date.
godzilla61 said:
Well as the title says, while installing twrp I erased cache. Now recovery loops, so how do I rebuild my cache? Does anyone know? I'm rooted, S-off, running stock KK up to date.
Click to expand...
Click to collapse
Reinstall twrp?
Sent from my lunar powered Inverted ViperONE using Tapatalk 2
That was the first thing I tried, no-joy!
godzilla61 said:
That was the first thing I tried, no-joy!
Click to expand...
Click to collapse
Re flash the stock kitkat update. Clearing your cache shouldn't have broke recovery or the rom. You either wiped something you shouldn't have and didn't tell us or somethings broken with your copy of TWRP
Kraizk said:
Re flash the stock kitkat update. Clearing your cache shouldn't have broke recovery or the rom. You either wiped something you shouldn't have and didn't tell us or somethings broken with your copy of TWRP
Click to expand...
Click to collapse
Some folks execute a "fastboot erase cache" after flashing a recovery. Do not do that! Instead, either "fastboot format cache" or leave it alone. The fastboot erase cache command just blows the file system away and leaves you with an unmountable /cache partition until it's formatted (wipe will do that if you end up with errors about 'cannot mount /cache').
Click to expand...
Click to collapse
The second quote is from the dev, now on to my question, how do I rebuild my cache partition? There has to be a way without loosing everything....
godzilla61 said:
The second quote is from the dev, now on to my question, how do I rebuild my cache partition? There has to be a way without loosing everything....
Click to expand...
Click to collapse
rebuild your cache partition? or your cache filesystem? two totally different things.
if your disk is wrecked (partitions no longer valid) you're likely into RUU.
If your disk is fine (partitions are there, just no file system), TWRP should boot fine, it'll just piss and moan about /cache not being there. If it keeps restarting to the curtain (the TWRP graphic while booting) no big deal -- adb should still be up. If it does come up, you can 'wipe cache' and it'll rebuild the file system for you. Either that or use fastboot to format it.
Either way -- if you actually placed interesting stuff on /cache (why would you do that?), it's gone. The cache partition is 99% useless to users, so it would surprise me if you put stuff there.
Here's what I'd do:
1) Boot TWRP (get my 2.7.1.1 version, fastboot flash it, start it up);
2) plug the phone into usb:
3) adb shell
4) mount
copy/paste what that last command says and let's see what's really up. If TWRP won't boot, you have bigger problems than you lead us to believe.
Ok, more info: phone works. no recovery it just keeps showing the curtain over and over...... So now ADB....can't do a thing with it. Can't fastboot flash anything.....error: cannot load 'openrecovery-m7wls-2.7.1.1-06-05-2014' so what now?
[email protected]:/ $ mount
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
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,seclabel,relatime 0 0
selinuxfs /sys/fs/selinux selinuxfs rw,relatime 0 0
/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
none /sys/fs/cgroup tmpfs rw,seclabel,relatime,mode=750,gid=1000 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
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
none /dev/timer_group cgroup rw,relatime,timer_slack 0 0
/dev/block/mmcblk0p37 /system ext4 ro,seclabel,noatime,data=ordered 0 0
/dev/block/mmcblk0p39 /data ext4 rw,seclabel,nosuid,nodev,noatime,discard,noauto
_da_alloc,data=ordered 0 0
/dev/block/mmcblk0p38 /cache ext4 rw,seclabel,nosuid,nodev,noatime,data=ordered
0 0
/dev/block/mmcblk0p22 /devlog ext4 rw,seclabel,nosuid,nodev,noatime 0 0
/dev/block/mmcblk0p30 /carrier ext4 rw,seclabel,nosuid,nodev,noatime,grpid,data=
ordered 0 0
/dev/block/mmcblk0p33 /firmware/mdm vfat ro,relatime,fmask=0000,dmask=0000,allow
_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=lower,errors=remount-ro
0 0
tmpfs /data/qcks tmpfs rw,seclabel,relatime,size=20480k,mode=750,gid=1000 0 0
tmpfs /data/efs tmpfs rw,seclabel,relatime,size=20480k,mode=750,gid=1000 0 0
/dev/block/mmcblk0p16 /firmware/q6 vfat ro,relatime,fmask=0000,dmask=0000,allow_
utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=lower,errors=remount-ro
0 0
tmpfs /data/secure/data tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
/dev/fuse /mnt/shell/emulated fuse rw,nosuid,nodev,relatime,user_id=1023,group_i
d=1023,default_permissions,allow_other 0 0
DxDrmServerIpc /data/DxDrm/fuse fuse.DxDrmServerIpc rw,nosuid,nodev,relatime,use
r_id=0,group_id=0,allow_other 0 0
[email protected]:/ $
Click to expand...
Click to collapse
godzilla61 said:
Ok, more info: phone works. no recovery it just keeps showing the curtain over and over...... So now ADB....can't do a thing with it. Can't fastboot flash anything.....error: cannot load 'openrecovery-m7wls-2.7.1.1-06-05-2014' so what now?
Click to expand...
Click to collapse
I have no idea why you think /cache is your problem:
"/dev/block/mmcblk0p38 /cache ext4 rw,seclabel,nosuid,nodev,noatime,data=ordered 0 0"
It mounted fine.
As for flashing TWRP, you have to give fastboot an actual file:
"error: cannot load 'openrecovery-m7wls-2.7.1.1-06-05-2014"
The file is (assuming you didn't rename it) "openrecovery-m7wls-2.7.1.1-06-05-2014.img" -- there's an extension on the end.
If you did rename it, then you didn't place the file where you have fastboot. Either give the *full path* to the .img file, or move (or copy) it to the directory in which fastboot exists.
Thanks for taking the time to help! This gave me a reason to update my tool box for android. It's funny I never had to use a file ext. before when installing. It was that simple! So twrp is up and running again, I wonder why it was looping.....for another time perhaps. Thanks once again tdhite!!!
Hi,
i got this mobile with bricked OS, all what i know is that he stop with working after regular update (it`s not rooted)
Problem is that he turn on with LG logo and that`s all, freeze there...
After couple reboot in some cases he got screen upgrading software and that`s all again..
I successful get recovery console but have only reboot, apply sd card update, wipe data and cache partition.
Also i can access to him via adb shell, but almost all options are permission denied... and that is why i cannot put new ROM in /sdcard folder
Mount looks like this:
Code:
rootfs / rootfs rw 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
/tmp /tmp tmpfs rw,relatime 0 0
/dev/block/mmcblk0p1 /system ext2 rw,relatime 0 0
/dev/block/mmcblk0p2 /cache ext3 rw,nodev,noatime,nodiratime,data=ordered 0 0
i tried many options without luck...
Can i get some help?
tnx.