Hi all,
I have gained temp root access on a japan phone, able to obtain rw access to all files & folders except /system. Edited default.prop file on ro.secure and ro.debuggable to 0 & 1, did setenforce to permissive but still unable to write on /system getting mount: permission denied, is there any advice anyone can give please?
On a seperate issue, this phone does not have fastboot or recovery mode, attempted to dd a modified boot.img to the dev/block/xxxxxxxxxx folder of where the original boot.img was resulting a bootloop, wondering under normal circumstances when there is no fastboot or recovery mode, dd a boot.img should achieve the same flash result of using fastboot?
Thanks in advance!
Hello and thank you for using XDA Assist,
please ask in our Q&A section:
Android Q&A, Help & Troubleshooting
The experts there know the best and should be able to help you!
Kind regards and good luck
Trafalgar Square
XDA Assist
Related
hi
i have rooted the phone using recovery method and install superSu ,thing went successfull but i want to change the file permission of /system/bin/playlpm file using Android Commander it is not happening
please help i have wasted 2 days for this on Google but didn't find anything
thanks,
jitu89 said:
hi
i have rooted the phone using recovery method and install superSu ,thing went successfull but i want to change the file permission of /system/bin/playlpm file using Android Commander it is not happening
please help i have wasted 2 days for this on Google but didn't find anything
thanks,
Click to expand...
Click to collapse
What about using another root explorer app?
(E.g. Root Explorer, ES File Manager, etc.)
Keep in mind that you have to enabe root features in the explorer app itself and grant it root permissions in SuperSU app.
In some root explorer apps, you have to mount system partition as R/W (read/write) before you are able to change something in there.
For further questions, please ask in the Galaxy Star Q&A, Help & Troubleshooting forum.
It_ler said:
What about using another root explorer app?
(E.g. Root Explorer, ES File Manager, etc.)
Keep in mind that you have to enabe root features in the explorer app itself and grant it root permissions in SuperSU app.
In some root explorer apps, you have to mount system partition as R/W (read/write) before you are able to change something in there.
For further questions, please ask in the Galaxy Star Q&A, Help & Troubleshooting forum.
Click to expand...
Click to collapse
I don't understand if i have rooted the phone and i am using adb shell to change the permission of the file system/bin/playlpm i can't do that event i try to mount R/W system form adb shell it doesn't happen .
I am new to all this please Kindly show the right way to me .I do not want to do by app .tell me how to mount read/write permission by adb shell .
I have rooted the phone and install the superSu and Enable SuperUser permission in the app
i Am stuck Help will be appreciated
Thank you
jitu89 said:
I don't understand if i have rooted the phone and i am using adb shell to change the permission of the file system/bin/playlpm i can't do that event i try to mount R/W system form adb shell it doesn't happen .
I am new to all this please Kindly show the right way to me .I do not want to do by app .tell me how to mount read/write permission by adb shell .
I have rooted the phone and install the superSu and Enable SuperUser permission in the app
i Am stuck Help will be appreciated
Thank you
Click to expand...
Click to collapse
Ok, here is a guide about adb shell: [GUIDE][ADB]Easiest How to use adb, logcat, etc for noobs and newbies.
And here are some useful shell commands: [GUIDE] Basic Unix/Linux command to use with ADB SHELL.
Including chmod, example "chmod 755 /system/tmp/root.sh".
Make sure to got into root mode with "su" before.
And here is a nice guide of a friend of mine about the different file permissions: [Guide]Noob Guide To Set File Permission's [28-08-2012].
It_ler said:
Ok, here is a guide about adb shell: [GUIDE][ADB]Easiest How to use adb, logcat, etc for noobs and newbies.
And here are some useful shell commands: [GUIDE] Basic Unix/Linux command to use with ADB SHELL.
Including chmod, example "chmod 755 /system/tmp/root.sh".
Make sure to got into root mode with "su" before.
And here is a nice guide of a friend of mine about the different file permissions: [Guide]Noob Guide To Set File Permission's [28-08-2012].
Click to expand...
Click to collapse
Hi ,
I have just deleted the file system/bin/playlpm file form the device using adb shell
And i Trying to push my own custom play lpm file to the location system/bin
but it show "permission denied"
This is the Command i am using ----> adb push playlpm /system/bin
jitu89 said:
Hi ,
I have just deleted the file system/bin/playlpm file form the device using adb shell
And i Trying to push my own custom play lpm file to the location system/bin
but it show "permission denied"
This is the Command i am using ----> adb push playlpm /system/bin
Click to expand...
Click to collapse
Please post your question in one of the threads I have linked in my previous answer.
There you will hopefully get proper help.
My tapatalk signature:
Device: SGS5 (SM-G900F)
ROM: AllianceROM v5.6
Kernel: Stock G900FXXU1ANG2
Recovery: TWRP by Ktoonsez
Modem: G900FXU1ANG7
If you have any question about or any issue with your SGS2, just ask in the New members friendly Q&A thread.
... for the SGS5, just ask in the Noob friendly S5 All in one support thread
If you need general help/assistence, please go to XDA-Assist.
Xda-assist is just to point to the best place for help on xda.
Thanks for your understanding. Thread closed.
My tapatalk signature:
Device: SGS5 (SM-G900F)
ROM: AllianceROM v5.6
Kernel: Stock G900FXXU1ANG2
Recovery: TWRP by Ktoonsez
Modem: G900FXU1ANG7
If you have any question about or any issue with your SGS2, just ask in the New members friendly Q&A thread.
... for the SGS5, just ask in the Noob friendly S5 All in one support thread
If you need general help/assistence, please go to XDA-Assist.
How can a manually root SM-910G running on android 5.1.1.
I did try adb but i every time i try i get permission denied error while pushing Su
Hello,
adb requires root to work.
Try posting your question in the forum linked below.
http://forum.xda-developers.com/note-4/help
The experts there may be able to help. Good luck.
Here's the SE link with my issue.
https://android.stackexchange.com/questions/131577/cannot-remove-rename-move-build-prop?newreg=528098aed3b24c58a1949dbf850b4387
But I think you guys are able to help me better because I think it's a device/huawei kind of thing, not generally android.
Anyhow, what I did aside from that SE link...
I've downloaded a "template" from here http://forum.xda-developers.com/showthread.php?t=732957, update-apps-signed, and done what he said, afterwards I resigned the zip with SignAPK.
Then I went into recovery and applied update from sd card, but I get the same error every time...
-- Installation /sdcard ...
Installation aborted.
I googled some more and from the looks of it I need an OEM key from Huawei to unlock the bootloader and flash CWM before I can proceed. I seriously hope I don't need to do this.
So here's what tools I got:
ADB accessible phone in normal boot. Phone appears to work, the interface just won't load.
Android system recovery 3e in recovery.
This is incredibly frustrating as I know just changing one bit is all I need to get my phone working again.
Anyone got ideas how to proceed?
XDA Visitor said:
Here's the SE link with my issue.
https://android.stackexchange.com/q...-prop?newreg=528098aed3b24c58a1949dbf850b4387
But I think you guys are able to help me better because I think it's a device/huawei kind of thing, not generally android.
Anyhow, what I did aside from that SE link...
I've downloaded a "template" from here http://forum.xda-developers.com/showthread.php?t=732957, update-apps-signed, and done what he said, afterwards I resigned the zip with SignAPK.
Then I went into recovery and applied update from sd card, but I get the same error every time...
-- Installation /sdcard ...
Installation aborted.
I googled some more and from the looks of it I need an OEM key from Huawei to unlock the bootloader and flash CWM before I can proceed. I seriously hope I don't need to do this.
So here's what tools I got:
ADB accessible phone in normal boot. Phone appears to work, the interface just won't load.
Android system recovery 3e in recovery.
This is incredibly frustrating as I know just changing one bit is all I need to get my phone working again.
Anyone got ideas how to proceed?
Click to expand...
Click to collapse
Hello,
Since adb works for you. You can try these (One by one)
Code:
adb root
adb remount
adb pull /system/build.prop
Make the required changes which you messed in build.prop
adb push build.prop /system/build.prop
adb shell chmod 644 /system/build.prop
adb reboot
Alteratively, you could register for a XDA Account so you could reply to the threads in the forums as well as get expertise help
-Vatsal
adb root -> I can't do that, it says it cannot run as root in production builds.
adb remount -> Not permitted
adb pull /system/build.prop -> This works, that's how I got the build.prop
Make the required changes which you messed in build.prop -> Donezo.
adb push build.prop /system/build.prop -> Read-only file system
adb shell chmod 644 /system/build.prop -> Read-only file system
adb reboot -> Works fine
And yes, I'm op, no idea how to claim the thread or change my name... xda said the mail address was already taken with this username.
I've already tried this as seen in the comments.
UsernameNotRecognized said:
adb root -> I can't do that, it says it cannot run as root in production builds.
adb remount -> Not permitted
adb pull /system/build.prop -> This works, that's how I got the build.prop
Make the required changes which you messed in build.prop -> Donezo.
adb push build.prop /system/build.prop -> Read-only file system
adb shell chmod 644 /system/build.prop -> Read-only file system
adb reboot -> Works fine
And yes, I'm op, no idea how to claim the thread or change my name... xda said the mail address was already taken with this username.
I've already tried this as seen in the comments.
Click to expand...
Click to collapse
Hello,
You need to get adb root working, Try running it as administrator.
If still doesnt work, then give a try to this
-Vatsal
I need root access before with ADB if I want to change that, which I can't get. To enable root access with ADB I need to have acccess to my device the normal way and edit the file with something like root ES Explorer. This is impossible as my device is soft-bricked. That's what I think, unless I'm overseeing some things?
UsernameNotRecognized said:
I need root access before with ADB if I want to change that, which I can't get. To enable root access with ADB I need to have acccess to my device the normal way and edit the file with something like root ES Explorer. This is impossible as my device is soft-bricked. That's what I think, unless I'm overseeing some things?
Click to expand...
Click to collapse
Hello,
Well, you edited build.prop and saved that so that would mean you were rooted? Isn't it?
ADB commands work without root. However the /data partition is only accessible by rooted users* and while /system can be read by anyone, it's a read-only partition and root is needed to remount it as writable.
-Vatsal
I did that before it was soft bricked with SuperSU and ES Xplorer. I don't know how to use SuperSU with ADB. su -s and su overall appear to do nothing.
UsernameNotRecognized said:
I did that before it was soft bricked with SuperSU and ES Xplorer. I don't know how to use SuperSU with ADB. su -s and su overall appear to do nothing.
Click to expand...
Click to collapse
Hello,
You may try posting your query here regarding this.
Android Q&A, Help & Troubleshooting or [URL="http://forum.xda-developers.com/showthread.php?t=2259645]General Q&A[/URL]
The experts there maybe able to assist you
-Vatsal
Abstrk_2dx said:
just flash the stock build.prop it will boot up
Click to expand...
Click to collapse
Yeah.... How
Spflasher doesn't work.
I do have a rom, but spflasher does not work.
UsernameNotRecognized said:
I do have a rom, but spflasher does not work.
Click to expand...
Click to collapse
Hello,
Read the post above, You may try asking there in that forum/thread. The experts there may be able to assist you
-Vatsal
I have but no one has replied as of yet.
UsernameNotRecognized said:
I have but no one has replied as of yet.
Click to expand...
Click to collapse
Hello,
I would recommend you waiting and having a bit of patience untill they figure out your problem and reply to it.
Thank you
-Vatsal
I'll try to make this as short and concise as possible as the wall of text may crit readers eyes. The device I have isn't your standard tablet, it has no standard manufacturer so no support or stock roms. I am quite novice.
What we know:
Android Version 4.4.4
Kernel Version 3.0.36+ [email protected] #876
Build Number rk3188-eng 4.4.4 KTU84Q
What it is running(was) is very basic, I rooted it and went to install TWRP via the APK installer which is where it all went wrong. Due to the lack of knowledge of the device I installed what I thought would be a similar enough device to not brick the device. Once the device restarted it would no longer boot into the OS, so I went into recovery mode (Dead android) however there are no options or access here.
Moving into ADB, the device does show with a bogus serial.
Code:
0123456789ABCDEF recovery
I can push and pull data, however other commands such as
Code:
adb reboot sideload-auto-reboot
results in cmd to permanently hang.
Shell commands all return with not being found.
Code:
#ls
/system/bin/sh: ls: not found
#
I would love to either get her back up and running or completely install a new rom. Thoughts comments and concerns are all welcome!
Echeltek said:
I'll try to make this as short and concise as possible as the wall of text may crit readers eyes. The device I have isn't your standard tablet, it has no standard manufacturer so no support or stock roms. I am quite novice.
What we know:
Android Version 4.4.4
Kernel Version 3.0.36+ [email protected] #876
Build Number rk3188-eng 4.4.4 KTU84Q
What it is running(was) is very basic, I rooted it and went to install TWRP via the APK installer which is where it all went wrong. Due to the lack of knowledge of the device I installed what I thought would be a similar enough device to not brick the device. Once the device restarted it would no longer boot into the OS, so I went into recovery mode (Dead android) however there are no options or access here.
Moving into ADB, the device does show with a bogus serial.
Code:
0123456789ABCDEF recovery
I can push and pull data, however other commands such as
Code:
adb reboot sideload-auto-reboot
results in cmd to permanently hang.
Shell commands all return with not being found.
Code:
#ls
/system/bin/sh: ls: not found
#
I would love to either get her back up and running or completely install a new rom. Thoughts comments and concerns are all welcome!
Click to expand...
Click to collapse
Hello,
Thanks for using XDA Assist.
There's no dedicated forum for your device here in XDA.Try posting your query in Android Q&A,Help and Troubleshooting or in one of the noob friendly Q&A thread here->[Ask Any Question][Newbie Friendly] .Experts there may be able to help you
___
v7
XDA Assist
I want to flash a Cm rom into my phone, I followed all the steps until it showed
Could not detect file system for dev/block/mmcblk0p8 assuming ext4
mount: failed to mount dev/block/mmcblk0p8 at /system : Block device required
ApplyParsedPerms: removexattr of system/xbin/zip to 0 failed: Operation not supported on transport endpoint
set_metadata_recursive:some changes failed
Hello and thank you for using XDA Assist,
please tell us, which device you are using:
svetius said:
How to use this forum:
1. If you ask a question, please create a new thread and post your question with as many details as you can (device type, model, running custom or official rom etc).
Click to expand...
Click to collapse
Kind regards
Trafalgar Square
XDA Assist