galaxy nexus 4.1.1 (JRO03C).
backed up & restored all apps and sdcard using GNex Toolkit v7.8.
after restoring, sdcard seems to be read-only, applications complain about "open failed: EACCES Permission denied" when trying to open files in /storage/sdcard0/... . tried remount, didn't help. directory permissions look fine to me.
what am i doing wrong?
how about trying to open /sdcard/?
and dont use a toolkit..
sent from my i9250
I bet you've done something on toolkit. I always backup and restore, but I have no problem at all
Can you install app from play store? If so, install root browser. It has a feature where you can change permission.
Swyped on my Galaxy Nexus running AOKP with Franco Kernel
bk201doesntexist said:
how about trying to open /sdcard/?
Click to expand...
Click to collapse
what do you mean by opening /sdcard ? the message above comes from an application which worked fine before backup-restore.
i can read files from /sdcard, it's just that the applications cannot write there.
e.g. camera does not work either.
kyokeun1234 said:
I bet you've done something on toolkit. I always backup and restore, but I have no problem at all
Can you install app from play store? If so, install root browser. It has a feature where you can change permission.
Click to expand...
Click to collapse
i've had this exact same problem twice in a row when restoring to two different nexuses (nexi?)
so i'm trying to find out what am i doing wrong.
yes, i can install applications. i already have ES file explorer installed; which permissions should I change? all permissions look fine to me.
All the permissions should be checked. I dunno about es file explorer, but on root browser, you'll have to check all the permissions like this
Swyped on my Galaxy Nexus running AOKP with Franco Kernel
op, have you tried fixing permissions in recovery?
sent from my i9250
kyokeun1234 said:
All the permissions should be checked. I dunno about es file explorer, but on root browser, you'll have to check all the permissions like this
Click to expand...
Click to collapse
mine permissions for /sdcard (/storage/sdcard0) are 775. is this a problem? it won't let me change them to 777...
bk201doesntexist said:
op, have you tried fixing permissions in recovery?
Click to expand...
Click to collapse
how do i do this? i've found this page: wiki.cyanogenmod.com/wiki/Fix_permissions (cannot post links), but running "fix_permissions" from terminal emulator gives me
Code:
[email protected]:/ $ su
[email protected]:/ # fix_permissions
sh: fix_permissions: not found
or do i have to boot into recovery first? (22 -> 4 from gnex toolkit)? how do i run terminal emulator then?
sorry, i'm really new with android..
qot said:
how do i do this? i've found this page: wiki.cyanogenmod.com/wiki/Fix_permissions (cannot post links), but running "fix_permissions" from terminal emulator gives me
Code:
[email protected]:/ $ su
[email protected]:/ # fix_permissions
sh: fix_permissions: not found
or do i have to boot into recovery first? (22 -> 4 from gnex toolkit)? how do i run terminal emulator then?
sorry, i'm really new with android..
Click to expand...
Click to collapse
boot into recovery, run the menus, but i think on cwm it's under Advanced > Fix permissions. wth? using a toolkit to BOOT into recovery? jeez... just power down the device, press vol up+vol down+power, select Recovery with vol keys, press start to boot into your currently installed recovery.
bk201doesntexist said:
boot into recovery, run the menus, but i think on cwm it's under Advanced > Fix permissions. wth? using a toolkit to BOOT into recovery? jeez... just power down the device, press vol up+vol down+power, select Recovery with vol keys, press start to boot into your currently installed recovery.
Click to expand...
Click to collapse
when I do this, i get a lying android with an exclamation mark in read triangle. is this "recovery"?
it does not seem to respond to any key, volume or power...
... somehow i got the following menu:
Code:
Android system recovery <3e>
Volume up/down to move highlight;
power button to select.
reboot system now
apply update from ADB
apply update from USB drive
wipe data/factory reset
wipe cache partition
which one should i select to fix permissions?
i've also found an app in play market called "fix permissions"
when i run it, i can select an application and it says "Permissions fixed, UIDs aligned".
however, nothing changes, sdcard is still not writable.
okay, you dont have a custom recovery installed. look for cwm latest non-touch, or twrp.
the stock recovery doesn't have this option.
is it only me or this is becoming quite freakin old very fast, we replying to "i used a toolkit to do"? i know this is q&a, but how in the hell how are we supposed to troubleshoot this?
i can only think of "redo things manually like it's supposed to." and to myself i think "witness the simplicity of command line interfaces and weep".
sent from my i9250
bk201doesntexist said:
okay, you dont have a custom recovery installed. look for cwm latest non-touch, or twrp.
the stock recovery doesn't have this option.
is it only me or this is becoming quite freakin old very fast, we replying to "i used a toolkit to do"? i know this is q&a, but how in the hell how are we supposed to troubleshoot this?
i can only think of "redo things manually like it's supposed to." and to myself i think "witness the simplicity of command line interfaces and weep".
Click to expand...
Click to collapse
i'd be glad to redo things manually, or whatever it takes to make sdcard writable again. this is really a nuisance.
i've downloaded "recovery-clockwork-6.0.1.0-maguro.img" and did the following from fastboot:
Code:
C:\Fastboot>fastboot devices
01498B0C1200F013 fastboot
C:\Fastboot>fastboot flash recovery recovery-clockwork-6.0.1.0-maguro.img
sending 'recovery' (4894 KB)... OKAY [ 0.703s]
writing 'recovery'... OKAY [ 0.757s]
finished. total time: 1.460s
C:\Fastboot>fastboot reboot
rebooting...
finished. total time: 0.006s
however, when i reboot into recovery again, i still get "Android system recovery <3e>"
am i doing something wrong?
I've also tried this with "fastboot flash recovery openrecovery-twrp-2.2.2.0-maguro.img" instead, no errors, same result.
check for /system/recovery-from-boot.p. is it there? rename it to recovery-from-boot.p.bak.
reflash recovery.
note: you can try 'fastboot boot recovery.img'.
sent from my i9250
bk201doesntexist said:
check for /system/recovery-from-boot.p. is it there? rename it to recovery-from-boot.p.bak.
Click to expand...
Click to collapse
yes, this worked. thanks!
however, even after i've installed twrp and ran "fix permissions", the problem remains exactly the same: applications complain about not being able to write to sdcard; camera does not work, etc. etc..
forget your data and start fresh manually by flashing factory images manually through fastboot.
sent from my i9250
It's not a permissions issue, it's an ownership issue...
If you have any directories/files that you can't modify or delete, then boot into CWM recovery, plug in the USB cable, go into adb shell. Also make sure that /data is mounted in the CWM mounts menu. Then:
cd /data/media
chown -R media_rw.media_rw *
danger-rat said:
It's not a permissions issue, it's an ownership issue...
If you have any directories/files that you can't modify or delete, then boot into CWM recovery, plug in the USB cable, go into adb shell. Also make sure that /data is mounted in the CWM mounts menu. Then:
cd /data/media
chown -R media_rw.media_rw *
Click to expand...
Click to collapse
yeah, thats it, i forgot. thanks.
sent from my i9250
danger-rat said:
It's not a permissions issue, it's an ownership issue...
If you have any directories/files that you can't modify or delete, then boot into CWM recovery, plug in the USB cable, go into adb shell. Also make sure that /data is mounted in the CWM mounts menu. Then:
cd /data/media
chown -R media_rw.media_rw *
Click to expand...
Click to collapse
that was it, thank you so much!
danger-rat said:
It's not a permissions issue, it's an ownership issue...
If you have any directories/files that you can't modify or delete, then boot into CWM recovery, plug in the USB cable, go into adb shell. Also make sure that /data is mounted in the CWM mounts menu. Then:
cd /data/media
chown -R media_rw.media_rw *
Click to expand...
Click to collapse
thanks a ton!
Related
Root from Paul didn't come with one, and seeing as we can't get full system access (from what i understand) im curious as to if we can actually get busybox?
The 'busybox on rooted desire' on MoDaCo didn't help at all.
I've installed bb via Titanium, yet Metamorph didn't recognise it anywhere.
Cheers in advance for help
It comes with A2SD - but you can push the busybox binary to /system while the phone is in recovery.
If you pushed bb yourself, use its absolute path (like /data/somewhere/busybox) or put its path in your $PATH to get it going. I personally, without root, put busybox in the free-to-write-to /sqlite* directory (I put * because I don't recall the full name) and it runs fine from there.
do you have a link to apps2sd & does it come with a guide as to how to install it so noobs can understand?
A2SD was taken down "temporarily".
http://android.modaco.com/content/h...ide-now-with-new-improved-easier-root-method/
Sorry
Although this still seems to work:
http://android.modaco.com/content/htc-desire-desire-modaco-com/307398/apps2sd-miniguide/
LeszekSwirski said:
Although this still seems to work:
http://android.modaco.com/content/htc-desire-desire-modaco-com/307398/apps2sd-miniguide/
Click to expand...
Click to collapse
Bare in mind I think it was taken down as (for some) it 'removed root' and also got some phones stuck in a reboot loop. Bad times.
GANJDROID said:
Root from Paul didn't come with one, and seeing as we can't get full system access (from what i understand) im curious as to if we can actually get busybox?
The 'busybox on rooted desire' on MoDaCo didn't help at all.
I've installed bb via Titanium, yet Metamorph didn't recognise it anywhere.
Cheers in advance for help
Click to expand...
Click to collapse
You didn't read to the end of that thread
* install Titanium
* run Titanium
* click the "problems" button and install Busybox
* boot into recovery
* adb shell from my Mac
* mount /system
* cp /data/data/com.keramidas.TitaniumBackup/files/busybox /system/bin
* cd /system/bin
* ./busybox --install -s .
Click to expand...
Click to collapse
By what I've read, though, Metamorph dies on its arse because of the lack of system rw access.
Loccy said:
You didn't read to the end of that thread
Click to expand...
Click to collapse
Aye, I read that, but no Mac, and I can't get to the folder where Titanium saved bb to (assuming that because it's not on the sd card in any data or the titanium folders) the phone system(?)
jayshah said:
Bare in mind I think it was taken down as (for some) it 'removed root' and also got some phones stuck in a reboot loop. Bad times.
Click to expand...
Click to collapse
Had heard about that, but I think he may be working for a solution?
From what I can remember from the rooting guide he said it was 'currently unavailable'
GANJDROID said:
Had heard about that, but I think he may be working for a solution?
From what I can remember from the rooting guide he said it was 'currently unavailable'
Click to expand...
Click to collapse
Yeah, hence it's hopefully only temporary.
GANJDROID said:
Aye, I read that, but no Mac, and I can't get to the folder where Titanium saved bb to (assuming that because it's not on the sd card in any data or the titanium folders) the phone system(?)
Click to expand...
Click to collapse
Install Titanium. Then get your phone into recovery using Paul's Linux ISO. In the Linux console (i.e. where you'll have typed ./step2.sh to get the recovery up), you should be able to do adb shell from there. Then follow my instructions from mount /system onwards.
I didn't follow Pauls guide as I only have access to Windows, so I used the lanarchy guide, which I think might have been taken from The Unlockr.
Maybe fill me in w/ bb according to that?
i am a bit ashamed to ask this but:
....
* boot into recovery
* adb shell from my Mac
* mount /system
....
boot into recovery -> ok
adb shell from mac.. ok? hm, i have macos as a seperate installation and i used it for rooting, so there is a pushfiles folder with recovery-mac.sh.. sudo ./recovery-mac.sh?
How do i mount /system then? Don't know where to navigate to find access to the sdcard . @volumes there are only my harddrive partitions, can't see the sdcard?
No idea, sorry, first time (ok, second time after root) i get in touch with adb, mac, sudo wtf?
Ok, all you need is some kind of environment where adb actually works.
Get your phone into recovery (the green menu screen) using whatever means or method you have.
Then, if you have Windows, you'll need the Android SDK. Ditto on a Mac. Anything with adb so that you can plug your device into your computer, do adb shell, and get a shell window up. Then
mount /system
onwards.
The key is that your phone needs to be in recovery before you do adb shell, otherwise you have no r/w access to /system.
ah! ok, perfect. The android sdk is on my windows computer, the push-files on my mac, that's the problem
thanks for your help!
the recovery is not the problem, but mount /system did nothing because there is no android sdk on my mac.. got it now i think.
mount system -> ok
copy busybok -> ok
when i try to install i get dozens of lines with "no such file or directory".
reboot -> phone not booting, hangs when displaying the HTC Logo omg
flash rom again?
same problem as watercool. Loads of "No such file or directory" messages.
But, I rebooted and it went through as normal, booted the OS fine.
hm, dont want to wipe again, pff..
flashed AhmgskMod mod again without wiping, everything ok now
watercool said:
mount system -> ok
copy busybok -> ok
when i try to install i get dozens of lines with "no such file or directory".
reboot -> phone not booting, hangs when displaying the HTC Logo omg
flash rom again?
Click to expand...
Click to collapse
Sounds like you missed the . off of the end of the
./busybox --install -s .
command.
You need that . if you're following my instructions.
ok, i did it with and without the "."
With the dot there was no response (so probably it installed correctly?).
Anyway it didn't boot afterwards. i will try it again
edit: ok, tried again and my phone stucks @ htc screen
i think busybox is installed but for some reason it doesn't boot (using the ahmgsk mod)
anyway, thanks for your kind help!
I'm trying to remove some preinstalled apps from /system/app folder. My phone is rooted.
When I'm trying this over adb it says that I only have Read permissions. What am I doing wrong?
Put the phone into recovery mode then do the adb commands.
You only have read access while booted. R/W access while in recovery.
Mh I tried this but I couldn't even open the shell, said something.sh is missing.
You mean the normal recovery and not Clockworkmod or something, right?
You have to put it in the custom recovery. Clockworkmod or whichever one you use.
Ah okay, thank you, I will try that.
Though I need to use the normal recovery.
I tried it with clockwork now. It works but when I do "cd system" and do "ls" it's empty...so I can't see any app-folder?!
Edit: Oh I forgot - do I need to mount system first using the partitions menu?!
Eggcake said:
I tried it with clockwork now. It works but when I do "cd system" and do "ls" it's empty...so I can't see any app-folder?!
Edit: Oh I forgot - do I need to mount system first using the partitions menu?!
Click to expand...
Click to collapse
Code:
mount /system
At the adb shell.
Oy, thanks now I finally got it
Remove worked, pull didn't (or it took >5min for a simple apk file and I aborted it too early).
Hello All,
I just updated my ROM to CR_Mod_2.13.531.1_OTA's
And then when I went to reboot into recovery I got the red Triangle exclamation, and thus decided to reflash my recovery image by using the terminal, and even in adb, I get "Flash_image" command not found, and I've tried googling (So please spare me the rude comments about learning to use it) and come with little to luck with finding a method of what went wrong with this. If anyone can shed some light on this, and what I can do to fix it so I can get into my recovery again would be a great help.
-Thanks
soulysephiroth said:
Hello All,
I just updated my ROM to CR_Mod_2.13.531.1_OTA's
And then when I went to reboot into recovery I got the red Triangle exclamation, and thus decided to reflash my recovery image by using the terminal, and even in adb, I get "Flash_image" command not found, and I've tried googling (So please spare me the rude comments about learning to use it) and come with little to luck with finding a method of what went wrong with this. If anyone can shed some light on this, and what I can do to fix it so I can get into my recovery again would be a great help.
-Thanks
Click to expand...
Click to collapse
same here friend when i find teh answer ill be sure to let u know
so when in terminal to try place Flash_image into /system/bin:
cp /sdcard/flash_image /system/bin
I get:
cp: can't create ' /system/bin/flash_image ' cannot allocate memory
When you get to the triangle with the Exclamation point
All you have to do is stay at that screen and click
VOLUME UP and POWER
then it will show you the options.
soulysephiroth said:
so when in terminal to try place Flash_image into /system/bin:
cp /sdcard/flash_image /system/bin
I get:
cp: can't create ' /system/bin/flash_image ' cannot allocate memory
Click to expand...
Click to collapse
You have to have s-off and /system mounted as r/w to do that. Otherwise you have to push it to /system/bin while in clockwork recovery.
@ xologist, I think they're looking to flash the clockwork recovery image, not the update.zip and stock recovery old way.
To mount system r/w within android tyoe mount -o rw,remount /system and try the copy again.
Sent from my T-Mobile myTouch 3G Slide
Well thats problem, I can't even access my recovey, thats why I'm trying to flash a new image. everytime I try I always get
"Error writing recovery: No space left on device"
soulysephiroth said:
Well thats problem, I can't even access my recovey, thats why I'm trying to flash a new image. everytime I try I always get
"Error writing recovery: No space left on device"
Click to expand...
Click to collapse
That means you don't have s-off. There's a stickied thread in the development section, an alpharev live linux CD that you can use to patch your phone's bootloader to allow you to write to protected partitions like /system, recovery, etc.
I have rooted my HTC One X and want to copy files in /system/xbin folder. My phone shows S-ON. And Eclipse is not able to copy files to /system and adb push from shell is also not working. Is there a way I can copy files to /system/xbin?
I am running stock ROM.
My phone is NOT associated with any vendor.
adb remount
adb push filename /system/xbin
Sent from my HTC One X
You can also use es file explorer and go into the options tick up to root and the request root and then tick mount as r/w.
Then just move files as you will.
Sent from my HTC One X using XDA Premium HD app
realunited123 said:
adb remount
adb push filename /system/xbin
Sent from my HTC One X
Click to expand...
Click to collapse
The above way does not seem to work. Whenever I use adb remount(or adb mount) it says operation not permitted and I am trying to this from root privileges
My OS is :- Ubuntu 12.04
ADB(platform-tools) -> Rev 20
If you need anything more please ask me .
Additional Question
treebill said:
You can also use es file explorer and go into the options tick up to root and the request root and then tick mount as r/w.
Then just move files as you will.
Sent from my HTC One X using XDA Premium HD app
Click to expand...
Click to collapse
First of all thanx it worked. I think I will have to live with this way A ADB/Eclipse based would have been cool
Will the files moved from SDcard to phones root in anyway lose and privileges(like losing executable)? If yes, please suggest a way to restore it.
KillerTheLord said:
The above way does not seem to work. Whenever I use adb remount(or adb mount) it says operation not permitted and I am trying to this from root privileges
My OS is :- Ubuntu 12.04
ADB(platform-tools) -> Rev 20
If you need anything more please ask me .
Click to expand...
Click to collapse
When doing adb shell su do you get any toast notification on your phone? Or does it just say denied ?
Strange it works perfectly here Also are you using SuperSU or any other superuser app?
---------- Post added at 03:37 PM ---------- Previous post was at 03:36 PM ----------
KillerTheLord said:
First of all thanx it worked. I think I will have to live with this way A ADB/Eclipse based would have been cool
Will the files moved from SDcard to phones root in anyway lose and privileges(like losing executable)? If yes, please suggest a way to restore it.
Click to expand...
Click to collapse
Yes you need to change the permissions after moving from sdcard. Use Root Explorer(Long press on the file--> Change permissions)
realunited123 said:
When doing adb shell su do you get any toast notification on your phone? Or does it just say denied ?
Strange it works perfectly here Also are you using SuperSU or any other superuser app?
---------- Post added at 03:37 PM ---------- Previous post was at 03:36 PM ----------
Yes you need to change the permissions after moving from sdcard. Use Root Explorer(Long press on the file--> Change permissions)
Click to expand...
Click to collapse
I am using SuperSU as Super User App. And I think I am doing something wrong here. You mentioned about adb shell su. I think I might be wrong here. Here is how I tried to execute the command.
[email protected]: <path to platformtools> ./adb remount
remount failed: Operation not permitted
do I have to raise ADB shell to SU level. If yes, how?
KillerTheLord said:
I am using SuperSU as Super User App. And I think I am doing something wrong here. You mentioned about adb shell su. I think I might be wrong here. Here is how I tried to execute the command.
[email protected]: <path to platformtools> ./adb remount
remount failed: Operation not permitted
do I have to raise ADB shell to SU level. If yes, how?
Click to expand...
Click to collapse
Strange. Are you using the stock kernel ? If that is the case then it does not have insecure adbd (ro.secure=0) so remount will not work. Try a custom kernel.
Does adb has SU permissions from recovery ? Try booting into recovery, mounting the system partitions and try to push something from adb. Check the SuperSU app to update binary but that should not be a problem.
realunited123 said:
Strange. Are you using the stock kernel ? If that is the case then it does not have insecure adbd (ro.secure=0) so remount will not work. Try a custom kernel.
Does adb has SU permissions from recovery ? Try booting into recovery, mounting the system partitions and try to push something from adb. Check the SuperSU app to update binary but that should not be a problem.
Click to expand...
Click to collapse
Yes I have rooted the phone but the ROM is stock(I was thinking to put in CM9 Alpha).
About the second thing. I know how to boot my phone into recovery(Vol Down + Power -> From Screen -> Recovery(ClockwerkMod))
But about the rest I don't know.
Sorry about my annoying questions this is my first time I am dealing with rooting and stuff.
KillerTheLord said:
Yes I have rooted the phone but the ROM is stock(I was thinking to put in CM9 Alpha).
About the second thing. I know how to boot my phone into recovery(Vol Down + Power -> From Screen -> Recovery(ClockwerkMod))
But about the rest I don't know.
Sorry about my annoying questions this is my first time I am dealing with rooting and stuff.
Click to expand...
Click to collapse
I guess you are using stock kernel then. Try franco's or faux's kernel.
adb remount wont work from os on stock boot.img.
After rebooting into recovery go to mounts and storage-->mount /system and then push something from adb. See if that works.
KillerTheLord said:
Yes I have rooted the phone but the ROM is stock(I was thinking to put in CM9 Alpha).
About the second thing. I know how to boot my phone into recovery(Vol Down + Power -> From Screen -> Recovery(ClockwerkMod))
But about the rest I don't know.
Sorry about my annoying questions this is my first time I am dealing with rooting and stuff.
Click to expand...
Click to collapse
I think this app does exactly what you want :
http://forum.xda-developers.com/showthread.php?t=1687590
realunited123 said:
I guess you are using stock kernel then. Try franco's or faux's kernel.
adb remount wont work from os on stock boot.img.
After rebooting into recovery go to mounts and storage-->mount /system and then push something from adb. See if that works.
Click to expand...
Click to collapse
Well this didn't work either. I hope to switch to some other ROM in future(I hate HTC Sense ). But as of now Root Explorer did the job. I mounted my sdcard and copied files to it and used Root Explorer to move files to /system and then changed permissions.
Thanks for help it really made it easy .
make sure your path devs are oke for su.
in terminal run:
sudo su
adb kill-server
adb devices
you should see your HOX HTxxxxx nr.
and here you should be able to connect eclipse to HOX by adb.
NikMel said:
make sure your path devs are oke for su.
in terminal run:
sudo su
adb kill-server
adb devices
you should see your HOX HTxxxxx nr.
and here you should be able to connect eclipse to HOX by adb.
Click to expand...
Click to collapse
The problem was not accessing the device using ADB. The problem was I was not able to write to root system. ES Explorer and Root Explorer both did the job for me. I will be putting the final instructions for the process(detailed ones) soon.
Instructions onw how to copy files to root file system on HTC One X with S-ON
1) Unlock and Root your phone. Follow instructions below
http://www.youtube.com/watch?v=gIeq8Jx28cs
and then
http://www.youtube.com/watch?v=80lMHUgxwww
2) Install ES Explorer(File Manager) Link :- https://play.google.com/store/apps/details?id=com.estrongs.android.pop&hl=en
3) Connect device to computer(even if it is not recognized by ADB/Computer)
4) In Phone select Disk drive option. Now the phone's storage will be mounted on your computer as removable device.
5) Copy the files you want to send to phone's root system to any folder here.
6) Change phone's mode to charge only and wait for 2-3 secs(let phone remount sdcard)
7) Open ES Explorer and open menu(those 3 dots at bottom and select Settings)
8) Tick the following options
Up to Root
Root Explorer
Mount File System
9) A dialog box for permission will open Grant it.
10) Now copy files from /sdcard/<Folder where u put files> to where ever you want o copy files to.
11) Long press on file to change permissions and stuff.
Post here if you are stuck someone will surely help you.
My phone is on 4.1.2 still, and I had edited the build.prop to not update to 4.2 (after hearing all the problems). Now that 4.2.2. is out i decided to update, I tried restoring the build.prop file that i had as a backup of 4.1.2. I guess I must've changed some text without realizing.
Now my phone is stuck, it gives me the Google Logo with the unlocked sign, and then it disappears...and where there should be a boot animation...black. Nothing. Stays like that.
Any way I can push the build.prop via the computer using abd or something?
Not sure if adb will push to system, since i had an issue pulling from system.
Are you rooted?
You could try booting to recovery to enable adb, then remount system as r/w
adb shell
su
mount -o remount,rw -t ext4 /dev/block/mmcblk0p1 /system
cd /system/ NOT SURE IF THIS IS REQUIRED, I'D TRY IT FIRST WITHOUT THIS LINE TO SEE
chmod 644 build.prop
chown root.root build.prop
exit
I've never had to do that, but i belive my linux syntax is correct, i pulled it from http://www.linux.org/article/view/file-permissions-chown. This is only of course if the build.prop failed bc on the incorrect permissions and ownership(maybe you had it on your sdcard). If this doesn't work, it looks like you'll be fastboot flashing a system image. [Sometimes the time and date of your build.prop may affect the ability to ota even if you get it to boot, to which you would need to reflash the system image anyway]. But i'd like to know if you try this and it works.
So what I ended up doing was installing clockwork recovery and then installing an odexed Rom version of the stock image of 4.1.2. Everything works, nothing got wiped.
Sent from my GT-N7100 using xda app-developers app
bodh said:
Not sure if adb will push to system, since i had an issue pulling from system.
Are you rooted?
You could try booting to recovery to enable adb, then remount system as r/w
adb shell
su
mount -o remount,rw -t ext4 /dev/block/mmcblk0p1 /system
cd /system/ NOT SURE IF THIS IS REQUIRED, I'D TRY IT FIRST WITHOUT THIS LINE TO SEE
chmod 644 build.prop
chown root.root build.prop
exit
I've never had to do that, but i belive my linux syntax is correct, i pulled it from http://www.linux.org/article/view/file-permissions-chown. This is only of course if the build.prop failed bc on the incorrect permissions and ownership(maybe you had it on your sdcard). If this doesn't work, it looks like you'll be fastboot flashing a system image. [Sometimes the time and date of your build.prop may affect the ability to ota even if you get it to boot, to which you would need to reflash the system image anyway]. But i'd like to know if you try this and it works.
Click to expand...
Click to collapse
Yes, you need to 'cd /system' before typing the commands to change permissions and ownership, as you have them.
Sent from my Nexus
ksc6000 said:
So what I ended up doing was installing clockwork recovery and then installing an odexed Rom version of the stock image of 4.1.2. Everything works, nothing got wiped.
Sent from my GT-N7100 using xda app-developers app
Click to expand...
Click to collapse
How did you install clockwork recovery when it was not booting at all ??! Could you please guide me ? I actually have an LG Optimus G stuck in boot loop ..... (T_T)
Claureid said:
How did you install clockwork recovery when it was not booting at all ??! Could you please guide me ? I actually have an LG Optimus G stuck in boot loop ..... (T_T)
Click to expand...
Click to collapse
Then you should go to your own forums, as 99% of the info here wont do you any good
Claureid said:
How did you install clockwork recovery when it was not booting at all ??! Could you pbootlease guide me ? I actually have an LG Optimus G stuck in boot loop ..... (T_T)
Click to expand...
Click to collapse
I don't think you can do that with your phone what I did. But here is the gu ide that I used to temporarily boot into clockwork recovery to use it:
http://forum.xda-developers.com/showpost.php?p=23229578&postcount=3
ksc6000 said:
I don't think you can do that with your phone what I did. But here is the gu ide that I used to temporarily boot into clockwork recovery to use it:
http://forum.xda-developers.com/showpost.php?p=23229578&postcount=3
Click to expand...
Click to collapse
Thanked you buddy !!