Related
Does having my bootloader unlocked affect getting updates? I have no interest in installing custom roms(for now), and mainly just want root to block ads, install seeder to fix this damn lag, and possibly connect a ps3 controller to play games. Figured I'd just unlock and root. I didn't plan on installing cwm so I could still get updates straight from google. I know an update would just overwrite root, but not sure if the bootloader would affect it. My galaxy nexus I always installed custom roms so I don't know how the bootloader affected OTA's. thanks guys.
In principle it should not affect updates.
Have a look at a prior OTA update's installer script
./META-INF/com/Google/android/updater-script
The OTAs perform binary patching on individual files, one by one. (That is why OTAs can be so small.) Before they perform the patching, a checksum is performed on every file on the tab/phone targeted for patching. If even one of those checksums fail, the entire install is aborted.
In addition the version of the recovery is sometimes checked, too - so merely having a custom recovery can trip up an OTA if that type of assert() check is performed.
To put that in general terms, you could say that an OTA update will almost always succeed if you merely add things to a ROM and leave the stock recovery in place.
If you want to flash stuff without altering the stock recovery just use a soft boot of a custom recovery, e.g. "fastboot boot custom-recovery-image-file.img"
If an OTA fails, don't get scared - you can simply unpack it, modify the updater-script file to remove the failing assert(), re-zip it and flash it. This would need to be done with a custom recovery, though as the modified OTA would no longer be correctly signed.
HTH
Yes but don't remove any of the Google apps that come preinstalled, don't edit the build prop, and that might be it.
Sent from my Nexus 7 using Tapatalk 2
BrianDigital said:
Yes but don't remove any of the Google apps that come preinstalled, don't edit the build prop, and that might be it.
Click to expand...
Click to collapse
yep.
The most recent OTA had the boot image file as one of its patching targets, so it was also subject to checksum verification during the initial assert() sequence of "updater-script".
I guess that means that if you hook anything into the boot sequence that needs to be in the ramdisk, that will trip up the OTA, as it is pretty typical for OTA updates to diddle the kernel or ramdisk. I guess that if you want to stay on a near-factory base distro including new ota updates, that puts the onus on you to either
(a) check the installers of the stuff you flash to make sure the boot image is not being re-packed -or-
(b) maintain a chain of pure stock backup sequences: then you can then restore them, run the OTA patch kit on them, make a new nandroid backup, and re-run your custom flashes. Probably use TiB to restore your apps on top of that, too. Almost like an OS re-install sequence, frankly.
cheers
thanks guys! Does an update from google relock the bootloader? I'm guessing not since its a nexus and they're okay with us unlocking it but just wondering. Just trying to decide if its worth it. I feel myself using my nexus 7 less cause of the latest update. It's smooth once its running but turning the screen on after its been sitting, it take some time to get together.
tu3218 said:
thanks guys! Does an update from google relock the bootloader? I'm guessing not since its a nexus and they're okay with us unlocking it but just wondering. Just trying to decide if its worth it. I feel myself using my nexus 7 less cause of the latest update. It's smooth once its running but turning the screen on after its been sitting, it take some time to get together.
Click to expand...
Click to collapse
Whoops (old timers disease) I said "bootloader" in that post above where I should have said "boot partition" or "boot image". (Now corrected.)
Updates typically don't touch the bootloaders. Interesting question though - if you replace a bootloader via fastboot, does it change the lock status? To that Q I don't know the answer from direct experience.
Maybe I'll give it a try. Ugh that's gonna be a lot of backup/restore ops.
In the meantime, have you seen a page with links to (older) *full* ROM install bundles that Google no longer has on their site? I only got a N7 in early Jan '13, so I don't have any of those older full-ROM+bootloader fastboot-based install bundles.
bftb0 said:
Whoops (old timers disease) I said "bootloader" in that post above where I should have said "boot partition" or "boot image". (Now corrected.)
Updates typically don't touch the bootloaders. Interesting question though - if you replace a bootloader via fastboot, does it change the lock status? To that Q I don't know the answer from direct experience.
Maybe I'll give it a try. Ugh that's gonna be a lot of backup/restore ops.
In the meantime, have you seen a page with links to (older) *full* ROM install bundles that Google no longer has on their site? I only got a N7 in early Jan '13, so I don't have any of those older full-ROM+bootloader fastboot-based install bundles.
Click to expand...
Click to collapse
Nah I haven't seen that. To be honest I've been so busy with flashing roms on my sgs3. I finally have settled down on a rom for my phone so I figured I'd give my nexus 7 a go. But I'd rather not be performing the whole backing up/flashing/modding on both. Its so much lol Plus my tablet I need to be dependable when I need it. That's why I hadn't planned on running roms, just basic root for blocking ads, etc. Before the last update this thing was so fast and enjoyable to use. It still is but its not to where it use to be. I was going to go back but I don't like knowing I'm not on the latest.
and mainly just want root to block ads, install seeder to fix this damn lag, and possibly connect a ps3 controller to play games.
Click to expand...
Click to collapse
Seeder doesn't fix lag. Doesn't work. If your n7 is lagging then there is another cause.
Sent from my Nexus 7 using Tapatalk HD
Hi all,
I am kinda new here and would like to put a question, hoping it's not a repetition (I have been browsing though this forum thoroughly, but apparently couldn't find a proper answer). This is the situation:
- bought a used Z2
- Z2 was from UK O2 operator and it had operator lock and unlockable bootloader
- network operator lock has been cleared with unlock code
- O2 customized firmware has been wiped away by flashing a recent 5.0.2 stock lollipop
- unlockable bootloader still exists so cannot upload any customized/rooted .zip system
Clearly, the only thing I can do to modify this phone is to upload .FTF firmares to it, due to unlockable bootloader. Right now, I see available online only unmodified stock .FTF firmwares.
THE QUESTION: is there ANY way to create a pre-rooted .FTF file (modding not strictly necessay but rooting essential) so that I can upload it to the phone?
Thanks for all your precious advice!!!
You can't modify .ftf files as they are signed by sony. easiest solution is to root your phone with kingroot , install nut's dual recovery and then flash any stock prerooted zip (or a custom rom if you want) you can find on this forum. kingroot will be gone when you finish the .zip install too
ptmaniac said:
You can't modify .ftf files as they are signed by sony. easiest solution is to root your phone with kingroot , install nut's dual recovery and then flash any stock prerooted zip (or a custom rom if you want) you can find on this forum. kingroot will be gone when you finish the .zip install too
Click to expand...
Click to collapse
Thanks for answering!
Wouldn't just installing kingroot be enough for a simple rooting of the stock fw?
All I need is the ability to run some apps which need root (e.g. ad-away, set dns, etc.) and nothing more. Is the latest version tested on Z2 running 5.0.2?
Thanks again!
derjaeger said:
Thanks for answering!
Wouldn't just installing kingroot be enough for a simple rooting of the stock fw?
All I need is the ability to run some apps which need root (e.g. ad-away, set dns, etc.) and nothing more. Is the latest version tested on Z2 running 5.0.2?
Thanks again!
Click to expand...
Click to collapse
Kingroot works fine on 5.0.2 but by itself will not disable sony RIC and you won't get a writable system. Nut's dual recovery will disable RIC on boot, just install it after rooting and you should be good to go.
I suggested flashing a preroot zip just because i don't like kingroot app to manage root permissions and it's hard to replace it with supersu. flash a preroot zip and you'll end with a clean stock rom+supersu+nut's dual recovery and fully writable system
Thanks a lot buddy!
I will try kingroot+nut recovery and see how I find myself.
I will always be one step away from uploading a custom .zip in case I need supersu.
You really made my day!!! )))
Drop bk to kitkat, root and recovery no problem using practically any tool, I used Z2 dual recover installer, once it reboots to recovery you flash su update from chainfire, rooted and recovery done.
Then just use prf creater to make an ftf into a flashable rooted room, yes you can add root and recovery to that too, flash that from recovery, job done.
You can use lollipop ftf to do that if you wish.
gazza35 said:
Drop bk to kitkat, root and recovery no problem using practically any tool, I used Z2 dual recover installer, once it reboots to recovery you flash su update from chainfire, rooted and recovery done.
Then just use prf creater to make an ftf into a flashable rooted room, yes you can add root and recovery to that too, flash that from recovery, job done.
You can use lollipop ftf to do that if you wish.
Click to expand...
Click to collapse
Thanks for your answer!
But isn't this procedure including downgrade somewhat longer than the previous suggested one?
gazza35 said:
Drop bk to kitkat, root and recovery no problem using practically any tool, I used Z2 dual recover installer, once it reboots to recovery you flash su update from chainfire, rooted and recovery done.
Then just use prf creater to make an ftf into a flashable rooted room, yes you can add root and recovery to that too, flash that from recovery, job done.
You can use lollipop ftf to do that if you wish.
Click to expand...
Click to collapse
Go back to kk? why? it's a waste of time nowadays... the solution i mentioned won't even need to touch flashtool it's easier and quicker...
Just one last question: reading thrads about 5.1.1 it looks that it's due in a few days.
Would it be better to root now (as kingroot is still untested on 5.1.1 ) and then flash 5.1.1.ftf or just wait for it and then root?
Thanks
ptmaniac said:
Go back to kk? why? it's a waste of time nowadays... the solution i mentioned won't even need to touch flashtool it's easier and quicker...
Click to expand...
Click to collapse
Very true and if all are happy then it's all good, just don't forget to check ya phone afterwards for all the intrusive crap that kingroot throws on ya phone, tried it and it definitely didn't root my Z2 or a load of others.
derjaeger said:
Just one last question: reading thrads about 5.1.1 it looks that it's due in a few days.
Would it be better to root now (as kingroot is still untested on 5.1.1 ) and then flash 5.1.1.ftf or just wait for it and then root?
Thanks
Click to expand...
Click to collapse
IF you root now and install nut's dual recovery, you'll just need to flash a preroot 5.1.1 zip when it's released.
gazza35 said:
Very true and if all are happy then it's all good, just don't forget to check ya phone afterwards for all the intrusive crap that kingroot throws on ya phone, tried it and it definitely didn't root my Z2 or a load of others.
Click to expand...
Click to collapse
Sure, i also don't like kingroot. Like i said before it does root fine but doesn't disable ric, flashing nut's recovery after solves this.
And if you flash a preroot zip after there will be no traces of kingroot on the phone. Downgrade to kk and flashtool is still not necessary...
ptmaniac said:
IF you root now and install nut's dual recovery, you'll just need to flash a preroot 5.1.1 zip when it's released.
Good afternoon!
I have been though your procedure and, I must say, kingroot and nut's recovery installed well. Now the phone is rooted. Also added Purify app. There is just one problem left.
At the moment I have a stock 23.1.A.1.28 FW installed, just wanted to make a try with a 23.2.A.1.62 to see how the whole process goes. Instead of preparing the full .zip file, I already had a ready one, so I uploaded it into the phone, plus another .zip for gapps. Then, trying to start recovery, the phone does not enter recovery, but boots normally.
I know that nut's recovery is installed well, as, after installation process, it showed up a recovery (philz's?) with grey keys, and I also went though its menus to check it up. Right now these are the ways I tried, failing, to start recovery:
- immediately after switching on the phone (after vibration), pressing volume up
- immediately after switching on the phone (after vibration), pressing volume down
- starting manually (any of the 3 proposed recoveries) from NDR UTILS app
- starting manually from XZRecovery app
None of these methods work, the phone sometimes makes a double reboot (i.e. stays at "sony" first screen goes black and then goes back to sony screen again) but always ends up with loading android system. Is this maybe due to my locked bootloader? In this case would the only option be every time doing FTF upgrade+kingroot+nut's? Or is there some sure method to boot the recovery and install whatever I want?
After all, if it started once, I believe it can start again....
Thanks!
Click to expand...
Click to collapse
derjaeger said:
ptmaniac said:
IF you root now and install nut's dual recovery, you'll just need to flash a preroot 5.1.1 zip when it's released.
Good afternoon!
I have been though your procedure and, I must say, kingroot and nut's recovery installed well. Now the phone is rooted. Also added Purify app. There is just one problem left.
At the moment I have a stock 23.1.A.1.28 FW installed, just wanted to make a try with a 23.2.A.1.62 to see how the whole process goes. Instead of preparing the full .zip file, I already had a ready one, so I uploaded it into the phone, plus another .zip for gapps. Then, trying to start recovery, the phone does not enter recovery, but boots normally.
I know that nut's recovery is installed well, as, after installation process, it showed up a recovery (philz's?) with grey keys, and I also went though its menus to check it up. Right now these are the ways I tried, failing, to start recovery:
- immediately after switching on the phone (after vibration), pressing volume up
- immediately after switching on the phone (after vibration), pressing volume down
- starting manually (any of the 3 proposed recoveries) from NDR UTILS app
- starting manually from XZRecovery app
None of these methods work, the phone sometimes makes a double reboot (i.e. stays at "sony" first screen goes black and then goes back to sony screen again) but always ends up with loading android system. Is this maybe due to my locked bootloader? In this case would the only option be every time doing FTF upgrade+kingroot+nut's? Or is there some sure method to boot the recovery and install whatever I want?
After all, if it started once, I believe it can start again....
Thanks!
Click to expand...
Click to collapse
Nut's dual recovery works fine on LB (i have unlockable bootloader too) probably something you installed messed up the recoveries, did you install/update busybox from the play store? Nut's dual recovery includes it's own busybox which can't be replaced / updated.
Reinstalling the recoveries with the installer on your pc should fix the problem and make them work again.
Click to expand...
Click to collapse
ptmaniac said:
derjaeger said:
Nut's dual recovery works fine on LB (i have unlockable bootloader too) probably something you installed messed up the recoveries, did you install/update busybox from the play store? Nut's dual recovery includes it's own busybox which can't be replaced / updated.
Reinstalling the recoveries with the installer on your pc should fix the problem and make them work again.
Click to expand...
Click to collapse
Hi,
it looks like the device was somewhat messed up. U were right that i had installed another busybox from gplay, nevertheless uninstalling it did not sort out any effect. Also nut's reinstall failed. Maybe there was some chaos still inside due to experiments done before using kingroot, like, for instance, trying towelroot.
This is how I acted to solve the issue:
- downloaded most recent fw with xperifirm (Telekom.de one, full of useless apps)
- completely flashed phone with .ftf
- reinstalled kingroot
- reinstalled nut's recovery
Now the phone is back again rooted and I deleted some stupid apps with root app delete.
I am now eagerly waiting for 5.1.1 release, hope there will be a vanilla firmware somewhere this week ))
Best would be to already download a patched .zip image.
Right now thanks for the ideas!
Click to expand...
Click to collapse
derjaeger said:
ptmaniac said:
Hi,
it looks like the device was somewhat messed up. U were right that i had installed another busybox from gplay, nevertheless uninstalling it did not sort out any effect. Also nut's reinstall failed. Maybe there was some chaos still inside due to experiments done before using kingroot, like, for instance, trying towelroot.
This is how I acted to solve the issue:
- downloaded most recent fw with xperifirm (Telekom.de one, full of useless apps)
- completely flashed phone with .ftf
- reinstalled kingroot
- reinstalled nut's recovery
Now the phone is back again rooted and I deleted some stupid apps with root app delete.
I am now eagerly waiting for 5.1.1 release, hope there will be a vanilla firmware somewhere this week ))
Best would be to already download a patched .zip image.
Right now thanks for the ideas!
Click to expand...
Click to collapse
It's all part of the experience of learning what's best, I always only use dual recovery because windows can install it directly and root at same time, there used to be plenty of rooting apps like kingroot but you don't see so many anymore, but I'm glad you're sorted, when ya get 5.1.1 just use prfcreater to make it into flashable zip then you don't lose root and have to go through the process all over again.
All the best
---------- Post added at 01:26 AM ---------- Previous post was at 01:21 AM ----------
http://forum.xda-developers.com/crossdevice-dev/sony/tool-prfcreator-easily-create-pre-t2859904
Click to expand...
Click to collapse
Thanks a lot!
Yes, it really goes this way, now waiting for an unbranded fw, as this night the first branded ones have started to roll out...
I am really happy: for a couple of months I thought I was buried behind that nasty unlockable bootloader, and now i discovered it's even better, as rooting it without touching bootloader allows the software to work at 100% of it specs
Coming from Samsung to Sony is kinda rough at first for nibbling but when the right instruments are present and clear it's worth dealing with superior hardware.
Also, must say that Sony is lately improving its behaviour, after so many years of mafia attitudes towards buyers
Inviato dal mio X500U utilizzando Tapatalk
I've had Samsung, HTC, Apple, blackberry and finally stuck with Sony, I guess they all have pros and cons, Samsung phones are the easiest to mod and flash, Sony is quite daunting for newcomers very much like HTC. Can be tricky to learn.
Horses for courses and all that, I much prefer a rooted phone with locked boot, no particular reason except the drm keys etc, I do think camera is better on lb, than the quality on ul, although there is a drm restore mod on cross Dev, for ul, it does make xreality work, but it doesn't remove the missing key error in security tests.
I read on a page that once drm keys are gone, Sony won't honour the warranty, very much like Samsung and the knox counter, I'm not sure tho, but I do know I'll always remain Lb and stock based rom.
Only problem I have is getting wifi tethering working properly, it's doing my head in, 4 weeks of decompiling and editing and still can't get my phone to broadcast on any other channel except 1.
GGGRRRRRR @ SONY.
#whattheheckhaveyoudonesony
All so true!
Btw1, when I reflashed last evening the phone was also complaining when I went to hotspot section in order to configure it.... I think they messed up something, but maybe 5.1.1 will have fix so let's see...
I have a couple of Mediacom X500U, which I discovered, besides being fairly nice phones after more than a year of use, that are basically rebranded HTC phones (this comes out of their factory hex code detected by Linux). Do you think they could be modded like for generic HTC or never heard about them?
derjaeger said:
All so true!
Btw1, when I reflashed last evening the phone was also complaining when I went to hotspot section in order to configure it.... I think they messed up something, but maybe 5.1.1 will have fix so let's see...
I have a couple of Mediacom X500U, which I discovered, besides being fairly nice phones after more than a year of use, that are basically rebranded HTC phones (this comes out of their factory hex code detected by Linux). Do you think they could be modded like for generic HTC or never heard about them?
Click to expand...
Click to collapse
Looks like a cheap option of unb
randed HTC, but no, I don't think a HTC section would help.
I think it's an Italian release, dual simply phone, simply Google pointed to an Italian forum androidiani androidiani, run the link through a webpage translator and you may be in luck for root and rom, I think towelroot may root it.
Actually framaroot already offered rooting at the price of a horrible hack (3-4 reboots before device is ready when turning on or rebooting, plus device instability on heavy loads), never tried towelroot on it.
But problem is not about rooting rather than getting rid of horrible stock firmware. The latest fw edition by Mediacom was a total disaster (forums cry loud) and I thought it would be great to try to put some mod on the phones: this is why I had in mind to ask you if there is a general toolkit for HTC phones (like flashtool for Sony) which I could use to try to take care of it and experiment....
Inviato dal mio X500U utilizzando Tapatalk
I wanted to share two things with you guys here in Tablet z forum:
1- First of all, @zxz0O0 has developed a code based on the CVE-2015-1805 vulnerability that gives temporary root access to a select range of devices (including Tablet Z4). Let me try to explain in my words what that means. A full blown root gives permanent read/write access to /system and /data partitions. On an unrooted Tablet Z4 you only have read access to /system and no access to /data. With this root, you will be able to have a temporary terminal or adb session that gives you read access to /system and read/write access to /data. Why not write access to /system? Because Sony runs a service called RIC on Xperia devices that makes it impossible to mount /system as writable. In the past this would be patched by modifying the system partition. But in the recent Kernels sony has implemented a mechanism (dm-verity) which checks /system and if it is modified the device does not boot. So even if this (or any other) root method gave you the ability to write in /system you could not use it because your device would not restart the next time you turn it off. The solution would be to patch the kernel which requires an unlocked bootloader. IF you unlock your bootloader you lose your TA partition permanently which includes some of the Xperia features and licenses that have to do with image processing and some DRM. So a lot of us do not want to unlock the bootloader.
Then what good is this new root method? Since it gives you read access to the system partitions you can use this method to back up your TA partition. The idea is that if you ever unlock your bootloader you may be able to use this TA back up to return the system to its original state if you ever decide to relock it. Another benefit is that tools like Titanium back up which require access to the /data partition can now function (in a limited sense) although someone has to work out the details of that.
To download the pack that allows backup and restore of the TA partition go to http://forum.xda-developers.com/crossdevice-dev/sony/iovyroot-temp-root-tool-t3349597
After you create the backup, you can unlock the bootloader, and use your TA backup and the procedure outlined here: http://forum.xda-developers.com/xperia-z5/development/root-automatic-repack-stock-kernel-dm-t3301605 to create a csutom kernel that uses all the good stuff in the TA backup and emulates an environment where your tablet behaves like one with an unlocked bootloader. The camera denoising algorithm and all other Sony proprietary software which would be disabled after unlocking the bootloader should work.
If you want to return the tablet to its unlocked condition you will need this TA backup. Some explanation about retrieving the TA partition from this backup, if you unlock the bootloader and decide to relock it, is given here http://forum.xda-developers.com/showpost.php?p=66142823&postcount=16 and methods to do so are outlined at: http://forum.xda-developers.com/showpost.php?p=66158970&postcount=68
Note that to use this root you need to downgrade to lollipop (preferably version 28.0.A.8.260)
I have explained procedures to use the above tools here http://forum.xda-developers.com/z4-tablet/general/guide-safe-bootloader-unlock-restore-t3362391 at length.
2- Now, here is the use I have found for this temporary root: I was always bothered by the fact that not only I could not (easily) get the 17 hour advertised on-screen use out of my tablet, the standby power consumption was always too much. Whereas I could optimize my other (rooted) devices to only drain 1-2% a day in standby, tablet Z4 seems to settle for nothing less that 5-10% a day in standby. This is what you can do to get excellent standby power from your tablet:
A) Say goodbye to your google apps (with the exception of Chrome and Maps) and other marginally advantageous apps. They wake your device up all the time when it is supposed be sleeping and endlessly chat with google servers even if you turn all the communications off in the google settings. So disable all of the apps listed in the attached pictures , plus lifelog,via settings. Don't complain about not being able to use the gmail or youtube apps. Other great replacements exist. Leave "Google App" active if you use the voice search or voice typing feature. Also uninstall the pre-loaded apps that you aren't using like facebook (which is cancer for any phone), Lifelog, Privilege, spotify, etc.
B) In settings under wifi open the advance menu turn off both "network notification" and "scanning always available", and change "keep wifi on" to "only when plugged in"
C) Under "power management" in settings, activate stamina mode and extended standby (no need to activate extended usage).
D) Finally (and here is where the temp root becomes useful) extract the file "iovyroot" from the file in the above link and put it in your adb directory. Open a command terminal and type:
Code:
adb push root\iovyroot /data/local/tmp/iovyroot
adb shell chmod 777 /data/local/tmp/iovyroot
adb shell
This gives you an android terminal shell. Continue with the following:
Code:
/data/local/tmp/iovyroot
pm disable com.sonyericsson.idd.agent
pm disable com.sonymobile.entrance
pm disable com.sonyericsson.updatecenter
pm disable com.sonymobile.anondata
pm disable com.dsi.ant.server
pm disable com.sonymobile.gmailreaderservice
pm disable com.sonymobile.googleanalyticsproxy
pm disable com.sonymobile.mx.android
pm disable com.sonymobile.enterprise.service
pm disable com.sonymobile.synchub
pm disable com.sonymobile.phoneusage
That is it. You just disabled the update service and a bunch of other things and extended your standby battery life. These settings will survive a reboot.
Let me know how it works out for you. If you find other creative uses for this temp root share here.
This is the BEST and probably the most right to the real point post ive ever readed in this particular forum since I joined....
Forgive me if I say I have had lost the faith on sony's z4t development here... It's a real pleasure to know there's still ppl working on what I think should be the right development direction on gettin' control of our loved devices, instead of breaking them and throw a lot of expensive features to the flush.
Thanks again mate to share it.
Interesting, if I downgrade do I also lose my Marshmallow data and settings (i.e. is it the same as factory reset?)
BTW Finally this tablet becomes viable, almost a year after its release...
Stevethegreat said:
Interesting, if I downgrade do I also lose my Marshmallow data and settings (i.e. is it the same as factory reset?)
BTW Finally this tablet becomes viable, almost a year after its release...
Click to expand...
Click to collapse
If you want to have a stable system you will need to overwrite the user data which means you will lose your apps and settings and possibly (depending on how you flash) your internal storage so make a back up.
In general application data of Android firmware are not downward compatible with older versions.
Hmm, but if you can also temp root then you can backup everything using TitaniumBackup anyway before unlocking.
So if I understand this right, if you can back up TA we can infact unlock the bootloader now with no loss of DRM ?
So can now actually get full root based on that ?
najoor said:
If you want to have a stable system you will need to overwrite the user data which means you will lose your apps and settings and possibly (depending on how you flash) your internal storage so make a back up.
In general application data of Android firmware are not downward compatible with older versions.
Click to expand...
Click to collapse
I will only downgrade to get a TA Backup, so stability is not an issue to me (after the TA Backup, I'll go back to MM and probably unlock it).
My only issue would be if downgrading would actually harm my data and/or my capacity to get the TA backup properly (if I'm not wipe first I mean).
Stevethegreat said:
I will only downgrade to get a TA Backup, so stability is not an issue to me (after the TA Backup, I'll go back to MM and probably unlock it).
My only issue would be if downgrading would actually harm my data and/or my capacity to get the TA backup properly (if I'm not wipe first I mean).
Click to expand...
Click to collapse
I don't think it will affect the TA back up process by it may harm you application data (not your sdcard data). The reason is that on every reboot android cleans up the) /data partition as much as it can (for example if it sees that an app has been uninstall but it has left some data behind). I'm doing so lollipop may corrupt some of your marshmallow data,
Why don't you take a backup of your data before a downgrade and the restore them later? The tablet itself has a utility to do it and I hear Helium is a tool that backs up your app data without the need for root.
najoor said:
I don't think it will affect the TA back up process by it may harm you application data (not your sdcard data). The reason is that on every reboot android cleans up the) /data partition as much as it can (for example if it sees that an app has been uninstall but it has left some data behind). I'm doing so lollipop may corrupt some of your marshmallow data,
Why don't you take a backup of your data before a downgrade and the restore them later? The tablet itself has a utility to do it and I hear Helium is a tool that backs up your app data without the need for root.
Click to expand...
Click to collapse
Mostly to save time as I have too much data. I though to do it like this
Downgrade to Lollipop -> Use the Exploit -> TA Backup -> Upgrade back to Marshmallow.
In principle everything should have had worked as by the end of it I would be back to Marshmallow (I would not linger into Lollipop). But now that you're telling me that lollipop may corrupt my data permanently I have second thoughts.
I thought, that my data would not work well on Lollipop, but that wouldn't matter to me; but now you're telling me that they won't work when I'll back in Marshmallow too, which is a totally different beast. Am I understanding you correctly?
Does everyone need to downgrade tho?
Once we have the TA partition available to restore, once its made available online surely everyone else can just restore the same one?
Or is the key unique?
Kinda assuming here that all the stuff that needs the TA partition will work with an unlocked bootloader, or does it have to be locked to be usable again?
Edit: Can we restore TA partition after unlocking bootloader?
Yes but this will also relock the bootloader.
Bugger
Ultimately never rooted my device for fear of losing something (that I will never use anyway!)
DRM Keys are unique, in fact that's the whole point of TA backups.
Also there's a talk (on the other thread) of a tool that would merge your particular keys with a particular custom kernel.
That way you'd keep all Sony Exclusive features, but also be able to make use of root apps. It would be great if such a tool becomes usable with AndroPlus Kernel...
Nice, had all but given up hope of being able to unlock my Z4 so that sounds promising!
I am looking for a high-end tablet and it seemed the Z4 Tablet was the best one for me over the Pixel C and even the iPad Air 2..though I did consider the budget Nvidia Shield K1 also.
The next thing I did was see if the bootloader could be unlocked and custom ROMs installed as I really hate the Sony UI that I have experienced with my sisters M2, and I never stick to the stock ROM in any of my phones. I just love knowing and doing customising!!
..Unfortunately, it seems like I will be stuck with it so I may have to look for another brand now
D0MINO said:
I am looking for a high-end tablet and it seemed the Z4 Tablet was the best one for me over the Pixel C and even the iPad Air 2..though I did consider the budget Nvidia Shield K1 also.
The next thing I did was see if the bootloader could be unlocked and custom ROMs installed as I really hate the Sony UI that I have experienced with my sisters M2, and I never stick to the stock ROM in any of my phones. I just love knowing and doing customising!!
..Unfortunately, it seems like I will be stuck with it so I may have to look for another brand now
Click to expand...
Click to collapse
I don't know how you got that impression, since the whole point of the OP and the links I posted with it is that you will not be stuck with the stock firmware.
So to summarize the points mentioned in the OP:
As of today, the following is possible with a tablet Z4:
1- The TA partition can be backed up.
2- The booloader can be unlocked.
3- The unlocking is reversible with the help of the backed up TA pertition
4- When the bootloader is unlocked a custom kernel can be flashed (currently one is posted in the Z4 forum courtesy of @AndroPlus).
5- When the bootloader is unlocked the stick Kernel can be patched to retrieve the Xperia proprietary facilities that are lost to the unlocking process (courtesy of @tobias.waldvogel).
6- When the bootloader is unlocked /system can be fully modified. That means flashing completely custom ROMs.
So you can either make your own modification to the system, or wait for someone to make a ROM. In light of the above possibilities it is only a matter of time before customs ROMs start to pop up.
By the way, to the extent that the stock firmware is customizable without unlocking the bootloader, it is actually a good ROM and you can change a lot of things from the general appearance to the default launcher.
PS: Tablet Z4 is my second Sony tablet and the third Sony mobile device and I have about 10 of this kind of devices at any given time. The other android devices are miles behind in terms of elegance and manufacturing quality. There is just something about a Sony device that is unique and unmatched.
Can anyone confirm how to re-lock the bootloader once unlocked?
I would say:
1. Flash a stock firmware (the lollipop version that you used to backup the TA partition).
2. Use the iovyroot temp root batch tarestore to restore your TA partition.
3. Reboot and that's it: you are back to unlocked bootloader unrooted original drm included stock firmware.
Anyone already tried?
Thank you.
I unlocked the bootloader and rooted the device SGP771.
Bevor that, i backed up the TA.
Then i flashed the androplus kernel.
Everything works great.
But you cannot modify androplus kernel with that tool. That means DRM restore is only possible on stock rom.
When you restore TA to stock rom, your bootloader will be in a lockes status again and there is no more root. Too bad
odicamillo said:
Can anyone confirm how to re-lock the bootloader once unlocked?
I would say:
1. Flash a stock firmware (the lollipop version that you used to backup the TA partition).
2. Use the iovyroot temp root batch tarestore to restore your TA partition.
3. Reboot and that's it: you are back to unlocked bootloader unrooted original drm included stock firmware.
Anyone already tried?
Thank you.
Click to expand...
Click to collapse
Can ta be restored on any fw like marshmallow or can it only be restored on the fw that you backed it up from?
This looks very promising, thanks OP.
Has anyone else managed to get it to work as described?
Thanks in advance
najoor said:
I don't know how you got that impression, since the whole point of the OP and the links I posted with it is that you will not be stuck with the stock firmware.
So to summarize the points mentioned in the OP:
As of today, the following is possible with a tablet Z4:
1- The TA partition can be backed up.
2- The booloader can be unlocked.
3- The unlocking is reversible with the help of the backed up TA pertition
4- When the bootloader is unlocked a custom kernel can be flashed (currently one is posted in the Z4 forum courtesy of @AndroPlus).
5- When the bootloader is unlocked the stick Kernel can be patched to retrieve the Xperia proprietary facilities that are lost to the unlocking process (courtesy of @tobias.waldvogel).
6- When the bootloader is unlocked /system can be fully modified. That means flashing completely custom ROMs.
So you can either make your own modification to the system, or wait for someone to make a ROM. In light of the above possibilities it is only a matter of time before customs ROMs start to pop up.
By the way, to the extent that the stock firmware is customizable without unlocking the bootloader, it is actually a good ROM and you can change a lot of things from the general appearance to the default launcher.
PS: Tablet Z4 is my second Sony tablet and the third Sony mobile device and I have about 10 of this kind of devices at any given time. The other android devices are miles behind in terms of elegance and manufacturing quality. There is just something about a Sony device that is unique and unmatched.
Click to expand...
Click to collapse
Dear najoor,
are you telling us that, now, we can unlock a z4 tablet which has the "rooting status: Bootloader unlock allowed: NO" , in the service info/configuration area ?!?
if it is the case, i would be delighted to know how to proceed step by step, as i would love to install a lineage rooted custom rom on it (it is the SGP771 one,with phone capability)!!!
thank you
kind regards from France
retikulatus said:
Dear najoor,
are you telling us that, now, we can unlock a z4 tablet which has the "rooting status: Bootloader unlock allowed: NO" , in the service info/configuration area ?!?
if it is the case, i would be delighted to know how to proceed step by step, as i would love to install a lineage rooted custom rom on it (it is the SGP771 one,with phone capability)!!!
thank you
kind regards from France
Click to expand...
Click to collapse
Unfortunately if that is the case you cannot unlock the bootloader.
I am just curious, why does yours look like that? Do you have myXperia or some other find-my-phone service activated on your phone?
najoor said:
Unfortunately if that is the case you cannot unlock the bootloader.
I am just curious, why does yours look like that? Do you have myXperia or some other find-my-phone service activated on your phone?
Click to expand...
Click to collapse
Thanks for the fast reply even if you ruined my hopes
no, i don't think i have myXperia , i checked on my apps and find nothing.
Since i had display issues with my tab s (sm-t800), i tried the z4 tablet for its LCD screen instead of the super amoled of samsung...
My bootloader was already locked when i purchased it, i updated it thinking it will change that but unfortunatly that did nothing.
It wasn't a new one though, perhaps the previews owner messed up with it and got its bootloader locked :/
Because it is some kind of lotery to have a bootloader unlockable with sony, i will wait patiently until samsumg release its 16:9/10 tab s4: imho, the tab s3 actual 4:3 format is a nonsense....
Thank you again
Kind regards from France
*I know this must have been answered before, I am sorry for playing the newbie, but I couldn't find this anywhere.
I need to know exactly what is at stake for rooting my device, what would I lose access to, and what not.
I've read somewhere that you lose DRM or something like that, is that meaning I will not be able to watch Netflix download and go, or Google Play Music, etc? what does it means?
LionLorena said:
*I know this must have been answered before, I am sorry for playing the newbie, but I couldn't find this anywhere.
I need to know exactly what is at stake for rooting my device, what would I lose access to, and what not.
I've read somewhere that you lose DRM or something like that, is that meaning I will not be able to watch Netflix download and go, or Google Play Music, etc? what does it means?
Click to expand...
Click to collapse
You will lose your warranty because you have to unlock your bootloader but if anything goes wrong you can always relock your bootloader and take your phone to a service center and claim your warranty they don't even check it in most cases other than that everything works fine
Sent from my Moto G4 Plus using Tapatalk
prajwal2001 said:
You will lose your warranty because you have to unlock your bootloader but if anything goes wrong you can always relock your bootloader and take your phone to a service center and claim your warranty they don't even check it in most cases other than that everything works fine
Sent from my Moto G4 Plus using Tapatalk
Click to expand...
Click to collapse
And apart from that, do I lose anything else?
Some guy said I would lose access to that extra anti theft security from Google that works kinda like iCloud, is it true?
LionLorena said:
And apart from that, do I lose anything else?
Some guy said I would lose access to that extra anti theft security from Google that works kinda like iCloud, is it true?
Click to expand...
Click to collapse
Nothing else only warranty
Sent from my Moto G4 Plus using Tapatalk
LionLorena said:
And apart from that, do I lose anything else?
Some guy said I would lose access to that extra anti theft security from Google that works kinda like iCloud, is it true?
Click to expand...
Click to collapse
Provided you're still on the stock ROM, I don't think rooting affects your anti-theft protection (I recall it's called Factory Reset Protection?). Even if you've enabled OEM unlocking in Developer Options, someone resetting your phone would still need your Google credentials to use the device. Also, if you're logged into your device at the time, you could still locate and wipe your phone via Android Device Manager.
Of course, with an unlocked bootloader and custom recovery (as is generally required to root), someone could still flash a custom ROM and bypass those protections and, also, could in theory still access your data. (but only if they have physical access to your device)
As for DRM, I'm not sure but some apps have been/are now detecting the presence of root and will refuse to work (Snapchat, Pokemon Go, some banking apps come to mind) or for other devices, Android Pay and other security dependent features may not work. I recall magisk, a root manager, does have the ability to mask root from those apps, as well as pass SafetyNet, which is Google's security/anti-tamper detection. Your experience may vary. However, some apps require root access to function properly (e.g. kernel managers, battery monitors) just as to how they function, it's entirely up to you if you see yourself using those rooted apps on a regular enough basis. The root managers available (e.g. SuperSU, magisk) are supported and work well, just ensure you're using the latest versions, and if you're on stock Nougat, to flash a custom kernel prior to rooting (since the stock kernel won't permit modifications, if I recall).
Overall, in my view, you're trading security and warranty (as mentioned by prajwal2001) for convenience/flexibility by rooting - the flexibility alone to flash what you wish is what interested me in rooting my device, if anyone else has any other comments, feel free to add.
echo92 said:
Provided you're still on the stock ROM, rooting shouldn't disable your anti-theft protection (which I recall is Factory Reset Protection). Even if you've enabled OEM unlocking in Developer Options, someone resetting your phone would still need your Google credentials to use the device. Of course, with an unlocked bootloader and custom recovery (as is generally required to root), someone could still flash a custom ROM and bypass those protections and, also, could in theory still access your data. (but only if they have physical access to your device)
As for DRM, I'm not sure but some apps have been/are now detecting the presence of root and will refuse to work (Snapchat, Pokemon Go, some banking apps come to mind) or for other devices, Android Pay and other security dependent features may not work. I recall magisk, a root manager, does have the ability to mask root from those apps, as well as pass SafetyNet, which is Google's security/anti-tamper detection. Your experience may vary. However, some apps require root access to function properly (e.g. kernel managers, battery monitors) just as to how they function, it's entirely up to you if you see yourself using those rooted apps on a regular enough basis. The root managers available (e.g. SuperSU, magisk) are supported and work well, just ensure you're using the latest versions, and if you're on stock Nougat, to flash a custom kernel prior to rooting (since the stock kernel won't permit modifications, if I recall).
Overall, in my view, you're trading security and warranty (as mentioned by prajwal2001) for convenience/flexibility by rooting - the flexibility alone to flash what you wish is what interested me in rooting my device, if anyone else has any other comments, feel free to add.
Click to expand...
Click to collapse
Hm I see.
That's a pretty big downside
I guess I will pass root for now, I was only wanting to do to use the ADB via USB OTG and boot disk creator.
Thanks everyone for all the information!
LionLorena said:
Hm I see.
That's a pretty big downside
I guess I will pass root for now, I was only wanting to do to use the ADB via USB OTG and boot disk creator.
Thanks everyone for all the information!
Click to expand...
Click to collapse
That's fair enough - there's nothing stopping you from rooting your device, then performing what you need, before unrooting your device. (Just curious, does what you want to do require root, or are there other non-root methods?)
However, this will still involve you voiding your warranty (via unlocking your bootloader), and may also involve re-flashing your stock firmware to remove the custom recovery (and relock your bootloader, if you wish, though this won't recover your warranty, sadly). Honestly though, it's your device, up to you what you wish to do
echo92 said:
That's fair enough - there's nothing stopping you from rooting your device, then performing what you need, before unrooting your device. (Just curious, does what you want to do require root, or are there other non-root methods?)
However, this will still involve you voiding your warranty (via unlocking your bootloader), and may also involve re-flashing your stock firmware to remove the custom recovery (and relock your bootloader, if you wish, though this won't recover your warranty, sadly). Honestly though, it's your device, up to you what you wish to do
Click to expand...
Click to collapse
Yeah the warranty is not on top of my mind right now, my concern are the other issues it may cause, such apps not working, and security issues.
Like, I had a Sony Xperia Play back some years and past a week I root it, and past 2 weeks it was on Cyanogenmod.
I had Bricked that device countless times and had somehow fixed, I had also replaced several internal components as well, but back then there were no DRM stuff and all, so the rooting part is not what I fear, is just this new wave of side effects regarding it.
LionLorena said:
Yeah the warranty is not on top of my mind right now, my concern are the other issues it may cause, such apps not working, and security issues.
Like, I had a Sony Xperia Play back some years and past a week I root it, and past 2 weeks it was on Cyanogenmod.
I had Bricked that device countless times and had somehow fixed, I had also replaced several internal components as well, but back then there were no DRM stuff and all, so the rooting part is not what I fear, is just this new wave of side effects regarding it.
Click to expand...
Click to collapse
There is no DRM to lose on Motorola devices. On Sony devices, what you said is applicable. As for apps that refuse to work with root access, you can simply switch to Magisk, and enabled hiding root access from all apps.
zeomal said:
There is no DRM to lose on Motorola devices. On Sony devices, what you said is applicable. As for apps that refuse to work with root access, you can simply switch to Magisk, and enabled hiding root access from all apps.
Click to expand...
Click to collapse
That's motivating.
And I've found a topic that says I don't even need to flash the custom recovery, I can simply hot boot it and do my stuff and keep the stock recovery.
LionLorena said:
That's motivating.
And I've found a topic that says I don't even need to flash the custom recovery, I can simply hot boot it and do my stuff and keep the stock recovery.
Click to expand...
Click to collapse
There's no real point of not changing the stock recovery, unless you are planning to stick with a rooted stock ROM. If you keep the stock recovery, you'll be able to enable OTA stock updates.
From a security standpoint, if your device is lost, it becomes much easier for an attacker to breach your system and much harder for you to protect it. However, according to most security principles, once your device is lost from you, it's no longer your device, anyway.
zeomal said:
There's no real point of not changing the stock recovery, unless you are planning to stick with a rooted stock ROM. If you keep the stock recovery, you'll be able to enable OTA stock updates.
From a security standpoint, if your device is lost, it becomes much easier for an attacker to breach your system and much harder for you to protect it. However, according to most security principles, once your device is lost from you, it's no longer your device, anyway.
Click to expand...
Click to collapse
The OTA updates are one of the reasons, yes.
And yes, from that point of view you are right.
I'm currently using some tracking solutions such as Cerberus, and disabling some features while the phone screen is locked, such as quick settings, and power off menu.
Also the extra layer of security imposed by Google version of iCloud, passes me some sense of safety.
The main thing that bothers me related to custom recovery is that the attacker can replace my software entirely.
While with stock I can have some time to recover the device using the tactics. Enabled.
And root could potentially aid me in that, I could add Cerberus to /system and etc.
You lose security. Every person with knowledge can access to your phone through TWRP, use the File Manager to erase files.key (this erases your gesture or PIN of lock screen) and can see all your info. If you unlock bootloader, every person can flash TWRP and do this steps.
alaindupus said:
You lose security. Every person with knowledge can access to your phone through TWRP, use the File Manager to erase files.key (this erases your gesture or PIN of lock screen) and can see all your info. If you unlock bootloader, every person can flash TWRP and do this steps.
Click to expand...
Click to collapse
thats why i'm thinking 3 times before doing it.
Hey guys.
Really sorry for having to post this again :/
Tried posting my issue in this thread but I think that thread's gone cold.
----
I have a Moto G5 Plus US, Model XT1687
Current ROM Info:
Software channel: retus
Build #: NPN 25.137-33
Security patch: Jan, 1 2017
Baseband: M8953_02.03.07.06R POTTER_NA_CUST
On a whim, unlocked the bootloader. Now id like to lock it back.
I haven't updated my phone / installed any OTA's, phone keeps asking to update to NPNS25.137-33-5, haven't done it.
Does this procedure work for me?
Which ROM should I use?
Id like to relock the bootloader and receive OTA updates as normal on my US variant phone!
Many thanks!
I'm pretty sure Motorola hasn't released stock firmware for the retus version.
Cats_PJs said:
I'm pretty sure Motorola hasn't released stock firmware for the retus version.
Click to expand...
Click to collapse
So, there's no way for me to relock my bootloader unless motorola releases it?
Can't I use another firmware that's available here at XDA?
What would you do?
Not update OTA and wait for motorola to release the firmware, or should just leave it unlocked?
Thanks
seed_87 said:
So, there's no way for me to relock my bootloader unless motorola releases it?
Can't I use another firmware that's available here at XDA?
What would you do?
Not update OTA and wait for motorola to release the firmware, or should just leave it unlocked?
Thanks
Click to expand...
Click to collapse
I don't think there's a way to relock the retus version, but maybe I'm wrong.
As far as what I would do. I always run a custom ROM, so I'd flash twrp, make a backup and try a few roms..
seed_87 said:
So, there's no way for me to relock my bootloader unless motorola releases it?
Can't I use another firmware that's available here at XDA?
What would you do?
Not update OTA and wait for motorola to release the firmware, or should just leave it unlocked?
Thanks
Click to expand...
Click to collapse
To relock the phone, you must flash a complete factory image that is the same or newer than what you have installed... Only way, not that it gains much except the ability to pass SafetyNet checks on pure stock, which you can do with some root magic anyway, but the bootloader will change to a state of 2 (Relocked), your warranty will still be void, and you will still get the bootloader unlocked warning screen (unless you flash a custom logo).
Cats_PJs said:
I don't think there's a way to relock the retus version, but maybe I'm wrong.
As far as what I would do. I always run a custom ROM, so I'd flash twrp, make a backup and try a few roms..
Click to expand...
Click to collapse
Well, I originally wanted to just root the stock ROM and install a couple of things like: Adaway, some Xposed modules (Like the Youtube ad remover one), WiFi ADB (which requires root, allows one to wirelessly debug apks)
acejavelin said:
To relock the phone, you must flash a complete factory image that is the same or newer than what you have installed... Only way, not that it gains much except the ability to pass SafetyNet checks on pure stock, which you can do with some root magic anyway, but the bootloader will change to a state of 2 (Relocked), your warranty will still be void, and you will still get the bootloader unlocked warning screen (unless you flash a custom logo).
Click to expand...
Click to collapse
Wow relocking the BL sounds really useless once you realize what you're getting from it. I really don't care much for SafetyNet as (this model has no NFC). I don't use Android Pay either.
Honestly, I unlocked the BL but finally didn't root mainly because I read some issues when rooting. Please see this post
Thanks for the enlightenment!
seed_87 said:
Well, I originally wanted to just root the stock ROM and install a couple of things like: Adaway, some Xposed modules (Like the Youtube ad remover one), WiFi ADB (which requires root, allows one to wirelessly debug apks)
Wow relocking the BL sounds really useless once you realize what you're getting from it. I really don't care much for SafetyNet as (this model has no NFC). I don't use Android Pay either.
Honestly, I unlocked the BL but finally didn't root mainly because I read some issues when rooting. Please see this post
Thanks for the enlightenment!
Click to expand...
Click to collapse
If you do decide to root, I would suggest using magisk instead of SuperSU. I switched a few months ago, and it works perfectly
Safetynet isn't just for nfc, other companies and apps have used it in their software as well ie: Snapchat, and Pokemon go are 2 I can think off the bat.
Installing and/or rooting with magisk is fairly easy and painless, and it will have superSU which will give you root.
How to:
Must have twrp recovery, or some other custom recovery, although these days I would recommend twrp, as it works and is more widely used than say cm recovery is, since cm project was taken over by lineage now. Anyways, flash a custom recovery and use it. (note: I haven't used cm recovery or any other recovery in years, so I do not know it this works with antyhing else, aside from twrp, which I know it works fine with). There are also tutorials all over xda on how to install/flash twrp, as well as youtube videos if you prefer that better.
Go grab magisk.zip, (do a google search or look on xda, it's all over the place just do a search for like magisk zip, you'll find it).
The latest as of right now I think is 14.0 and you will also (if I recall correctly) need magisk manager, (and just like the zip file you can do a quick search it's also all over the place).
Once you have that, reboot into recovery, then flash the magisk.zip file, and reboot, it should give you magisk manager app in your app drawer and you should be rooted. (Note: You may need to update magisk manager.)
To check root grab an app called root checker on the plays store. (it's free)
It's that easy.
Short summary:
1: Install custom recovery (if you haven't already)
2: Boot to recovery, flash magisk.zip
3: reboot to system, and profit from root + safetynet hide.
Quick and painless root method.
I do all my rooting now this way, in fact I recently re-flashed my nexus 5x rom and instead of flashing superSU I flashed the magisk way instead, and it cover 2 things,
1: gives you root
2: it hides root from safetynet and lets you use nfc, pokemon go, snapchat, and other apps that use safetynet as well.
Cats_PJs said:
If you do decide to root, I would suggest using magisk instead of SuperSU. I switched a few months ago, and it works perfectly
Click to expand...
Click to collapse
Oh, wow, I had the (wrong) idea that the SuperSU method was the better one and superseeded magisk. If that works great then awesome I will root using magisk, thanks @Cats_PJs !
easyrider77 said:
Safetynet isn't just for nfc, other companies and apps have used it in their software as well ie: Snapchat, and Pokemon go are 2 I can think off the bat.
Installing and/or rooting with magisk is fairly easy and painless, and it will have superSU which will give you root.
How to:
Must have twrp recovery, or some other custom recovery, although these days I would recommend twrp, as it works and is more widely used than say cm recovery is, since cm project was taken over by lineage now. Anyways, flash a custom recovery and use it. (note: I haven't used cm recovery or any other recovery in years, so I do not know it this works with antyhing else, aside from twrp, which I know it works fine with). There are also tutorials all over xda on how to install/flash twrp, as well as youtube videos if you prefer that better.
Go grab magisk.zip, (do a google search or look on xda, it's all over the place just do a search for like magisk zip, you'll find it).
The latest as of right now I think is 14.0 and you will also (if I recall correctly) need magisk manager, (and just like the zip file you can do a quick search it's also all over the place).
Once you have that, reboot into recovery, then flash the magisk.zip file, and reboot, it should give you magisk manager app in your app drawer and you should be rooted. (Note: You may need to update magisk manager.)
To check root grab an app called root checker on the plays store. (it's free)
It's that easy.
Short summary:
1: Install custom recovery (if you haven't already)
2: Boot to recovery, flash magisk.zip
3: reboot to system, and profit from root + safetynet hide.
Quick and painless root method.
I do all my rooting now this way, in fact I recently re-flashed my nexus 5x rom and instead of flashing superSU I flashed the magisk way instead, and it cover 2 things,
1: gives you root
2: it hides root from safetynet and lets you use nfc, pokemon go, snapchat, and other apps that use safetynet as well.
Click to expand...
Click to collapse
Awesome explanation @easyrider77 I will definitely try to root using magisk. Thanks for the warning, don't play Pokemon go and haven't used Snapchat in years so i'm good! I'll try flashing the latest Magisk (v14.0)
One thing tho:
I think I want to (for now anyways) stay stock-ish (stock rom + stock kernel + twrp + magisk).
If I understand it correctly, flashing a custom recovery renders the phone unable to get OTA's (Not that I'd want to apply an OTA update on a modified rooted phone and risk a brick anyways) So, how would one eventually update Android? (Keeping in mind that Motorola hasn't released any retus firmware) Can I flash other non-retus firmwares? (Which wouldn't flash over twrp I think, I would then just loose root and have to flash magisk again, right?)
Thanks a ton guys :good::good::good:
EDIT:
Short xda search pointed me to this official TWRP link, will follow fastboot method to install TWRP.
I'm not sure what exactly stops ota from coming in. I've heard unlocking the bootloader is what causes it, and I've also heard that flashing a custom recovery is what causes it, and I've also heard a custom rom is what does it.
There are options as far as ota goes though, and work the same way, but you'd jsut have to wait. People release flashable ota files all the time, and can be flashed via twrp.
If you want to keep stock, and root that's fine too, but I personally wouldn't worry much about the ota issue at all, because eventually every phone will not get ota as it will lose support, but you can still get the latest and greatest up to date rom with it's features.
Prime examples would be:
Oneplus One,
Oneplus 3
some of the samsung devices like s4
These are just a few, and although they don't receive support officially, they are sporting the brand new android 8 oreo.
Even the samsung s4 has N for it and it came out in 2013 (that's near 5 yrs ago now) and started on Android 4.2.2 (Jelly Bean) and said it was upgradable to 5.0.1 (Lollipop), and now here we are running android 7.1.x.
https://forum.xda-developers.com/galaxy-s4-tmobile/development
(not sure if there were any unlocked variants of that phone at the time as it wasn't a common thing like it is now, that's why I chose the tmobile thread but there are other variants that get it as well)
So when it comes to ota, I personally would not an do not worry about that when I root, that's the last of my worries.
I prefer functionality and customization over ota myself, because most times someone comes out with either an official link to an ota or makes an flashable ota you can flash via twrp, although my semi-educated guess would be if you decide to install the official/stock ota, then it will erase everything you have anyways which can be a pain.
DO keep in mind once you unlock the bootloader, it "officially" voids any warranty and moto does have the option to refuse service if anything goes wrong with the phone, but I have heard some people had no issues and moto took the phone back even when rooted, but that is something you would have to make a choice and live with IF you decided to unlock the bootloader, as there is no way to undo that process.
I have re-locked the bootloader on a moto phone so yes it CAN be re-locked, but........it still gets triggered and moto will know that it's been unlocked even if you re-lock it, because that part is irreversible and cannot be undone, aside from you locking and unlocking it on your side.
As for flashing firmware and all that, make DOUBLY sure you know your phones model number and/or codename, this is key in flashing most anything you do with your phone, because even though a phone may have multiple variants, ie: tmobile, sprint, at&t versions, and even European versions, and the phones are identical in EVERY way hardware wise, you can't just simply pick a rom of choice and use it, it's a matter of knowing what your phones info is.
Example: you cannot take a t-mobile phone rom and flash it's official firmware or it's roms, and updates on a at&t variant, or a metroPCS on a tmobile variant, even though they use the same network, and are the exact same phone and hardware, there are subtle differences and can most likely brick the phone, either hard or soft.
So if I had the US variant of the g5 plus that would be codenamed the same "potter" like the rest, but, the number is different which is XT1687, so I would use that number as my reference, as apposed to the potter name, because there are 3 other variants of that phone which are Amazon Edition and the consumer cellular and of corse the European variants as well, I'm not exactly sure what numbers go with what phones other than the US unlocked variant, but on a quick look the other numbers are XT1684 and XT1685, perhaps someone else with more experience than I have can tell you what those number match up with said phone.
As far as the US variant goes though, I do not want to take a rom or firmware meant for the XT1684 XT1685 and use it on the XT1687 US variant, as it will most likely have bad results, ie: brick of some sort.
That's the main thing you have to worry about, other than that, there isn't much worry. Just do some major research and goggling and read and re-read and read again the directions on the threads at xda as most generally all of them are pretty simple to follow, if you do it step by step.
I recently bought an lg k20 plus phone from metroPCS, have never rooted that phone before and came to xda and followed the rooting thread and rooted it the first time. In a matter of 30 mins I had full root with stock rom (since there are no roms for that phone as of yet) but it is a metroPCS variant, (mp260) and in the case above, this phone is also sold by tmobile, is the exact same phones specs hardware, etc....I could not use the tmobile rom or firmware on this phone.
Hope this helps clear it up some.
Update:
I just bought a 64gb storage/4gb ram US variant of the g5 plus. It brought back some older memories of when I had my other moto, X I think it was, not sure anymore, but I DO remember you can unlock the bootloader as well as re-lock it, but, do keep in mind it still triggers something internally that can't be reveresed, so if moto did decide to check into things, they can tell if it's been bootloader unlocked.
So while you can unlock and lock the bootloader on our side, moto can still tell it's been unlocked, even when re-locked. Just hope if you send it back in they just don't check it and even if they do, hope they don't bother sending it back saying your warranty is void sorry.
Thanks @easyrider77
I used to install custom ROMs on my older phones. Recently though, stock android has gotten pretty good so maybe when this phone loses support I'll try some ROMs. Out of curiosity, what ROM/hacks/kernel do you use?
So, how does this sound:
- Install the OTA my phone's been prompting me to update to (upgrading from NPN25.137-33 to NPNS25.137-33-5 and I think it will then try to update to NPN25.137-83 with an August 1 security patch)
- Install TWRP via fastboot, make a nandroid backup!
- Root with Magisk v14.0
- Looking into maybe changing the boot.img "Your device is not trustworthy" thing
- Adaway! Xposed! Other goodies yay!
- Any other recommendations?
PS: Can Magisk root every firmware released by Motorola for the Moto G5+?
I've used it on my nexus 5x, and a lg k20 plus phone to root. I'm not sure if it has any limits when it comes to phones, but to my knowledge it should work fine.
Be careful with the boot.img file, if its not the correct size it will brick the phone too.
easyrider77 said:
I've used it on my nexus 5x, and a lg k20 plus phone to root. I'm not sure if it has any limits when it comes to phones, but to my knowledge it should work fine.
Be careful with the boot.img file, if its not the correct size it will brick the phone too.
Click to expand...
Click to collapse
WIll do, many thanks for all your help guys!
@easyrider77 @Cats_PJs @acejavelin
:good::good::good:
Every rom I've tried on this phone works well, with only minor bugs. Right now I'm using the Pixel ROM. Elemental x is my kernel of choice because it's stable and has a sound option to increase volume. I use Kernel Adiutor for settings. The viper magisk module by ahrion works great, and ad away is a must. Good luck
Cats_PJs said:
Every rom I've tried on this phone works well, with only minor bugs. Right now I'm using the Pixel ROM. Elemental x is my kernel of choice because it's stable and has a sound option to increase volume. I use Kernel Adiutor for settings. The viper magisk module by ahrion works great, and ad away is a must. Good luck
Click to expand...
Click to collapse
Nice to hear cat.
I'm holding off on rooting just yet, although the temptation is really really great and pulling at me right now ina bad way . I just want to make doubly sure the phone isn't going to have issues, and hardware glitches. Anytime you mass produce a product, inevitably there will always be a bad batch(s) so I am just watching and waiting patiently on stock non-root (yes I said non-root LOL) but it's not as bad of an experience as I thought it would be.
I have to give this phone props, this phone is simply great. I bought the 64gb storage/4gb ram US variant, and have been nothing but happy with it, even on stock.
Camera isn't exactly your top tier phone camera but it certainly stands out as one of the not bad at all cameras. I see many saying the camera sucks, well if your zooming in and expect to get a good picture, good luck with that, simply put as I read in an article, two things 1: just don't use zoom, it's a digital zoom as apposed to an optical zoom, and simply will give you fuzzy and blurry pics a alot 2: if your after a good picture taking experience, for crimeny sake, buy a dang camera, these are phones people, NOT cameras. If they were meant for that, photographers around the world would be using phones, but guess what, news flash, they are using things called "cameras" wow what a concept LOL.
Anyways, if you just use very little zoom (I'd say 1.5 - 2.0x at most) but mostly just get closer to the subject or item you are takeing pics of, you'll have a much more pleasant experience with picture taking, trust me.
Ok of my soap box and tangent, sorry .
I will eventually root this bad boy, as I cannot resist the urge. For now I am just making sure the phone has no hiccups or glitches hardware wise, so glad to know roms are working well.
I did have a question about the sound though. I see people saying low sound volume with this phone, and I personally do not see (or hear in this case) the problems. I watched a few youtube videos last night and honestly I had to turn it down some because it was plenty loud, at least from this side.
Does the sound get lower with roms? (in wich case I can use viper) but I'm just curious.
easyrider77 said:
Nice to hear cat.
I'm holding off on rooting just yet, although the temptation is really really great and pulling at me right now ina bad way . I just want to make doubly sure the phone isn't going to have issues, and hardware glitches. Anytime you mass produce a product, inevitably there will always be a bad batch(s) so I am just watching and waiting patiently on stock non-root (yes I said non-root LOL) but it's not as bad of an experience as I thought it would be.
I have to give this phone props, this phone is simply great. I bought the 64gb storage/4gb ram US variant, and have been nothing but happy with it, even on stock.
Camera isn't exactly your top tier phone camera but it certainly stands out as one of the not bad at all cameras. I see many saying the camera sucks, well if your zooming in and expect to get a good picture, good luck with that, simply put as I read in an article, two things 1: just don't use zoom, it's a digital zoom as apposed to an optical zoom, and simply will give you fuzzy and blurry pics a alot 2: if your after a good picture taking experience, for crimeny sake, buy a dang camera, these are phones people, NOT cameras. If they were meant for that, photographers around the world would be using phones, but guess what, news flash, they are using things called "cameras" wow what a concept LOL.
Anyways, if you just use very little zoom (I'd say 1.5 - 2.0x at most) but mostly just get closer to the subject or item you are takeing pics of, you'll have a much more pleasant experience with picture taking, trust me.
Ok of my soap box and tangent, sorry .
I will eventually root this bad boy, as I cannot resist the urge. For now I am just making sure the phone has no hiccups or glitches hardware wise, so glad to know roms are working well.
I did have a question about the sound though. I see people saying low sound volume with this phone, and I personally do not see (or hear in this case) the problems. I watched a few youtube videos last night and honestly I had to turn it down some because it was plenty loud, at least from this side.
Does the sound get lower with roms? (in wich case I can use viper) but I'm just curious.
Click to expand...
Click to collapse
I really don't have a problem with the sound volume, except when I plug it into my truck. If there's a good song on, and I really want to crank it up, I run out of volume, so I usually turn up the headphone gain in the kernel settings by 3.
I haven't noticed variance between ROM volumes on this phone, but I know on my old note 3 there was definitely fairly large variance between ROMs.