how to replace? by using metamorph? i did with root explorer and ended up with bricked x10 mini.
It's probably best to do it via ADB.
yes adb / shell is my favourite method
I use Root expl. only to rw mount /system partition.
How to do via adb?
Sent from my E10i using XDA App
from: http://forum.xda-developers.com/showthread.php?t=759320
0. Root !
1. adb push framework-res.apk /sdcard/fr-black.apk
2. adb shell
3. su
4. mount -o remount,rw -t yaffs2 /dev/block/mtdblock2 /system
5. mv /system/framework/framework-res.apk /sdcard/framework-resORIG.apk
6. cat /sdcard/fr-black.apk > /system/framework/framework-res.apk
7. chmod 755 /system/framework/framework-res.apk
8. sync
9. reboot
why cat and not mv/cp ? Because the file is created with "root" user and group and not "sdcard" group.
Means the framework file is first placed on sd card which i want to replace? Asking noob questions cause dnt want to install whole software again
Sent from my E10i using XDA App
abhi98228 said:
Means the framework file is first placed on sd card which i want to replace? Asking noob questions cause dnt want to install whole software again
Click to expand...
Click to collapse
Here, I'll try to explain what happens
1. adb push framework-res.apk /sdcard/fr-black.apk
-copies "frarework-res.apk" from ADB's folder and moves it to the phone's SD card, names it "fr-black.apk"
2. adb shell
-opens the linux shell on the phone
3. su
-goes into superuser mode, i.e. runs apps as admin if you're familiar with windows terms
4. mount -o remount,rw -t yaffs2 /dev/block/mtdblock2 /system
-remounts the /system folder on the phone so that it is read-write, allowing you to mess with the system files
5. mv /system/framework/framework-res.apk /sdcard/framework-resORIG.apk
-backs up the default framework-res.apk from the phone by moving it to the SD card
6. cat /sdcard/fr-black.apk > /system/framework/framework-res.apk
-copies the fr-black.apk from the SD card and puts it in the old framework-res' place
7. chmod 755 /system/framework/framework-res.apk
-changes the user permissions for the new file
Eseb0 said:
Here, I'll try to explain what happens
1. adb push framework-res.apk /sdcard/fr-black.apk
-copies "frarework-res.apk" from ADB's folder and moves it to the phone's SD card, names it "fr-black.apk"
2. adb shell
-opens the linux shell on the phone
3. su
-goes into superuser mode, i.e. runs apps as admin if you're familiar with windows terms
4. mount -o remount,rw -t yaffs2 /dev/block/mtdblock2 /system
-remounts the /system folder on the phone so that it is read-write, allowing you to mess with the system files
5. mv /system/framework/framework-res.apk /sdcard/framework-resORIG.apk
-backs up the default framework-res.apk from the phone by moving it to the SD card
6. cat /sdcard/fr-black.apk > /system/framework/framework-res.apk
-copies the fr-black.apk from the SD card and puts it in the old framework-res' place
7. chmod 755 /system/framework/framework-res.apk
-changes the user permissions for the new file
Click to expand...
Click to collapse
hehe ty bro
Hi
I need some help pls, when i wanna replace the framework-res.apk i get this:
C:\exploid_x10mini>adb push framework-res.apk /sdcard/fr-black.apk
* daemon not running. starting it now *
* daemon started successfully *
1523 KB/s (7108054 bytes in 4.557s)
C:\exploid_x10mini>adb shell
$ su
su
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock2 /system
mount -o remount,rw -t yaffs2 /dev/block/mtdblock2 /system
# mv /system/framework/framework-res.apk /sdcard/framework-resORIG.apk
mv /system/framework/framework-res.apk /sdcard/framework-resORIG.apk
failed on '/system/framework/framework-res.apk' - Cross-device link
Please help
try
mount -o rw,remount /dev/block/mtdblock0 /system
and check first-after with mount bash command the mountpoint
oversim said:
try
mount -o rw,remount /dev/block/mtdblock0 /system
and check first-after with mount bash command the mountpoint
Click to expand...
Click to collapse
I still get the same:
C:\exploid_x10mini>adb shell
$ su
su
# mount -o rw,remount /dev/block/mtdblock0 /system
mount -o rw,remount /dev/block/mtdblock0 /system
# mv /system/framework/framework-res.apk /sdcard/framework-resORIG.apk
mv /system/framework/framework-res.apk /sdcard/framework-resORIG.apk
failed on '/system/framework/framework-res.apk' - Cross-device link
#
Can you explain .. " and check first-after with mount bash command the mountpoint" .. please
Skip mv step instade backup by root expkorer.
Sent from my E10i using XDA App
Thank you my mini is now black
kimb0 said:
Hi
I need some help pls, when i wanna replace the framework-res.apk i get this:
C:\exploid_x10mini>adb push framework-res.apk /sdcard/fr-black.apk
* daemon not running. starting it now *
* daemon started successfully *
1523 KB/s (7108054 bytes in 4.557s)
C:\exploid_x10mini>adb shell
$ su
su
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock2 /system
mount -o remount,rw -t yaffs2 /dev/block/mtdblock2 /system
# mv /system/framework/framework-res.apk /sdcard/framework-resORIG.apk
mv /system/framework/framework-res.apk /sdcard/framework-resORIG.apk
failed on '/system/framework/framework-res.apk' - Cross-device link
Please help
Click to expand...
Click to collapse
you can use cat /system/framework/framework-res.apk > /sdcard/framework-resORIG.a
as a work around
It help me
Related
Ok I am on a rooted 345 us White dell streak.
I am trying to deodex. I have used the deo 1.2.1 deodexer in the xda forum thread for auto deodex 2.3.
I pulled all my apks and their odex files from the /system/app/ folder
and the jars and odex files from the /system/framework folder
I am trying to use adb to copy them from my sdcard to the correct folders, but when i reboot my phone hangs at the dell logo.
Hopefully someone can see what I am doing wrong.
I enter:
adb shell
su (then I allow permission on my phone)
mount -o rw,remount -t yaffs2 /dev/block/mtdblock6 /system
cp /sdcard/doneapk/* /system/app/
cp /sdcard/doneframework/* /system/framework/
rm /system/app/*.odex
rm /system/framework/*.odex
mount -o ro,remount -t yaffs2 /dev/block/mtdblock6 /system
reboot
what am i missing?
adb shell
su
stop
mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
cp /sdcard/done_app/* /system/app/
cp /sdcard/done_frame/* /system/framework/
rm /system/app/*.odex
rm /system/framework/*.odex
mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
sync
reboot
also u can find them here as i done this to intgrade arabic to streak its in done_app & done_fram
my rom 345
http://hotfile.com/dl/110981641/4de9442/arabic_streak_345_15380_00.7z.html
bump..
can you guys post a quick guide with steps on how to do this? How hard is it to go back and edit files later like services.odex? if it doesn't exist anymore?
I have no idea what bump means......forum noob obviously.
But if you search auto deodex 2.3 in xda forums it is under droidx forums.
So I changed the mount command to yaffs2 /dev/bkock/mtdblock6 where theirs is different because from what I understand, that is the streaks mount command for mounting.
But I will try the other path and see if it works. I will keep you updated when I try it later.
freepal08 said:
adb shell
su
stop
mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
cp /sdcard/done_app/* /system/app/
cp /sdcard/done_frame/* /system/framework/
rm /system/app/*.odex
rm /system/framework/*.odex
mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
sync
reboot
also u can find them here as i done this to intgrade arabic to streak its in done_app & done_fram
my rom 345
http://hotfile.com/dl/110981641/4de9442/arabic_streak_345_15380_00.7z.html
Click to expand...
Click to collapse
so I tried your command path and no luck. still stuck on the dell logo.
Thank GOD for nandroid backup.
how exactly did you deodex your files? maybe thats what i am missing. Maybe the deodexed files i put in have an issue.
i used xUltimate-v2.2.2
and if u are 345 rom
u can use my files
also its take up to 10 min to load the phone
Krad said:
bump..
can you guys post a quick guide with steps on how to do this? How hard is it to go back and edit files later like services.odex? if it doesn't exist anymore?
Click to expand...
Click to collapse
Whenever you edit services.odex you first doedex it...then you modify it...then you carefully and painfully re-odex it...with a deodexed file system you get rid of the first and last steps...
so it would be services.dex, you copy it to your pc, edit it, and send it back...quicker and easier modding
freepal08 said:
adb shell
su
stop
mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
cp /sdcard/done_app/* /system/app/
cp /sdcard/done_frame/* /system/framework/
rm /system/app/*.odex
rm /system/framework/*.odex
mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
sync
reboot
also u can find them here as i done this to intgrade arabic to streak its in done_app & done_fram
my rom 345
http://hotfile.com/dl/110981641/4de9442/arabic_streak_345_15380_00.7z.html
Click to expand...
Click to collapse
ok I am trying your files. I see you put sync as your last command after you remount. that differs than the droidx forum How to manually deodex thread.
what does sync do?
I got farther with your files than i have before. So maybe I might have some luck after all, but still stuck on a frozen boot animation
I have no idea what I did differently but I am now deodexed using the file provided above.
My phone is now a rooted and deodexed 345 build. Nice!
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.
Ok so the Rezound has the bootloader unlocked and rooted with 1click method.
Root Explorer, and Root Checker verify.
Going into adb I am trying to adb rm /system/app/".apk"
It doesnt work.
I tried adb remount and it is not letting me and says operation not permitted.
If I type in adb shell I get the $, then type in su and get #
Titanium Backup. More than worth the money. You can freeze, remove, and backup anything/everything.
Sent from my ADR6425LVW using xda premium
Code:
adb shell
su
busybox mount -o rw,remount -t / rootfs
rm /system/app/NameOfApp.apk
busybox mount -o ro,remount -t / rootfs
adb shell
$ su
su
# busybox mount -o rw,remount -t yaffs2 /rootfs
busybox mount -o rw,remount -t yaffs2 /rootfs
mount: can't find /rootfs in /proc/mounts
# rm /system/app/com.mobitv.client.nfl2010.apk
rm /system/app/com.mobitv.client.nfl2010.apk
rm failed for /system/app/com.mobitv.client.nfl2010.apk, Read-only file system
Try ROM Toolbox. You can find it free in Market.
Code:
busybox mount -o rw,remount -t yaffs2 /dev/block/mmcblk029p /system
This Will Mount The System As "read/write" And Switch It To "ro" To Go Back To "read-only"
Xtreme Outcast said:
Code:
busybox mount -o rw,remount -t yaffs2 /dev/block/mmcblk029p /system
This Will Mount The System As "read/write" And Switch It To "ro" To Go Back To "read-only"
Click to expand...
Click to collapse
I would suggest to drop the extra bits that someone could mis-type and shorten this to
"busybox mount -o remount,rw /system"
It's worked for me and takes a little chance out of the equation. Just my opinion take it for what it's worth.
I Was In A Rush Yesterday That I Typed In The Wrong Code And Just Realized It Now When He Said It Didn't Work. It's All Fixed Thanks For The Suggestions Always Appreciated On My Posts Or Threads.
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
- Root devices
Code:
adb shell
su
mount -o remount,rw /system
rm /system/csc/language.xml
reboot
Or
Code:
adb shell
su
mount -o remount,rw /system
mv /system/csc/language.xml /system/csc/language.xml.bak
reboot
Done