Is root absolutely necessery for flashing ports? - Galaxy S III Q&A, Help & Troubleshooting

Hi everybody. I learned so much from this forum (and also from others) in one year and tried to share my knowledge to those who try to learn like me.
Now i would like to share one of my experiences. i dont know if someone wrote about this, yet i could not find anywhere in this forum. When we share a "port" for example "s4 keyboard for s3", we say that we need root access in order to use this port. But when i think, if this apk files replace themselves with the original ones and rom thinks that they are the originals, why should we need root access? Of course we need recovery to flash them but do we absolutely need root? And i flashed 3 separate ports (keyboard, launcher and callrecord) into a fresh installed 4.3 MK6 stock rom without root and they worked... and still do... (scripts have to delete odex files automatically)
Installing a recovery will increase the binary counter and since your binary is up why not rooting right? But those who dont want to root their phone but still want to use the visuality, can install a recovery and flash the ports without rooting... Tested and proven...

You need root access for applications/ports that will need to be installed in system directories (that only the superuser can alter). Some directories/partitions are read-only, so you have to mount the them as writable too. It all depends on the application.

alex.sg said:
You need root access for applications/ports that will need to be installed in system directories (that only the superuser can alter). Some directories/partitions are read-only, so you have to mount the them as writable too. It all depends on the application.
Click to expand...
Click to collapse
If editing apps from rom then yes. But if you are flashing them through recovery you dont need root access for read and write permitions. Script also does that itself. Thats what im talking about
Galaxy S3 tapatalk 2 ile

Related

[Q] Root (technically) explained

This is not a question about how to root the Atrix. I've already done that.
My question is about what actually is changed in the phone by following the root procedure. (I searched the forum but didn't find elsewhere the answers I look for).
Why do I ask?
1) Because I'd like to have a better understanding of the android OS.
2) Because I'd like to understand and know what do I need to do in case I want to unroot and return to plain stock.
My case:
(I've just rooted my Atrix. I didn't unlock it)
I've followed the "manual" procedure proposed by BriefMobile.
I can essentially understand (more or less) the commands listed (mount, remount, cp, install, chmod 6755, flash...)
What I'd like to understand better is what changes does the command
Code:
fastboot flash preinstall root.img
Does it just copy new files? Or does it copy (and replace) files on the phone?
(In the second case I'm afraid I made a mistake in not backing them up before running that command...)
Thanks in advance for your help.
Putting it in Windows terms (because Android is Linux), root is like having administrator privileges on your computer. It allows you to modify any system files that would normally be kept locked down. It also allows you to run applications, such as SetCPU, which can directly control hardware (in this case CPU frequency/speed and voltage) and low-level system files. Root in Android is comprised of two main files: the "su" binary (which is the command that applications use to invoke a request to do something with root privileges) and the SuperUser.apk (SuperUser app that's in the app drawer). The SuperUser app exists to prompt you whenever an application asks for root permission. So if you go into the terminal and type a low-level command, you'll see something like, "You do not have permission to do this". But if you type "su" before the command, it will run if you hit "Allow" on the SuperUser request.
Get it?
Product F(RED) said:
....
Get it?
Click to expand...
Click to collapse
Thanks Product F(RED) .
Yes I got it.
I already knew what rooting means in general terms.
What I really asked (sorry if I wasn't clear enough) is what does the root "physically" change on the phone.
According to your answer I assume it just adds the "su" binary and the "SuperUser" app (apart from changing some permission on some system folders) and that it doesn't replace any "stock" system file.
I also assume that these new files are extracted from the "root.img" (or "preinstall.img") files flashed by the fastboot command.
Is it so?
I was a little confused because I saw in some other forum a reference to some "stock" files wiped out in the /preinstall/app/ folder by the root process, mining the reversibility of the procedure (in case of no previous full system backup).
sphere314 said:
Thanks Product F(RED) .
Yes I got it.
I already knew what rooting means in general terms.
What I really asked (sorry if I wasn't clear enough) is what does the root "physically" change on the phone.
According to your answer I assume it just adds the "su" binary and the "SuperUser" app (apart from changing some permission on some system folders) and that it doesn't replace any "stock" system file.
I also assume that these new files are extracted from the "root.img" (or "preinstall.img") files flashed by the fastboot command.
Is it so?
I was a little confused because I saw in some other forum a reference to some "stock" files wiped out in the /preinstall/app/ folder by the root process.
Click to expand...
Click to collapse
Pretty much, yes, you're adding those two files (as well as another called BusyBox that allows other files to run, but this you can install after you root). The scenario I'm describing is that you're on a stock ROM and you just rooted your phone for the first time.
Though fastboot is present on every phone, using it to flash those two files seems to be unique to your phone because rooting methods vary from phone to phone. But basically the two most common methods are:
1. You flash a custom recovery from your computer if your phone's bootloader is not locked, and then you can flash the root files (su/SuperUser.apk) to the ROM from there or just flash a custom ROM that includes them.
or
2. You use fastboot/adb/some third-party method to root the stock ROM on your phone from your computer, then you install a custom recovery, and then you can flash custom ROMs/kernels/etc.
That /preinstall/app folder seems to be unique to your phone, but if I had to guess, it has something to do with deleting preloaded bloatware that comes with the phone. Because out of the box you can't, but once you have root permissions, you can go to that folder with a file manager to delete the APKs or use something like Titanium Backup to do it.
Product F(RED) said:
Pretty much, yes, you're adding those two files (as well as another called BusyBox that allows other files to run, but this you can install after you root). The scenario I'm describing is that you're on a stock ROM and you just rooted your phone for the first time.
Though fastboot is present on every phone, using it to flash those two files seems to be unique to your phone because rooting methods vary from phone to phone. But basically the two most common methods are:
1. You flash a custom recovery from your computer if your phone's bootloader is not locked, and then you can flash the root files (su/SuperUser.apk) to the ROM from there or just flash a custom ROM that includes them.
or
2. You use fastboot/adb/some third-party method to root the stock ROM on your phone from your computer, then you install a custom recovery, and then you can flash custom ROMs/kernels/etc.
That /preinstall/app folder seems to be unique to your phone, but if I had to guess, it has something to do with deleting preloaded bloatware that comes with the phone. Because out of the box you can't, but once you have root permissions, you can go to that folder with a file manager to delete the APKs or use something like Titanium Backup to do it.
Click to expand...
Click to collapse
Thanks again Product F(RED).
Things are clearer now.
I wasn't aware of the installation of "BusyBox" (I found it in my phone in the folder /osh/bin/)
I think the root method I used (BriefMobile) is the type 2. I didn't install a custom recovery as I'm not interested yet in flashing custom ROMs/kernels/etc.
So, to summarize...
The basic root methods (no unlock) consists in
1) install the "su" binary
2) install the "busybox" binary
3) install the "superuser.apk" app
4) change some r-w permissions
In my case (probably) the root method also wiped out some preloaded bloatware file in the /preinstall/app folder but that's not essential (unless Moto makes a check for the presence of those files before an OTA update).
They usually do check (and will fail) because OTA's are like patches; not really replacements for the whole /system/ partition. Never take an OTA when you're rooted, especially because they can do things like update and lock your bootloader, among other things. It's safer to wait until rooted versions pop up in the development section for your phone.

[Q] MTK6573 custom recovery and backups / Stock Boot, Recovery + Scatter included

Phone is a Star X19i
Now I'm looking at getting a system to allow me to back up the rom and re-flash if needed.
Post 4 has attachments of my boot, recovery and scatter files.
Old issue: (Solved)
Stupid thing I did I renamed the mtklockscreen.odex to mtklockscreen.odex1 just as a test in a half asleep phase to see if I would get the stock lockscreen loading.
Suffice to say the phone no longer boots.
Really don't think I can get into ADB and rename the file to get the phone booting again unless anyone knows a way.
Android was 2.3.6 and I asked the seller if it was possible to get the rom incase anything like happened which they didn't.
So anyone have any ideas?
I have attached the stock recovery and boot images made with cat and a scatter file I made to post 4.
As I have no idea about modifying these for hard root can anyone take a look?
I don't know the specifics of the phone, but if you can go into recovery mode maybe you can get adb working, or use a flashable zip to rename the file by installing it from recovery (just need to edit the zips' updater script)
dxppxd said:
I don't know the specifics of the phone, but if you can go into recovery mode maybe you can get adb working, or use a flashable zip to rename the file by installing it from recovery (just need to edit the zips' updater script)
Click to expand...
Click to collapse
I got into built in Factory mode and can see the file I renamed through ADB and android commander but cannot rename it back due to not having hard root access.
I also have a copy of the boot and recovery partitions 5 and 6 respectively I made in the adb shell yesterday as I was half looking at getting hard root access.
ren mtklockscreen.odex1 mtklockscreen.odex
ren: permission denied
I read you can do a custom recovery with root using SP Tools still so can anyone help me do this?
I know about system root etc and stuff and have flashed roms before on other tablets and have been a PC I.T tech (wouldn't think it due to the stupid mistake) but this recovery and scatter files etc is kinda new to me.
I have a scatter file now I just made if anyone is interested in helping me.
Yes I have a MTK6573 but the scatter file came from the MT6516 Rom Studio which I read works the same for the 6573.
Attached is also my stock boot and recovery partitions I made with cat yesterday if there usable to anyone to help.
Well I got it working and fixed.
I had to go into adb shell and su and mount the file system as writable, as I have used linux before I didn't know about android and what needed to be done and permission locks etc.
The stock boot, recovery and scatter files will remain on this thread if anyone wants to help create or find a recovery which can allow me to create backups and flash custom roms.
I may be able to provide a dump of android 2.3.6 for those that want it once I'm provided with a backup solution as I have read a few people wanting this updated android rom.
This got too close to what I would like liked with bricking this phone.
And I'm not comfortable unless I have a rom backup of this.
Rooting Advice: For anyone with a MTK6573 on Android 2.3.6 trying to root but having issues with super one click make sure you only turn on USB debugging after Android has loaded and just before you plug the usb cable in to run super one click.
I have seen a few thread and posters here about not being able to root the phone and this is the cause that debug needs to be switched on right before you connect and try to root.
Original seller has agreed to send the firmware and flashing stuff on cd for me so I can upload it for you all.
This is a win for MTK6573 Star X19i owners as I'll have the updated 2.3.6 Gingerbread firmware to release for you all root modify etc in a week or so.
Be careful with ROM studio. I believe it is not compatible with MT6573.
You want to read this: http://bm-smartphone-reviews.blogspot.com/2012_04_01_archive.html
cybermaus said:
Be careful with ROM studio. I believe it is not compatible with MT6573.
You want to read this: http://bm-smartphone-reviews.blogspot.com/2012_04_01_archive.html
Click to expand...
Click to collapse
That's what I read and did to get my scatter as I used cat then used the program linked in that thread to generate the scatter.

[Q] I still can't access system file permission

My XZU kitkat 4.4.4 .108 have rooted. Stock rom. I want to set Ext SDcard for Titanium Backup. But I can't access permission (etc/permissions/platform.xml) to change to writeable. I have tried Root Browser, Root Explorer, Solid Explorer and ES File Explorer. All no luck.
It pop up error ***operation failed message: cannot write to filesystem. Mount as read/write has failed***
But I have success to my rooted TabPro 8.4 SMT-325. Kitkat 4.4.2 with Solid Explorer or Root Explorer.
Another problem is I can't install busybox.
Any help or input
Thanks
Hi there,
Please wait until mods will move this thread to the device specific forum for more relevant answers.
Stand by
talongt said:
My XZU kitkat 4.4.4 .108 have rooted. Stock rom. I want to set Ext SDcard for Titanium Backup. But I can't access permission (etc/permissions/platform.xml) to change to writeable. I have tried Root Browser, Root Explorer, Solid Explorer and ES File Explorer. All no luck.
It pop up error ***operation failed message: cannot write to filesystem. Mount as read/write has failed***
But I have success to my rooted TabPro 8.4 SMT-325. Kitkat 4.4.2 with Solid Explorer or Root Explorer.
Another problem is I can't install busybox.
Any help or input
Thanks
Click to expand...
Click to collapse
Did you install nut's dual recovery by chance? It has busybox included and if you try to install another busybox it screws up root. For SD card try this app, if you are still rooted and have superuser installed properly it should work.
https://play.google.com/store/apps/details?id=nextapp.sdfix&hl=en
adfurgerson said:
Did you install nut's dual recovery by chance? It has busybox included and if you try to install another busybox it screws up root. For SD card try this app, if you are still rooted and have superuser installed properly it should work.
What's nut's dual recovery?
I did try SDFix already, it doesn't work to me.
The purpose I need access permission is modify platform.xml for Titanium backup and mixer_paths.xml for volume boost headphone.
I heard about a custom rom can access permission mostly, is it true? If yes, I might try flash to custom rom.
Click to expand...
Click to collapse
If SD card fix doesn't work and gives you an error message. You don't have true root access.
I know because I faced this issue about a month ago, I was able to get superuser access just not edit files I know because I tried to edit the platform as well, so re-root your phone and install the dual recovery (optional?) if you make it that far, run kk fix it should work.
The volume boost is meh, you're better with viper4android
RealityFails said:
If SD card fix doesn't work and gives you an error message. You don't have true root access.
I know because I faced this issue about a month ago, I was able to get superuser access just not edit files I know because I tried to edit the platform as well, so re-root your phone and install the dual recovery (optional?) if you make it that far, run kk fix it should work.
The volume boost is meh, you're better with viper4android
Click to expand...
Click to collapse
The root checker show **device have rooted**
I used Easyroot. Does your meaning use easyroot to re-root the phone again? Or get another tool? Any rooting tool suggestion.
Should I unroot from supersu before re-root?
Yes I know that.. Like I said I had the same issue, you may have root access but you don't have true root, so re-root your phone. It will fix the issue.
So again re root your phone.
And for me I did not uproot I just ran the root exploit and overwrited the old su
Great! I'll try to root again tonight.
BTW, is your device is XZU and root by Easyroot.
Thanks
Nah I have galaxy s2 but posting in xzu section. Yes I have Xperia Z ultra. And yes I did the easy Xperia root, plus I have dual recovery
IT WORK !
As you said re-root device again. Access permission available and Titanium backup to extsd.
Thanks all you guys input.
Zomg don't forget to thank me, hit the thanks button. *sarcasm

Root access development

Before you read this trough : This is not a question about how to root my phone or add root access to an app. This is about how I can add root acess to my phone. I mean like ading root acess to a phone where no root is yet released. If anyone knows a github repo with the commits of adding root to the phone, please tell me. Thanks!
CTXz said:
Before you read this trough : This is not a question about how to root my phone or add root access to an app. This is about how I can add root acess to my phone. I mean like ading root acess to a phone where no root is yet released. If anyone knows a github repo with the commits of adding root to the phone, please tell me. Thanks!
Click to expand...
Click to collapse
you don't want to root device (for example: kingo root, Iroot, etc) u want to compile su file or what??
Paget96 said:
you don't want to root device (for example: kingo root, Iroot, etc) u want to compile su file or what??
Click to expand...
Click to collapse
I currently don't look to compile for a specific device but I want it as basic knowledge when it comes to the case of a new device that has no root yet.
CTXz said:
Before you read this trough : This is not a question about how to root my phone or add root access to an app. This is about how I can add root acess to my phone. I mean like ading root acess to a phone where no root is yet released. If anyone knows a github repo with the commits of adding root to the phone, please tell me. Thanks!
Click to expand...
Click to collapse
"How I can add root access to my phone" = root your phone? There's not much difference between the two sentences. Unless you mean adding the root path to the device without installing SuperSU or any other SU app?
popthosegaskets said:
"How I can add root access to my phone" = root your phone? There's not much difference between the two sentences. Unless you mean adding the root path to the device without installing SuperSU or any other SU app?
Click to expand...
Click to collapse
Look. You have a phone that doesn't have root access. So what I would do is go to xda, find a root IMG to flash on my phone and then flash it. That would give me root access to the phone. The thing is, if there is no flashable IMG I would develop one by myself. Now I can't find any tutorials or sources of how to build a image like that.
Sent from my SM-G800F using XDA Free mobile app
1. Such methods would depend on your phone, not all phones go through .img file flash.
2. Usually I would associate .img files as kernel. So I assume you want to flash a custom kernel?
3. If you indeed want to flash a custom kernel, you still need root on the ROM before the custom kernel can have root access.
CTXz said:
Look. You have a phone that doesn't have root access. So what I would do is go to xda, find a root IMG to flash on my phone and then flash it. That would give me root access to the phone. The thing is, if there is no flashable IMG I would develop one by myself. Now I can't find any tutorials or sources of how to build a image like that.
Sent from my SM-G800F using XDA Free mobile app
Click to expand...
Click to collapse
There are several steps to go about to developing a rooting procedure for a device when none has been released yet. The first key step would be to identify whether the device has a looked bootloader. If it does then you will need to resort to an exploit to gain root access rather then flashing a pre-rooted boot.img for example unless you can figure you a way of bypassing the img signature check which in many cases using an exploit is easier. A good basic place to start looking for exploits is here. You will then have to do research on how to exploit the security flaw which involves knowledge of Assembly, C, and Linux. If the bootloader is unlocked you can attempt to make a superboot or autoroot type boot.img which I would suggest taking an existing .img of those types and disasembling them to learn how they were created. Let me know if you still have any questions.

Can't install SuperSU with TWRP

Hi everyone. I'm trying to root my Alcatel 1T 7 8067, by using TWRP 3.2.1 and zip SuperSu images, but rooting was unsuccessful.
The last successful root that I got with that method, was on a marshmallow android device (a CATS60), with no issues; but on my recent device (with oreo go), when I try to install supersu by TWRP option "install", it begins to install, and the process log shows apparently an error: "Patching Sepolicy -----Failure, aborting", and when I reboot to system, there is no root access.
As result of those failed attempts, I have tried by installing old versions of supersu with apparent success, but then, when I try to boot the device, it enters into a bootloop.
So I think, that unsuccessful rooting is related to that Sepolicy error ¿Am I right?
I've noticed that there's no SU folder inside /system folder, so, as I understand, it means supersu wasn't installed (I can see that by using the TWRP's file explorer).
So ¿What can I do with that issue?
I've read that Magisk can solve this problem. Following tutorials about, I tried by flashing a magisk patched boot image, but supersu installation issue still continues.
I must say, that I prefer supersu over magisk, because is more familiar to me, but in general what I need, is a system root, a real root access; not a systemless root; and based on my experience, I only can get that with supersu.
@Camilo Gil I don't really understand your point "real root access".
On my Magisk rooted devices I can access any system file and even change it externally and write it back into system.
I used SU previously but as further development has stopped I had to switch anyway.
superSU? do you live in 2010? get rid of that old stuff and use magisk, SupeSu is totally useless in android 7+
bmwdroid said:
@Camilo Gil I don't really understand your point "real root access".
On my Magisk rooted devices I can access any system file and even change it externally and write it back into system.
I used SU previously but as further development has stopped I had to switch anyway.
Click to expand...
Click to collapse
By real root access, I want to mean, that SU binaries are installed on /system folder. As I understand, if that requirement is given, all apps that need root access, can fully work, without any limitations. Recently, I tested magisk, supposedly my device already had root access. Then I installed ES file explorer to give it root access, and it was granted on magisk but root access couldn't be activated in the app. That never happened me before.
As I understand, that's because ES file explorer couldn't find SU binaries, because magisk root method is systemless root.
I hope I would explain myself right.
tutibreaker said:
superSU? do you live in 2010? get rid of that old stuff and use magisk, SupeSu is totally useless in android 7+
Click to expand...
Click to collapse
¡More o less! I live in 2018, or at least that was the last date when I rooted a device (CAT S60, android 6.0). I don't trust on Magisk, just because I couldn't give root access to ES file explorer. That never happened me before. And I know there are many more file explorers; I know that Es file explorer is kinda deprecated, and root explorer works fine; but I want a root access on which any app that needs root access, and that I want to install obviously, can work without any limitation. My firsts impressions of magisk root is that it cannot provide that service.
Now, what you say that supersu is useless, it's worrying to me, because I can't see any other alternative for root access.
¿Why do you say it's useless?
Camilo Gil said:
¡.... I want a root access on which any app that needs root access, and that I want to install obviously, can work without any limitation. My firsts impressions of magisk root is that it cannot provide that service......
Click to expand...
Click to collapse
Yes it can but in a different way.
You're asked once to grant root privileges for each app that needs it and if you let it have root that's it.
Or you grant root temporarily and will be asked every time for this app.
Apps that don't need it don't get it.
You can change your decision afterwards as well.
Btw I use Total Commander with LAN plugin to access my NAS.
bmwdroid said:
Yes it can but in a different way.
You're asked once to grant root privileges for each app that needs it and if you let it have root that's it.
Or you grant root temporarily and will be asked every time for this app.
Apps that don't need it don't get it.
You can change your decision afterwards as well.
Btw I use Total Commander with LAN plugin to access my NAS.
Click to expand...
Click to collapse
With magisk, I grant root access to ES file explorer, but I can't enable it on the app. As I read, that's because ES File Explorer can't find SU folder in system folder (which actually happens on system root), and because of that, some apps like es file explorer, won't detect systemless root or better, to them, systemless root is detected as non root access.
I read that even supersu must be installed as systemless root, because if installed as system root (or what I refer as "real root") on android 7+, causes bootloops. On my particular case, system root causes an endless boot. As I understand, that happens because supersu can't set /system folder to R/W, on android 7+.
On the other hand, I know there are several alternatives to ES file explorer, for instance Root Explorer, Total Commander, etc. But it's just I'm accustomed to it. But also I read that systemless root not only can cause issues with ES File explorer, but also with Viper4android and some other Xposed modules.
PS 1: We should suggest to google, that release an official rooted android version, specially addressed for us, the medium skilled and advanced android users (that normally we like to root android and get the most of it).
PS 2: So finally ¿is there any way to have a working system root access in oreo, or systemless root is the only option?
Camilo Gil said:
... because if installed as system root (or what I refer as "real root") on android 7+, causes bootloops.
Click to expand...
Click to collapse
I can't remember on which LOS version or when I used it the last time before switching to Magisk.
Camilo Gil said:
On my particular case, system root causes an endless boot. As I understand, that happens because supersu can't set /system folder to R/W, on android 7+.
Click to expand...
Click to collapse
Idk
Camilo Gil said:
On the other hand, I know there are several alternatives to ES file explorer,
Click to expand...
Click to collapse
There seem to be several with that name so just tell me it's full correct name and I will install it on my Magisk rooted LOS14.1=Nougat tablet and see if I get problems with it.
Camilo Gil said:
... Viper4android and some other Xposed modules.
Click to expand...
Click to collapse
don't use them so can't tell
Camilo Gil said:
PS 1: We should suggest to google, that release an official rooted android version, specially addressed for us, the medium skilled and advanced android users (that normally we like to root android and get the most of it).....
Click to expand...
Click to collapse
afaik the pure Vanilla is the base from which most custom ROMs are built by the devs and imo most ROMs you can get are not rooted as it's of course a safety hazard.
bmwdroid said:
afaik the pure Vanilla is the base from which most custom ROMs are built by the devs and imo most ROMs you can get are not rooted as it's of course a safety hazard.
Click to expand...
Click to collapse
I know a rooted android is a security and stability hazard of the device. But evidently who wants to root his/her device, is fully warned about its potential consequences. So google could publish a prerooted version, previously warning about its use, warning that its use is exclusively under user responsability, and maybe disclaiming liability for damages. I guess there's no problem if users of that (at the current moment) imaginary OS , are aware of the risk that they are taking by using it. At least, I would use it if could (and as it doesn't exist, it's because I'm trying to root my current one).

Categories

Resources