hello, guys.
Finally, we waitting for the offical cm13 out for our Moto X 2014.
but when i edit the file in /system, but failed.
I found a usful way to get it work.
Code:
adb remount
will get the /system & / remount as RW.
wat?
Sent from my XT1095 using Tapatalk
Related
I've been trying to figure out how to fix my phone and through using the adb logcat the only thing left is just getting the core.jar file in the /system/framework to change from read only to rw. Each time I try to change it it says its read only or bad mode. Any ideas?
Metatronx said:
I've been trying to figure out how to fix my phone and through using the adb logcat the only thing left is just getting the core.jar file in the /system/framework to change from read only to rw. Each time I try to change it it says its read only or bad mode. Any ideas?
Click to expand...
Click to collapse
try
Code:
adb remount
What would the syntax be for remounting the core.jar and is it possible to do in terminal? Thank you especially for the quick response\!
From your other thread..
The entire /system partition is always read-only, unless you tell your phone to remount it read-write.
Code:
mount -o remount,rw /dev/block/mtdblock3 /system
But for your problem.. You shouldn't really need to manually tweak files in /system if you flash another ROM. The new ROM will replace that entire partition. Have you wiped? What ROM are you trying to flash?
Kudos for using logcat and trying to jump in yourself though.
I have a rooted (rage) N1 that I loaded the G2 Launcher2.apk on to. Doing this caused the N1 to fail the update when it tried to apply FRG83D.
Stupidly, I decided that deleting the /system/app/launcher2.apk file was the right idea. And then rebooted.
Now the phone hangs on the boot animation. Attempting to apply with NO launcher2.apk results in the same error.
I have ADB installed, and I can adb shell into the phone and su. I have the old, original N1 launcher backed up on my SD card, but I can't figure out how to:
1) Mount the sdcard while ADB shell'd in from just the boot animation screen so that I can browse the card
2) Move the launcher2.apk backup file into the /system/app directory without getting a "Cross-device link" error when I use mv.
Can someone provide me with the exact commands to get the /sdcard/launcher2 backup/launcher2.apk file on to /system/app while ADB'd in only from the boot animation?
Thanks so much, I'm digging through the forums in the mean time, but it's tricky to track down exactly what to do.
I appear to have fixed everything. I wasn't able to access the SD card through ADB, but I *was* able to mount it using the:
Code:
echo /dev/block/mmcblk0 > /sys/devices/platform/usb_mass_storage/lun0/file
method.
From there, I copied my backup to my desktop, and I found I was able to ADB push to just the /data/local/tmp directory. Don't know if I could've gone anywhere else, but that worked.
From there, I was about to:
Code:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
to mount/make writable the /system/app directory,
and then:
Code:
cat /data/local/tmp/launcher2.apk > /system/app/launcher2.apk
So there's that. All to restore the Launcher to a version that would allow for a somewhat pointless update. Woo!
I have a verizon Samsung Galaxy tab. I would like to use clockwork recovery. The tab is rooted and I used ROM manager from the marketplace to flash the recovery for a Samsung Tab (Verizon). When I flash the ROM everything is successful. However, when I boot into recovery the Android System Recovery <3e> shell loads which doesn't allow nandroid backups etc... all the neat recovery tools that come with clockwork recovery.
I searched around the forum and saw a thread titled how to replace Android System Recovery with a Custom ROM. These were the commands
adb shell
su
mount -o remount,rw -t yaffs2 /dev/mtdblock3 /system
rm /system/etc/install-recovery.sh
cd sdcard
mount -o remount,exec /dev/block//vold/179:1 /sdcard
./flash_image recovery /sdcard/recovery.img
exit
exit
I went into abd shell I tried the commands but by the time I got to the third line I keep getting permission errors before I can even finish typing the command. I cut and paste the command string from "mount-->" thinking I just wasn't typing fast enough and it still doesn't work.
Is there another way to remove the Android system recovery so that ROM manager will work properly?
Have a look at installing boushh's kernel, it probably going to be the best option around for you.
Sent from my X10i using XDA App
I don't know what that is?
I have also same problem ı tryed many flashes ı coudnt fix it yet.if you allready fixed could you please share thanks.....
Alright.. I wanted the Note 8 version of gallery and i went into system/app folder and deleted the SecGallery2_Galaxy.apk but before deleting i saw that its size was 0.00 kb lol ..
But when i tried tried to copy and pasted in the extsd it pasted and showed 13mb..
Now i deleted the file and copied the Note 8 Galley and pasted in the system/app folder only to get an error " Operation failed " and i realized only 7 mb free space is there in the partition by going into the android emulator!
Now i also found out that, full size SecGallery2_Galaxy.apk was in the preload partition and i instead of replacing that i deleted the file in system/app..
Now how do i get back that file in system/app?.. is that what they call deodexed file?.. Please help..
Thanks a lot in advance
Just copy it from other rom, that You can explore with winrar.
Sent from galaxy n7105
The actual apk was in preload and was symlinked to system partition. Thats why it showed 0 KB in system.
You can get it back by typing in shell
Code:
$ su
# ln -s "Path of apk in preload" /system/app/
And this is not called deodexing.
nokiamodeln91 said:
The actual apk was in preload and was symlinked to system partition. Thats why it showed 0 KB in system.
You can get it back by typing in shell
Code:
$ su
# ln -s "Path of apk in preload" /system/app/
And this is not called deodexing.
Click to expand...
Click to collapse
Thanks but i dont know the path.. the name of the file is SecGallery2_Galaxy.apk, so whats the path of the file?..
can u please type and show?..
Thanks in advance
CustomRomAddicts said:
Thanks but i dont know the path.. the name of the file is SecGallery2_Galaxy.apk, so whats the path of the file?..
can u please type and show?..
Thanks in advance
Click to expand...
Click to collapse
I dont remember... but something like
/preload/symlink/system/app/SecGallery2_Galaxy.apk
but double check.
nokiamodeln91 said:
I dont remember... but something like
/preload/symlink/system/app/SecGallery2_Galaxy.apk
but double check.
Click to expand...
Click to collapse
It says read only file system
I even changed the permission of the file in preload to 644 ( rw-r--r-- )
still the same message?.. any idea what it might be?.
Thanks in advance
use adb shell
then mount the preload partition as rw
# mount -o remount rw /preload
# mount -o remount rw /system
the use the codes written above.
nokiamodeln91 said:
use adb shell
then mount the preload partition as rw
# mount -o remount rw /preload
# mount -o remount rw /system
the use the codes written above.
Click to expand...
Click to collapse
Honestly i just now searched in google for adb shell and it says to run windows but when i download and double click the adb.exe it runs and exits!.. Please help..
Will mounting the preload and system in recovery and rebooting the device and running the script again in android emulator work?..
Keep in recovery and mount both.. Then run....
nokiamodeln91 said:
Keep in recovery and mount both.. Then run....
Click to expand...
Click to collapse
I tried in adb shell too.. but its not working
Do u guys have the symlink file?.. can u share with me?.. will it work?..
Thanks in advance
Oh Yeah! SOLVED IT!!
I installed Root explorer and created symlink via that and Voila it worked!
Although i dont know why when i open a photo in gallery i experience FC!
I've noticed that I'm unable to mount /system using adb to pull or push files. Whether I use adb remount or mount -o rw,remount blahblahblah /system through adb or terminal.
If I open root explorer and mount system rw, it will then let me pull or push.
I've read its because of not having insecure adb. Now this seems to be only on a stock ROM or my stock rooted.
I sent it through the kitchen again and unpacked the kernel, chose the adb insecure option, repacked ...rebuilt...flashed...and still the same.
How can I get around this?
Sent from my SAMSUNG-SM-G870A using Tapatalk
Nickovtyme said:
I've noticed that I'm unable to mount /system using adb to pull or push files. Whether I use adb remount or mount -o rw,remount blahblahblah /system through adb or terminal.
If I open root explorer and mount system rw, it will then let me pull or push.
I've read its because of not having insecure adb. Now this seems to be only on a stock ROM or my stock rooted.
I sent it through the kitchen again and unpacked the kernel, chose the adb insecure option, repacked ...rebuilt...flashed...and still the same.
How can I get around this?
Sent from my SAMSUNG-SM-G870A using Tapatalk
Click to expand...
Click to collapse
you can't change anything in the kernel ramdisk, Locked BL prevents that. :crying: