Related
Hi guys,
Just wondering if anyone has an update on the availability or possibility of root for LB Xperia Z5s on Marshmallow?
Also, can I assume that because root is not available on Marshmallow, then it will be equally unavailable on Nougat?
Just a quick thought for the more technically minded - Would it not be possible to deconstruct a valid stock .ftf file and insert a modified kernel, allowing root, before recompiling it and flashing it? I know the locked bootloader stops us from flashing a custom kernel, but is there no way to spoof an .ftf file into using a modified kernel?
Sorry for the n00bish questions, just wondering aloud.
Cheers!
As far as I know you need to disable some security settings in the kernel to have permanent root access. But a locked bootloader won't let the system boot with this modified kernel.
I don't think there will come a method to have root without unlocking the bootloader in the near future.
Nope. No root without unlocked the BL as far as I am informed.
ianrobbie said:
Hi guys,
Just wondering if anyone has an update on the availability or possibility of root for LB Xperia Z5s on Marshmallow?
Also, can I assume that because root is not available on Marshmallow, then it will be equally unavailable on Nougat?
Just a quick thought for the more technically minded - Would it not be possible to deconstruct a valid stock .ftf file and insert a modified kernel, allowing root, before recompiling it and flashing it? I know the locked bootloader stops us from flashing a custom kernel, but is there no way to spoof an .ftf file into using a modified kernel?
Sorry for the n00bish questions, just wondering aloud.
Cheers!
Click to expand...
Click to collapse
Short answer: not possible without unlocking the bootloader.
Long answer:
There are two possible methods for acquiring permanent root on Marshmallow on the Z5:
Conventional root - you provide root by modifying certain /system files on the phone. The problem with this is that you are modifying the system partition on the phone. The stock kernels on the Z5 (and most other phones) have something called dm-verity which basically checks everything on the system partition against what it expects to be there. If the kernel notices that something in the system partition has changed, the phone will fail to boot. You can install a modified kernel that has dm-verity disabled, but then you run into the issue described with systemless root.
Systemless root - you modify the kernel to allow for root either with Systemless SuperSU or through Magisk. This allows for you to have an unmodified system partition and pass any potential system checks, however you have to modify and flash a new kernel. Herein lies the problem with a locked bootloader. A locked bootloader checks the file signature for the file you're trying to flash. These files are typically signed by the phone manufacturer or carrier, so when the bootloader checks the file signature and it matches what it expects, then it allows the flash, if the signature doesn't match, then it aborts the flash. If you modify a stock kernel to disable dm-verity or try to flash a custom kernel, you will be prevented doing so because your signature won't match what the bootloader expects. By unlocking the bootloader you are essentially disabling that signature check process.
So basically permanent root on Marshmallow isn't possible unless somebody can exploit a vulnerability in the boot chain.
As for modifying a stock ftf package. You again run into issues with the bootloader signature checks. The ftf files is basically a special zip container that contains a bunch of files. Most of these files if not all of them are signed by either the manufacturer or carrier so you are able to flash it because all of these files pass the bootloader signature checks. Once you modify one of those files within the ftf, you destroy the signature and flashing of the ftf file will abort.
In summary, you need to unlock the bootloader so that you can flash a modified kernel that has dm-verity disabled.
Thanks very much for all the replies. Looks like I'm stuck with stock for the time being.
Ever since TA backup and bypassing the TA checks was possible since MM or whatever, unlocking the bootloader is not a big deal. Very easy to backup, unlock, root, re-lock, restore.
xasbo said:
Ever since TA backup and bypassing the TA checks was possible since MM or whatever, unlocking the bootloader is not a big deal. Very easy to backup, unlock, root, re-lock, restore.
Click to expand...
Click to collapse
Yeah, but unfortunately I'm not allowed to unlock my bootloader.
ianrobbie said:
Yeah, but unfortunately I'm not allowed to unlock my bootloader.
Click to expand...
Click to collapse
Ahhh, sure, forgot that some carriers lock these phones. I had that same problem on my Z1, but fortunately they found a LB root exploit.
How long have you had your phone? If the upcoming Nokia offering looks good, I'll sell you my mint condition UB Z5
I have successfully unlocked the bootloader my H83010i version.
I started down the path to root my device using H83010d tot file but stopped because I didn't know if when I upgrade to android 7.0 versions if I would lose root?
Therefore what is the easiest way to get to H83020f rooted?
How do I go from H83010i to H83020f and be rooted?
I have rooted a lot of samsung galaxy phones but this is my first LG so I am struggling a bit to understand how to upgrade. I assume if I do an OTA update it will install the latest version? I checked for system updates and it just said there is an update and to start downloading it but I don't know which update version that is?
Please advise.
Thanks in advance.
buyslake said:
I have successfully unlocked the bootloader my H83010i version.
I started down the path to root my device using H83010d tot file but stopped because I didn't know if when I upgrade to android 7.0 versions if I would lose root?
Therefore what is the easiest way to get to H83020f rooted?
How do I go from H83010i to H83020f and be rooted?
I have rooted a lot of samsung galaxy phones but this is my first LG so I am struggling a bit to understand how to upgrade. I assume if I do an OTA update it will install the latest version? I checked for system updates and it just said there is an update and to start downloading it but I don't know which update version that is?
Please advise.
Thanks in advance.
Click to expand...
Click to collapse
First of all, no need to use 10D tot file anymore. Download and install 20A kdz front autoprime located here:
https://forum.xda-developers.com/tmobile-lg-g5/development/stock-h830-20a-rom-flashable-zips-imgs-t3511294
Once that's installed, set up your system and then follow the following guide to get TWRP an root:
https://forum.xda-developers.com/tmobile-lg-g5/development/root-h830-running-30a-nougat-t3524322
After you have TWRP and root download the flashable 20F zip and install from TWRP (make sure to delete recovery from boot.p file after installing and also flash root). Here's the link to 20F:
https://forum.xda-developers.com/tmobile-lg-g5/development/stock-h830-20f-rom-flashable-zips-imgs-t3592855
If you follow all of that, you will be on stock 20F, rooted and with TWRP. After that, I recommend checking out the following custom kernel and installing that and using magisk instead of SuperSU. Kernel located here:
https://forum.xda-developers.com/tmobile-lg-g5/development/jan-17-2017-20c-deodexed-kernels-t3539611
Hopefully that helps, if you need more help just ask.
Thanks so much for taking the time to write me this great information. I have a question about the (make sure to delete recovery from boot.p file after installing and also flash root). ???????? Is this explained clearly somewhere? I don't know what I should do.
buyslake said:
Thanks so much for taking the time to write me this great information. I have a question about the (make sure to delete recovery from boot.p file after installing and also flash root). ???????? Is this explained clearly somewhere? I don't know what I should do.
Click to expand...
Click to collapse
After flashing the 20F version from TWRP, it creates a recovery from boot.p file in the system directory. If you don't delete this file before rebooting, you will lose TWRP. So, after doing the recowvery method to get root and TWRP and then after you flash the 20F from TWRP, after it's done flashing go to main menu of TWRP, click on mount, check system, go back to main menu, click advanced, click file manager and go-to system directory and click on the recovery from boot.p file and then delete. Now you can reboot without losing TWRP. Then you can flash SuperSU or magisk for root
Your Device software cannot be checked for corruption. Lock the bootloader
Thanks for the fast responses. After many hours of studying the posts and I finally got my LG G5 running on H830_20F_DeOdexed rom withh Asgard version 4.5 kernal and rooted with SuperSU v2.74.
However I keep getting the "your device software cannot be checked for corruption. lock the bootloader message upon starting up. see attachment
Does everyone get that message? Or is there a way to remove it?
I thought the Asgard kernal said it got rid of that?
buyslake said:
Thanks for the fast responses. After many hours of studying the posts and I finally got my LG G5 running on H830_20F_DeOdexed rom withh Asgard version 4.5 kernal and rooted with SuperSU v2.74.
However I keep getting the "your device software cannot be checked for corruption. lock the bootloader message upon starting up. see attachment
Does everyone get that message? Or is there a way to remove it?
I thought the Asgard kernal said it got rid of that?
Click to expand...
Click to collapse
You'll always have that message, no current way around it. Asgard kennel will allow you to pass safety net if you use magisk instead of SuperSU for root as it hides that the bootloader is unlocked from the system.
Where is Magisk?
jeffsga88 said:
You'll always have that message, no current way around it. Asgard kennel will allow you to pass safety net if you use magisk instead of SuperSU for root as it hides that the bootloader is unlocked from the system.
Click to expand...
Click to collapse
Are you saying that boot up message will not be there if I switch to Magisk?
I tried to find magisk but I was unable to locate the install file and instructions on how to change from SuperSU to magisk. Do you know the link to it?
buyslake said:
Are you saying that boot up message will not be there if I switch to Magisk?
I tried to find magisk but I was unable to locate the install file and instructions on how to change from SuperSU to magisk. Do you know the link to it?
Click to expand...
Click to collapse
No. I said currently there is no way to get rid of that message unless you lock the bootloader and you can't do that after modifying the system (i.e. installing TWRP and root). I said magisk will allow you to pass safety net. All that does is allow you to use apps that won't work with root / unlocked bootloader. If you don't use apps like Android pay or other apps that don't work when rooted, it really isn't necessary to switch from SuperSU to magisk. Anyways, if you're interested in magisk use Google (or XDA search) and search magisk XDA.
As title say, i have a M503 Just5 Phone, i was trying to install xposed on it but i think i wipe the OS, what can i do now?
Hi!
Download SP-Flash Tools and install oficial firmware again, you can download SP-Flash Tools and original FW from here:
https://forum.zwame.pt/threads/smar...ghz-1gb-ram-8-mpx-tras-5-mpx-frontal.1008028/
Is there any newer rom for this phone apart from the one on Zwame forum?
brunomcf said:
Is there any newer rom for this phone apart from the one on Zwame forum?
Click to expand...
Click to collapse
There's a modified stock without malware just posted there
Anyone knows how to bypass FRP?
Tried to delete persist, but not allowed cause bootloader is locked...
cant unlock bootloader in fastboot with oem unloock, i guess i have to turn on debugging mode on first, but im locked out of the system.
EDIT: Finally managed to digg into talkback mess around with youtube app and open browser to download Apex Installer
My brother asked me to root his phone, but later on he said he didn't want to format. I had already flash dm-verity disabler, so I'm now trying to re-enable it or something to boot back to stock ROM again, even if it means no root. Any thoughts? (Samsung Galaxy S7 GM-930F oreo)
Hyoretsu said:
My brother asked me to root his phone, but later on he said he didn't want to format. I had already flash dm-verity disabler, so I'm now trying to re-enable it or something to boot back to stock ROM again, even if it means no root. Any thoughts? (Samsung Galaxy S7 GM-930F oreo)
Click to expand...
Click to collapse
You can encrypt your device though settings menu ( in security menu ). I have not used this method so can't say what happens to root. If twrp is installed you will have to reformat data again to flash anything.
Or
Flash stock firmware through Odin. This will generally remove root ( and twrp if installed ).
Always do a backup before doing anything.
Hi guys and girls,
I bought a oneplus 7 pro recently and wanted to unlock the bootloader and root it to install the xXx Nolimits mod except I made some errors (I believe I removed too much bloatware with the .profile file, my WIFI and my mobile data were no longer working), so I re-lock the bootloader except that I got this error message: "Your Device is corrupt. It can't be trusted and will not boot", I was scared for a moment but I managed to access the fastboot and re-unlock the bootloader this time to remove everything that was not there in the stock phone and re-lock the bootloader.
I did all the checks after re-locking my bootloader (root check, safety net check, sensor check, Widevine check and stock recovery check).
My question is: is it possible that something has been changed in the low level of android? (I just install TWRP with fastboot, flash Magisk with TWRP and finally flash the xXx nolimits mod).
Thanks for your help !
oops I created another thread by editing my old one. Sorry.
isman77 said:
oops I created another thread by editing my old one. Sorry.
Click to expand...
Click to collapse
Hi
You are going to be flogged! [emoji6]
Envoyé de mon GM1913 en utilisant Tapatalk
isman77 said:
Hi guys and girls,
I bought a oneplus 7 pro recently and wanted to unlock the bootloader and root it to install the xXx Nolimits mod except I made some errors (I believe I removed too much bloatware with the .profile file, my WIFI and my mobile data were no longer working), so I re-lock the bootloader except that I got this error message: "Your Device is corrupt. It can't be trusted and will not boot", I was scared for a moment but I managed to access the fastboot and re-unlock the bootloader this time to remove everything that was not there in the stock phone and re-lock the bootloader.
I did all the checks after re-locking my bootloader (root check, safety net check, sensor check, Widevine check and stock recovery check).
My question is: is it possible that something has been changed in the low level of android? (I just install TWRP with fastboot, flash Magisk with TWRP and finally flash the xXx nolimits mod).
Thanks for your help !
Click to expand...
Click to collapse
Just use MSMtool to reflash your phone. The links are in the guides section
isman77 said:
Hi guys and girls,
I bought a oneplus 7 pro recently and wanted to unlock the bootloader and root it to install the xXx Nolimits mod except I made some errors (I believe I removed too much bloatware with the .profile file, my WIFI and my mobile data were no longer working), so I re-lock the bootloader except that I got this error message: "Your Device is corrupt. It can't be trusted and will not boot", I was scared for a moment but I managed to access the fastboot and re-unlock the bootloader this time to remove everything that was not there in the stock phone and re-lock the bootloader.
I did all the checks after re-locking my bootloader (root check, safety net check, sensor check, Widevine check and stock recovery check).
My question is: is it possible that something has been changed in the low level of android? (I just install TWRP with fastboot, flash Magisk with TWRP and finally flash the xXx nolimits mod).
Thanks for your help !
Click to expand...
Click to collapse
From what I've seen from a few people on here, nolimits doesn't really do anything useful. Debloat a few apps but everything else it doesn't isn't that good, apparently. I used it before and thought it was good. But I'm pretty sure I get better battery and performance on stock with a custom kernel and used something else to debloat.
Also, as some else suggested, MSM tool is great to get back to stock with everything proper.
Thank you for your answers @Jinsuke32 and @GeekMcLeod
I would like to know if you can use MSM Tool with a locked bootloader and does this tool erase all data during flash?
isman77 said:
Thank you for your answers @Jinsuke32 and @GeekMcLeod
I would like to know if you can use MSM Tool with a locked bootloader and does this tool erase all data during flash?
Click to expand...
Click to collapse
Not sure if it can be used with locked bootloader. But it erases everything.
GeekMcLeod said:
Not sure if it can be used with locked bootloader. But it erases everything.
Click to expand...
Click to collapse
Ok, thanks for your quick response.