Related
Hello everyone,
I'm back to a nexus 6 after a very short stint with a 6+.
A little background for my questions: This is the very first time that I rooted a phone. I'm rooting to only install these 3 apps:
adaway
titanium backup
greenify
I do not plan on using any custom ROMs or kernels.
I see from all the guides and tutorials that people also create a custom recovery whenever they root. I haven't done that yet and wasn't sure if I had to. I would like to maintain the stock recovery that I have currently so that I can go back to stock if I unRoot. My questions are:
1. Am I wrong in thinking that I can still use the stock recovery if I unRoot?
2. When a new OTA comes out and I flash it (since I'm rooted an no longer can install them automatically), will that also upgrade my still stock recovery properly?
3. Following up on the previous question, when I upgrade manually because I'm rooted, would that be a fresh install where I have to go in and configure things the way I like them again (system settings, apps and their settings, root the phone again, etc)?
Thanks in advance!
LordGrahf said:
Hello everyone,
I'm back to a nexus 6 after a very short stint with a 6+.
A little background for my questions: This is the very first time that I rooted a phone. I'm rooting to only install these 3 apps:
adaway
titanium backup
greenify
I do not plan on using any custom ROMs or kernels.
I see from all the guides and tutorials that people also create a custom recovery whenever they root. I haven't done that yet and wasn't sure if I had to. I would like to maintain the stock recovery that I have currently so that I can go back to stock if I unRoot. My questions are:
1. Am I wrong in thinking that I can still use the stock recovery if I unRoot?
2. When a new OTA comes out and I flash it (since I'm rooted an no longer can install them automatically), will that also upgrade my still stock recovery properly?
3. Following up on the previous question, when I upgrade manually because I'm rooted, would that be a fresh install where I have to go in and configure things the way I like them again (system settings, apps and their settings, root the phone again, etc)?
Thanks in advance!
Click to expand...
Click to collapse
1. No, you're not wrong. Recovery will stay stock and can be used normally
2. You can't simply flash the new OTA. This will not work manually nor automatically.
3. All you need to do is not flash the user data image and you will not loose your data, settings etc. You will loose root however. See bellow.
Google posts android stock images for each device typically before OTA hits your phone. That's what you want to grab and use for the update. Just make sure you don't run the automatic scripts that come with those images because you need to avoid flashing user data image.
OTA zip file does you no good unless you get your system back to unmodified stock.
Thank you sir!
obsanity said:
1. No, you're not wrong. Recovery will stay stock and can be used normally
2. You can't simply flash the new OTA. This will not work manually nor automatically.
3. All you need to do is not flash the user data image and you will not loose your data, settings etc. You will loose root however. See bellow.
Google posts android stock images for each device typically before OTA hits your phone. That's what you want to grab and use for the update. Just make sure you don't run the automatic scripts that come with those images because you need to avoid flashing user data image.
OTA zip file does you no good unless you get your system back to unmodified stock.
Click to expand...
Click to collapse
Based on the OP, it sounds like he has only rooted. Thus, the OTA will work fine. No need to flash image files.
Edit: I see that at least one other member has stated that an unroot still did not allow OTAs to function. That's a bit strange and unique. Not sure what root is modifying to prevent the OTA.
I'm kinda curious myself. I had no idea root killed OTA's. Maybe I wouldn't have done that if I knew that. I'm very new to the Nexus device. It's my 1st. I unlocked the bootloader and rooted already.
Sent from Mark's Nexus 6
crowbarman said:
Edit: I see that at least one other member has stated that an unroot still did not allow OTAs to function. That's a bit strange and unique. Not sure what root is modifying to prevent the OTA.
Click to expand...
Click to collapse
This is pretty scary. So you can unroot and GI back to stock and still can't update in anyway?
I have always side-loaded OTAs, I have never flashed anything.
After installing an OTA, on the next reboot, Android takes some time to optimize all your apps. Does this also happen after flashing a new system image? Thanks!
LordGrahf said:
This is pretty scary. So you can unroot and GI back to stock and still can't update in anyway?
Click to expand...
Click to collapse
not sure what you mean by GI, but according to some others, after uninstalling root via SuperSU an OTA will still not install. This should not be the case unless the boot or recovery images are modified. Easily fixed by following the procedures above to fastboot the stock images on your phone.
kjnangre said:
I have always side-loaded OTAs, I have never flashed anything.
After installing an OTA, on the next reboot, Android takes some time to optimize all your apps. Does this also happen after flashing a new system image? Thanks!
Click to expand...
Click to collapse
Yes, it behaves exactly the same.
crowbarman said:
Based on the OP, it sounds like he has only rooted. Thus, the OTA will work fine. No need to flash image files.
Edit: I see that at least one other member has stated that an unroot still did not allow OTAs to function. That's a bit strange and unique. Not sure what root is modifying to prevent the OTA.
Click to expand...
Click to collapse
Root on Lollipop is not what it used to be. There are files that need to be modified in order to allow root. That's why this time OTA will fail if you are rooted.
Un-rooting however, will allow OTA as long as it is done properly and all traces are covered up and returned to stock. If it does fail after you have un-rooted, go back to the developer of that un-root method and let the know they missed something.
Here is the best way to un-root. Flash all of the old stock images besides user data image.
obsanity said:
Root on Lollipop is not what it used to be. There are files that need to be modified in order to allow root. That's why this time OTA will fail if you are rooted.
Un-rooting however, will allow OTA as long as it is done properly and all traces are covered up and returned to stock. If it does fail after you have un-rooted, go back to the developer of that un-root method and let the know they missed something.
Here is the best way to un-root. Flash all of the old stock images besides user data image.
Click to expand...
Click to collapse
That makes sense. Is there a manual root procedure or list of required modifications for root out there? I did some precursors searches but Came up empty. Can't tell what's missing in SuperSU unroot without those details.
crowbarman said:
That makes sense. Is there a manual root procedure or list of required modifications for root out there? I did some precursors searches but Came up empty. Can't tell what's missing in SuperSU unroot without those details.
Click to expand...
Click to collapse
Explanation from Chainfire:
https://plus.google.com/113517319477420052449/posts/S5zoKTzKUW1
obsanity said:
Explanation from Chainfire:
https://plus.google.com/113517319477420052449/posts/S5zoKTzKUW1
Click to expand...
Click to collapse
Thanks for this. A good read, but I'm surprised nobody has demanded more details than 'patched the policies in SELinux'. Not that I don't trust Chain fire (I do) , but who really knows what has been done to our phones?
crowbarman said:
Thanks for this. A good read, but I'm surprised nobody has demanded more details than 'patched the policies in SELinux'. Not that I don't trust Chain fire (I do) , but who really knows what has been done to our phones?
Click to expand...
Click to collapse
That's the problem with Chainfire's work... he does not release source.
Again, best un-root method is to flash original images less user data.
obsanity said:
That's the problem with Chainfire's work... he does not release source.
Again, best un-root method is to flash original images less user data.
Click to expand...
Click to collapse
Thanks for sharing this info. Its a bit concerning tbh. Is there a cleaner way to root other than using superSU?
LordGrahf said:
Thanks for sharing this info. Its a bit concerning tbh. Is there a cleaner way to root other than using superSU?
Click to expand...
Click to collapse
I'm afraid not but Chainfire's is probably the cleanest possible. Koush was the one with an open source solution but he hasn't updated his to 5.0 yet.
obsanity said:
I'm afraid not but Chainfire's is probably the cleanest possible. Koush was the one with an open source solution but he hasn't updated his to 5.0 yet.
Click to expand...
Click to collapse
There is an argument that publishing the method would allow Google to close it that much quicker, I suppose.
crowbarman said:
Thanks for this. A good read, but I'm surprised nobody has demanded more details than 'patched the policies in SELinux'. Not that I don't trust Chain fire (I do) , but who really knows what has been done to our phones?
Click to expand...
Click to collapse
The base changes and reasoning for those changes are actually documented on my website. Specific policy adjustments are present in plain text in the supolicy executable, as any hex editor will show you. Those who really wanted to know rather than whine about OSS, know.
By far most policy adjustments just drop audit log output for contexts that are already permissive, though.
All that information is still completely useless unless you understand SELinux in detail and how it's implemented on Android, though.
I assume that the encryption doesn't get in the way of being able to flash the images?
When I went from 5.0 to 5.0.1 on my old Nexus 5 all I did was flash the two new 5.0.1 images I extracted from the full factory image, then re-rooted. This is far cleaner than reverting back to the previous image then doing an OTA. I've not had to update my N6 yet so I don't know if my method will work still, but I hope it does.
Chainfire said:
The base changes and reasoning for those changes are actually documented on my website. Specific policy adjustments are present in plain text in the supolicy executable, as any hex editor will show you. Those who really wanted to know rather than whine about OSS, know.
By far most policy adjustments just drop audit log output for contexts that are already permissive, though.
All that information is still completely useless unless you understand SELinux in detail and how it's implemented on Android, though.
Click to expand...
Click to collapse
Thanks for the additional information.
I did spend a fair amount of time reading your documentation but failed to utilize a hex editor. I am not 'whining' about the lack of open source, rather, simply mildly surprised, but your website aptly describes the challenges with 5.0. Many are used to various root methods being available.
Your solution is fine with me.. I love your work.
Edit: I thought I'd add that the discussion has devolved from the OP, which was whether an OTA can be applied after uninstalling root. The answer was no, due to the unknowns about what still might be modified following the uninstall via SuperSU.
So far I've been running my OP3T with stock rom with TWRP recovery and SuperSU to have root. This was mostly because I wanted the Adaway and titanium backup to work. I undid everything so I could update to the latest OxygenOS version, and now I'm on the stock recovery too, but with bootloader still unlocked I believe. I no longer have root after doing the upgrade as far as I can tell, still a bit new to all this flashing, haha. The last time I did this was when the nexus 4 came out
What is the best option for maintaining root while still being able to upgrade smoothly? I'm not against using one of the custom ROMs if that will help, but I do kinda like the stock rom so far!
thanks!
bluesrph said:
So far I've been running my OP3T with stock rom with TWRP recovery and SuperSU to have root. This was mostly because I wanted the Adaway and titanium backup to work. I undid everything so I could update to the latest OxygenOS version, and now I'm on the stock recovery too, but with bootloader still unlocked I believe. I no longer have root after doing the upgrade as far as I can tell, still a bit new to all this flashing, haha. The last time I did this was when the nexus 4 came out
What is the best option for maintaining root while still being able to upgrade smoothly? I'm not against using one of the custom ROMs if that will help, but I do kinda like the stock rom so far!
thanks!
Click to expand...
Click to collapse
This thread should answer all your questions and doubts
https://forums.oneplus.net/threads/...-or-custom-recovery-without-data-loss.479265/
saurabh40629 said:
This thread should answer all your questions and doubts
https://forums.oneplus.net/threads/...-or-custom-recovery-without-data-loss.479265/
Click to expand...
Click to collapse
Thank you, I have seen that post. I'm guessing any route I go I'll have to flash updates then? I was hoping to find a way to be able to use OTA updates.
I've also never been able to get rid of the dm-verity error, even after going back to stock and locking the bootloader. Is there anything I need to worry about with that or is it just an annoyance?
Sent from my OnePlus3T using XDA Labs
bluesrph said:
Thank you, I have seen that post. I'm guessing any route I go I'll have to flash updates then? I was hoping to find a way to be able to use OTA updates.
I've also never been able to get rid of the dm-verity error, even after going back to stock and locking the bootloader. Is there anything I need to worry about with that or is it just an annoyance?
Click to expand...
Click to collapse
Dm-verity u can bypass but bootloader one, you can not. Look at the apps, mods section.
bluesrph said:
Thank you, I have seen that post. I'm guessing any route I go I'll have to flash updates then? I was hoping to find a way to be able to use OTA updates.
I've also never been able to get rid of the dm-verity error, even after going back to stock and locking the bootloader. Is there anything I need to worry about with that or is it just an annoyance?
Sent from my OnePlus3T using XDA Labs
Click to expand...
Click to collapse
You shouldn't try to flash the partial OTAs while you are rooted and have a custom recovery installed. The partial zip will try to make specific changes in the restricted partitions (/system, /boot, /recovery, etc.) related to the update and prior modifications to these files may cause the update to fail and the phone to brick. You can still use the "Update" tab in the Settings menu to download the update though as OOS will detect root and download the full zip of the update for you. Simply flash the full zip in TWRP, wipe cache/dalvik, then flash SuperSU and you're good to go the next time an update rolls out. Updating by this method (rooting immedately after flashing update) will also prevent OOS from replacing TWRP with the stock recovery again. When you download the update, you'll know if it's the full zip if the file is >1 GB (they're usually ~1.4 GB,, whereas the partial zips are a few hundred MB).
Unlocked bootloader warning screen is cannot be removed without relocked and fully resetting (wiping) the phone. DM-verity warning screen can be removed by following this guide. Make sure that you are flashing the correct firmware for you current version of OOS though, flashing the wrong version can brick you phone.
Howdy guys and gals. Once again, it has been a VERY long time since I have posted. I just received my new Pixel XL today (free warranty replacement from Google for battery issues on my 6P).
Very first thing I did was install twrp recovery and SuperSU, so I could do the Carrier Entitlement mod and have my wifi hotspot. I have a couple of questions:
1. Can I unroot and keep the work I have done to enable my wifi hotspot or will it revert back after I unroot?
2. What can I do to update to 8.0? Honestly, I wouldn't mind losing root via updating OTA, but I don't want to end up with a brick and I don't want to lose my newly added wifi hotspot.
I greatly appreciate any help or input!! Thanks!
EDIT: I did find a tiny bit of info on this topic in the last few posts on this thread (page 2), but I really was hoping for some clarification since it is a bit vague. Link: https://forum.xda-developers.com/pi...ermod-systemless-install-guide-t3501448/page2
jonmike13 said:
Howdy guys and gals. Once again, it has been a VERY long time since I have posted. I just received my new Pixel XL today (free warranty replacement from Google for battery issues on my 6P).
Very first thing I did was install twrp recovery and SuperSU, so I could do the Carrier Entitlement mod and have my wifi hotspot. I have a couple of questions:
1. Can I unroot and keep the work I have done to enable my wifi hotspot or will it revert back after I unroot?
2. What can I do to update to 8.0? Honestly, I wouldn't mind losing root via updating OTA, but I don't want to end up with a brick and I don't want to lose my newly added wifi hotspot.
I greatly appreciate any help or input!! Thanks!
EDIT: I did find a tiny bit of info on this topic in the last few posts on this thread (page 2), but I really was hoping for some clarification since it is a bit vague. Link: https://forum.xda-developers.com/pi...ermod-systemless-install-guide-t3501448/page2
Click to expand...
Click to collapse
1 - If you unroot, the CarrierEntitlement.apk mod will stop working. Assuming you are using the method you linked below. This method on Nougat, relied on placing a modified CarrierEntitlement.apk in the SuperSu (or sbin/supersu directories and then binding that modified app to the original version in priv-app on boot. Essentially replacing the real app with this modified one which short circuits the provisioning check for tethering and allows tethering to work as needed. However, once you unroot those root directories will not exist or won't be accessible and this method will cease to work. Also, once you upgrade to 8.0, this specific method for gaining tethering also won't work. It appears that in 8.0 and above CarrierEntitlement.apk has been deprecated and replaced by TetheringEntitlement.apk. And a similarly modified version of TetheringEntitlement.apk doesn't exist at this point. (I tried and failed to create one.) However, as the posts you linked to indicate, on 8.0 you are able (if rooted) to add the needed line at the end of the build.prop which prevents the provisioning check from running at all. You do need to be rooted to make that build.prop modification. I do not know if making the change while rooted and then unrooting would still allow that build.prop modification to work. I suspect that it would still work since that line would remain in the build.prop even once unrooted, but I have not personally verified this. I would ask why you are so anxious to unroot...if you are wanting android pay to work, safetynet to pass, etc...you can install suhide after rooting and that would solve that problem. The simplest rooting with SuperSu / install suhide instructions I have found are in the OP of Chainfire's suhide post....linked below...
https://forum.xda-developers.com/apps/supersu/suhide-lite-t3653855
2 - See above. Once you upgrade, you will need to reroot and make the same modifications referenced above in the build.prop.
Good luck!
sb1893 said:
1 - If you unroot, the CarrierEntitlement.apk mod will stop working. Assuming you are using the method you linked below. This method on Nougat, relied on placing a modified CarrierEntitlement.apk in the SuperSu (or sbin/supersu directories and then binding that modified app to the original version in priv-app on boot. Essentially replacing the real app with this modified one which short circuits the provisioning check for tethering and allows tethering to work as needed. However, once you unroot those root directories will not exist or won't be accessible and this method will cease to work. Also, once you upgrade to 8.0, this specific method for gaining tethering also won't work. It appears that in 8.0 and above CarrierEntitlement.apk has been deprecated and replaced by TetheringEntitlement.apk. And a similarly modified version of TetheringEntitlement.apk doesn't exist at this point. (I tried and failed to create one.) However, as the posts you linked to indicate, on 8.0 you are able (if rooted) to add the needed line at the end of the build.prop which prevents the provisioning check from running at all. You do need to be rooted to make that build.prop modification. I do not know if making the change while rooted and then unrooting would still allow that build.prop modification to work. I suspect that it would still work since that line would remain in the build.prop even once unrooted, but I have not personally verified this. I would ask why you are so anxious to unroot...if you are wanting android pay to work, safetynet to pass, etc...you can install suhide after rooting and that would solve that problem. The simplest rooting with SuperSu / install suhide instructions I have found are in the OP of Chainfire's suhide post....linked below...
https://forum.xda-developers.com/apps/supersu/suhide-lite-t3653855
2 - See above. Once you upgrade, you will need to reroot and make the same modifications referenced above in the build.prop.
Good luck!
Click to expand...
Click to collapse
I greatly appreciate you bringing me up to speed. It has been so long since I have done anything like this. It seems like I'm away for a year or so until I get a new phone, and then I'm back at it again. :laugh:
I used the first method on this link to carry out the deed: https://www.theandroidsoul.com/enab...ing-pixel-and-pixel-xl-verizon-sprint-others/
Really, the only reason I want to unroot is to update to 8.0. I would be totally fine with keeping root (would actually prefer it), but I want to get on 8.0, and I can't find any guides for updating and retaining root and my tethering. It appears as though that won't be an option for now based on your post unless I want to modify the build.prop. I wouldn't mind doing that, but I would need a guide for updating and then another guide for the build.prop, and I'm just not as brave as I used to be with this stuff. Back in the day, I would take some info a run with it, and adapt as necessary. It's almost like I have gotten "old" and haven't kept up with the times and constantly worry I'm going to turn the phone into a paper weight. :laugh:
EDIT: Would I be able to just use the OTA update and it basically undo everything I have done and then re-root myself and then do the build.prop mod, or would I need to get back to a factory state before being able to run the OTA update?
My preferred method of taking upgrades on the pixel xl has been to just sideload the OTA for both monthly security patches and minor releases. I did flash the full factory image for the upgrade to 8.0 (removing the -w from flashall.bat to retain my data). Both methods have worked great for me. In either case, you do need to reroot, reflash suhide, reedit build.prop. But the entire process takes less than 45 min start to finish and had worked well each month since December 2016 for me. When you sideload the OTA or flash the factory image, any changes to build.prop, etc do not prevent the update from completing which is in contrast to what happens if you try to just take the OTA the standard way within android without first restoring to factory stock.
Guides for all of these steps are easily found here on the pixel xl forum. The basic steps for side loading ota/flashing factory can be found at the location they are published on Google's Android image pages.
sb1893 said:
My preferred method of taking upgrades on the pixel xl has been to just sideload the OTA for both monthly security patches and minor releases. I did flash the full factory image for the upgrade to 8.0 (removing the -w from flashall.bat to retain my data). Both methods have worked great for me. In either case, you do need to reroot, reflash suhide, reedit build.prop. But the entire process takes less than 45 min start to finish and had worked well each month since December 2016 for me. When you sideload the OTA or flash the factory image, any changes to build.prop, etc do not prevent the update from completing which is in contrast to what happens if you try to just take the OTA the standard way within android without first restoring to factory stock.
Guides for all of these steps are easily found here on the pixel xl forum. The basic steps for side loading ota/flashing factory can be found at the location they are published on Google's Android image pages.
Click to expand...
Click to collapse
Thanks for the information! I got impatient today and went ahead and updated to 8.0. I tried using the Disable Services app to get rid of the annoying notification to update, but was unsuccessful.
I'm going to re-root tomorrow evening and go through the whole process again to gain the hotspot. Now with the information I received in this thread, and the other links I emailed myself today at work, I'm starting to ease back into the modding world.
jonmike13 said:
Thanks for the information! I got impatient today and went ahead and updated to 8.0. I tried using the Disable Services app to get rid of the annoying notification to update, but was unsuccessful.
I'm going to re-root tomorrow evening and go through the whole process again to gain the hotspot. Now with the information I received in this thread, and the other links I emailed myself today at work, I'm starting to ease back into the modding world.
Click to expand...
Click to collapse
Nice work! Welcome back to the fun! Good luck!
Hi! I picked up my Canadian P20 Pro last week and couldn't be happier. It's been many years since I've owned a rootable device though and a lot has changed! I've done my best to read through all the guides for rooting the P20 Pro and it's only lead to further confusion as there seem to be many recent advancements. There seem to be a lot of different versions of this phone too. So I have some questions I'm hoping someone can answer easily! Let's assume my bootloader is already unlocked....
1) there's a really great guide on rooting the P20 Pro using All In One tool. But that requires flashing TWRP to achieve root using Magisk. I do not require TWRP as I only want root and do not wish to flash any roms.
a) is there a way to root with Magisk and NOT flash TWRP? I can't seem to find a straight answer on this...
b) failing that, can TWRP safely be removed and keep root afterward?
2) after unlocking the bootloader I was welcomed by a terrifyingly orange warning about my now 'unsafe' phone. I've read mixed things on hiding this. Is there currently a way to hide it?
3) how does the process work for OTA updates on an unlocked bootloader assuming there is no TWRP? I've read differing opinions on the necessity of flashing a no_check.img to the ramdisk and have no understanding of the new security checks on these phones. Can I run risk of bricking my phone through an automated update?
Ultimately I'm scared of forgetting TWRP is on my phone and accepting an update that'll brick it. Any information is welcome as are similar questions!
I am also curious if there is a good root process for this phone. Find anything yet?
djparent said:
Hi! I picked up my Canadian P20 Pro last week and couldn't be happier. It's been many years since I've owned a rootable device though and a lot has changed! I've done my best to read through all the guides for rooting the P20 Pro and it's only lead to further confusion as there seem to be many recent advancements. There seem to be a lot of different versions of this phone too. So I have some questions I'm hoping someone can answer easily! Let's assume my bootloader is already unlocked....
1) there's a really great guide on rooting the P20 Pro using All In One tool. But that requires flashing TWRP to achieve root using Magisk. I do not require TWRP as I only want root and do not wish to flash any roms.
a) is there a way to root with Magisk and NOT flash TWRP? I can't seem to find a straight answer on this...
b) failing that, can TWRP safely be removed and keep root afterward?
2) after unlocking the bootloader I was welcomed by a terrifyingly orange warning about my now 'unsafe' phone. I've read mixed things on hiding this. Is there currently a way to hide it?
3) how does the process work for OTA updates on an unlocked bootloader assuming there is no TWRP? I've read differing opinions on the necessity of flashing a no_check.img to the ramdisk and have no understanding of the new security checks on these phones. Can I run risk of bricking my phone through an automated update?
Ultimately I'm scared of forgetting TWRP is on my phone and accepting an update that'll brick it. Any information is welcome as are similar questions!
Click to expand...
Click to collapse
I have a Canadian CLT-L04 that i rebranded and rooted to CLT-L29 with the guide on here.
https://forum.xda-developers.com/hu...de-how-to-root-debrand-remove-retail-t3788326
if you want better firmware compared to version 109 thats still on clt-l04 you can follow this guide, it worked well for me. (don't wait canadian OTA it'll take too long)
1) quite sure that TWRP is the easiest and safest way to root. Currently unaware of a better way to root the phone.
b) if you remove TWRP by flashing a stock recovery_ramdisk, root is kept. If you do an OTA though you might lose root.
2) thats here to stay i believe. Cannot find a way to hide it currently.
3)In this guide under the "install an OTA Stock Update: PC Method" you will find all the information you need.
cheers
I finally found the info I needed in this thread:
https://forum.xda-developers.com/hu...ide-getting-started-unlock-twrp-root-t3806180
Overall it was a very simple process and took less than an hour including reading. Once you've got your bootloader unlock code the all in one tool handles it from there. Unlock the bootloader, flash TWRP, reboot into TWRP, flash Magisk and you're done. You can flash the no_check file over TWRP if you want to be ready for updates but I decided to leave TWRP on for now. Loving having root on this phone so far!
On a different note, has anyone discovered any ROMs for this phone yet that can handle the notch? I almost tried Lineage until I found out there is no notch support. I've grown strangely fond of the thing for some reason lol
rhinogator said:
I have a Canadian CLT-L04 that i rebranded and rooted to CLT-L29 with the guide on here.
https://forum.xda-developers.com/hu...de-how-to-root-debrand-remove-retail-t3788326
if you want better firmware compared to version 109 thats still on clt-l04 you can follow this guide, it worked well for me. (don't wait canadian OTA it'll take too long)
1) quite sure that TWRP is the easiest and safest way to root. Currently unaware of a better way to root the phone.
b) if you remove TWRP by flashing a stock recovery_ramdisk, root is kept. If you do an OTA though you might lose root.
2) thats here to stay i believe. Cannot find a way to hide it currently.
3)In this guide under the "install an OTA Stock Update: PC Method" you will find all the information you need.
cheers
Click to expand...
Click to collapse
Did you by any chance find a way to go back to CLT-L04 by any chance?
mrnovanova said:
Did you by any chance find a way to go back to CLT-L04 by any chance?
Click to expand...
Click to collapse
unfortunately no
mrnovanova said:
Did you by any chance find a way to go back to CLT-L04 by any chance?
Click to expand...
Click to collapse
If you do a full backup of the L04 in TWRP before rebranding you should be able to go back to it easily at any time, just remember to save it somewhere safe other than the phone itself. If you've already flashed and are looking to go back you may find someone willing to share a stock backup if you ask around. But always best to do your own backup first, then you can go back whenever you like!
djparent said:
If you do a full backup of the L04 in TWRP before rebranding you should be able to go back to it easily at any time, just remember to save it somewhere safe other than the phone itself. If you've already flashed and are looking to go back you may find someone willing to share a stock backup if you ask around. But always best to do your own backup first, then you can go back whenever you like!
Click to expand...
Click to collapse
I never thought of backing up my L04. ??? I guess I'm stuck with L29. Oh well... Thanks for the reply.
help with rebranding tutorial
mrnovanova said:
I never thought of backing up my L04. I guess I'm stuck with L29. Oh well... Thanks for the reply.
Click to expand...
Click to collapse
bro did u use the same files as the main tutorial that you share? cause I have the L04 but the mexican one, and I want to rebrand it
but i'm a noob in this things, hope you can help me.:good:
Search for dladz's tutorial.
ON THIS THREAD : https://forum.xda-developers.com/hu...to-root-debrand-remove-retail-t3788326/page46
Page 16
Sent from my Google Pixel 2 XL using XDA Labs
Anyone unlocked bootloader and rooted recently for the L04 model with 120(C792) Sept-2018 update?
Im scared to update before unlocking and rooting as the update might do something to fastboot etc. (this has happened to LG)
If not, then Ill update but if so, Ill just not update and unlock it as it is.
JF-GINO said:
Anyone unlocked bootloader and rooted recently for the L04 model with 120(C792) Sept-2018 update?
Im scared to update before unlocking and rooting as the update might do something to fastboot etc. (this has happened to LG)
If not, then Ill update but if so, Ill just not update and unlock it as it is.
Click to expand...
Click to collapse
It's really easy to update once you've unlocked, I would suggest unlocking first if you have concerns. I have an L04 as well and just updated to 120 with no problems.
djparent said:
It's really easy to update once you've unlocked, I would suggest unlocking first if you have concerns. I have an L04 as well and just updated to 120 with no problems.
Click to expand...
Click to collapse
Hey, Thanks djparent, I unlocked and updated as you suggested.
Everything working properly, just need to root/twrp etc. now.
Thnaks again
No problem, glad it worked for you. I've soft bricked and recovered my phone a few times now experimenting so if you run into any problems I'm happy to help! Lots to learn with the P20.
I have a CLT-L04 8.1.0.136 C69 with October security patch from Mexico I want to rebrand it to CLT- L29 to get wifi calling and get rid of all the bloatware. Could I use this tutorial from dladz's tutorial:
ON THIS THREAD : https://forum.xda-developers.com/hua...3788326/page46
Page 16
One of the notes mentions the following: I) ]NOTE*** If you are on a later firmware than 120, please do not attempt this guide!!
I have only rooted one phone before in my life so I am no expert. I do no want to mess up my phone becuse it is the only one that I have. Also If I unlock the boot loader and rebrand can i get OTAs and the upcoming Pie release? Thanks for the help!
LineageOS 15.1 on L04
I installed LineageOS 15.1 on my L04 with out any issue. Some things to consider. USB-C will only charge the device, Titanium Backup will install but doesn't get root access and you'll miss the camera application.
Vedrick said:
I installed LineageOS 15.1 on my L04 with out any issue. Some things to consider. USB-C will only charge the device, Titanium Backup will install but doesn't get root access and you'll miss the camera application.
Click to expand...
Click to collapse
Did you install it with a locked bootloader ? I really dont feel like paying for an unlock code. Would like to try Lineage though.
matever said:
Did you install it with a locked bootloader ? I really dont feel like paying for an unlock code. Would like to try Lineage though.
Click to expand...
Click to collapse
I do have an unlocked bootloader. Truth is i'm addicted to Rom's lol. That in mind I have tried every Rom, kernel, flash-able zip within this Forum and I can't brick this thing. L04 Canadian. Lineage is the best Rom for our device.
Roms that work:
- Lineage - Hauwei camera can be installed and works, dark mode works well.
------- Doesn't work: USB-C audio, NFC, RAW Option in the camera, Second ear piece as speaker, main speaker works well.
- First Ever Android 9 - Being the first build it works well. (Note: When I installed this rom I never installed the RemoveEncryption-P20Pro.zip) Seemed to work just fine without it. I did run it just because I wanted to see if it would brick my phone. It didn't.
-------Doesn't work: Dark mode, NFC, RAW Option in camera, Second ear piece as speaker, main speaker works well, seems to kill TWRP. eRecovery needed to get TWRP to function.
- AOSP 9 - Berkeley-Flex - Do Not Use...not ready.
Vedrick said:
I do have an unlocked bootloader. Truth is i'm addicted to Rom's lol. That in mind I have tried every Rom, kernel, flash-able zip within this Forum and I can't brick this thing. L04 Canadian. Lineage is the best Rom for our device.
Roms that work:
- Lineage - Hauwei camera can be installed and works, dark mode works well.
------- Doesn't work: USB-C audio, NFC, RAW Option in the camera, Second ear piece as speaker, main speaker works well.
- First Ever Android 9 - Being the first build it works well. (Note: When I installed this rom I never installed the RemoveEncryption-P20Pro.zip) Seemed to work just fine without it. I did run it just because I wanted to see if it would brick my phone. It didn't.
-------Doesn't work: Dark mode, NFC, RAW Option in camera, Second ear piece as speaker, main speaker works well, seems to kill TWRP. eRecovery needed to get TWRP to function.
- AOSP 9 - Berkeley-Flex - Do Not Use...not ready.
Click to expand...
Click to collapse
What did you use to unlock your bootloader ? Funky ? Also I know what you mean I am addicted to Roms as well :laugh: Thanks for all the info I really appreciate it.
Hello everyone,
I have to say I am completely lost regarding the whole rooting process for the XZ1C. I usually manage to get where I want just by carefully reading the forums, but with this device, I feel overwhelmed by information. And I sometimes feel like what I am reading contradicts what I though I understood from previous reads...
I will try to sum up what I know so far.
First of all, I have a just-out-of-the-box Sony model G8441 with firmware 47.1.A.12.179 / Oreo 8.0.0 (never been connected to the outside world yet), and I want to properly root the device and install TWRP with no loss of feature.
What I think I understand:
To root, I first need to unlock the bootloader, which seems to be a trivial operation. However, this will break some functionalities due to DRM keys being erased. Once it is done, there is no way, ever, to get them back. There are however ways to "trick" DRM-related functionalities into believing DRM keys are still there.
Alternatively, there seems to be a way to backup the DRM keys prior to unlocking the BL, and this backup can somehow be reused and injected back into the unlocked device. If true, then this would certainly be a preferable method than the previous one, which would then be obsolete. However, it obviously doesn't look obsolete when I read the related topics, so I must be missing something...
Another thing I noted (but do not quite understand): There are ROMs for this device that "include" a DRM fix.
Last important thing I read: there is a paid "do-it-all" tool which takes my locked device and, with one click, makes it unlocked - rooted - DRM-fixed - TWRP-enabled. Now that sounds really good! Maybe too good?
As far as i know (but I learn new stuff every day on this topic) this DRM stuff is the main difficulty here. I understand that the rest of the process (root + TWRP) will be much simpler (although I'm old-school and completly missed all this magisk trend...!)
What I don't understand:
I read that some people downgrade to Oreo to be able to root properly, and at the same time, I read that Pie removed the restrictions on unlocked bootloader. So I still have no idea if I should connect and receive Sony updates, or avoid them.
Another thing I don't get, is how many ways do we have to root this thing? In the past, I was used to see, for a specific device, always one major and widly used rooting method. Here I fail to identify it...
What I think I will do:
1. Backup TA partition with j4nn's tool. This will probably imply flashing an older firmware right? Is there any link that could help me with this flashing process? (I only know Odin - did I mention old-school?) I saw this page for generic sony Z devices, but the thread is from 2013 and now closed. Is it still up-to-date or is there a newer thread?
2. Unlock bootloader and restore TA partition.
3. Wait for Sony updates? Or should I first hide unlock status?
3bis. Alternaltively to waiting for updates, maybe I can just flash the latest build? (47.2.A.8.24 if I am not mistaken)
4. Flash modpunk's TWRP.
5. Flash janjan's Boot.img to get root functionalities?
Alternaltively to all the above (except maybe step 1 that I will probably do in any case), buy the paid all-in-one tool (Xperifix), plug, click and wait... But will I really end up the same as with the manual way?
I saw a few other methods in the forums but it seems my brain is currently refusing to bring them back...
That's all I have right now. I would really appreciate if you guys could share some insight and tell me what you think about this, whether there are missing steps, useless steps, incorrectly ordered steps, silly steps, or if I'm just completely wrong about the whole thing.
Feel free also to correct me on the assumptions I made at the beginning.
Thank you very much for reading this repulsive piece of text.
SunJu22 said:
I would really appreciate if you guys could share some insight and tell me what you think about this
Click to expand...
Click to collapse
By the looks of it you have done a great deal of research on the project.
Yes, go down the route of backing up your TA partition first, but that is not a small step in itself, it's pretty complicated and if you get that working then the rest of the project will be a breeze.
You don't say what version of firmware you want to end up on. If you want to end up on Pie then forget the DRMfix . But if you're staying on Oreo and can't be bothered with lots of files & flashing, then this is the easy way out, I bought the paid version and can verify it works.
More recently I ended up janjan's kernel (Oreo build). Hidden root (Google Pay works), lots of performance tweaks, DRM completely working.
It's unlikely that anyone will bother making a DRM fix for Pie as the camera works and there are only a couple of other features that get disabled.
It sounds like you're not the sort of person who's only going to read the first couple of pages of a thread (or the last) flash the xxxxxx and then complain when it's broken.
The people on the forum here are very helpful and if you go into any of the threads you mentioned in your post with a question, you'll get a reply.
Good luck.
I agree, there is a lot of information out there and different methods of achieving what you want - very confusing if you have not been following the threads since the beginning.
In my opinion, the preferred method is j4nn's method outlined here: https://forum.xda-developers.com/xp...devonly-exploits-temp-root-to-backup-t3795510
Use that post as your main guide (the final step in that guide, #13, is how you will achieve root). You will use Newflasher to flash the various firmwares along the way (this is linked from j4nn's procedure in step #2). User munted made a very detailed pdf file that fills in some of the details on j4nn's procedure - see the following post and download the pdf attached: https://forum.xda-developers.com/showpost.php?p=78255334&postcount=382
Most of the other methods out there came before j4nn's work - they didn't include DRM backup/restore.
If you follow j4nn's procedure, you won't need to use the janjan kernel as you assumed - janjan method is different and does not overlap with j4nn.
SunJu22 said:
Feel free also to correct me on the assumptions I made at the beginning.
Click to expand...
Click to collapse
Sorry, I didn't point out that I was one of the early 'jumpers' who unlocked their bootloader without any backups, so I have been forced into always using fixes and all the information I have is based on having to fix your phone for it to work, but that's all changed now. I'm so out of date :-/
@camaro322hp is right, if you follow j4nn's method correctly you'll be rooted with no DRM loss. All of the other stuff is not required.
Thank you Digesteve and camaro322hp for your help.
From what I understand the XZ1C didn't get as much love as other devices, thus there was a long period of tinkering before a "do-it-all guide" could be considered "the" solution. That could explain all these different approaches that are proposed. Like you said camaro322hp it's rather difficult to jump on this train, and I can only guess how interesting this ride has been.
Anyway, I didn't see that the TA backup thread from j4nn also encompassed all the information I needed; I am glad to finally know that there is indeed a centralized "do-it-all guide" . To make it easier for XZ1C newcomers, I think j4nn should update his opening post to make this clearer.
Since I managed to grab the attention of 2 XZ1C power users, I would like to ask you: Did you keep stock? Did you try alternative ROMs? Do you like some of them? Do you prefer Oreo or Pie?
For information, the most up-to-date experience I have on a Android phone is my LG90 with CyanogenMod 11 (KitKat 4.4.4! Yes sir!). I heard that it's becoming less and less useful to flash a custom ROM due to major OS improvements, but I would still enjoy the simplest and lightest Android possible.
SunJu22 said:
Did you keep stock? Did you try alternative ROMs?
Click to expand...
Click to collapse
I've always been on stock, the camera is an important part of what I want from my phone and although there's lots of alternative camera apps, there's no competition to the stock camera app. Then I theme it black with swift installer and just uninstall or freeze any apps I don't want with Titanium Backup. I have stuck with Oreo, everything works perfect and I remember seeing so many people jumping to 9 then wanting to go back to 8 because they didn't like it. Something about changing the way the drop down menu works, among other things, but having never installed it, I'm not the person to comment on if it's any good or not.
I have been watching the XZ1c thread and Lineage is gaining ground, it even has a stock camera now. I would have thought something like that with miniGapps is going to be pretty lightweight and very similar to your carbon rom of before. At the moment this is based on 8, but is working well. Depends how keen you are to move to Pie.
Thank you Digesteve.
One thing I still don't understand. Part of the process is to hide unlock status. If I do this, FOTA will be applied and I will automatically end up on Pie, right? Should I skip this step if I want Oreo?
EDIT: when you say "a stock camera", you mean the Sony camera?
@SunJu22 I've stuck with the Sony ROM. A rooted stock ROM meets all my needs, so I've never felt the need to experiment with custom ROMs. There are some custom options out there that people seem fairly happy with, so if that's your thing, I'd encourage it.
Without going into too much detail, I'm still on Oreo for the moment, for a variety of reasons, but I don't know of anything that would keep me from recommending Pie.
One thing you should note is that once you unlock, there is no going back. AFAIK there is no known or working method to relock the bootloader.
SunJu22 said:
FOTA will be applied and I will automatically end up on Pie, right? Should I skip this step if I want Oreo?
EDIT: when you say "a stock camera", you mean the Sony camera?
Click to expand...
Click to collapse
Yes, I'm not entirely sure why having your rooted phone try and update itself is an advantage, but something I'd recomend avoiding.
Stock camera is the Sony camera, yes.
Thank you everyone, I believe I now have enough information to jump into this with confidence. The adventure begins, and will be reported in this thread for future reference, in the hope that it will help others like me!
Well, I am a bit sad... I wanted to report my "adventure" here in detail, but I'm afraid I have nothing to say.
Indeed, following the procedure from j4nn with a printed copy of munted's awesome guide, I managed to do all I wanted on the first attempt.
I don't have anything to add to this guide, everyone wanting to root their XZ1C can do it just by reading the opening post from j4nn and the mentioned guide. It takes a bit of time but nothing complicated thanks to the clear and detailed explanations.
I now have a fully functional rooted XZ1C (including camera) on Pie with Magisk root and TWRP.
Thank you all again from pointing me to the right direction.
I however have a slight disappointment. I wanted to start with Oreo and make an Nandroid backup before moving to Pie, but I didn't find Oreo builds on Xperifirm. So I jumped straight to Pie.
In case I want to test Oreo, I read that a downgrade is more complicated than an upgrade, but apart from the fact that a factory reset is needed for downgrade, I couldn't find an explanation for this. Any idea?
Last but not least: I looked for the latest Oreo build version number but couldn't find it. Do you guys know what it is and where I can download it?
I guess this will be all for this thread after this. Although it is very convenient to have my own thread to ask questions rather than finding the relevant page for each one, I don't want to annoy you too much...
EDIT: Please ignore the last question. I found out last Oreo build is 47.1.A.16.20, and I found the files via the download link in the opening post of the Lineage thread.
SunJu22 said:
In case I want to test Oreo, I read that a downgrade is more complicated than an upgrade, but apart from the fact that a factory reset is needed for downgrade, I couldn't find an explanation for this. Any idea? Lineage thread.
Click to expand...
Click to collapse
There is an easy solution to downgrade:
Newflasher
Hi, I've been thinking about rooting my XZ1c for a long time now. So, do I understand correctly that the ONLY disadvantage compared to non-rooted device is not possible to receive the OTA updates from Sony anymore?
mEREHAIGE said:
Hi, I've been thinking about rooting my XZ1c for a long time now. So, do I understand correctly that the ONLY disadvantage compared to non-rooted device is not possible to receive the OTA updates from Sony anymore?
Click to expand...
Click to collapse
No, you can flash a kernel to hide the bootloader unlock flag, this will mean that you will receive OTA updates, although depending on how you're rooted an update will most likely break your phone, so not that useful.
*made a thread*
Thanks--rooted withOUT adventure too
Very happily rooted now. Just wanted to say a quick thanks and add a few notes:
1. j4nn's renoroot to enable TA key backup and restore is fantastic. My advice: use and donate
2. munted's guide is excellent. clear and thorough...a rare combination.
3. do expect that renoroot may need to be restarted a couple of times. it took me 3 or 4 attempts to get temp root to pull the TA keys, although it took only 1 effort to get root back to restore.
4. topjohnwu's magisk is, of course, a key component to all this. Thx and $s there too.
I did a few things slightly differently/additionally than SunJu22.
5. I am on T-Mobile US, so I opted to create a hybrid Pie FW to get wifi calling and VoLTE. There are a number of discussions on this. I did it by combining the vendor**.sin and system**.sin files from custom-CH FW with the other files from custom-US FW. Of course (a) use IDENTICAL release numbers only, e.g. 47.A.2.10.28 w/ 47.A.2.10.28 and (b) you still need to delete .TA and persist files from the hybrid before you flash it.
Note: I don't really care about these features, but I have *heard* that T-mobile won't allow BYOD on their band-12 sites if they don't have VoLTE. Don't know if it is true (or where it is true) but figured why not?
6. I decided (for now, at least) to leave boot and recovery stock. So, I am using fastboot to run TWRP or a rooted kernel. Thanks again to j4nn for the method.
Note: I don't plan on allowing FOTA upgrades---I just like passing all the security checks and being able to *see* if updates are available.
That's all. Fine work in development and guides has made life simple and happy for me
kirkzp said:
Very happily rooted now. Just wanted to say a quick thanks and add a few notes:
1. j4nn's renoroot to enable TA key backup and restore is fantastic. My advice: use and donate
2. munted's guide is excellent. clear and thorough...a rare combination.
3. do expect that renoroot may need to be restarted a couple of times. it took me 3 or 4 attempts to get temp root to pull the TA keys, although it took only 1 effort to get root back to restore.
4. topjohnwu's magisk is, of course, a key component to all this. Thx and $s there too.
I did a few things slightly differently/additionally than SunJu22.
5. I am on T-Mobile US, so I opted to create a hybrid Pie FW to get wifi calling and VoLTE. There are a number of discussions on this. I did it by combining the vendor**.sin and system**.sin files from custom-CH FW with the other files from custom-US FW. Of course (a) use IDENTICAL release numbers only, e.g. 47.A.2.10.28 w/ 47.A.2.10.28 and (b) you still need to delete .TA and persist files from the hybrid before you flash it.
Note: I don't really care about these features, but I have *heard* that T-mobile won't allow BYOD on their band-12 sites if they don't have VoLTE. Don't know if it is true (or where it is true) but figured why not?
6. I decided (for now, at least) to leave boot and recovery stock. So, I am using fastboot to run TWRP or a rooted kernel. Thanks again to j4nn for the method.
Note: I don't plan on allowing FOTA upgrades---I just like passing all the security checks and being able to *see* if updates are available.
That's all. Fine work in development and guides has made life simple and happy for me
Click to expand...
Click to collapse
Now riddle me this cause I'm on Tmo USA as well and I did the hybrid work fine as well but heres the question, does googlepay and banking apps still work with a unlocked bootloader or did you flash a modified kernel to hide the unlocked status.
Sitting on the fence about unlocking mine so I can do a full nandroid before trying out some gsi pie roms infact this is the first phone I haven't unlocked or least put twrp on since my samsung sidekick 4g o.o
kernel with hide-unlock
T_Tank said:
Now riddle me this cause I'm on Tmo USA as well and I did the hybrid work fine as well but heres the question, does googlepay and banking apps still work with a unlocked bootloader or did you flash a modified kernel to hide the unlocked status.
Sitting on the fence about unlocking mine so I can do a full nandroid before trying out some gsi pie roms infact this is the first phone I haven't unlocked or least put twrp on since my samsung sidekick 4g o.o
Click to expand...
Click to collapse
Full disclosure: I don't use Google pay or too many banking apps, so YMMV. But, I am using j4nn's kernel with unlock hidden. (See link in my note 6.) You can flash this, or you can leave in your stock kernel and merely fastboot to this. From what I have seen, it hides most - if not all -- indicators that the phone is rooted and the BL in unlocked.
Does somebody has :
G8441_1310-7123_47.1.A.16.20-R7B_Customized_CE1.ftf ?
Only backup i did not make, and its gone from XperiFirm.
Still have the feeling battery life was better in Oreo, and would be nice for experimenting.
Would be nice.
Thanks in advance.