So I was trying to change some icons..
wanted to use ninja morph
the icons are in the framework.apk
so i backed it up frist by copying it to another location in root explorer
worked fine
then i tried to rename it worked fine
the i tried moving the renamed copy somewhere else and everything froze
couldnt do anything
had to do battery pull
now im stuck on X
at boot
i can still get into bootloader but adb remount is saying device not found
i dont wanna do nand restore havent backup since like
3 weeks ago
any ideas?
push the old framework back?
try adb shell if you can't remount, you may be able to issue mv commands with su
Solved. Thanks!
Anyone wanna help? -.-
xGary said:
So I did some modding (unfortunately) to the framework-res.apk file and it worked the first time and a few other times but then I changed something and now when I turn on the phone it freezes at the "Sony Ericsson" screen before the logo. What do I do?
I tried pushing the backup framework file but it says "failed to copy framework-res.apk to /sdcard/framework-res.apk: Permission denied
however, when I use adb devices, it does show my device as being attached.
So what can I do now?
Edit
I was also able to pull files...
Also tried manually putting the framework-res.apk in the sdcard and then using adb to copy it to the framework folder. Doesnt work. Saids that the directory cannot be open for read. I guess the device cant read the SD card until it boots up
Also, if you are replying, please stay on the thread. I will probably comment back ASAP
Click to expand...
Click to collapse
Hey... are you sure that you've got your phone rooted? I mean sure pulling files work irrespective if you are rooted or not, but in order to replace files under the /system filesystem you've gotta have root and remount it as read/write.
Happen to me too, for the exact same reason. I had to reformat the phone... I simply re-rooted the damn phone.
cp /system/bin/sh /system/bin/rootsh
chmod 6755 /system/bin/rootsh
Try using this script before trying to push your framework back on
Well it was rooted and I already flashed it and re rooted it. However, I have three questions
1) Should I update from the v24 to 26?
2) I have a x10a, after running step 3 my phone still says its an x10i with baseband version of 1.1.28
3) And those apps that were supposed to be installed in step 2 didnt go so well. I could install them manually with ADB right?
This is the second time I tried to root it. I can only get temp Root but once i reset and gfree_verify and type #su on command prompt i get permision denied.....
The only thing i can think of that was out of the ordinary was when I try to lock in root and get "mkdir: /system/xbin already exists" On the guide it said not to worry about that.....
Any help or tip would be great.
Desire Z (Bell) flashed with generic rom (goldcard method)
Simunlocked on ATT
Was your SD card unmounted from Windows?
Best thing really is just to start over step by step slowly. The method works (did for me) so simplest explanation is a small mistake somewhere...
Paste the full message. The message is okay if it says that xbin is a directory, but one time I had xbin turn into a binary file for some reason(I was told it was because of VISIONary).
The message you will get is on the lines of "xbin not a directory" or something.
If so, then before using ADB push to send the rooting script, edit the rooting script(I don't know if notepad will recognize the line endings):
Change:
Code:
#set up busybox
mkdir /system/xbin
To:
Code:
#set up busybox
mv /system/xbin xbin.bak
mkdir /system/xbin
Do note that my experience is with the G2.
Thanks for all the help. It turns out my phone was rooted but gfree_verify seems to be not working.
Installed a Rooted app and realized it was rooted lol.
Now runing CM7 nightly Best **** ever. Finally getting more than 12 hours of battery life.
I recently rooted my android (Nexus 4). I wanted to make /system folder permissions 777, I needed that for another application. I got Root Explorer application, and changed permissions to 777. Then root folder disappeared and hanged up. I tried to restart my phone, but now it doesn't even boot up. What should I do? ... Please, don't tell me I bricked my phone.. It was just permissions, nothing more... I have no idea how to recover now.
When I do
Code:
adb shell
in my PC console, I also get mesaage:
Code:
/system/bin/sh: /system/etc/mkshrc[9]: getprop: can't execute: Permission denied
Also I can't go to root mode (adb root) in console, from $ to #.. so it means.. I even can't change permissions anymore?
just curious...what app required you to change the system folder permission to 777?
Cracken6 said:
I recently rooted my android (Nexus 4). I wanted to make /system folder permissions 777, I needed that for another application. I got Root Explorer application, and changed permissions to 777. Then root folder disappeared and hanged up. I tried to restart my phone, but now it doesn't even boot up. What should I do? ... Please, don't tell me I bricked my phone.. It was just permissions, nothing more... I have no idea how to recover now.
When I do
Code:
adb shell
in my PC console, I also get mesaage:
Code:
/system/bin/sh: /system/etc/mkshrc[9]: getprop: can't execute: Permission denied
Also I can't go to root mode (adb root) in console, from $ to #.. so it means.. I even can't change permissions anymore?
Click to expand...
Click to collapse
Flash the system.img from the version of android you're on with fastboot.
Sent from my Nexus 5 using XDA Free mobile app
metpage said:
just curious...what app required you to change the system folder permission to 777?
Click to expand...
Click to collapse
I wanted to make custom boot loading animation. So I found Boot animation app. But I couldn't install any animations because of permissions on /system/media (read-only). I tried manually, and same. So I did little research, found that one guy set system to 777. Tried to do same, but hanged my phone, and after restart, couldn't boot it up.
I just fixed it. Successfully Flashed my ROM to original 5.0.1. And now I can put files in /system/media, I don 't know how that fixed itself.. but now it works and I have also custom loading screen.
Ty!
after ROOTING Nougat 32.3.A.0.376 (E6833 E6853 E6883) (E6633 E6653 E6683 ), we will still face ERROR while removing system apps, because GOOGLE has changed file system properties in Android N to READ ONLY
in order to make system directory WRITABLE, install busybox, and terminal,
type these lines and enter one by one in #terminal
Code:
su
mount -o rw,remount /system
ORRR
Code:
su
busybox mount -o rw,remount,rw /system
-----------
What???
Why ??? I still can not write anything on the SYSTEM partition
I have full ROOT access and everything , no reboot or error issue !!
Please share if you find any solution to that
chinmoy32 said:
Why ??? I still can not write anything on the SYSTEM partition
I have full ROOT access and everything , no reboot or error issue !!
Please share if you find any solution to that
Click to expand...
Click to collapse
Mee too unable to write on system
download terminal on google play
open terminal
write "su" command and give root permission
then you will see "#"
after that, write this command:
Code:
echo 0 > /sys/kernel/security/sony_ric/enable
then you write this command:
Code:
mount -o rw,remount /system
if you see "#" again, it worked
but if you see "mount: Operation not permitted" it has not, sorry
Credits: https://forum.xda-developers.com/showpost.php?p=70677335&postcount=92
I did what @serajr described here:
https://forum.xda-developers.com/xp...-kernel-dm-t3301605/post70595975#post70595975
works like a charm, system always writable!
Can any of you share here your perfectly rooted working kernel for Z5 E6683 DSDS ????
chinmoy32 said:
Why ??? I still can not write anything on the SYSTEM partition
I have full ROOT access and everything , no reboot or error issue !!
Please share if you find any solution to that
Click to expand...
Click to collapse
i found a workaround and it goes
installing busybox
installing terminal
and writing following codes
Code:
su
'to give terminal root access
busybox mount -o rw,remount /system
later using ROOT APP REMOVER i manage to remove all bloatware!
toncheee said:
I did what @serajr described here:
https://forum.xda-developers.com/xp...-kernel-dm-t3301605/post70595975#post70595975
works like a charm, system always writable!
Click to expand...
Click to collapse
@serajr workaround was fo when rootkernel4.51 wasn't able to support Nougat kernel
however if you follow carefully, the lines mentioned
Code:
on post-fs
export LD_PRELOAD libNimsWrap.so:libdrmfix.so
and
Code:
write /sys/kernel/security/sony_ric/enable 0
will switchoff SONYRIC and will fix DRM
the issue is NOT sony RIC,
Google in general with or without any security/rootaccess changed the system folder properties from default Writable in <+ 6.01 Android version to READABLE ONLY from android 7.xx
so when i followed the both method of altering file via notepad++ in the ramdisk folder using N kernel and rootkernel version4.5, I ended up having fully root system with READLY ONLY ACCESS to /system partition and i could only switchoff the apps but can't remove!
YasuHamed said:
@serajr workaround was fo when rootkernel4.51 wasn't able to support Nougat kernel
however if you follow carefully, the lines mentioned
Code:
on post-fs
export LD_PRELOAD libNimsWrap.so:libdrmfix.so
and
Code:
write /sys/kernel/security/sony_ric/enable 0
will switchoff SONYRIC and will fix DRM
the issue is NOT sony RIC,
Google in general with or without any security/rootaccess changed the system folder properties from default Writable in <+ 6.01 Android version to READABLE ONLY from android 7.xx
so when i followed the both method of altering file via notepad++ in the ramdisk folder using N kernel and rootkernel version4.5, I ended up having fully root system with READLY ONLY ACCESS to /system partition and i could only switchoff the apps but can't remove!
Click to expand...
Click to collapse
I also think the issue is not the RIC but something to do with the Nougat filesystem itself.
I can delete all the files and folders with any file managers I like but like after 1 sec they all reappear as nothing ever happened to them !!!
How strange is that ??
It shows file sizes when I delete them and take times to delete the folders with , say for 500MB
but they still reappear after just 1 refresh or 1 sec.
I cant figure it out at all for the sake of my sanity --- why the hell this is happening ????
https://www.dropbox.com/sh/2kf8wg3g13pv869/AACB3l8iPJHJnBlpnGorRqrha?dl=0
@bungadudu @chinmoy32
I followed bungadudu-s steps and it worked i can change permissions and prove it with link i provided.
And chenges, yes they stick after reboot and i can rename files allso, but:
after reboot i have to repeat this steps if i want to change something elsewhere, old changes do stick aroind though
I deletet phone to 0 mb in twrp, flashed AU nougat .372 with flashtool, rebooted into twrp, flashed zip file provided in link, then flashed supersu in link and rebooted, no custom kernel used
Next i will try to copy modified thermal files now and see if they stick after reboot and if kernel aduitor uses them, see you later
Observations:
-i changed permissions from file /system/build.prop and changed lcd density to 320 and i have bootloop
working on how to boot it up...
YasuHamed said:
after ROOTING Nougat 32.3.A.0.372 (e6833 e6853 e6883) (E6633 E6653 E6683 ), we will still face ERROR because GOOGLE has changed file system properties in Android N to READ ONLY
in order to make system directory WRITABLE, install busybox, and terminal,
type these lines and enter one by one in terminal
Code:
su
busybox mount -o rw,remount /system
-----------
Click to expand...
Click to collapse
Please share the exact name / way to install busybox and terminal
i.e. which version of busybox I need to install from where ?? Which terminal app you used ?? if possible please share the links
https://www.dropbox.com/s/d9ie598b618feiz/recovery.log?dl=0
i managed to get somesort of log from twrp in link from previous post will this sufice?
i am reflashing my phone so i can not look at versions, for now i used:
when i reboot it i can look into busybox version
SR3-SuperSU-v2.79-SR3-20170114223742, on top of that i installed pro:
https://play.google.com/store/apps/details?id=eu.chainfire.supersu.pro
busyboxpro
https://play.google.com/store/apps/details?id=stericson.busybox.donate
terminal from romtoolbox pro:
https://play.google.com/store/apps/details?id=com.jrummy.liberty.toolboxpro
those are some apps i support so i dot know if it makes a diference from non paid
chinmoy32 said:
Please share the exact name / way to install busybox and terminal
i.e. which version of busybox I need to install from where ?? Which terminal app you used ?? if possible please share the links
Click to expand...
Click to collapse
chinmoy32 said:
Please share the exact name / way to install busybox and terminal
i.e. which version of busybox I need to install from where ?? Which terminal app you used ?? if possible please share the links
Click to expand...
Click to collapse
I install both of them via play.google.com
https://play.google.com/store/apps/details?id=stericson.busybox&hl=en
&
https://play.google.com/store/apps/details?id=jackpal.androidterm&hl=en
later i opened terminal and ran those commands
later i installed System App remover
https://play.google.com/store/apps/details?id=com.jumobile.manager.systemapp&hl=en
granted it SU rights and removed HANGOUTS and GOOGLE MOVIES etc
It seems to work to some extend but if you want to go tweak it up, kablaaam
i did not managed to boot it up after bootloop sadly, i need my phone so this is it for me this week
stipi69 said:
https://www.dropbox.com/s/d9ie598b618feiz/recovery.log?dl=0
i managed to get somesort of log from twrp in link from previous post will this sufice?
i am reflashing my phone so i can not look at versions, for now i used:
when i reboot it i can look into busybox version
SR3-SuperSU-v2.79-SR3-20170114223742, on top of that i installed pro:
https://play.google.com/store/apps/details?id=eu.chainfire.supersu.pro
busyboxpro
https://play.google.com/store/apps/details?id=stericson.busybox.donate
terminal from romtoolbox pro:
https://play.google.com/store/apps/details?id=com.jrummy.liberty.toolboxpro
those are some apps i support so i dot know if it makes a diference from non paid
Click to expand...
Click to collapse
I just clean install 372 and patched the kernel once again .................
tried the terminal commands ---- both commands were successful (without any errors )
but still the deleted apps and the edited files came back to normal as before
I did not manage to delete anny apps as my phone crashed before, i am glad you get commands to work.
oh, by the waj roomtoolbox is great as you can make shortcuts of the commands and then you klik it one after another and you get rid of the typing
example (first shortcut command depends of busybox install folder i think)
1.st shortcut "cd /su"
2.nd shortcut "su"
3.rd shortcut "echo 0 > /sys/kernel/security/sony_ric/enable"
4.th shortcut "mount -o rw,remount /system"
that way some people can do this quick and you dont need to remember commands, and you can experiment quicker.
sorry i dont know howto annything else for now
chinmoy32 said:
I just clean install 372 and patched the kernel once again .................
tried the terminal commands ---- both commands were successful (without any errors )
but still the deleted apps and the edited files came back to normal as before
Click to expand...
Click to collapse
stipi69 said:
I did not manage to delete anny apps as my phone crashed before, i am glad you get commands to work.
oh, by the waj roomtoolbox is great as you can make shortcuts of the commands and then you klik it one after another and you get rid of the typing
example (first shortcut command depends of busybox install folder i think)
1.st shortcut "md /su"
2.nd shortcut "su"
3.rd shortcut "echo 0 > /sys/kernel/security/sony_ric/enable"
4.th shortcut "mount -o rw,remount /system"
that way some people can do this quick and you dont need to remember commands, and you can experiment quicker.
sorry i dont know howto annything else for now
Click to expand...
Click to collapse
I just managed to restart my phone successfully after changing the LCD density to 320 [I also use this value since always ]
But then I carefully just deleted 1 single app and booom--- boot loop
PS. i used root explorer to just click mount as R/W and then do anything to system partition --
Great you magaged it, and yes 320 seems so right.
And i asume there is no way to break bootloop?...other than reflashing?
I had trouble afterwards on downgrading to.253, 3x times error on start, even after reseting " power & + " and couple of full wipes in twrp.
I had to flash lineage from twrp and boot it up and only then flashtool succeeded pushing. 253.
This nougat will be fun i see
If there is something to try tell me i will flash it once more tonight, otherways i can do it on weekends
Oh i did not tell, i managed to copy modified thermal files with no error and then changed lcd density so i can not 100% tell which caused bootlop, since i did not reboot in between...
chinmoy32 said:
I just clean install 372 and patched the kernel once again .................
tried the terminal commands ---- both commands were successful (without any errors )
but still the deleted apps and the edited files came back to normal as before
Click to expand...
Click to collapse
there is another way which i did not try because the busybox commands worked for me
its about flashsing updater script
delete_recursive(
"/system/app/GoogleAnalyticsProxy",
"/system/priv-app/GoogleBackupTransport",
"/system/priv-app/textinput-chn-xxhdpi",
);
https://forum.xda-developers.com/showpost.php?p=70920831&postcount=2015