Hi all
I need to disable HDCP on my phone, I found many sources what to change but all need root f.e.
https://forum.xda-developers.com/xperia-z2/help/fix-hdcp-error-miracast-ezcast-screen-t3123560
I want to change those settings without unlocking boot-loader.
I already found a possible solution to use temp-root from backup drm keys thread.
https://forum.xda-developers.com/xp...devonly-exploits-temp-root-to-backup-t3795510
I'm not sure if later upgrade to the latest firmware overwrite /system/etc/ files. Does anyone know if FOTA upgrade will restore those settings
Related
Hi,
i've got the windows-boot-freeze issue on my wifes phone. Problem is, there are some important files stored in the main flash. as it is possible to gain access to the flash partitions via the bootloader, i think there should be a way or even a tool to access the files stored within. My problem is, i cant find such a tool / way
Maybe some of u guys can help me out
If the phone is CID unlocked you can use mtty to make a dump of the User Area to an SD card with the command: r2sd (something i can't recall now)
its a locked G4 device
Hi, I would like to have root access to my phone, but not necessarily with a custom ROM. I would also prefer to not change my bootloader.
What exactly is rooting? Is it replacing the whole system image with an image that gives the user root access? Or is it just like enabling sudo for the user? Or is a smaller part replaced? (I am somewhat familiar with electronics, computers and Linux, but I find the Android hacking a bit confusing )
Also, is it possible to run stock Android, only with root access? Will the access be lost when upgrading?
c3c0l0n said:
Hi, I would like to have root access to my phone, but not necessarily with a custom ROM.
DEV section rooting post /
What exactly is rooting?
root is the user account in Linux with all privileges. The root user can edit anything on the system. For safety reasons, users do not have all those privileges. When you root your phone, you will gain write access to areas of the phone you couldn't previously access and are allowed to run more commands in the terminal. Because applications do not get a lot of privileges, some of them require you to root the device in order for them to function properly (or fully).
Also, is it possible to run stock Android, only with root access?
Yes and Yes lost root on upgrade usually .
jje
Click to expand...
Click to collapse
Thank you. How is the rooting performed? Is only an ACL modified, or is a more fundamental part of the system changed (like the kernel, bootloader etc)?
I know that a custom ROM might be unstable/experimental, but does the same apply for rooting, or is the modification so small that one could expect the exact same stability as in the stock ROM?
c3c0l0n said:
Thank you. How is the rooting performed? Is only an ACL modified, or is a more fundamental part of the system changed (like the kernel, bootloader etc)?
I know that a custom ROM might be unstable/experimental, but does the same apply for rooting, or is the modification so small that one could expect the exact same stability as in the stock ROM?
Click to expand...
Click to collapse
All your questions are explained in detail in the Development section
Sorry, I did not find it. However, I read this without getting smarter. This video suggests that rooting is a process that does something with your phone without replacing everything. An exact list of what the rooting tools do would be perfect
Not all tools do the same thing. To get a specific answer, you will have to ask the person that came up with whatever rooting tool you are referring to. Some phones take more to root than others.
This distinction is written from the perspective of the TF201 - some of it is generic, some is specific to ASUS, or to just this device.
Bootloader unlock:
Custom Kernel possible
Official updates impossible
Waranty impacted
CWM backups possible
Need to use community ROMs in future
improved but not great chance of recovering from bad ROM flash (really needs NVFLASH)
Possible to overclock/overvolt through custom kernel
Rooted:
Now possible with tool with firmwares up to .28 (background)
Permits write access to /system partition
Makes it easier to brick and block OTA updates
Should be reversible
Allows most tweaks to be applied except for replacing kernel (which is a prerequisite for some kernels)
Can be maintained through incremental (OTA) updates using rootkeeper app.
Included in most custom ROMs by default
Limited overclock possible with stock kernel
The stock locked bootloader is cryptographically signed, and also checks that the kernal it loads is signed. These two parts are the first things to execute when you boot. The bootloader also checks for recovery/update files and installs them if they are signed. The unlocked bootloader is (probably) still signed, but it no longer cares about the kernel being signed, or updates being signed - this is how it gives you access to full custom ROMs.
Root/Unlock give you the following options:
+ Tweak system parameters to your preference
+ More functionality for launcher apps, etc
+ Backup/restore apps and settings
+ Lock/remove bloatware
+ Themes etc.
- Easy chance to brick with bad configs (maybe unrecoverable)
- High chance of problems with OTA updates
- Prevents movie rental if detected
- Waranty impacts (e.g. overclock/overheat, LCD damage, audio damage)
- Less secure, easier (or quicker with physical access) for hacker to bypass your security
Unwinding - Unroot/Relock
Rooting is reversable. In effect, root requires you to add a couple of files to the normally read-only /system area. These files may be included in a ROM which you flash, and you could easily un-root any ROM if you needed to. Some apps may check for the presence of root, for example.
On the prime, bootloader unlock is a one-way street. First, your serial number is logged by ASUS. 2nd, the process of unlocking is to replace your bootloader with one which no longer checks that it is loading a signed kernel - you are still unable to replace the bootloader. This makes it impossible for any dev to easily re-lock your prime. Unlocked can still flash any ROM (custom one or re-packaged stock) - just never a stock ROM direct from ASUS (either OTA or as a full-wipe).
I'll add links to some other posts later for most of the bullets above - feel free to offer contributions...
reserved...
very nice
maybe later you can add the difference between stock and rooted
some people still have no idea what the difference is
and or categorize them with + and -
Here are some questions about Android 4.3 and upper.
A pair of questions about unrooting/locking/unlocking/booting.
1) What are the benefits of rooting other than being able to a) set custom cpufrequency policies, b) being able to update your phone (to custom new ROMs like cyanogenmod) when your OEM has decided to stop supporting it, c) full filesystem access, d) tuning sysctl parameters?
I don't like the fact the rooting totally breaks Android's security model.
2) Do I understand correctly that a locked phone is the phone in which you cannot overwrite/replace/customize vmlinuz? or there are even stricter limitations?
3) Do I understand correctly that in order to change e.g. /etc files you don't really need a custom ROM, you can boot into TWRP and replace/edit/remove the needed files?
4) Why does unlock wipe all your data?
5) If the phone is locked, how bootloader/firmware understands that our bootloader is untempered? Does the bootloader have a digital signature? I have this question because let's imagine that I 1) unlock 2) change vmlinuz (allow superuser) 3) lock?
6) How does "oem lock" verifies that system data is genuine? Or it simply wipes everything clean? Does Android has some (RO) partition which always contains a genuine virgin ROM you cannot meddle with?
7) If I do "unlock" on my Nexus device, without changing anything or installing any 3d party bootloader (like TWRP), will I be able to update to new official ROMs via OTA updates?
8) Why every "lock" manual says that I need to upload a genuine official ROM - what if I've changed it and made it "rooted"?
Storage.
Why does Android has so many partitions?
What method is used to break the internal storage into partitions? Is it some kind of partition table (MS-DOS, GPT) or it's hardware based?
Thank you for answers.
Lovely. 4 years and zero answers.
Hi everyone!
I would like to know some things... Is it possible to unlock OEM/bootloader of said device? Dev options doesn't have the option and looking on the internet i only found solution for kirin960 while my model has kirin985 hardware. Primarily i've been looking for a possibility to root my device but as far as i know it's impossible without unlocking OEM. There was a thread on 4PDA which mentioned that it's only possible now by paying for the unlock code which is a bit ridiculous in my opinion.
To root a device's Android unlocking device's bootloader is NOT required at all.
jwoegerbauer said:
To root a device's Android unlocking device's bootloader is NOT required at all.
Click to expand...
Click to collapse
The only way i know of is to root using Magisk, and https://topjohnwu.github.io/Magisk/install.html here it says that your bootloader needs to be unlocked. Is there another way i don't know of?
Edit - also says that huawei devices are not supported
A phone's Android is rooted when SU ( read: Superuser , root ) binary is present in Android OS.
Here is what you have to do to root your device's Android:
Replace Android's Toybox binary - what is a restricted version by default - by unrestricted Toybox v0.8.5, means what has SU-binary implemented.
This can get achieved by means of ADB.
jwoegerbauer said:
Replace Android's Toybox binary - what is a restricted version by default - by unrestricted Toybox v0.8.5, means what has SU-binary implemented.
This can get achieved by means of ADB.
Click to expand...
Click to collapse
Is there a tutorial on how to do that? I've spent some time looking on forums what is toybox exactly and how to install it but i couldn't really find something beginner friendly