[Completed] Set wrong value in build.prop, stuck in boot - XDA Assist

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

Related

[Q] little adb help?

ok guys im trying to help my friend use adb to push an app that he has on his SDcard to /system/app with the same permissions. i did it with root explorer, but he didnt wanna buy it (i tried to convince him, to no avail)
ok so im not that good at adb but i know some things, i need to mount the system as read-write, then adb push app to system/app and use chmod (644? i believe) to give it system permissions. im just missing the technical lines of code to get it to work. anyone wanna help a fella out?? line by line would be greatly appreciated
thanks!
DX-FTW said:
ok guys im trying to help my friend use adb to push an app that he has on his SDcard to /system/app with the same permissions. i did it with root explorer, but he didnt wanna buy it (i tried to convince him, to no avail)
ok so im not that good at adb but i know some things, i need to mount the system as read-write, then adb push app to system/app and use chmod (644? i believe) to give it system permissions. im just missing the technical lines of code to get it to work. anyone wanna help a fella out?? line by line would be greatly appreciated
thanks!
Click to expand...
Click to collapse
Make sure your phone is recognized by running "adb devices", then do the following:
1. adb remount
2. adb shell cp /sdcard/yourapkname.apk /system/app
Your done. I've never had to chmod something to make it work.
madj42 said:
Make sure your phone is recognized by running "adb devices", then do the following:
1. adb remount
2. adb shell cp /sdcard/yourapkname.apk /system/app
Your done. I've never had to chmod something to make it work.
Click to expand...
Click to collapse
thank you for the response. its a system replacement app and needs to be recognized as one so would i just do
3. adb shell chmod 644 /system/app/apkname.apk
DX-FTW said:
thank you for the response. its a system replacement app and needs to be recognized as one so would i just do
3. adb shell chmod 644 /system/app/apkname.apk
Click to expand...
Click to collapse
yes you could do that. For more help with the many adb commands you can always type adb with no parameters and it will give you a list.
madj42 said:
yes you could do that. For more help with the many adb commands you can always type adb with no parameters and it will give you a list.
Click to expand...
Click to collapse
ok thanks. anything about unmounting as R/W or does that matter?
DX-FTW said:
ok thanks. anything about unmounting as R/W or does that matter?
Click to expand...
Click to collapse
Doesn't matter.. Reboot the device and it will be read-only again.

[Q] Is there any way to reinstall a system app?

Hi,
I was having trouble with my app YouTubeTablet.apk, it stopped working while I was using it. thinking I was starting to get the hang of this OS, I found the apk in system/app/ and, thinking I could just reinstall it, I deleted it. It wont let me reinstall it. it trys to install, then just gives an error saying "app did not install"
I have been reading and searching all night, I have tried the chmod 644 and a few other things but nothing I have done has seemed to work to get this reinstalled.
Does anyone know a way to get this app back?
thanks,
John
Hello I'm not 100% certain as I'm also pretty new to this scene, but couldn't you just copy the apk back to /system/app ?
Sent from my ADR6300 using XDA App
Use a root explorer and copy the new app to /system/app. Restart and it should work.
I use ES File Explorer, but you have to check mount as read/write in the settings before you copy to system/
Install in /system/app and make sure your permissions are correct. Read: User, Group and Others checked and Write: User checked. Reboot
BTW Youtube crashed last night for everyone. Was a thread about it.
Thanks for the reply's,
I have tried most of this stuff, I tried the rest (changing the permissions) and it still doesn't show up in apps or install
not sure what else to try??
John
Try pushing it via adb then fixing permissions.
Beamed from my TF101 using Tapatalk HD
Xerravon said:
Thanks for the reply's,
I have tried most of this stuff, I tried the rest (changing the permissions) and it still doesn't show up in apps or install
not sure what else to try??
John
Click to expand...
Click to collapse
What ROM are you running? Just flash that ROM again without wiping.
infazzdar said:
Try pushing it via adb then fixing permissions.
Beamed from my TF101 using Tapatalk HD
Click to expand...
Click to collapse
Hi,
I have been trying to do this, I cant seem to do it
after installing sdk I am
1. booting into apx vol up + power while plugged into the pc (plus I tried pluging nto the pc after going into apx mode)
2. adb devices (none show) If I boot normally the devices do show
3. in apx mode, apx shows under devices and printers in my pc
so I tried to do adb remount with the TF booted normally it says not permitted, if I try in apx mode it says no device
I dont know, I am lost, I hope this is all my fault, it has to be, I am reading and reading, nothing I find, or stuff people tell me to try works. I am really starting to wonder about this OS
John
Xerravon said:
Hi,
I have been trying to do this, I cant seem to do it
after installing sdk I am
1. booting into apx vol up + power while plugged into the pc (plus I tried pluging nto the pc after going into apx mode)
2. adb devices (none show) If I boot normally the devices do show
3. in apx mode, apx shows under devices and printers in my pc
so I tried to do adb remount with the TF booted normally it says not permitted, if I try in apx mode it says no device
I dont know, I am lost, I hope this is all my fault, it has to be, I am reading and reading, nothing I find, or stuff people tell me to try works. I am really starting to wonder about this OS
John
Click to expand...
Click to collapse
It's ADB, you do NOT put it in APX mode. Just turn USB Debugging on.
Open the command window and type in ADB devices to see if your device come up.
This thread help with driver's and such for ADB
http://forum.xda-developers.com/showthread.php?t=1071584
baseballfanz said:
What ROM are you running? Just flash that ROM again without wiping.
Click to expand...
Click to collapse
I think I am running the stock rom, rooted. I dont have anyidea how to flash
Is there a way for me to reflash the same stock rom? If you can point me to same directions or info where I can try to learn this?
thanks
baseballfanz said:
It's ADB, you do NOT put it in APX mode. Just turn USB Debugging on.
Open the command window and type in ADB devices to see if your device come up.
This thread help with driver's and such for ADB
http://forum.xda-developers.com/showthread.php?t=1071584
Click to expand...
Click to collapse
thank you, I just read somewhere it had to be in apx for adb
Ok the devices do show in the list
I read to type
adb remount
adb push youtubetablet.apk /system/app/
adb push youtubetablet.odex /system/app/
to push these into system/app
when I type adb remount I get the error
"remount failed operation not permitted"
any idea what I am doing wrong
thanks
John
try
Code:
adb shell remount rw
baseballfanz said:
try
Code:
adb shell remount rw
Click to expand...
Click to collapse
It gives me
remount: permission denied
I just read I will quote below
"If it shows a $ sign when u type adb shell then u got no root son"
Ok, when I type adb shell I do get the $ does this mean I am not rooted? I do have su and can get su permissions in root explorer. heck that is what got me in this trouble, I was able to delete the youtubetablet apk from system/app/
adb
Xerravon said:
It gives me
remount: permission denied
I just read I will quote below
"If it shows a $ sign when u type adb shell then u got no root son"
Ok, when I type adb shell I do get the $ does this mean I am not rooted? I do have su and can get su permissions in root explorer. heck that is what got me in this trouble, I was able to delete the youtubetablet apk from system/app/
adb
Click to expand...
Click to collapse
What method did you use to root?
baseballfanz said:
What method did you use to root?
Click to expand...
Click to collapse
I used this one to root back on (8.6.5.9)
ASUS Transformer Root ToolKit V7.1 Universal (Windows) | 2011-09-22 (brk's)
http://forum.xda-developers.com/showthread.php?t=1185104
and I updated with these
[UPDATE] CWM - Stock + Root - 8.6.5.21 US 8.6.5.21-WW 8.6.6.23-WW Updated 12/29/2011 (daoist )
http://forum.xda-developers.com/showthread.php?t=1334673
I was able to do this in terminal emulator
mount -o rw,remount /system
cp sdcard/download/youtubetablet.apk /system/app/
cp sdcard/download/youtubetablet.apk /system/app/
mount -o ro,remount /system
this did seem to work, i mean It did copy the files into the system/app dir however I still dont see the app in my apps and still cannot install
One difference this time, if I copied the files into the system/app dir using root explorer then changed the permissions with root explorer I could, I mean it would allow me to check the box's and save the change
this time In root explorer I cannot keep or save the changes to the permissions, it gives some error about "not being able to change permissions on some file formats such as sdcard etc..." something like that
thanks
John
I was able to push the files over using this method found here (pushing it via adb with my TF in recovery (CWM)
http://androidforums.com/optimus-m-...anyone-who-has-rooted-deleted-lghome-apk.html
it did push the files but still doesnt show up as an app
The may seems simple and don't get mad at me for saying this, but did you reboot after you pushed it to /system /app? It should show up then. At least that is the way I push them and usually when it doesn't work, it is because I forgot that part.
Xerravon said:
[UPDATE] CWM - Stock + Root - 8.6.5.21 US 8.6.5.21-WW 8.6.6.23-WW Updated 12/29/2011 (daoist )
http://forum.xda-developers.com/showthread.php?t=1334673
John
Click to expand...
Click to collapse
Have you tried flashing that ROM again?
baseballfanz said:
Have you tried flashing that ROM again?
Click to expand...
Click to collapse
No I havent, is it ok to just reflash like that? I ask cause it says (in the thread) it wont work unless you have the update before that one installed.
Hi, Yes, I did reboot, actually tried the whole thing a few times/
thanks guys

[Q] [HELP] /system read-only can't fix on adb no su response

i ported a LeWa OS ROM for my device and everything seemed to work perfectly, booted up without hassle, apps working, and everything was fine. not until i came to the point where i have to check the root capability. it seems like the /system partition was locked as read-only. i pre-rooted the rom with supersu and su binaries properly placed just like i do with other roms i ported. but this one is different. even on adb, the su isn't responding. although the request is showing on the phone and i click on grant, still there is no su response or whatsoever, that is why i cant remount it as rw.
so i was wondering if there is something i have to port from stock boot.img to port boot.img to permanently mount /system partition in RW capability.
i hope anyone can help me
How about making an insecure kernel so you can access root without requesting su?
xlSKYFiRElx said:
i ported a LeWa OS ROM for my device and everything seemed to work perfectly, booted up without hassle, apps working, and everything was fine. not until i came to the point where i have to check the root capability. it seems like the /system partition was locked as read-only. i pre-rooted the rom with supersu and su binaries properly placed just like i do with other roms i ported. but this one is different. even on adb, the su isn't responding. although the request is showing on the phone and i click on grant, still there is no su response or whatsoever, that is why i cant remount it as rw.
so i was wondering if there is something i have to port from stock boot.img to port boot.img to permanently mount /system partition in RW capability.
i hope anyone can help me
Click to expand...
Click to collapse
Download SuperSU and reinstall its binaries again.
Or you can try adbd Insecure app (not free)
janekmuric said:
Download SuperSU and reinstall its binaries again.
Or you can try adbd Insecure app (not free)
Click to expand...
Click to collapse
supersu or any of its binaries cannot help me. as every app that request root privileges hangs when grant permission is given. ill try adbd insecure app. gonna throw my money to this one
xlSKYFiRElx said:
supersu or any of its binaries cannot help me. as every app that request root privileges hangs when grant permission is given. ill try adbd insecure app. gonna throw my money to this one
Click to expand...
Click to collapse
I think the adb insecure app still requires su, you can upload the boot.img and i'll make it insecure (automatically root via adb, no su required)
Oooohh
xlSKYFiRElx said:
supersu or any of its binaries cannot help me. as every app that request root privileges hangs when grant permission is given. ill try adbd insecure app. gonna throw my money to this one
Click to expand...
Click to collapse
I didn't understand you correctly. Anyways from what I understand noe you can't give root to any app at all. Try using framaroot to re-root maybe it works. You have to find out the reason it hangs. I'm placing my bet on the corrupt or bad binary.
janekmuric said:
I didn't understand you correctly. Anyways from what I understand noe you can't give root to any app at all. Try using framaroot to re-root maybe it works. You have to find out the reason it hangs. I'm placing my bet on the corrupt or bad binary.
Click to expand...
Click to collapse
He's right, redownload the binaries again, if it still hangs, it might be the ROM.
Add this to build.prop if you want root via adb:
ro.secure=0
janekmuric said:
I didn't understand you correctly. Anyways from what I understand noe you can't give root to any app at all. Try using framaroot to re-root maybe it works. You have to find out the reason it hangs. I'm placing my bet on the corrupt or bad binary.
Click to expand...
Click to collapse
3DMapPlayer said:
He's right, redownload the binaries again, if it still hangs, it might be the ROM.
Add this to build.prop if you want root via adb:
ro.secure=0
Click to expand...
Click to collapse
sorry for the confusion but here is the case, i ported this (LEWA) ROM and i pre rooted with, placed the updated su binary to /system/xbin and the latest supersu.apk to /system/app. the phone boots properly and according to the rom. i installed root checker but when it checked for root it says the root is not installed properly but the supersu dialog box is appearing and i can press the grant button and a toast appears saying that it is granted superuser permissions. i tried to re-root using framaroots barahir exploit but it said "Half-Success" because the system partition is mounted read-only.
i tried using root explorer, when i try to mount system as r/w the supersu dialog appears and i can press the grant button again, also the toast appears saying that the app is granted superuser permission but then the application (root explorer) hangs, i tried other root explorer application still the same.
so what i want to achieve is to mount /system as read-write partition
i tried using ADB, but when i try to type su everything i type reappears
example: when i type 'su' the result is like this:
Code:
what i type: su
what show: su
what i type: busybox mount
what show: busybox mount
or simply, everything i type reappears and the command is not executed.
i tried to modify boot.img by editing build.prop and setting this values
#
# ADDITIONAL_DEFAULT_PROPERTIES
#
ro.secure=0
ro.allow.mock.location=1
persist.mtk.aee.aed=on
ro.debuggable=1
persist.sys.usb.config=mass_storage,mtp
persist.service.acm.enable=0
ro.mount.fs=EXT4
Click to expand...
Click to collapse
and also editing init.rc and setting this values
Code:
mount yaffs2 [email protected] /system rw remount
mount ubifs [email protected] /system rw remount
but still no luck. i hope you guys understand, sorry for my crappy english. not my language
i'll try to reflash the rom so that i can supply screenshots
also, here is a copy of my boot.img
Got it!
xlSKYFiRElx said:
sorry for the confusion but here is the case, i ported this (LEWA) ROM and i pre rooted with, placed the updated su binary to /system/xbin and the latest supersu.apk to /system/app. the phone boots properly and according to the rom. i installed root checker but when it checked for root it says the root is not installed properly but the supersu dialog box is appearing and i can press the grant button and a toast appears saying that it is granted superuser permissions. i tried to re-root using framaroots barahir exploit but it said "Half-Success" because the system partition is mounted read-only.
i tried using root explorer, when i try to mount system as r/w the supersu dialog appears and i can press the grant button again, also the toast appears saying that the app is granted superuser permission but then the application (root explorer) hangs, i tried other root explorer application still the same.
so what i want to achieve is to mount /system as read-write partition
i tried using ADB, but when i try to type su everything i type reappears
example: when i type 'su' the result is like this:
Code:
what i type: su
what show: su
what i type: busybox mount
what show: busybox mount
or simply, everything i type reappears and the command is not executed.
i tried to modify boot.img by editing build.prop and setting this values
and also editing init.rc and setting this values
Code:
mount yaffs2 [email protected] /system rw remount
mount ubifs [email protected] /system rw remount
but still no luck. i hope you guys understand, sorry for my crappy english. not my language
i'll try to reflash the rom so that i can supply screenshots
also, here is a copy of my boot.img
Click to expand...
Click to collapse
Flash the attached ZIP. It will reinstall SuperSU and all needed files.

Root access on adb shell but not for apps

Hello,
i am working on chinese android tablet called "MID-U705B". The device came half rooted i guess. I am getting an # in the adb shell, even without running "su", right from the start of adb shell. Nevertheless i am not able to run any root apps. When i am trying to call a root shell command from my app i am getting: [java.io.IOException] : write failed: EPIPE (Broken pipe).
There is a su file inside my /system/xbin folder and i also created a symbolic link to it in /system/bin.
Does someone know how to get full root access on this devices? Whats missing?
Thanks for your help and advice!
Best regards,
Hans
skatehans said:
Hello,
i am working on chinese android tablet called "MID-U705B". The device came half rooted i guess. I am getting an # in the adb shell, even without running "su", right from the start of adb shell. Nevertheless i am not able to run any root apps. When i am trying to call a root shell command from my app i am getting: [java.io.IOException] : write failed: EPIPE (Broken pipe).
There is a su file inside my /system/xbin folder and i also created a symbolic link to it in /system/bin.
Does someone know how to get full root access on this devices? Whats missing?
Thanks for your help and advice!
Best regards,
Hans
Click to expand...
Click to collapse
If you can get root on ADB then just install SuperSU app and its binaries and you are good to go.
Flashing the attached ZIP will install SuperSU app and everything it requires to function.
NOTE: You probably need a custom recovery because the zip isn't signed.
Thanks for your reply!
Unfortunately i dont have a custom recovery because its a no name device an there does not exist a custom recovery for this device. Is there any way to install this without a custom recovery? What happens when i try to flash it from a (chinese) stock-recovery?
skatehans said:
Thanks for your reply!
Unfortunately i dont have a custom recovery because its a no name device an there does not exist a custom recovery for this device. Is there any way to install this without a custom recovery? What happens when i try to flash it from a (chinese) stock-recovery?
Click to expand...
Click to collapse
You should be able to flash it via fastboot.
Thats the next Problem. I cant boot into fastboot mode. When i execute "adb reboot bootloader" or "adb reboot download" the device boots up like normal, so i guess fastboot is not available on this device.
Do you know any other way?

Question How to pull Build.Prop...

Here's where I'm at. I've got the system to give me the Mount /System option in recovery, now i just need assistance getting the build.prop pulled to my PC. What's the procedure for pulling the build.prop from the Android to PC via ADB while the system is mounted in recovery? Why am I getting one of these two ADB errors?
Error 1: Connect failed: closed.
error 2: Failed to get feature set: no devices or emulators
OR, am I approaching it wrong?
Thanks in advance,
K0mraid3
you dont need to be in recovery to do it via adb....
adb pull /system/build.prop
that will pull it to where evr you run the adb command
which would be
C;\adb more than likely
or you can choose a destination with
adb pull /system/build.prop c:\buildprop
if you create a folder called "buildprop" in the root directory of c:\
at least thats how i remember doing it many years ago, ive been away for a while at her majesties pleasure, so i cant try it currently as im not rooted
gav83collins said:
you dont need to be in recovery to do it via adb....
adb pull /system/build.prop
that will pull it to where evr you run the adb command
which would be
C;\adb more than likely
or you can choose a destination with
adb pull /system/build.prop c:\buildprop
if you create a folder called "buildprop" in the root directory of c:\
at least thats how i remember doing it many years ago, ive been away for a while at her majesties pleasure, so i cant try it currently as im not rooted
Click to expand...
Click to collapse
Thanks, so far, its still for some reason denying me permission when OS is booted. So i just cant quite figure out where im supposed to execute these commands, is my issue. I can boot directly to BL from recovery menu, but i can also mount system. i think maybe i need sto send command for r/w.. will try that now.
Another question, when i mount /system in recovery, does that carry over on boot?
no you can re mount system via adb though
Code:
$ adb shell
$ su
# mount -o rw,remount /system
gav83collins said:
no you can re mount system via adb though
Code:
$ adb shell
$ su
# mount -o rw,remount /system
Click to expand...
Click to collapse
1.Needs root for this command. If he have rooted device then why so much trouble needed. Simply use root explorer to copy
2.Since long Samsung have removed system from proc/mounts still magisk system_root can be used
3.Even with system in mounts you can't do system rw on S22 because of Samsung have implemented extra layer of protection. Even not with magisk system_root too
Indeed as of now there is no method available to make stock system/vendor/product/odm rw on S22 even with root access.
4.To copy file from system rw mount not needed, ro is fine
dr.ketan said:
1.Needs root for this command. If he have rooted device then why so much trouble needed. Simply use root explorer to copy
2.Since long Samsung have removed system from proc/mounts still magisk system_root can be used
3.Even with system in mounts you can't do system rw on S22 because of Samsung have implemented extra layer of protection. Even not with magisk system_root too
Indeed as of now there is no method available to make stock system/vendor/product/odm rw on S22 even with root access.
4.To copy file from system rw mount not needed, ro is fine
Click to expand...
Click to collapse
im yet to root my device so i cant test but what about
Code:
adb root
adb disable-verity
adb reboot
Then
Code:
adb root
adb remount
gav83collins said:
im yet to root my device so i cant test but what about
Code:
adb root
adb disable-verity
adb reboot
Then
Code:
adb root
adb remount
Click to expand...
Click to collapse
Do you got what I meant?
leave it.
dr.ketan said:
WTF
Do you got what I meant?
leave it.
Click to expand...
Click to collapse
look, there is no need for condescension and bad language, a simple "no" would have sufficed
Lol not meant to hurt you! but on which planet WTF is bad language
Here search WTF on xda
dr.ketan said:
1.Needs root for this command. If he have rooted device then why so much trouble needed. Simply use root explorer to copy
2.Since long Samsung have removed system from proc/mounts still magisk system_root can be used
3.Even with system in mounts you can't do system rw on S22 because of Samsung have implemented extra layer of protection. Even not with magisk system_root too
Indeed as of now there is no method available to make stock system/vendor/product/odm rw on S22 even with root access.
4.To copy file from system rw mount not needed, ro is fine
Click to expand...
Click to collapse
So my device is strange. It doesn't have root, but it indeed shows options in recovery to apply updates from ADB, SD Card aswell as boot directly to BL and to Mount /System, but when I'm booted, the OS is denying me permission to "Su" . I have verified that USB debugging is activated. So I'm trying to see if there's a way to pull the build.prop from Recovery since the Mount /System option is available, but my computer refuses to recognize the device in while in recovery, but easily finds it in Download, BL mode. No FRP lock. No accounts on device. But also no option to unlock bootloader. This device in particular is/was a development sample so I have no clue what the current state of the bootloader etc is in terms of being unlocked prior to me working on it.
It'd also worth noting that this device was loaded with Android 11 when I received it. I'm not kidding. So idk what's going on with this FrankenGalaxy
K0mraid3 said:
It'd also worth noting that this device was loaded with Android 11 when I received it. I'm not kidding. So idk what's going on with this FrankenGalaxy
Click to expand...
Click to collapse
K0mraid3 said:
So my device is strange. It doesn't have root, but it indeed shows options in recovery to apply updates from ADB, SD Card aswell as boot directly to BL and to Mount /System, but when I'm booted, the OS is denying me permission to "Su" . I have verified that USB debugging is activated. So I'm trying to see if there's a way to pull the build.prop from Recovery since the Mount /System option is available, but my computer refuses to recognize the device in while in recovery, but easily finds it in Download, BL mode. No FRP lock. No accounts on device. But also no option to unlock bootloader. This device in particular is/was a development sample so I have no clue what the current state of the bootloader etc is in terms of being unlocked prior to me working on it.
Click to expand...
Click to collapse
These options are normal in stock recovery and can be used only for flashing official zip (OTA), To have root access on your recovery, you needs custom one (TWRP) which is in development stage on S22
Without twrp, You needs to root device (must have oem unlock option in development option) to access system files while you are booted to android.
Android 11 on S22? Can you show me screenshot of settings - about phone - software info?
dr.ketan said:
These options are normal in stock recovery and can be used only for flashing official zip (OTA), To have root access on your recovery, you needs custom one (TWRP) which is in development stage on S22
Without twrp, You needs to root device (must have oem unlock option in development option) to access system files while you are booted to android.
Android 11 on S22? Can you show me screenshot of settings - about phone - software info?
Click to expand...
Click to collapse
Thanks for the clear answer, that's kind of what I'm working on is trying to gain root access, but like you said, I need oem unlocking, which isn't on this device. So I'm trying to find a backdoor/vulnerability that will take me even one step closer to atleast finding a way to set ro.secure. prop. Something VERY interesting I did find, is that if you put the device to Debug medium or high via device keystring activity, and play with the key combos, you can get booted into a mode called RDX, if you plug it into your dev system with the right drivers, it's treats the phone as if it were a Disk and shows a bunch of VZW upgrade software ment for PCs. I've installed it but haven't got it working quite yett.
No idea what you have shown in screenshot, I'd asked something else.
dr.ketan said:
No idea what you have shown in screenshot, I'd asked something else.
Click to expand...
Click to collapse
Maybe Heindall will give me better results. I just refuse to believe the manufacturers have outsmarted us all on this.

Categories

Resources