Hello everybody
I needed to push a file to /system/app but since I was on stock rom & kernel, that didnt support adb root.
I needed to be able to push the backup file after restart but ADBD Insecure couldn't patch after restart.
my phone is optimus G E975 , fully stock 4.1.2
I found this command which could do the thing BUT :
adb shell
su
chmod 777 /system
since it didnt restore to default after restarted I tried to restore it myself(didn't work) with:
adb shell
su
chmod 644 /system
but after that every thing force stopped & after restart, phone can't boot anymore,just when want t start boot animation, it just cant & goes to recovery every time!
even Hard reset didnt work, but as stock recovery supports adb, I wish you guys can help me. but It seems adb shell gives permission denied(13) in recovery. please someone help...
Anyway am I able to flash in download mode????? (for the last solution)
any help to change that CHMOD to 777 in recovery or something else?
any help appreciated so much!
After using this command, it seems the /system directory became unreadable,
FIX: after flashing e975tot rom through LGNPST in DW mode, the phone booted up normally & problem fixed.
Related
ok, so before i reflashed my rooted hero with Modaco on it to stock sprint ROM, all adb commands were working fine, I could easily write a file to phone's system using adb push command.
NOW, after updating and rerooting it,
it won't give me a permission to do adb remount in order to do adb push.
It will still let me get into SU and write a file from there,
for example i'll have to adb push a file to /sdcard/ then get into SU and do cat /sdcard/myfile >/system/myfile and it works fine,
but NOT adb remount!!
Any ideas why this is happening? (thanks)
not sure , but its been confirmed that flash modaco first then then fresh rom and then push to system, btw that's what i did, and im using fresh rom .4 with MR. Working Great here...
matthenry87 said:
try
Code:
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
Click to expand...
Click to collapse
I did it, it's a part of the rooting process, and that's wat let me write files within the shell or remove them, but when i exit out to do adb commands it seems like it remounts back to read only mode and doesnt permit to remount from adb remount
I'M HAVINg this same problem. No idea why.
I'm pretty sure this is because the /default.prop file has the permissions set to read only. I've been trying to figure out how to change this, but having no luck with this or other modifications that MoDaCo built into this ROM. started a thread over here:
http://forum.xda-developers.com/showthread.php?t=586630
There's other mods, such as setting up the superuser whitelist app. Hopefully someone with some experience helps us newbie's along.
I need some help please, my phone wont boot and is stuck at the M logo. I am using dexters ROM with its patch. I wanted to change the android font from the standard droidsans to the Ubuntu font. I downloaded the ttf's from the ubuntu website and started looking on how to go about it.
So after searching the internet, I saw most people were doing it using adb push to replace the fonts in the /system folder. First problem that I encountered was adb not working, but after updating my $PATH to add platform tools it started working. After that when I tried the push command it said the /system was read only. I followed these instructons to make the /system folder read/write.
adb shell
$ su
# mount
# # mount -o remount,rw -t yaffs2 /dev/block/mtdblock7 /system
After this I did:
mv /system/fonts/DroidSans.ttf /system/fonts/DroidSans_org.ttf
# exit
$ exit
I tried to adb push the fonts but they permission was denied. I them removed the original fonts and thats when the screen went black. I did adb reboot and now the phone wont go past the M logo. Went into normal recovery using the camera, media and power keys. Did a factory reset. Still stuck. I have no idea wtf I did, I just usually follow instructions and everything is fine dunno what happened this time. I dont know how to go back into open recovery and flash the rom again. Any help would be appretiated. Thanks!
You should be able to get into openrecovery by pressing and holding the volume up key while powering on.
Thank you! It worked now to get around to fixing this Thanks again
I've been working on my /System/App folder with root access and I changed the permissions to R/W, R and R. Afterwards, the device freezes at the AT&T screen, looping at the stage where it loads certain apps. It attempts to load them, but because it can't access them due to permissions, they freeze and then force close. I'm rooted and have CWM installed, so I have ADB access. I'm using the UCLD2 ICS build, and my question is this:
I know that it's possible to change the permission of folders in the root folder using chmod, but I've had no luck with this so far.
Using ADB shell, and these are the commands that I've been using:
adb shell
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
chmod 755 /system/app
I've got it mounted, but when I chmod, it tells me "No such file or directory"
If I can change the permissions on the /system/app folder back to the way it was, my phone'll be fine, but right now, fixing permissions doesn't solve the problem, and I'm stuck in loop for now. Any thoughts would be appreciated. I've read through multiple forums and the closest I came to finding my problem was with the Kindle Fire forum, and I've been trying to carbon copy the solution from that forum. http://forum.xda-developers.com/showthread.php?t=1389728
Any help would be appreciated =)
Sorry for the post...I answered my own question. I rebooted recovery and restarted adb.
I ran this as follows:
adb root
adb remount
adb shell chmod 777 /system/app
This did it!
Sorry about the spam on the thread =)
I wanted to share my experience with following this thread
http://forum.xda-developers.com/showthread.php?t=1709296
i unfortunatly do not meet the 10 post limit
Following the process i got stuck here
Code:
Now it's time to reboot
adb reboot
After phones reboots
adb remount <-----------------HERE---------------------------
adb push su /system/xbin/su
adb shell chown 0.0 /system/xbin/su
adb shell chmod 06755 /system/xbin/su
adb shell rm /data/local.prop
adb reboot
ADB told me that i dod not have the correct permissions to push the SU file to the phone. The phone would boot, but would not load the widgets or bottom menu. Attempting to open settings would prompt Android.Core to crash.
Scary stuff
The problem was with the ADB Reboot command. It normally reboots the phone properly, but when i ran ADB Reboot, the phone cut power (off) instead of rebooting. Something did not go as intended and i needed to power on my phone, and reboot it manually without the USB cable connected (lagged too much).
After that, the ADB Remount was successful and the rest of the process ran smoothly. I am happily rooted
Thank you to all
~Can someone copy this into the actual thread? I want to help spread rootsauce.
hi .. i copied build.prop to sdcard , edited the one in system and it was ok , i replaced the one on sdcard back and restarted it didnt start (stucks on the logo thing)
i read this : http://forum.xda-developers.com/showthread.php?t=1927198
and followed the instructions but when i run "chmod 644 build.prop" i get :"no such file or directory"
same i tried to pull and push it , i got the same message when trying to pull
so i pulled from the sdcard and pushed to the system and restarted .. didnt work
i used these for pulling and pushing
Code:
adb root
adb remount
adb pull /sdcard1/build.prop
adb push build.prop /system/build.prop
adb shell chmod 644 /system/build.prop
adb reboot
i still don't know what to do and i hope you help me .. you'all are my last hope :\
note: i need to not wipe data