Hello~
I search some topic at this url
Clockwork Recovery v3.0.0.5 for LG Optimus One/T/S + CyanogenMod 7 Gingerbread based ROM
i using LG Optimus One P500,but the Clockwork Recovery flash recovery Img Command
Code:
#mount -o remount,rw -t yaffs2 /dev/block/[COLOR="Blue"]mtdblock5[/COLOR] /system
#cat /sdcard/flash_image > /system/bin/flash_image
#chmod 755 /system/bin/flash_image
#mount -o remount,ro -t yaffs2 /dev/block/[COLOR="blue"]mtdblock5[/COLOR] /system
#flash_image recovery /sdcard/recovery.img
#reboot recovery
but I find the other one recovery recovery-RA-thunderg-1.1.0-GNM.img flash Command
Code:
mount -o remount,rw -t yaffs2 /dev/block/[COLOR="blue"]mtdblock1[/COLOR] /system
cat /sdcard/flash_image > /system/bin/flash_image
chmod 755 /system/bin/flash_image
mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.bak
mount -o remount,ro -t yaffs2 /dev/block/[COLOR="blue"]mtdblock1[/COLOR] /system
flash_image recovery /sdcard/recovery-RA-GNM-thunderg-1.1.0.img
i using adb shell connect to my LG P500 try this command
Code:
cat /proc/mtd
Code:
dev: size erasesize name
mtd0: 00440000 00020000 "boot"
[COLOR="blue"]mtd1: 0be00000 00020000 "system"[/COLOR]
mtd2: 00500000 00020000 "recovery"
mtd3: 002c0000 00020000 "lgdrm"
mtd4: 00100000 00020000 "splash"
mtd5: 00180000 00020000 "FOTABIN"
mtd6: 005c0000 00020000 "FOTA"
mtd7: 00040000 00020000 "misc"
mtd8: 04000000 00020000 "cache"
mtd9: 0c780000 00020000 "userdata"
so if i want flash Clockwork Custom Recovery Mod the Correct flash Clockwork Command is this??
Code:
#mount -o remount,rw -t yaffs2 /dev/block/[COLOR="Blue"]mtdblock1[/COLOR] /system
#cat /sdcard/flash_image > /system/bin/flash_image
#chmod 755 /system/bin/flash_image
#mount -o remount,ro -t yaffs2 /dev/block/[COLOR="blue"]mtdblock1[/COLOR] /system
#flash_image recovery /sdcard/recovery.img
#reboot recovery
right??
and the other question?
which one custom recovery /recovery-RA-GNM-thunderg-2.2.1.img(the Newest) and Clockwork 3.0 is Best for LG P500?
thank you~~
Install rom manager from market and install clock work mod recovery from it...
Sent from my LG-P500 using XDA App
socialdistortion said:
Install rom manager from market and install clock work mod recovery from it...
Sent from my LG-P500 using XDA App
Click to expand...
Click to collapse
So Install ROM Manager and Install Clockwork by ROM manager it's all automatic..
hollowaysxp said:
So Install ROM Manager and Install Clockwork by ROM manager it's all automatic..
Click to expand...
Click to collapse
yes itb is simple like 123..how u are holding in wrong...walk with simple way only..
Yup!
My message was too short
You should post such questions in general section after searching. This is development section. Thanks.
I am so sorry~
when I eating my lunch...
I try to think all command...that's very easy...
/system can rw Read/Write...
mount -o remount,rw -t yaffs2 /dev/block/mtdblock1 /system
copy flash_image to /system/bin
#cat /sdcard/flash_image > /system/bin/flash_image
/system Read Only
#mount -o remount,ro -t yaffs2 /dev/block/mtdblock1 /system
flash image......Done.....
So this Clockwork Mod Support LG Optimus One P500?
but i think what's different between Clockwork and recovery-RA-GNM-thunderg....
which is best Cuestom Recovery.....
hollowaysxp said:
I am so sorry~
when I eating my lunch...
I try to think all command...that's very easy...
/system can rw Read/Write...
mount -o remount,rw -t yaffs2 /dev/block/mtdblock1 /system
copy flash_image to /system/bin
#cat /sdcard/flash_image > /system/bin/flash_image
/system Read Only
#mount -o remount,ro -t yaffs2 /dev/block/mtdblock1 /system
flash image......Done.....
So this Clockwork Mod Support LG Optimus One P500?
but i think what's different between Clockwork and recovery-RA-GNM-thunderg....
which is best Cuestom Recovery.....
Click to expand...
Click to collapse
both recoveries does their job well. Only limitation with Clockwork is it cant partition the ext to ext2 and ext3. The default is ext4. Rest recoveries are meant for flashing roms, you should compare roms instead of recoveries.
well....
thanks a lot...I don't want to my LG p500 become brick.
try like 123 easy flash Clockwork from ROM Manerger...
the first option..easy flash clockwork
{
"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"
}
hollowaysxp said:
well....
thanks a lot...I don't want to my LG p500 become brick.
try like 123 easy flash Clockwork from ROM Manerger...
the first option..easy flash clockwork
Click to expand...
Click to collapse
Lol. Ur funny.
Sent from my LG-P500 using XDA Premium App
People complicate what's easy, and then they complain their phones brick or they come crying at the devs... Use your head and install the recovery from Rom Manager or go to the topic on Ciaox's signature.
well rom manager downladed from market works best -the latest version orelse warez or old version put u in problem
My LG P500 Firmware is Original LG Firmware V10c.
I haven't Install the Clockwork Recovery....
because I am afraid LG P500 have some problem need to repair.
My LG P500 using Original LG Firmware for six months.
always root and unroot....it's always happen Hardware problem need to repair.
Yesterday I am taken my LG P500 to Taiwan LG agent for repair.
so my LG P500 bought at FEB-06-2011,but it's repair three tomes for hardware problem.
I want to using Custom Recovery flash unofficial Firmware get very well efficacy.
but the phone always have some hardware repair...
some let the phone keep Original LG Firmware for Warranty.
this is I Can't flash Clockwork Recovery Reson.
ROm manager
rom manager is good gor lg optimus one because in other recovery chance to brick ur phone but in rome manager its to easy or succsec so just use rom manager it toooo gudddd
Related
Since I've got DropBear and SSH on my Hero (MCR 3.2) I thought I'd try to remove APK-files via SSH, instead of using the USB-connection. I've successfully managed to connect to my phone, both via PuTTY and ConnectBot, but whenever I try to remove something from /system I get a message saying it's a read-only file system. What am I doing wrong? I should be able to perform what I've described above, right?
jeans2 said:
Since I've got DropBear and SSH on my Hero (MCR 3.2) I thought I'd try to remove APK-files via SSH, instead of using the USB-connection. I've successfully managed to connect to my phone, both via PuTTY and ConnectBot, but whenever I try to remove something from /system I get a message saying it's a read-only file system. What am I doing wrong? I should be able to perform what I've described above, right?
Click to expand...
Click to collapse
remount /system as rw
jeans2 said:
Since I've got DropBear and SSH on my Hero (MCR 3.2) I thought I'd try to remove APK-files via SSH, instead of using the USB-connection. I've successfully managed to connect to my phone, both via PuTTY and ConnectBot, but whenever I try to remove something from /system I get a message saying it's a read-only file system. What am I doing wrong? I should be able to perform what I've described above, right?
Click to expand...
Click to collapse
/system is by default read only, even for root.
Execute this in shell to remount it as read/write
mount -o remount,rw /dev/block/mtdblock3 /system
Eddie1506 said:
/system is by default read only, even for root.
Execute this in shell to remount it as read/write
mount -o remount,rw /dev/block/mtdblock3 /system
Click to expand...
Click to collapse
I'm guessing that line is similar to "adb remount"?
Is it something I have to execute each time I wan't to make changes in the /system-folder?
Yes, you can execute it through adb with "adb shell ...". I guess you have to execute it after reboot, I'm not really sure.
/system will stay mounted read/write until you reboot or remount to read only, however I'd always either reboot or remount it read only as soon as I was finished making changes, to be safe & avoid any accidental modifications/deletions. Also, yes, adb remount is just a quicker way to execute the same (or very similar) command.
cauli said:
/system will stay mounted read/write until you reboot or remount to read only, however I'd always either reboot or remount it read only as soon as I was finished making changes, to be safe & avoid any accidental modifications/deletions. Also, yes, adb remount is just a quicker way to execute the same (or very similar) command.
Click to expand...
Click to collapse
Okay, so mount -o rw /dev/block/mtdblock3 /system for mount and remount -o rw /dev/block/mtdblock3 /system for remount, right?
Btw, what does mtdblock3 contain?
jeans2 said:
Okay, so mount -o rw /dev/block/mtdblock3 /system for mount and remount -o rw /dev/block/mtdblock3 /system for remount, right?
Btw, what does mtdblock3 contain?
Click to expand...
Click to collapse
Last question first: /system System contains most of the operating system.
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
&
mount -o remount,ro -t yaffs2 /dev/block/mtdblock3 /system
to mount system read/write & read-only respectively. You might not need the '-t yaffs2' option which tells it what format the partition is, as it should auto detect the type, however the above should be most reliable.
cauli said:
Last question first: /system System contains most of the operating system.
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
&
mount -o remount,ro -t yaffs2 /dev/block/mtdblock3 /system
to mount system read/write & read-only respectively. You might not need the '-t yaffs2' option which tells it what format the partition is, as it should auto detect the type, however the above should be most reliable.
Click to expand...
Click to collapse
Okay, but what are the differences between the above and executing mount -o remount,rw (-t yaffs2) /system and mount -o remount,ro (-t yaffs2) /system, leaving the /dev/block/mtdblock3-part out?
remount isn't a command of itself (if you're using adb, adb remount is, so perhaps this is the source of that misapprehension) so that line above simply wouldn't do anything.
As to missing out the /dev/block/mtdblock3, aiui, in this case the mount command will attempt to infer the block device associated with the given mount point (ie with /system). Usually I think it relies on a config file /etc/fstab to do this, but that is often not present in Android ROMs (it seems to be absent from MCR 3.2 for one). In this particular case it works because the remount option implies it must use the device currently mounted at that mount point.
Essentially, you can often keep the command simple by missing out various parts, but if you have any kind of problem with it executing it's worthwhile specifying everything in case that is the cause of your problem. HTH
fyi:
Code:
$ adb shell cat /proc/mtd
dev: size erasesize name
mtd0: 00040000 00020000 "misc"
mtd1: 00500000 00020000 "recovery"
mtd2: 00280000 00020000 "boot"
mtd3: 0aa00000 00020000 "system"
mtd4: 08200000 00020000 "cache"
mtd5: 0a5c0000 00020000 "userdata"
cauli said:
remount isn't a command of itself (if you're using adb, adb remount is, so perhaps this is the source of that misapprehension) so that line above simply wouldn't do anything.
As to missing out the /dev/block/mtdblock3, aiui, in this case the mount command will attempt to infer the block device associated with the given mount point (ie with /system). Usually I think it relies on a config file /etc/fstab to do this, but that is often not present in Android ROMs (it seems to be absent from MCR 3.2 for one). In this particular case it works because the remount option implies it must use the device currently mounted at that mount point.
Essentially, you can often keep the command simple by missing out various parts, but if you have any kind of problem with it executing it's worthwhile specifying everything in case that is the cause of your problem. HTH
Click to expand...
Click to collapse
Ah, it was a typo. Should've been "mount" and not "remount", just as you pointed out.
Thank you for the explanation! And to you too, kendong2.
OBJECTIVE - Install CyanogenMod 7
http://forum.xda-developers.com/showthread.php?t=946354
Obstacle - Failed at INSTALLING A CUSTOM RECOVERY
http://androidforums.com/getitnowmarketing/221388-custom-recovery-optimus-one-p500-thunderg.html
1. I have successfully root by following this guide
http://forum.xda-developers.com/showthread.php?t=1001713
2. I have placed both flash_image and recovery-RA-GNM-thunderg-1.1.0at the root of sd card
http://forum.xda-developers.com/showthread.php?t=1007244
3. I am stucked at "INSTALLING A CUSTOM RECOVERY" and need help (I am getting error messages of file not found. Pictures attached)
Picture 1:
http://www.flickr.com/photos/[email protected]/5562426547/
Picture 2:
http://www.flickr.com/photos/[email protected]/5563002890/
Picture 3:
http://www.flickr.com/photos/[email protected]/5563002928/
PS: My phone is still locked to Koodo, does it matter I leave it locked ?
I think '>' has error
You'd better typing it in terminal no in cmd
need root and type in terminal
su
mount -o remount,rw -t yaffs2 /dev/block/mtdblock1 /system
cat /sdcard/flash_image > /system/bin/flash_image
chmod 755 /system/bin/flash_image
mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.bak
mount -o remount,ro -t yaffs2 /dev/block/mtdblock1 /system
flash_image recovery /sdcard/recovery-RA-GNM-thunderg-1.1.0.img
reboot recovery
It will help you
sondw said:
I think '>' has error
You'd better typing it in terminal no in cmd
need root and type in terminal
su
mount -o remount,rw -t yaffs2 /dev/block/mtdblock1 /system
cat /sdcard/flash_image > /system/bin/flash_image
chmod 755 /system/bin/flash_image
mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.bak
mount -o remount,ro -t yaffs2 /dev/block/mtdblock1 /system
flash_image recovery /sdcard/recovery-RA-GNM-thunderg-1.1.0.img
reboot recovery
It will help you
Click to expand...
Click to collapse
Thanks and it works.
How can I do this without a sd card... thanks in advance.
Sent from my LG-VM670 using Tapatalk
Flash the recovery image?
Root
Adb push a flash_image binary to /system/bin or xbin
adb push recovery.image to /cache or something
flash_image recovery /cache/recovery.img
I'm trying to flash the recovery without a SD card, because my phone can't mount a SD card anymore. So I'm using the recovery here http://www.lg-phones.org/lg-optimus-v-custom-recovery.html and Flash_image to flash it, but I need ADB codes to do so. I'm not very good with ADB, so I need the ones without the flash_image recovery /sdcard/ recovery-thunderc-v-1.2.0-GNM.img /sdcard/ part. :/
Curiousn00b said:
I'm trying to flash the recovery without a SD card, because my phone can't mount a SD card anymore. So I'm using the recovery here http://www.lg-phones.org/lg-optimus-v-custom-recovery.html and Flash_image to flash it, but I need ADB codes to do so. I'm not very good with ADB, so I need the ones without the flash_image recovery /sdcard/ recovery-thunderc-v-1.2.0-GNM.img /sdcard/ part. :/
Click to expand...
Click to collapse
It the same thing as tvall has mentioned but I will make it more easy for you.
As mentioned in the link that you have provided, just do this instead:
A) Type in 'adb remount'
B) Copy recovery-thunderc-v-1.2.0-GNM.img to platform-tools directory where android SDK is installed.
C) Do a 'adb push recovery-thunderc-v-1.2.0-GNM.img /system/xbin'
[Now the recovery image is inside your phones memory @/system/xbin location]
Following are the existing steps from the link: Modified step is made bold.
1) mount -o remount,rw -t yaffs2 /dev/block/mtdblock5 /system
2) cat /sdcard/flash_image > /system/bin/flash_image
3) chmod 755 /system/bin/flash_image
4) mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.bak
5) mount -o remount,ro -t yaffs2 /dev/block/mtdblock5 /system
6) flash_image recovery /system/xbin/recovery-thunderc-v-1.2.0-GNM.img
7) reboot recover
tvall said:
Flash the recovery image?
Root
Adb push a flash_image binary to /system/bin or xbin
adb push recovery.image to /cache or something
flash_image recovery /cache/recovery.img
Click to expand...
Click to collapse
developer++ said:
It the same thing as tvall has mentioned but I will make it more easy for you.
As mentioned in the link that you have provided, just do this instead:
A) Type in 'adb remount'
B) Copy recovery-thunderc-v-1.2.0-GNM.img to platform-tools directory where android SDK is installed.
C) Do a 'adb push recovery-thunderc-v-1.2.0-GNM.img /system/xbin'
[Now the recovery image is inside your phones memory @/system/xbin location]
Following are the existing steps from the link: Modified step is made bold.
1) mount -o remount,rw -t yaffs2 /dev/block/mtdblock5 /system
2) cat /sdcard/flash_image > /system/bin/flash_image
3) chmod 755 /system/bin/flash_image
4) mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.bak
5) mount -o remount,ro -t yaffs2 /dev/block/mtdblock5 /system
6) flash_image recovery /system/xbin/recovery-thunderc-v-1.2.0-GNM.img
7) reboot recover
Click to expand...
Click to collapse
Thanks alot guys, I really appreciate it, but I get stuck at
C:\android-sdk\platform-tools>adb remount
remount succeeded
C:\android-sdk\platform-tools>adb push recovery-thunderc-v-1.2.0-GNM.img /system
/xbin
cannot stat 'recovery-thunderc-v-1.2.0-GNM.img': No such file or directory
C:\android-sdk\platform-tools>
I'm starting to learn more, as I knew alot back when I first rooted my phone. As time went by..... easier ways were made.
Help plz.
EDIT: Been messing around with it, but still no go. This is what I got. Keep in mind I messed with some stuff if it doesn't look right..... :s
C:\android-sdk\platform-tools>adb remount
remount succeeded
C:\android-sdk\platform-tools>adb shell
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock5 /system
mount -o remount,rw -t yaffs2 /dev/block/mtdblock5 /system
# chmod 755 /system/bin/flash_image
chmod 755 /system/bin/flash_image
# mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.bak
mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.bak
mv: can't rename '/system/etc/install-recovery.sh': No such file or directory
# mount -o remount,ro -t yaffs2 /dev/block/mtdblock5 /system
mount -o remount,ro -t yaffs2 /dev/block/mtdblock5 /system
# flash_image recovery /system/xbin/recovery-thunderc-v-1.2.0-GNM.img
flash_image recovery /system/xbin/recovery-thunderc-v-1.2.0-GNM.img
failed with error: -1
error reading /system/xbin/recovery-thunderc-v-1.2.0-GNM.img header# flash_image
recovery /system/xbin/recovery-thunderc-v-1.2.0-GNM.img
flash_image recovery /system/xbin/recovery-thunderc-v-1.2.0-GNM.img
failed with error: -1
error reading /system/xbin/recovery-thunderc-v-1.2.0-GNM.img header# /system/xbi
n/flash_image recovery /system/xbin/recovery-thunderc-v-1.2.0-GNM.img
/system/xbin/flash_image recovery /system/xbin/recovery-thunderc-v-1.2.0-GNM.img
/system/xbin/flash_image: permission denied
#
Bump...
Sent from my LG-VM670 using Tapatalk
I have made inline comments. Just take note of it.
Curiousn00b said:
C:\android-sdk\platform-tools>adb remount
remount succeeded
C:\android-sdk\platform-tools>adb push recovery-thunderc-v-1.2.0-GNM.img /system
/xbin
cannot stat 'recovery-thunderc-v-1.2.0-GNM.img': No such file or directory
Click to expand...
Click to collapse
Here the 'recovery-thunderc-v-1.2.0-GNM.img' file should be present inside the C:\android-sdk\platform-tools directory. Also check if the spelling is correct.
Curiousn00b said:
C:\android-sdk\platform-tools>adb remount
remount succeeded
C:\android-sdk\platform-tools>adb shell
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock5 /system
mount -o remount,rw -t yaffs2 /dev/block/mtdblock5 /system
# chmod 755 /system/bin/flash_image
chmod 755 /system/bin/flash_image
# mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.bak
mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.bak
mv: can't rename '/system/etc/install-recovery.sh': No such file or directory
Click to expand...
Click to collapse
This error came because there is no file called 'install-recovery.sh' inside /system/etc. This is fine since you are anyways not going to use that file.
Curiousn00b said:
# mount -o remount,ro -t yaffs2 /dev/block/mtdblock5 /system
mount -o remount,ro -t yaffs2 /dev/block/mtdblock5 /system
# flash_image recovery /system/xbin/recovery-thunderc-v-1.2.0-GNM.img
flash_image recovery /system/xbin/recovery-thunderc-v-1.2.0-GNM.img
failed with error: -1
error reading /system/xbin/recovery-thunderc-v-1.2.0-GNM.img header# flash_image
recovery /system/xbin/recovery-thunderc-v-1.2.0-GNM.img
flash_image recovery /system/xbin/recovery-thunderc-v-1.2.0-GNM.img
failed with error: -1
error reading /system/xbin/recovery-thunderc-v-1.2.0-GNM.img header# /system/xbi
n/flash_image recovery /system/xbin/recovery-thunderc-v-1.2.0-GNM.img
/system/xbin/flash_image recovery /system/xbin/recovery-thunderc-v-1.2.0-GNM.img
/system/xbin/flash_image: permission denied
#
Click to expand...
Click to collapse
This part I am not that clear but it might be that the recovery 'recovery-thunderc-v-1.2.0-GNM.img' is corrupt or may be 'flash_image' is corrupt. You can also check for the amount of free memory by typing in 'df' and 'free' respectively. df would give you phone memory stats and free would give you RAM stats. Verify if anything is too low.
For the last permission denied error do a 'ls -l' at /system/xbin and check for the permissions.
I will look around to see if I can get some clues till then, lets wait for someone who can help you better.
[ADVICE: Since you are playing around with system binaries make sure you take a backup of /system/bin atleast.]
developer++ said:
I have made inline comments. Just take note of it.
Here the 'recovery-thunderc-v-1.2.0-GNM.img' file should be present inside the C:\android-sdk\platform-tools directory. Also check if the spelling is correct.
This error came because there is no file called 'install-recovery.sh' inside /system/etc. This is fine since you are anyways not going to use that file.
This part I am not that clear but it might be that the recovery 'recovery-thunderc-v-1.2.0-GNM.img' is corrupt or may be 'flash_image' is corrupt. You can also check for the amount of free memory by typing in 'df' and 'free' respectively. df would give you phone memory stats and free would give you RAM stats. Verify if anything is too low.
For the last permission denied error do a 'ls -l' at /system/xbin and check for the permissions.
I will look around to see if I can get some clues till then, lets wait for someone who can help you better.
[ADVICE: Since you are playing around with system binaries make sure you take a backup of /system/bin atleast.]
Click to expand...
Click to collapse
I tried again about 8 hours ago. I got through everything with no error, but when I got to recovery, it was still the old one. I'll try again once I get home.
Sent from my LG-VM670 using Tapatalk.
Other option (if your phone is rooted)
Install RomManager and install CWM or alternative.
If you're not rooted you need to do that first.
After that you can flash any recovery you want and you don't need to mess with adb
You can try to flash a recovery via LGMDP. I've flashed CWM 4.0 by this way.
_Arjen_ said:
Other option (if your phone is rooted)
Install RomManager and install CWM or alternative.
If you're not rooted you need to do that first.
After that you can flash any recovery you want and you don't need to mess with adb
Click to expand...
Click to collapse
Rom manager bricks the Optimus.
Dan_Jacques said:
You can try to flash a recovery via LGMDP. I've flashed CWM 4.0 by this way.
Click to expand...
Click to collapse
Sent from my LG-VM670 using Tapatalk
I got it flashed, thanks to Jerryscript.
Sent from my LG-VM670 using Tapatalk
Curiousn00b said:
Rom manager bricks the Optimus.
Sent from my LG-VM670 using Tapatalk
Click to expand...
Click to collapse
well most time i did it via rom manger and all time it was a sucess ,still lgmdp is good option but rom manger does it quiet easily just make sure u ahve a good internet connection so that its not disrupted when downloading better connected via wifi orelse better to go wth lgmdp method
Curiousn00b said:
I got it flashed, thanks to Jerryscript.
Sent from my LG-VM670 using Tapatalk
Click to expand...
Click to collapse
You can share the solution and provide a link so that in the future if someone has the same problem he can visit this thread and get things sorted out.
Edit the title of the thread to SOLVED
developer++ said:
You can share the solution and provide a link so that in the future if someone has the same problem he can visit this thread and get things sorted out.
Edit the title of the thread to SOLVED
Click to expand...
Click to collapse
I never found out how to change the thread name.
And ill edit the post tomorrow. I also have another question.
Sent from my LG-VM670 using Tapatalk
Can someone with a sd card, and adb, test this out? I don't want to test it out, cause without a sd card mounter, if it doesn't work, I'm screwed. If it doesn't work, I'm sure you have a nandroid on your sd card, hopefully. Please and thank you.
http://www.addictivetips.com/mobile/how-to-install-a-rom-to-an-android-phone-device-without-sd-card/
Sent from my LG-VM670 using Tapatalk
hi,
When i install custom font in my rooted HTC one M7, font works fine. but new font does not exists after reboot. Do have any idea. please refer following procedure i followed.
mount -o rw,remount -t yaffs2 /dev/block/mtdblock4 /system
cd /system/fonts
dd if=/sdcard/NotoSansSinhala-Bold.ttf of=/system/fonts/NotoSansMyanmar-Bold.ttf
dd if=/sdcard/NotoSansSinhala-Regular.ttf of=/system/fonts/NotoSansMyanmar-Regular.ttf
reboot.
I have an old Xperia (Android 4.4.2) here and I'm having trouble using it as root (SuperSu) I can grant permission to the root applications, but none can read / write permission to / system, so I can not install busybox, Xposed or any other that needs r / w permission, with root explorers the permissions can not be changed. Is there a solution?
Ps:Google Translation.
EvertonLinyx said:
I have an old Xperia (Android 4.4.2) here and I'm having trouble using it as root (SuperSu) I can grant permission to the root applications, but none can read / write permission to / system, so I can not install busybox, Xposed or any other that needs r / w permission, with root explorers the permissions can not be changed. Is there a solution?
Ps:Google Translation.
Click to expand...
Click to collapse
Install Terminal Emulator app then run following and give output
Code:
mount -o remount,rw /system
and also
Code:
mount | grep " /system "
HemanthJabalpuri said:
Install Terminal Emulator app then run following and give output
Code:
mount -o remount,rw /system
and also
Code:
mount | grep " /system "
Click to expand...
Click to collapse
{
"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"
}
[email protected]:/ $ su
[email protected]:/ #mount -o remount,rw /system
mount: Operation not permitted
255|[email protected]:/ # su mount -o remount,rw /system
tmp-mksh: remount,rw /system: bad option
1|[email protected]:/ # mount | grep "/system"
/dev/block/platform/msm_sdcc.1/by-name/system /system ext4 ro,seclabel,relatime,data=ordered 0 0
[email protected]:/ #
Click to expand...
Click to collapse
@osm0sis
Is the above is related to dm-verity?
is there dm-verity in 4.4.2?
HemanthJabalpuri said:
@osm0sis
Is the above is related to dm-verity?
is there dm-verity in 4.4.2?
Click to expand...
Click to collapse
Nope. That's just not how you use `su`.
To run a command with su the syntax is `su -c`, but for a mount you wouldn't want to do it with su -c because of possible namespace issues. So you need to type `su` be at a root # prompt, then try your mount commands.
Also that's not the best way to pass mount arguments if you want it to work on old toolbox, toybox and/or busybox. They need to be ordered the other way around. You should do `mount -o rw,remount -t auto /system`
Hopefully you can take it from here. My random user help thread support hours are spent for the day.
@EvertonLinyx
Try this
Code:
su
mount -o rw,remount -t auto /system
and also
Code:
setenforce 0
getenforce
mount -o rw,remount -t auto /system
HemanthJabalpuri said:
@EvertonLinyx
Try this
Code:
su
mount -o rw,remount -t auto /system
and also
Code:
setenforce 0
getenforce
mount -o rw,remount -t auto /system
Click to expand...
Click to collapse
@HemanthJabalpuri
[email protected] :/ $ su
[email protected]:/ # mount -o rw,remount -t auto /system
mount: Operation not permitted
remount -t auto /system <
tmp-mksh: rw,remount -t auto /system: bad option
1|[email protected]:/ #
EvertonLinyx said:
and also
@HemanthJabalpuri
[email protected] :/ $ su
[email protected]:/ # mount -o rw,remount -t auto /system
mount: Operation not permitted
remount -t auto /system <
tmp-mksh: rw,remount -t auto /system: bad option
1|[email protected]:/ #
Click to expand...
Click to collapse
Hey,
Also try remaining commands in my above post.
setenforce is not recognized :s
is there a script or APP that fixes this?
EvertonLinyx said:
setenforce is not recognized :s
is there a script or APP that fixes this?
Click to expand...
Click to collapse
May be you can get better support at https://forum.xda-developers.com/showthread.php?t=2259645 ....
Post your question there and they will reply.
Solved
osm0sis said:
Nope. That's just not how you use `su`.
To run a command with su the syntax is `su -c`, but for a mount you wouldn't want to do it with su -c because of possible namespace issues. So you need to type `su` be at a root # prompt, then try your mount commands.
Also that's not the best way to pass mount arguments if you want it to work on old toolbox, toybox and/or busybox. They need to be ordered the other way around. You should do `mount -o rw,remount -t auto /system`
Hopefully you can take it from here. My random user help thread support hours are spent for the day.
Click to expand...
Click to collapse
HemanthJabalpuri said:
May be you can get better support at https://forum.xda-developers.com/showthread.php?t=2259645 ....
Post your question there and they will reply.
Click to expand...
Click to collapse
Finally I solved this and all the other problems in this posthttps://forum.xda-developers.com/xperia-e3/help/root-metods-unlock-bootloader-help-t3943561, thanks for everything