Guys I need some help !!
I have official firmware in my phone S7 edge ( Android 7.0 G935F ) but once i tried to root it and it was stuck in boot logo so i went to a store for a suppose unroot ,but know e cant use Samsung health app because gives me an error. I already searched this error and just have to change the tima value to 0 in build.prop
My real question is can I edit build.prop to fix this error without root or do i have to root my device again to fix this error ??
Please help
thanksssss, waiting 4 answers
Your phone KNOX is ticked 0X1 that's why not working, you must root your phone and edit built prob, edit line TIMA=0 and will work
so i have to root it again ?? i have some problems (fear) doing it again because i don't know how to do it right
Or othe way to make it work. But need to be Root. Delete v5 restar install v4. Loging abd update. Done
I would recommend you the recovery mode if you don't want root the phone again. You have full access to system files in recovery mode, but only if it is mounted.*
Many stock recoveries don't have option to mount system partition or don't have adb access for commands. You might want a custom recovery for this. And no, you don't need root for custom recovery. So now all you need to do is, boot into recovery (custom preferred), mount system and then using adb, pull the build.prop file:
adb pull /system/build.prop <path to save file>
Now edit the file you just extracted and save it*
Push it back to your phone via adb
adb push <path to your file> /system/build.prop
You're not done yet. You need to set permissions too. So open she'll via terminal
adb shell
Now from shell, set the right permissions
chmod 644 /system/build.prop
And you're done
Reboot your phone and see the changes
Related
I've been stupid enough and replaced my modified build and local.prop files on B310 ROM with the ones I've backed up from my B121SP06 ROM and after I've rebooted the phone it just stays on "Honor, powered by android" logo. Is there some way I can't replace those files with the originals before the intervention ( I have them on my SD card)? I can boot into recovery or in bootloader, also I can flash CWM recovery.
doctorat said:
I've been stupid enough and replaced my modified build and local.prop files on B310 ROM with the ones I've backed up from my B121SP06 ROM and after I've rebooted the phone it just stays on "Honor, powered by android" logo. Is there some way I can't replace those files with the originals before the intervention ( I have them on my SD card)? I can boot into recovery or in bootloader, also I can flash CWM recovery.
Click to expand...
Click to collapse
I had also problems with these two files.
Install cwm on your phone and start your phone in cwm-mode to use adb
in cwm you have to mount system, data and cust
open a command line and use adb as following:
"adb remount"
"adb pull /system/build.prop" --> this will download the build.prop-file to your local folder, where your adb-file is located. At this point you can also download another file like your mentioned backup of the build.prop. for the local.prop-file you have to use: "adb pull /data/cust/prop/local.prop"
When you are ready with changes on the two files or you just want to upload the right ones to your phone back use this command:
"adb push build.prop /system/build.prop" and/or "adb push local.prop /data/cust/prop/local.prop" --> it will copy the file build.prop or local.prop from the local folder, where your adb-file is located to the phone.
After uploading the files to your phone you have to fix permissions:
"adb shell chmod 644 /system/build.prop" and/or "adb shell chmod 644 /data/cust/prop/local.prop"
reboot your phone via cwm.
This is how it worked for me. I hope it will help you too. :fingers-crossed:
By the way, I'm actually looking for a stock local.prop-file for the L04 (from the firmware B109SP1 or B114) or the L12 (from the firmware B118 or B607). Do you have one of these?
Thanks for the reply but I've already succeeded flashing B313. I've been trying with "adb pull" command but it was saying "no device found " or something similar.
My phone is H60-L02 so i don't have the files you're looking for.
Hi all,
I have been through douzens of threads and forums looking for a solution to this.
I followed some instructions to modify the build.prop file on my Huawei G535-L11 to disable Huawei theme manager in order to get Xsposed working fully (changed ro.config.hwtheme: 0). I did a backup of my original build.prop before hand, and my phone was rooted and unlocked but running the stock rom.
Unfortunately, it rebooted but won't go past the first 'EE' splash screen (just turns off again).
I can inconsistently get in to both fastboot and Android recovery, so I have been trying to use adb to push the original build.prop to /system/ on the phone.
However, this fails as /system/ is apparently RO. I have now discovered that I can't get SU permissions despite my phone being rooted.
If I try:
adb shell
$ su
nothing happens and it goes back to a $ prompt.
If I try:
adb root
I get the message (paraphrased):
adb cannot run as root in production builds.
So I can't push or do any adb method of restoring the build.prop file?! I don't understand why it is acting as if it is not rooted. I had Link2sd, Gravity Box, No Frills Cpu Controller all set up and working before, so I'm fairly sure I did truly have root.
I have also tried flashing a TWRP recovery, which apparently is successful, but when I go in to recovery it is still the Android Recovery.
Does anyone have any ideas what I could do to get my phone working again please?! This is my last gasp before the phone gets filed under 'B' in the cylindrical cabinet in the corner of the room! :crying:
Any assistance greatly appreciated!
Bumpty bump?
So what ro.debuggable should be 0 with ro.secure
It looks to me like the best phone $80 can buy I spent couple hours trying to figure out how to enable Multi User module.
My understanding is that adding this to /system/build.prop would bring users module back:
fw.max_users=3
fw.show_multiuserui=1
None of the commonly used apps can root this phone.
Without root I cannot remount /system to read-write to edit build.prop
Stock recovery can mount /system
There are options in recovery to run update from sd card or to update via adb sideload but the phone does not show in adb devices while in recovery. There is also fastboot option.
I also tried dirty cow exploit but it fails with "only position independent executables (PIE) are supported"
I am into this for only couple hours, so I know I am missing a lot. Any pointers that could get me closer to enabling Users module would be welcome.
So, after some reading, i figured I should be able to apply update form recovery that will replace build.prop with modified one. For start, to test things out, I just want to copy file from update.zip to /system/build.prop.test
I created update.zip with update-script and the file I want to add to /system.
Here is update.zip: www . filedropper.com /update_10
I signed update.zip using this:
www . learn2crack.com /2014/02/sign-android-apk-zip.html
I get error "Signature verification failed". Is the problem that keys are test keys or that they are outdated? Is some special manufacturer key required to sign updates?
I am not looking for someone to do this, I just need to be pointed in the right direction.
I have multiple users now :
- downloaded TWRP from bluroms.info
- connected the phone, enabled USB debugging and OEM unlocking in developer options
- run "adb reboot bootloader"
- after phone booted in fastboot mode
fastboot oem unlock (followed instructions on screen / all data wiped)
fastboot boot blutwrp.img (downloaded TWRP)
- twrp started...
- mounted /system
adb pull /system/build.prop
- edited build.prop
adb push build.prop /system/build.prop
adb reboot
- phone got stuck on logo after reboot
removed battery and started the phone again and all seems good
@sasha_ Hey I know this isn't about how to root but could you tell me exactly how you managed to root your Blu Advance 5.0 HD? PM me.
mrfunnybone said:
@sasha_ Hey I know this isn't about how to root but could you tell me exactly how you managed to root your Blu Advance 5.0 HD? PM me.
Click to expand...
Click to collapse
If by rooting you mean, installing supersu so that apps can request root access, i did not do that, because i do not need it. There must be some tutorial around about installing supersu once you root access to the /system - and the steps I described can you get there.
sasha_ said:
If by rooting you mean, installing supersu so that apps can request root access, i did not do that, because i do not need it. There must be some tutorial around about installing supersu once you root access to the /system - and the steps I described can you get there.
Click to expand...
Click to collapse
So is getting root access to system like booting recovery TWRP? then pressing the Mount button and checking System? Sorry I'm a newb at this.
I'd love to gain root on this phone I have twrp installed but can't seem to find a root method that works
Just in case you guys are still watching this, I posted my experience with this phone here
https://forum.xda-developers.com/showpost.php?p=75164672&postcount=26
I have a Samsung galaxy tab 2.One day as I decided to wipe everything,i noticed a message in the recovery mode saying unable to mount efs.I cant open my tablet or anything.After looking on the internet,people were telling me to flash a custom recovery like CWM.In order to do that I need to root my tablet.To root my tablet I need to enable USB debugging,which I can't because I can't access it.Can you help me please?
Shedopen123 said:
I have a Samsung galaxy tab 2.One day as I decided to wipe everything,i noticed a message in the recovery mode saying unable to mount efs.I cant open my tablet or anything.After looking on the internet,people were telling me to flash a custom recovery like CWM.In order to do that I need to root my tablet.To root my tablet I need to enable USB debugging,which I can't because I can't access it.Can you help me please?
Click to expand...
Click to collapse
Boot to download mode and flash CWM or TWRP for your model number via Odin. Then you boot into CWM or TWRP and flash SuperSU.zip to root your device. I suggest TWRP instead of CWM.
Then, if you have TWRP you can use the built in file manager in TWRP to pull a copy of your build.prop file from /system, then copy it to PC then open build.prop in a text editor then find these lines in it:
persist.service.adb.enable=1 persist.service.debuggable=1 persist.sys.usb.config=mtp,adb
Change these lines in your build.prop to match the example above. You may not have all of these lines, change the ones you have and/or type the lines you don't have in for yourself then save the edited build.prop then adb push that copy back to /system to overwrite the existing unedited build.prop. Reboot the device and USB debugging should be enabled.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Droidriven said:
Boot to download mode and flash CWM or TWRP for your model number via Odin. Then you boot into CWM or TWRP and flash SuperSU.zip to root your device. I suggest TWRP instead of CWM.
Then, if you have TWRP you can use the built in file manager in TWRP to pull a copy of your build.prop file from /system, then copy it to PC then open build.prop in a text editor then find these lines in it:
persist.service.adb.enable=1 persist.service.debuggable=1 persist.sys.usb.config=mtp,adb
Change these lines in your build.prop to match the example above. You may not have all of these lines, change the ones you have and/or type the lines you don't have in for yourself then save the edited build.prop then adb push that copy back to /system to overwrite the existing unedited build.prop. Reboot the device and USB debugging should be enabled.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Click to expand...
Click to collapse
I'm having trouble flashing Supersu.zip.Everytime I flash,i type SU into the Terminal and it always says SU not found.Do I have to use adb from now on in order to replace efs?I also can't find the build.prop file that you are referring to in your comment.Thank you
Shedopen123 said:
I'm having trouble flashing Supersu.zip.Everytime I flash,i type SU into the Terminal and it always says SU not found.Do I have to use adb from now on in order to replace efs?I also can't find the build.prop file that you are referring to in your comment.Thank you
Click to expand...
Click to collapse
You don't flash SuperSU.zip with adb/fastboot.
Move the SuperSU.zip file to your device's internal storage or put it on an external sdcard, then boot into TWRP and choose the "install" option, then browse to where you stored SuperSU.zip and flash it.
In my first reply to you, I didn't say anything about flashing SuperSU.zip in a terminal, I told you to boot into TWRP and flash SuperSU.zip. Pay attention to what is told to you, word for word.
You could have easily done some searching to understand those instructions. Learn to search for answers.
You need to be rooted first, then you can find and edit build.prop.
Build.prop is very easy to find, again, learn how to search for answers.
Build.prop is located in /system/build.prop. It's in system partition, not in your internal storage.
Try using adb pull to get a copy of build.prop then edit the copy, save the copy and adb push it back to its location in /system/build.prop.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
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.