Question Trying To Root Samsung A76 5G - Samsung Galaxy A73 5G

This is my first time rooting my phone (tried rooting an o+ phone but couldn't unlock the bootloader) and I want to know how to my get phone's firmware. I tried using the Samsung Firmware Downloader but it won't accept my model and region.
I've tried using SuperSu to root but Root Checker says root access wasn't properly installed. What do I do now? Can I download a different firmware from a different site and is it safe? Does showing my pda code safe?
Edit: Forgot to mention I've already flashed TWRP.

Excuse me but what is your region and model number

tech-mаn said:
Excuse me but what is your region and model number
Click to expand...
Click to collapse
Never mind, I manage to download the firmware and root my phone thanks to Samsung Downloader. I wasn't able to download it at first because I keep using XXU (the one I saw in *#1234#, samsung firmware) as my region but it was actually XTC (I checked Software information in the About Phone).

Ok

if twrp is installed
root the phone with magisk

My next problem is changing the /system/ into read/write. I can't access build.prop. Haven't tried using adbd insecure but I have a feeling it won't work with Android 13. I'm currently trying to find the flashable zip from this thread to convert my /system/ into read/write.

MasterKwonKaichi said:
My next problem is changing the /system/ into read/write. I can't access build.prop. Haven't tried using adbd insecure but I have a feeling it won't work with Android 13. I'm currently trying to find the flashable zip from this thread to convert my /system/ into read/write.
Click to expand...
Click to collapse
Maybe it'll work

MasterKwonKaichi said:
My next problem is changing the /system/ into read/write. I can't access build.prop. Haven't tried using adbd insecure but I have a feeling it won't work with Android 13. I'm currently trying to find the flashable zip from this thread to convert my /system/ into read/write.
Click to expand...
Click to collapse
first root your device
then use mt manager to access build.prop file
i tested this in my sm-t585 with lineage os custom rom

alireza9082 said:
then use mt manager to access build.prop file
Click to expand...
Click to collapse
Accessing the build.prop file was not the problem, I can access it with any app (build.prop file, root explorer, etc..). My problem is whatever change I did to the build.prop file will not be saved since I don't have read/write access.

MasterKwonKaichi said:
Accessing the build.prop file was not the problem, I can access it with any app (build.prop file, root explorer, etc..). My problem is whatever change I did to the build.prop file will not be saved since I don't have read/write access.
Click to expand...
Click to collapse
as i said
use mt manager to save changes in build.prop

Since our system is F2FS you can't modify system it stays RO you can make a magisk module yourself to modify build prop also don't use supersu rooting is very easy just flash twrp then flash magisk. I'm making a custom rom which I'm hoping to release soon that's ext4 but I'm limited by time and the recent events from where I live so I can't give a ETA

Related

build.prop update.zip

Is it possible to make an update.zip file that replaces the build.prop file, or any way to replace the build.prop file without doing a full restore?
I did it using adb commands.
Well I tried using adb shell to swap the file, but when I ran su I got "[1] + Stopped (signal) su"
So I guess I'm going to be forced to do a nadroid restore of my system
Just use root explorer to copy the file to /sd, then use astro to edit it, and root explorer it back to the original spot and reboot. You don't need to change file permissions or any thing. No computer needed.
Sent from my GT-I9000 using Tapatalk
Boot loop
Clienterror said:
Just use root explorer to copy the file to /sd, then use astro to edit it, and root explorer it back to the original spot and reboot. You don't need to change file permissions or any thing. No computer needed.
Click to expand...
Click to collapse
Hi Clienterror,
What if the system is not booting?
I had installed an application which changes resolution and now ended up with a boot loop.
I have searched for ways how to extract the build.prop and correct the error, but none appears to exist.
I was asking if it is possible to extract the current build.prop via the update.zip method so that the build.prop can be repaired...
I read that from the update.zip you can execute code, would it be possible to use a similar method for extracting files from the system folder?
Thanks
remuscat said:
Hi Clienterror,
What if the system is not booting?
I had installed an application which changes resolution and now ended up with a boot loop.
I have searched for ways how to extract the build.prop and correct the error, but none appears to exist.
I was asking if it is possible to extract the current build.prop via the update.zip method so that the build.prop can be repaired...
I read that from the update.zip you can execute code, would it be possible to use a similar method for extracting files from the system folder?
Thanks
Click to expand...
Click to collapse
You could just reflash your current ROM and it should replace it.
korockinout13 said:
You could just reflash your current ROM and it should replace it.
Click to expand...
Click to collapse
Hi korockinout13,
I have tried to refresh from a rom i got, but I am prompted an error with Nand version.
The android in question is not common (Subor, a chinese Android Tablet) and have not found any firmware for my particular model except for the one supplied by the supplier, which still does not install.
At this stage reflashing is not an option, so I am looking for something else...
Thanks for your time
P
remuscat said:
Hi Clienterror,
What if the system is not booting?
I had installed an application which changes resolution and now ended up with a boot loop.
I have searched for ways how to extract the build.prop and correct the error, but none appears to exist.
I was asking if it is possible to extract the current build.prop via the update.zip method so that the build.prop can be repaired...
I read that from the update.zip you can execute code, would it be possible to use a similar method for extracting files from the system folder?
Thanks
Click to expand...
Click to collapse
Actually there is a potential option... can you get into recovery? And does your recovery have a file manager? If so go into mounts and mount /system. Then use the file manager in recovery and you should be able to access build.prop. copy it to your SD and then you should be able to mount your SD to your computer through recovery.
Edit: when you mount /system make sure you mount the SD as well or you won't be able to copy to it while you're in the recovery file manager.
Sent from my SGH-I897 using xda app-developers app
Hi m1batt1,
The recovery does not have any file mount option
I have lost all hope of being able to get the system to boot.
Thanks the same.
remuscat said:
Hi m1batt1,
The recovery does not have any file mount option
I have lost all hope of being able to get the system to boot.
Thanks the same.
Click to expand...
Click to collapse
You might have to flash stock KK4 at this point and go from there.
What kernel do you have for it not to have a file mount? I believe even stock kernel has it Since you can get in download mode, I would flash a newer kernel if I were you (with Odin) to be able to mount in recovery.
remuscat said:
Hi korockinout13,
I have tried to refresh from a rom i got, but I am prompted an error with Nand version.
The android in question is not common (Subor, a chinese Android Tablet) and have not found any firmware for my particular model except for the one supplied by the supplier, which still does not install.
At this stage reflashing is not an option, so I am looking for something else...
Thanks for your time
Click to expand...
Click to collapse
BWolf56 said:
You might have to flash stock KK4 at this point and go from there.
What kernel do you have for it not to have a file mount? I believe even stock kernel has it Since you can get in download mode, I would flash a newer kernel if I were you (with Odin) to be able to mount in recovery.
Click to expand...
Click to collapse
From what I'm reading he doesn't even have a captivate. He's using some Chinese tablet.
Sent from my SGH-I897 using xda app-developers app

[Q] what is the new update??

sorry for posting new thread but I don't know where to ask...can anybody please tell me tge new update 4.5.269 and someting3..is it the new version of gingerbread,is it safe to update..please tell me...
The new update is 4.5.629. It goes from Gingerbread 2.3.3 to Gingerbread 2.3.4, so a slight update. There are a few bug fixes, but it has a number of undesirable things.
1) 4.5.629 is currently not rootable
2) You cannot simply return to an earlier version via SBF.
You can overcome the first by using Voodoo Rootkeeper or similar to root on your current version, back up root with Rootkeeper and then update.
Recently, a method was found for this release to unbrick phones damaged by attempts to SBF or from bad ROMs: http://rootzwiki.com/topic/23207-how-to-sbf-unbricking-root-d2g-629 This also allows users who did upgrade to 4.5.629 to return to the previous version, root there and then upgrade again.
So it is sort of safe, but not ideal. The changelog is here, decide if the bug fixes are important enough for the added inconvenience
http://support.verizonwireless.com/pdf/system_update/droid_2_global.pdf
ok...thank u very much +1..I prefer not to update for now,and by mistake ,i select yes button in the update prompt,and its in the pull down bar,stucked and is ready to start downloading as soon as I connect to wi-fi,how will I cancel the download
You can block the update by renaming these files (e.g., append ".bak" to each filename):
/system/app/BlurUpdater_VZW.apk
/system/app/BlurUpdater_VZW.odex
Since these are in /system, renaming them requires root privileges and a root-enabled file manager (such as Root Browser Lite, available in the Google Play store).
ok..thanks,will do that,but after doing that,will I be able ro manually update it,or all the updates have been blocked???
Renaming those files will disable the OTA update client completely. You can still manually install an update by rebooting into recovery, but you will first have to download the update file from another source, rename it to "update.zip", and place it in the root level of your SD card.
Of course, you can also change those files back to their original names to re-enable OTA updates at any time.
jabberwockish said:
Renaming those files will disable the OTA update client completely. You can still manually install an update by rebooting into recovery, but you will first have to download the update file from another source, rename it to "update.zip", and place it in the root level of your SD card.
Of course, you can also change those files back to their original names to re-enable OTA updates at any time.
Click to expand...
Click to collapse
okok..thanks man +1
edit : i got this 'failed to rename file' error ..what should I do??
What app did you use to try to rename the files?
Did you root your phone before attempting the rename? (See http://www.psouza4.com/droid3/ for instructions.)
jabberwockish said:
What app did you use to try to rename the files?
Did you root your phone before attempting the rename? (See http://www.psouza4.com/droid3/ for instructions.)
Click to expand...
Click to collapse
the app that u suggested me,root browser lite and my phone was rooted and also have been granted superuser's permissions..
You didn't remount /system in Read/Write mode.
Gasai Yuno said:
You didn't remount /system in Read/Write mode.
Click to expand...
Click to collapse
please tell me how to do that
Root Explorer has a button for that.
“adb remount” when connected to a PC with USB debugging enabled will do that as well.
It's also possible to do from the terminal emulator, however I don't remember the exact command.
i can't find that button,by long pressing the file/folder or what?
It looks like this app defaults to RW once it gets superuser permission (GY was referring to Root Explorer, a different app). How about copying a system file, does that work?

Editing permissions

I root my phone as a thread
In the site but when I use root Explorer to edit permissions of some
Folders ex: system it says Warning
Permissions change was not successful. Please note that some file systems
(E. G. SD cars) do not allow permission changes
Also I use root Explorer as r-w
Sameh Amnoun said:
I root my phone as a thread
In the site but when I use root Explorer to edit permissions of some
Folders ex: system it says Warning
Permissions change was not successful. Please note that some file systems
(E. G. SD cars) do not allow permission changes
Also I use root Explorer as r-w
Click to expand...
Click to collapse
you rooted your phone as a thread?
what does that mean?
No some permissions are unable to change because it is for safe purposes because you might screw up your phone if you change the permissions or there is a duplicate file of it
Sent from my GT-S7500 using xda app-developers app
ShadowsDie said:
you rooted your phone as a thread?
what does that mean?
Click to expand...
Click to collapse
Sorryyyyyyyy for confusing you by not describing the way that I rooted the phone with
I ROOTED the phone by
1.put the phone in download mode
2. Flash CWM by ordin
3. put the phone in recovery mode
4.install zip superuser 3.1.1 arm. Zip
And I want to edit permissions of system folder to copy files to system/bin
Sameh Amnoun said:
Sorryyyyyyyy for confusing you by not describing the way that I rooted the phone with
I ROOTED the phone by
1.put the phone in download mode
2. Flash CWM by ordin
3. put the phone in recovery mode
4.install zip superuser 3.1.1 arm. Zip
And I want to edit permissions of system folder to copy files to system/bin
Click to expand...
Click to collapse
ok... i think there is a newer one in development section, with superuser 3.1.3
but i don't know if that is the problem, anyway you can redo the whole process of rooting, starting with flashing stock or you can change the app
i use root explorer and it works nicely, never had a problem with it
another thing you can try is flashing a custom rom, maybe its a firmware problem
ShadowsDie said:
ok... i think there is a newer one in development section, with superuser 3.1.3
but i don't know if that is the problem, anyway you can redo the whole process of rooting, starting with flashing stock or you can change the app
i use root explorer and it works nicely, never had a problem with it
another thing you can try is flashing a custom rom, maybe its a firmware problem
Click to expand...
Click to collapse
May you tell me a nice custom room
Sameh Amnoun said:
May you tell me a nice custom room
Click to expand...
Click to collapse
stock based: inspiration v17.3
AOSP: CM by TheWhisp

rooted but can't grant RW permissions on system folder

Z5 e6633 latest nougat patched kernel with twrp the root is installed properly but can't get RW permissions on system folder
I've tried every method and terminal command still doesn't work
MabroukM said:
Z5 e6633 latest nougat patched kernel with twrp the root is installed properly but can't get RW permissions on system folder
I've tried every method and terminal command still doesn't work
Click to expand...
Click to collapse
What you want to do ?
You can do everything in twrp.
L33Tgod said:
What you want to do ?
You can do everything in twrp.
Click to expand...
Click to collapse
I wan't to mount system as Read/write instead of read only.
MabroukM said:
I wan't to mount system as Read/write instead of read only.
Click to expand...
Click to collapse
I know that, I am not blind, but why do you want to mount it r/w, what you want to edit ?
MabroukM said:
Z5 e6633 latest nougat patched kernel with twrp the root is installed properly but can't get RW permissions on system folder
I've tried every method and terminal command still doesn't work
Click to expand...
Click to collapse
Explain clearly what you want to do with R/W permission?
Use Root Explorer : https://drive.google.com/drive/u/2/folders/0B9v3aNFonkyMdEtqYks0T0lPc2c
Use fx or ES File Explorer, there should be an option to mount system as r/w

I'm rooted, trying to install Xposed Framework, how do I delete a file from /system/?

I tried installing it with both Flashify and Magisk, but both methods failed.
When I tried installing it via the included Xposed Installer, it also failed, but gave me the message:
> Error: Xposed_Framework.jar already exists in /system/framework
I'm guessing a previous installation failed, but left the file there.
My next idea is to delete that file from /system/framework and try again, but since it's in an RO directory I don't have permission.
I tried using a terminal emulator to mount the drive in rw mode, and also tried using a root file explorer, but either both methods don't work, or I just couldn't figure it out.
Anyone have an idea of how to remove or rename that file so I can try to install the .zip ?
-Thanks
Highfiverobot said:
I tried installing it with both Flashify and Magisk, but both methods failed.
When I tried installing it via the included Xposed Installer, it also failed, but gave me the message:
> Error: Xposed_Framework.jar already exists in /system/framework
I'm guessing a previous installation failed, but left the file there.
My next idea is to delete that file from /system/framework and try again, but since it's in an RO directory I don't have permission.
I tried using a terminal emulator to mount the drive in rw mode, and also tried using a root file explorer, but either both methods don't work, or I just couldn't figure it out.
Anyone have an idea of how to remove or rename that file so I can try to install the .zip ?
-Thanks
Click to expand...
Click to collapse
In the Xposed app you should be able to just run the uninstaller script. If that doesn't work, boot TRWP and delete it from there.
D3RP_ said:
In the Xposed app you should be able to just run the uninstaller script. If that doesn't work, boot TRWP and delete it from there.
Click to expand...
Click to collapse
Unfortunately, the uninstaller also fails.
It says it can't remove that file from a read only directory..
Highfiverobot said:
Unfortunately, the uninstaller also fails.
It says it can't remove that file from a read only directory..
Click to expand...
Click to collapse
flash installer or uninstaller through TWRP
wmcdrugs said:
flash installer or uninstaller through TWRP
Click to expand...
Click to collapse
Root Explorer....
This app does wonders, it allows you to modify directories in /system and other root folders. You can even change permissions of specific folders/files from read/write/read-only....etc. I've had this app since the earliest of android days and it has been my go to file explorer. Root Explorer of course requires root....but it completely unlocks your phone and allows you to modify any system file that is set to any permission. Of course there are other file explorers that allow you to modify system files, but this is the one that i have the most experience with. You should be able to access the system folder where the Xposed file remains and modify it so it can fix your problem.
djer34 said:
Root Explorer....
This app does wonders, it allows you to modify directories in /system and other root folders. You can even change permissions of specific folders/files from read/write/read-only....etc. I've had this app since the earliest of android days and it has been my go to file explorer. Root Explorer of course requires root....but it completely unlocks your phone and allows you to modify and system file that is set to any permission. Of course there are other file explorers that allow you to modify system files, but this is the one that i have the most experience with. You should be able to access the system folder where the Xposed file remains and modify it so it can fix your problem.
Click to expand...
Click to collapse
This!. I've used it for years. Not muss no fuss. It's not bloated like a certain couple others I know of. It just does what it does and does it well. Manages files. No extra garbage.Give it a try. I'd be surprised if you can't delete it with Root Explorer. If you do try it, go to the folder you want to delete the file from. Once in there, look at the top right of the screen. Somewhere up there It will say MOUNT R/W. Touch that and you should be able to do whatever you want to within that folder.
Do you have the magisk DNSCrypt module installed? If so, thats why you cant modify anything in /system. Not sure why or how it breaks it, but it does. Took me for ever to figure out what was causing it. Now that i removed the module, i can modify anything i want again.
Sent from my [device_name] using XDA-Developers Legacy app

Categories

Resources